Nexenta RsyncShare: Complete Setup and Configuration Guide
Overview
Nexenta RsyncShare provides rsync-based file replication and synchronization for NexentaStor environments. This guide walks through prerequisites, installation, configuration, security, scheduling, verification, and troubleshooting to implement reliable file replication between Nexenta systems or to remote rsync targets.
Prerequisites
- NexentaStor installed and networked (assume NexentaStor 5.x or later).
- Root or administrator access to the Nexenta GUI/CLI.
- SSH access between source and target systems if using rsync over SSH.
- Sufficient disk space and filesystem permissions for source datasets.
- Basic familiarity with rsync options and SSH keys.
Step 1 — Plan your replication topology
- Decide roles: choose a source (primary dataset) and one or more targets (secondary systems).
- Network: ensure reliable connectivity, consider bandwidth limits, and plan for firewalls/NAT.
- Retention & scheduling: determine snapshot/replication frequency and retention policy.
- Permissions: identify which user will run rsync (typically a restricted service account).
Step 2 — Prepare datasets and snapshots
- Create dataset: in Nexenta GUI, create a ZFS dataset for data to be replicated.
- Set permissions: set dataset ownership and ACLs so the rsync account can read files.
- Create initial snapshot (optional but recommended):
- CLI:
Code
zfs snapshot pool/dataset@initial
Step 3 — Configure SSH access (for rsync over SSH)
- Create service account on source or target if not using root (recommended to limit privileges).
- Generate SSH key pair on the rsync initiator:
Code
ssh-keygen -t ed25519 -f /home/rsync/.ssh/id_ed25519 -N “” - Copy public key to target authorizedkeys:
Code
ssh-copy-id -i /home/rsync/.ssh/id_ed25519.pub rsync@target - Harden SSH: set PermitRootLogin no, use AllowUsers, restrict commands via authorizedkeys forced-commands if desired.
Step 4 — Install/enable rsync utilities
- NexentaStor typically includes rsync. Verify with:
Code
which rsync rsync –version
- If absent, install via the appropriate package manager or enable the service per Nexenta documentation.
Step 5 — Create RsyncShare configuration
- Define share point: identify source directory (e.g., /export/datasets/data) and target path (e.g., rsync@target:/var/rsync/data).
- Select rsync options (common recommended options):
-aarchive mode (preserve permissions, timestamps, symlinks)-vverbose for logs-zcompress during transfer (useful over WAN)–deleteremove files on target that were removed on source (use carefully)–bwlimit=KBPSto throttle bandwidth–partial –progressfor resumable transfers
- Example command:
Code
rsync -azv –delete –bwlimit=10240 /export/datasets/data/ rsync@target:/var/rsync/data/
- Wrap into a script (e.g., /usr/local/bin/nexentarsync.sh) to handle pre/post actions:
- Create snapshot before sync
- Mount/unmount or export operations if needed
- Logging to a central log file
Example script skeleton:
bash
#!/bin/bash SRC=”/export/datasets/data/” DST=“rsync@target:/var/rsync/data/” LOG=”/var/log/nexentarsync.log” SNAP=“pool/dataset@\((</span><span class="token" style="color: rgb(57, 58, 52);">date</span><span class="token" style="color: rgb(54, 172, 170);"> +%Y%m%d%H%M</span><span class="token" style="color: rgb(54, 172, 170);">)</span><span class="token" style="color: rgb(163, 21, 21);">"</span><span> </span> <span>zfs snapshot </span><span class="token" style="color: rgb(54, 172, 170);">\)SNAP rsync -azv –delete –bwlimit=10240 –log-file=\(LOG</span><span> </span><span class="token" style="color: rgb(54, 172, 170);">\)SRC $DST
Step 6 — Schedule synchronization
- Use cron on the initiator to run the script at desired intervals.
- Example cron entry for hourly:
Code
0/usr/local/bin/nexenta_rsync.sh >> /var/log/nexenta_rsynccron.log 2>&1
- For more advanced scheduling, use systemd timers or a job scheduler.
Step 7 — Verify and monitor
- Test dry-run before enabling destructive flags:
Code
rsync -azvn –delete /export/datasets/data/ rsync@target:/var/rsync/data/
- Check logs after runs for errors or file transfer counts.
- Periodic integrity checks: use checksums (rsync –checksum) or zfs send/receive for full replication verification.
- Alerting: forward logs to a monitoring system or configure simple email notifications on failures.
Step 8 — Security and best practices
- Use non-root rsync accounts and restrict them to specific directories.
- Use SSH keys and disable password auth for the rsync account.
- Avoid using –delete unless retention snapshots/backups exist.
- Throttle bandwidth during business hours.
- Keep rsync and system packages updated.
- Consider using ZFS replication (zfs send/receive) for block-level, efficient replication if both endpoints are Nexenta/ZFS — rsync is file-level and may be slower for large datasets.
Troubleshooting common issues
- Permission denied: verify dataset ACLs and rsync user permissions.
- Slow transfers: check network, enable compression, or use –bwlimit appropriately.
- Partial transfers: use –partial and ensure disk space on target.
- SSH authentication failures: check key permissions (600 on private key) and authorized_keys contents.
- Unexpected deletions: run
–dry-runand confirm snapshot/backup policies before–delete.
Example: Simple one-way replication recipe
- Create rsync user on target with home directory /var/rsync.
- Share dataset on source, ensure rsync user can read.
- Generate keys on source and copy public key to target.
- Use script above with hourly cron, start with dry-run then remove dry-run flag after verification.
Further reading
- NexentaStor administration documentation (check your NexentaStor version for exact commands).
- rsync man page (
man rsync) for full option descriptions. - ZFS send/receive guides if you need block-level replication.
Summary
Set up Nexenta RsyncShare by planning topology, preparing datasets and SSH keys, configuring rsync options and scripts, scheduling with cron, and validating with dry-runs and monitoring. For large ZFS datasets on Nexenta endpoints, evaluate zfs send/receive as an alternative for efficiency and consistency.
Leave a Reply