DR Configuration Guides
Advanced Settings
Home

Advanced Settings

How to Change the Robot Scheduled interval

See Eyeglass Administration Guide igls adv failover timeout section 

Manual Export Create for Runbook Robot

In some cases, creating the NFS export used by the Robot should be disabled on each run of the Robot job and allow manual export creation to be done.

Follow these steps only when directed by support:

  1. Open Eyeglass shell from main menu.
  2. Enter command “igls adv runbookrobot set --createExport=false”.
  3. This will require manual export create on the Robot policy path with root client set to the IP address of the Eyeglass appliance.
  4. Configuration sync will sync the export once created on the cluster with the enabled policy

Multiple Robot Feature Support (Hub and Spoke)

Testing multi-site replication topology:

A -> B

A -> C

set it up as follows:

cluster A

policy 1 = source path 1 to cluster B

policy 2 = source path 2 to cluster C

TopologyAccess Zone pathAccess Zone namePolicy source pathPolicy target path
A → Bifs/AZ1/EyeglassRunbookRobot-1Clstr A: ifs/AZ1/P1

Clstr B:

ifs/AZ1/P1

A → Cifs/AZ2/EyeglassRunbookRobot-2

Clstr A:

ifs/AZ2/P2

Clstr C;

ifs/AZ2/P2

Hints pool mapping setup:

 SourceTarget
A → Bigls-01-prodigls-01-dr
A → Cigls-02-prodigls-02-dr

Multiple Robot Feature Support (Chain)

Testing multi-site replication topology:

A -> B

B -> C

set up as follows:

cluster A

policy 1 = source path 1 to cluster B ,

cluster B

policy 2 = source path 2 to cluster C ,  

TopologyAccess Zone pathAccess zone namePolicy source pathPolicy target path
A → Bifs/AZ1/EyeglassRunbookRobot-1Clstr A: ifs/AZ1/P1

Clstr B:

ifs/AZ1/P1

B → Cifs/AZ2/EyeglassRunbookRobot-2

Clstr B:

ifs/AZ2/P2

Clstr C;

ifs/AZ2/P2

Hints pool mapping setup:

 SourceTarget
A → Bigls-01-prodigls-01-dr
B → Cigls-02-prodigls-02-dr

Run Multi site Runbook job

  1. Further details for prerequisite step before execute Runbook Robot DR Automation can be found in prerequisite section in this document.
  2. Create subnet pool ( Robot-pool) for Runbook Access Zone, set mapping alias for the Robot pool to point SmartConnect Zones between source and target Robot-pool. More inforamtion for best practice creating Runbook Robot policy and other configuration (like,  zone readiness and igs hints alias, etc can be found in above sections or in this link for Runbook Access Zone advance configuration.
  3. Enable the Runbook job,  Run the config replication policy job.
  4. Run the Runbook Failover and check the running job to find the Failover steps  

Multiple Robot Feature Support (Multiple Instances on Cluster Pairs)

Replicating in pairs:

Cluster A -> Cluster B

Cluster C -> Cluster D

1 eyeglass managing 4 clusters

Set it up as follows: Different Access Zone name and path on each pair

Summary of setup:

 

Access Zone

Path

SyncIQ PolicyMapping Hint on Robot Subnet Pool
Cluster A

EyeglassRunbookRobot-1

/ifs/data/Robot

EyeglassRunbookRobot-Puru

Source path: /ifs/data/Robot

Target path: /ifs/data/Robot

igls-Robot-source8002
Cluster B

EyeglassRunbookRobot-1

/ifs/data/Robot

 igls-Robot-target8002
Cluster C

EyeglassRunbookRobot-2

/ifs/data/Robot2

EyeglassRunbookRobot-Robot2

Source path: /ifs/data/Robot2

Target path: /ifs/data/Robot2

igls-Robot1-gbisi01
Cluster D

EyeglassRunbookRobot-2

/ifs/data/Robot2

 igls-Robot1-gbisi02

Example:

cluster A (Source-8002)

policy 1 (EyeglassRunbookRobot-Puru) = source path: /ifs/data/Robot to target path: /ifs/data/Robot

Cluster C (SourceRobot7201)

policy 1 (EyeglassRunbookRobot-Robot2) = source path: /ifs/data/Robot2 to target path: /ifs/data/Robot2 

Detailed configuration:

  1. Create an Access Zone with name beginning with “EyeglassRunbookRobot” on all four clusters ( i.e two source and two target cluster to be tested for DR. ).

 Note: Two source Access Zone name, basepath  need to be unique and not overlapping.

  1. Create a SyncIQ policy on two source cluster See Basic setup above for detailed steps.
  2. Create a subnet pool and make it a member of the Access Zone.

Note: the IP address used should be reachable by Eyeglass to mount with NFS export.  Create this pool on all four clusters.

  1. Dual DNS delegation needs to be done on both Source cluster Smartconnect Zone name and make sure it is resolving. (See Geographic Highly Available Storage solution with Eyeglass Access Zone Failover and Dual Delegation)
  2. Now create mapping alias for the Robot to move SmartConnect Zones from one pool to another. (See Eyeglass Access Zone Failover Guide “Configure Eyeglass Subnet IP Pool Mapping Hints” section )
  1. Example on Source cluster A:  isi network pools modify groupnet0.subnet0.pool4 --add-sc-dns-zone-aliases=igls-Robot-source8002
  2. Example on Source cluster C:  isi network modify pool --name=subnet0:prod-Robot After inventory runs (5 minutes default interval) you should see the Robot Jobs in “userdisabled” state therefore need to enable it and run it
  3. --add-zone-aliases=igls-Robot1-gbisi01
  4. Example on target cluster B: isi network pools modify groupnet0.subnet0.pool4 --add-sc-dns-zone-aliases=igls-Robot-target8002
  5. Example on target cluster D: isi network modify pool --name=subnet0:dr-Robot --add-zone-aliases=igls-Robot1-gbisi02

  1. To get the Zone Readiness updated See Advanced setup above for detailed steps
  2. Now open the DR Dashboard and select Zone Readiness to view the Robot Zone Readiness status

  1. After verifying Zone readiness status, we have to run the Failover: Runbook Robot (AUTOMATIC) job to start failover

  1. After Failover you can check the SmartConnect Zone alias on each cluster and look for igls-original prefix on SmartConnect Zone name failed over. See Advanced setup above for detailed steps
  2. Here is the Failover History

  1. Done


© Superna LLC