On Mon, 5 Feb 2001, Brian Tao wrote:
I guess I should be asking: are 5.3.x and 6.0.x snapmirrorscompatible? The 6.0 Data Protection Guide doesn't mention caveats or incompatibilities.
Patience pays off, I guess. I let the filers mull over their purpose in life overnight, and come morning, they were happily snapmirroring away. Looking in the logs:
[1] Sun Feb 4 23:20:00 EST [drp-na1: worker_thread:error]: snapmirror: destination volume nocna1_vol0 is on-line and not in snapmirrore d state, aborting transfer [2] Sun Feb 4 23:20:43 EST [drp-na1: raid_admin:notice]: RAID checksum upgrade phase 1 (of 2) on volume nocna1_vol0 aborted. [3] Sun Feb 4 23:23:00 EST [drp-na1: worker_thread:error]: snapmirror: Filesystem version mismatch for destination volume nocna1_vol0, reverting the version and aborting transfer. SnapMirror will retry until this revert is complete. [...] [4] Mon Feb 5 00:23:48 EST [drp-na1: cksum_block_zeroer:info]: Checksum revert of volume nocna1_vol0 completed; vol copy and snapmirror now allowed.
1. I put in a snapmirror.conf and turned on snapmirror. 2. "vol offline nocna1_vol0" 3. First occurrence of the message... repeated once a minute (in accordance to my schedule in snapmirror.conf) 4. One hour to revert this filesystem. Seems to vary quite a bit on filesystem size and filer load. I haven't found any sort of progress indicator for this operation.
I haven't done much else with it yet, so there may still be 5.3.6R2 -> 6.0.1R1 caveats that I have not yet uncovered. Seems pretty slick so far though (mmmmm, fast snapshots...).