Yes, it's readable. -- Craig On Aug 2, 2012, at 4:22 PM, Hunter Matthews wrote:
0. Facts needed - which filesystem by zpool name is moving and from which server and to which server. Recommendations: use 2 windows, one with the source and target logged in as root.
1. Make sure the add on utility called "mbuffer" is installed in the PATH on _both the source and target machines. (The current situation is with the SEED servers sto02 and sto09 and I have already installed it there. /usr/bin/mbuffer and its tested and working).
2. Create an initial SNAPSHOT on the source side. For the data-servers filesystem on sto02 this becomes: zfs snapshot dpool/data-servers@aug2 Note: I (hunter) typically use the partial date of snap creation for these transfer snapshots. Many filesystems have autogenerated snaps and I never use these.
3. Create an mbuffer instance to receive this filesystem on the target. For sto09 as the target this becomes: mbuffer -s 128k -m 10G -I 9092 | zfs receive -v dpool/data-servers Note 1: 9092 is the port number and they simply have to match and not be used Note 2: -s and -m are the buffering options These are overkill, but work well. Note 3: we don't list the snapshot name on the TARGET, IE leave off the "@aug2" part Note 4: this command will block, waiting for the input to start.
4. Using zfs send, send it through another mbuffer instance. To send the snapshot created above to our waiting target, this is: zfs send dpool/data-servers@aug2 | mbuffer -s 128k -m 10G -O sto09.mcs.anl.gov:9092 Note 1: mbuffer on both sides will start showing traffic immediately basically. Note 2: zfs send/recieve will always transfer more data than the listed size of the filesystem. 10-15% is typical. Don't panic.
More notes coming. Is this readable/comprehensive enough?
-- Hunter Matthews Unix Administrator Office: Bldg 240 Room 2139 Argonne National Labs, MCS Key: F0F88438 / FFB5 34C0 B350 99A4 BB02 9779 A5DB 8B09 F0F8 8438 Never take candy from strangers. Especially on the internet.