Data Backup and Recovery

VServer failback process

FelixZhou
388 Views

we are testing the VServer snapmirror failover and failback process. we have multiple CIFS volumes in the VServer, each one has multiple millions files, we found the failback took a few hours to complete. According to NetApp support, the failover process will have to check the data integrity, this is why take so long to complete. it means our application will need additional hours down time.

is there any way to improve the failover process? Such as to skip the data integrity check if we know the source side data is good, or kick off the data integrity check before kick off the fail over. 

Please share your experience if you were on same or similar situation.

thanks,

1 ACCEPTED SOLUTION

ansley_tj
361 Views

What version of ONTAP?

Starting with ONTAP 9.11.1, we support the -quick-resync true parameter. This will replicate changed data without a data warehouse rebuild...dramatically improving the resync times.  

 

Note, that using this feature will replicate data without any storage efficiency. This storage efficiency will be recovered after the failback is completed as a background process.

Thanks
Tony Ansley
I am a NetApp employee.

View solution in original post

1 REPLY 1

ansley_tj
362 Views

What version of ONTAP?

Starting with ONTAP 9.11.1, we support the -quick-resync true parameter. This will replicate changed data without a data warehouse rebuild...dramatically improving the resync times.  

 

Note, that using this feature will replicate data without any storage efficiency. This storage efficiency will be recovered after the failback is completed as a background process.

Thanks
Tony Ansley
I am a NetApp employee.
Public