UNSOLVED
Permanent share failover with syncIQ
I need some insight on a permanent share failover with syncIQ. We have a share(20tb) that we were running on our DR cluster, using snaps and a synciq copy to production. I completed a share failover to our production cluster which is where the share will stay going forward.
My question is, will I need to create a new synciq session and re-sync to a new folder on the DR cluster, (which is where the old share/folder was) or can I somehow use the old folder with the data and just copy the new data to the old folder? I hope I do not have to create a new folder and start a sync from the beginning.
How will this work?
DELL-Sam L
Community Manager
•
8058 Posts
•
34386 Points
920
0
Posted September 25th, 2020 11:00
**********************
FAILBACK
**********************
IMPORTANT NOTE: Prior to running this step, check SECONDARY cluster for the existence of a source_record xml for the same policy ID as on the original policy see (KB 461814).
For example, for source policy ID 7da67596f099b75ad687a05f6b11781d run on target:ls -l /ifs/.ifsvar/modules/tsm/config/source_records/7da67596f099b75ad687a05f6b11781d*1) The new [POLICY]_mirror policy on the SECONDARY cluster can be run to start syncing back to the PRIMARY.
7.0
# isi sync policy run [POLICY]_mirror
7.1+
# isi sync jobs start --policy-name= [POLICY]_mirror2) Stop all writes to the SECONDARY policy's path.
3) Disable all schedules by setting the policies to manual.
7.0
# isi sync policy modify [POLICY]_mirror --schedule=""
7.1+
# isi sync policies modify --policy=[POLICY]_mirror --schedule=""
4) At SECONDARY run one last sync job
7.0
# isi sync policy start [POLICY]_mirror
7.1+
# isi sync jobs start [POLICY]_mirror5) At PRIMARY cluster perform 'Allow Writes' action and verify that the local job finishes that action.
7.0
# isi sync target allow_write [POLICY]_mirror
# isi sync target list
Name Source Target Path Last Job State FOFB State
-----------------------------------------------------------------------------------
qtestsync_mirror secondary_clust /ifs/data/siq_quota_test finished writes_enabled
-----------------------------------------------------------------------------------
Total: 1
7.1+
# isi sync recovery allow-write --policy-name=[POLICY]_mirror
# isi sync target list
Name Source Target Path Last Job State FOFB State
-----------------------------------------------------------------------------------
qtestsync_mirror secondary_clust /ifs/data/siq_quota_test finished writes_enabled
-----------------------------------------------------------------------------------
Total: 16) Redirect clients (SMB, NFS, HTTP, FTP etc) to the PRIMARY cluster.
*Note: The specifics of this step is outside the scope of this KB and require creating SMB shares, NFS exports and redirecting SmartConnect DNS.
7) At SECONDARY cluster perform the failback job with prepare re-sync and confirm that the resync_prep_finalize suceeded
7.0
# isi sync resync prep [POLICY]_mirror
# isi sync pol report qtestsync_mirror
qtestsync_mirror:
Start Stop Act Status
02/12/15 08:31:27 02/12/15 08:31:34 sync Success
02/12/15 08:41:19 02/12/15 08:41:31 resync_prep Success
02/12/15 08:41:31 02/12/15 08:41:34 resync_prep_domain_mark Success
02/12/15 08:41:34 02/12/15 08:41:42 resync_prep_restore Success
02/12/15 08:41:42 02/12/15 08:41:45 resync_prep_finalize Success
7.1+
# isi sync recovery resync-prep --policy-name=[POLICY]_mirror
# isi sync reports list --policy-name=qtestsync_mirror --sort job_id
Policy Name Job ID Start Time End Time Action State
---------------------------------------------------------------------------------------------
qtestsync_mirror 1 2015-02-12T08:31:27 2015-02-12T08:31:34 run finished
qtestsync_mirror 2 2015-02-12T08:41:19 2015-02-12T08:41:31 resync_prep finished
qtestsync_mirror 3 2015-02-12T08:41:31 2015-02-12T08:41:34 resync_prep_domain_mark finished
qtestsync_mirror 4 2015-02-12T08:41:34 2015-02-12T08:41:42 resync_prep_restore finished
qtestsync_mirror 5 2015-02-12T08:41:42 2015-02-12T08:41:45 resync_prep_finalize finishedThe SECONDARY is now READ-ONLY and the SECONDARY [POLICY]_mirror policy is disabled.
*NOTE: Do not delete any mirror policies.
The original policies on PRIMARY are now enabled. Use the backup file from FAILOVER step 3 to restore your policy schedules. On PRIMARY:
View the saved copy of the policy schedules:
# cat /ifs/.ifsvar/modules/tsm/config/policy-schedules.txt
Restore the policy schedules:
7.0
# isi sync policy modify [POLICY] --schedule=[schedule]
7.1+
# isi sync policies modify --policy=[POLICY] --schedule=[schedule]Hi Sam, thank you for the response. Your first link is for a failover which has already been performed successfully. Your second link is not valid.
My question is, will I need to create a new synciq session on the source system and re-sync to a new folder on the DR cluster, (which is where the old share/folder was) or can I somehow use the old folder with the data and just copy the new data to the old folder?
DELL-Sam L
Community Manager
•
8058 Posts
•
34386 Points
946
0
Posted September 24th, 2020 16:00
Hello tocs_1T,
Here is a couple of links that may help.
https://dell.to/3mNtEbn
https://dell.to/364z6Rf