Subscribe

Snapmirror replication issue...

Hi, We have V6080 in DC & V6040 in DR...we have storage - storage replication via Snap Mirror. Recently, we planned to have our DR Drill testing for 21 applications..hence created flex cone for all those applications at DR..now we are facing problem in lag in replication to DR...

Will creating too much of flexcone cause delay in replication ?

how to overcome this problem ?

please help...

Snapmirror replication issue...

The FlexClone locks a snapshot so if that snapshot has an update on the source, it can't update.  One workaround... create the snapshot you want to clone on the source, then after a snapmirror update, create the flexclone on that snapshot.  That snapshot won't change on the source so won't cause a lag or lock on the destination.  For example, hourly.0, hourly.1 will update but a snapshot you manually create for the flexclone called "snap_for_clone" won't be affected on the source.   When you are done with the target mirror flexclone, delete the manual snapshot on the source then the next update will update and delete it on the target.

Snapmirror replication issue...

Thanks Scott, let me try this and get back to you..if this works for me...