Hi Jim, Thanks for the reply. I come back to work on AVS today. Here are the latest results and some thoughts.
1) When changes are made to the secondary, a. SNDR is in logging mode b. primary is unmounted using zpool export c. secondary is mounted using zpool import 2) Data changes are made on secondary. The data will be synchronized back to the primary later. 3) After I export the ZFS at secondary, SNDR is put in reverse synchronization mode. I assume it takes some time to do the update, which I constantly check using dsstat. 4) I wait until dsstat reports no activity. Assuming zpool import will receive corrupted data if the synchronization is still in place, I manually place SNDR into logging mode before issuing zpool import. 5) Unfortunately corruption still occurs which lead me to two possible reasons a. data corruption on the network transfer b. data incompatibility on the ZFS Here are my questions, 1. Does AVS ensure data integrity during replication? 2. Does AVS need to convert data from x86 to SPARC during the replication? Regards, Joseph This message posted from opensolaris.org _______________________________________________ storage-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/storage-discuss
