Community

Subscribe
Highlighted

Disaster Recovery Test Fail-over Script

========= Context :

# dfpm dataset failover test data-set-name-or-id

Start a job to test disaster recovery failover scripts.

The job will run the failover script, if configured in the data protection policy, as if about to break disaster recovery mirrors, then re-run the failover script as if the the mirror relationships had been broken.

The script will get a special input parameter indicating that this is only a test and not a real failover.

DP_FAILOVER_STATUS

DP_BEFORE_FAILOVER_MIRROR_BREAK

DFDRM_FAILOVER_STATUS

DFDRM_PRE_BREAK

DFDRM_POST_BREAK

DFDRM_PRE_RESYNC

DFDRM_POST_RESYNC

========= Assistance required with the following :

- I am not sure of the enviroment this test failover script is to run under (^DP_ or ^DFDRM) ?

- The failover commands are "dfpm dataset" based but resync are at the volume level "dfdrm" based ?

- Can we use a script to clone the most recent snapshot on the destination volumes followed by creating shares to the cloned path such that DR can be tested without affect RPO ?

- It seems like the use case for "Failover Test" scripts within Protection Manager was to inject pre and post functionality but not cloning ?

Any help or sample script to clone destination volumes in a DRMirror dataset would be great.

CIFS shares or exports can then be aimed at the cloned paths to test.

Thanks

Modi

Disaster Recovery Test Fail-over Script

Hi Modi,

    

- I am not sure of the enviroment this test failover script is to run under (^DP_ or ^DFDRM) ?

Its under DP.

- The failover commands are "dfpm dataset" based but resync are at the volume level "dfdrm" based ?

Yes, failback is using dfdrm.  In the below link the procedure is explained in detailed(failback).

http://now.netapp.com/NOW/knowledge/docs/oncommand/relcore50/pdfs/pdp_work.pdf

Under "Disaster recovery example workflow"->"Manual failback using the command line interface"

- Can we use a script to clone the most recent snapshot on the destination volumes followed by creating shares to the cloned path such that DR can be tested without affect RPO ?

- It seems like the use case for "Failover Test" scripts within Protection Manager was to inject pre and post functionality but not cloning ?

Your cloing can be done as part of pre or post functionality.

Regards

adai

Disaster Recovery Test Fail-over Script

Hi Adai,

In the case of starting a test failover by clicking test failover on the Disaster Recovery tab i.e. DP_FAILOVER_SCRIPT_TEST=1 :

Both of the following stages are run at the same time one after the other ?

DP_FAILOVER_STATUS=DP_BEFORE_FAILOVER_MIRROR_BREAK

DP_FAILOVER_STATUS=DP_AFTER_FAILOVER_MIRROR_BREAK

OR

During a test failover, we would never have "DP_AFTER_FAILOVER_MIRROR_BREAK" as is never quiesced / broken ?

In which case, the cloning commands would need to be included under stage "DP_BEFORE_FAILOVER_MIRROR_BREAK" ?

Finally, since there is only one button for "test failover", suppose the clone was created ... we would have to manually destroy the clone from ontap CLI ?

Thanks

Modi

Re: Disaster Recovery Test Fail-over Script

Does this process work the same for the "DR mirror and Mirror" policy in OC 5.1, when I've tested it with a customer what we are left with is the Mirror pointing in the right direction (Prod - > Mirror) and the DR mirror is still reversed, yet PM thinks it's going the right way (Prod -> DR).