Home Top

Basic DR Robot Configuration

The basic option requires a non-production, Eyeglass specific SyncIQ policy to exist.  The Runbook Robot will exercise the failover and failback of the data for this SyncIQ policy. This configuration does not fully exercise all automation required for failover but it’s quick and easy to setup.

Prerequisites

1. SyncIQ policy in any Access Zone BUT only “EyeglassRunbookRobot” prefixed policies will execute the failover logic.  
2. This type of Robot policy will not failover SmartConnect names, alias, SPN’s.
3. This is designed to ensure no SmartConnect Zones used by non Robot policies will be failed over in the Access Zone:
2. The Basic Robot is intended to operate on non-production data.  The steps below include directions to create the Runbook Robot specific SyncIQ policy on the cluster for the Basic Runbook Robot operation.
3. If you create shares, exports or quotas in the path of the Robot SyncIQ policy, they will be failed over as well using normal configuration sync jobs.  It's a good way to test the whole failover of the configuration.  The configuration names of shares, exports can be any name.

Note: Eyeglass will modify the description, Root Client and Map Root User settings as required for Robot operation on an existing export with same path as the Robot SyncIQ Policy root path.

4. Quotas will be failed over during the Robot execution and deleted on source automatically if quotas have been created within the SyncIQ policy used for the Robot.
5. Eyeglass Hostname on the Network Card Setup and the Network Settings (setup using yast during initial Eyeglass appliance configuration) must be identical.

Configuration Steps for Basic DR Robot

The steps are the following:

1. Log into the PowerScale Source cluster via OneFS.
2. Click on Data Protection, then SyncIQ, then on the Policies tab.
3. Click on + Create a SyncIQ Policy.

4. In the Settings section of the Create SyncIQ Policy window, enter EyeglassRunbookRobot-XYZ (where XYZ is a random string) in the Policy Name field.

IMPORTANT: This name format must be followed exactly in order for the Basic Runbook Robot job to execute.

5. In Source Cluster section, select a Source Root Directory by clicking Browse next to the box and navigating to the desired folder.

IMPORTANT: This should be a directory containing NON production data as it will be failed over by default once a day.

6. In Target Cluster section under Target Host, enter the target cluster SmartConnect zone name used for SyncIQ replication of the Target cluster , and under Target Directory the path on the Target cluster to where the data will be replicated .

7. Do not enter or modify anything in the Target Snapshots and Advanced Settings sections.
8. Click on Create Policy. The policy will appear in the SyncIQ Policies chart.

9. Click on More and select Start Job on newly created policy.
10. Ensure that the policy completes successfully.
11. Log into Eyeglass.
12. Open the Jobs window and select the Job Definitions section.
13. Under the Configuration Replication jobs, look for a Job Name that resembles SourceClusterName_EyeglassRunbookRobot-XYZ (where XYZ is the random string chosen when creating the policy). Make sure it’s State is OK.

Notes:

1. This Job will be created after Eyeglass discovery has found the SyncIQ Policy created in the previous steps.  If the Job is not present, wait for the next Eyeglass discovery cycle and then check again. 
2. NOTE:  You can enable DFS mode on the basic robot policy.  Eyeglass will still use NFS to write data to the cluster but DFS mount can be created to verify faiover and failback operations over DFS by manually check the DFS mount each day.   Eyelgass will still execute normal NFS failover and failback data integrity check.
   1. How to Enable DFS mode Basic Robot
   2. Find the policy the Configuration replication section of the Jobs icon.
   3. Select the checkbox on the left-hand side for the Job mentioned above and click the Select a bulk action button at the bottom of the Jobs window. This time, click the Enable/Disable option.
   4. Select the checkbox on the left-hand side for the Job mentioned above and click the Select a bulk action button at the bottom of the Jobs window and click the Enable/Disable Microsoft DFS option.
3. Inventory runs with every Eyeglass Replication cycle ( every 5 minutes by default ) so you may need to wait for the next Eyeglass Replication cycle for the new Job to appear in the jobs window.

14. If the SyncIQ Policy Name that was created has been entered properly, a new type of Job category will appear in Eyeglass: Failover: Runbook Robot (AUTOMATIC).

15. By default, the Job will be queued to run at midnight every day.
16. If you want to test it after creating the policy, select the job in the jobs windows and use bulk action to run now.

16. When the Runbook Robot Job runs, in the Running Jobs section a job will appear with the Name Runbook Robot, followed by a time stamp.

17. The Runbook Robot job will run a three-stage Failover Test, which consists of a Failover Preparation, SyncIQ Policy Failover, and Failover Validation. Once this is done, it will run a Failover Cleanup.
18. The Failover Preparation component consists of the following steps:
19. The job will create a new Eyeglass export or update an existing Eyeglass export with the following parameters:
    3. Description: Superna Eyeglass Runbook Robot export Appliance ID
    4. Root Clients: The Eyeglass IP address used
    5. Map Root User settings
    6. Directory Paths: The Source Root Directory chosen when creating the SyncIQ Policy
    7. This export is then mounted on the Eyeglass appliance.
    8. Data is then written to the export, which is dependent on the SyncIQ Policy Path and timestamp.
20. The export is then unmounted
21. To view the exports created: open OneFS with the IP address of the source cluster, click on the Protocols tab, then click on UNIX Sharing (NFS), followed by the NFS Exports tab.
22. 
23. Once the preparation is successfully completed, Eyeglass performs a SyncIQ Policy Failover.
24. On completion of the failover, Runbook Robot will run a Failover Validation in order to make sure that the data was failed over without issues. The Failover Validation component consists of the following steps:
    1. The export created is mounted on the Eyeglass appliance using the IP address of the failover target cluster.
    2. The timestamp is read to confirm it is identical to what was written during the Failover Preparation step.
    3. A new timestamp is written to the Failover.ts file.
    4. This new timestamp is then read to confirm it has been written correctly.
    5. This export is then unmounted from the Eyeglass appliance.
25. Once the Failover Test has been completed, the Runbook Robot job will run a Failover Cleanup, which consists of unmounting the export from the Eyeglass appliance.
26. The default Robot jobs run every day at midnight and executes a failover Robot policy.  
    1. Creates export.
    2. Mounts the cluster writes test data using the export created.
    3. It failovers the policy.
    4. Runs the policy.
    5. Mounts the data on synced export on target.
    6. Unmounts.
    7. Moves the schedule on policy to the target.
    8. Runs resync prep on source.
    9. Goes to sleep until time to failback.
27. Methods to verify it was successful:
    1. Check the DR Dashboard policies tab and verify it’s green.
    2. Check the cluster SyncIQ policy status on both clusters and make sure the policy moves from one cluster to the other each day.
    3. Make sure the test file exists with a current date and time stamp on the active cluster (Hint; look in the policy path root file system for the test file).
    4. If a quota was applied to Robot policy path, make sure the quota moved to the target cluster AND was deleted on the source cluster (Eyeglass moves policies on failover).
    5. Review the Failover Log (DR Assistant / Failover History / Open log file).  Failover log may also be downloaded from the Failover Log Viewer using the Download File link.

    
    

DFS Mode manual Validation of Basic Robot

© Superna Inc