Skip to main content
Version: 2.9.0

User Guide

This guide provides a comprehensive overview of setting up and configuring Disaster Recovery for PowerScale OneFS, VAST and Qumulo.

Requirements​

VAST Requirements​

  • VAST Version: 5.0 or 5.1
  • Administrator Level Account within VAST
  • Eyeglass VM successfully deployed
  • Network Connectivity from Eyeglass Appliance to VAST storage device

Installation​

Adding a VAST Cluster to Eyeglass​

  1. Open Eyeglass Main Menu: On the Eyeglass Appliance, go to the bottom left corner and click on Eyeglass Main Menu. Then, choose Add Managed Device.

  2. Select VAST: In the Add Managed Device window, choose VAST from the options on the left.

  3. Enter VAST Details: Fill in the following fields and click Submit:

    • IP Address of the VAST cluster
    • Username
    • Password

    VAST Cluster Configuration

  4. Check Inventory View: Once submitted, the VAST cluster should appear in the Inventory View.

    VAST Cluster in Inventory View

  5. Success: You have now successfully added the VAST cluster to Eyeglass.

info

The device should appear in the inventory right away, but it might take a few minutes for all inventory details to show up.

Configuration Replication Guide​

What is Configuration Replication?​

Configuration replication involves copying metadata associated with files on a storage cluster. This metadata controls access to data, as well as failback and replication mappings, schedules, and properties. For detailed information on what is specifically replicated, please refer to the sections for different storage vendors below.

Configuration Replication: What is Being Copied?​

PowerScale OneFS​

Configuration replication for PowerScale OneFS’s PowerScale OneFS cluster covers the following elements:

  • SMB Shares
  • NFS Exports
  • Policies
  • IP Pools
  • Access Zones
  • Network Configuration
  • Quotas
  • Snapshot Schedules
  • User Access Controls

How-to: Initiating, Monitoring, and Completing Configuration Replication​

This section explains how to start, monitor, and finish configuration replication. In Eyeglass, these replication tasks are handled as Jobs that run automatically every 5 minutes in the Running Jobs section of the Jobs window, regardless of the vendor. If you need to manually start a configuration replication or check your system’s readiness, follow the steps below.

Prerequisites​

Before starting configuration replication, ensure you have:

  • A predetermined candidate for configuration replication.
  • Access to the Jobs page within Eyeglass.

  1. Navigate to the Jobs page within Eyeglass.

  2. In the Jobs window, select Job Definitions from the left-hand menu.

  3. In the Job Definitions table, navigate to the section relevant to your candidate. All configuration replication jobs are nested under sections that begin with “Configuration Replication.”

  4. Our supported storage vendors are organized in the following manner:

    • Configuration Replication: Share, Export, Alias replication
    • Configuration Replication: Snapshot Schedules
    • Configuration Replication: Access Zone replication

  5. Find your specific candidate in the list, then click on the row or checkbox next to it. The row will be highlighted in yellow.

    info

    You can select multiple rows if you want to run several jobs at the same time.

  6. Look at the State column in the table. If the state is OK, you can proceed. The State column can show the following statuses:

    • OK: No action needed; the job is ready to run.

    • User Disabled: The job was turned off by a user. To enable it, click Select a bulk action at the bottom right of the Jobs window, then choose Enable/Disable.

    • Warning: This indicates a non-blocking issue that might cause problems if the job runs.

      • To investigate the warning:
        • Go to DR Dashboard.
        • Select the job type from the left-hand menu.
        • In the next screen, find the object associated with the warning and click the value in the DR Failover Status column.
        • In the new window, expand the Eyeglass Configuration Replication Readiness folder.
        • Click the value that appears below to view the warning details in the Additional Status Information section at the bottom of the window.

    • Error: This indicates a blocking issue, meaning the job cannot run until the issue is resolved.

      • If a job failed recently, you can:
        • Click on Running Jobs in the left-hand navigation.
        • Find the failed job in the resulting table.
        • Click on the row to view more details.
      • To investigate the blocking error:
        • Go to DR Dashboard.
        • Select the job type from the left-hand menu.
        • In the next screen, locate the object associated with the error and click the value in the DR Failover Status column.
        • In the new window, expand the Eyeglass Configuration Replication Readiness folder.
        • Click the value that appears below to view the error details in the **Additional Status

    • Pending: The job is waiting in the queue to run.

    • Policy Disabled: The configuration replication job was turned off on the host cluster. Go to the host cluster and enable it to change this status.

  7. To start the configuration replication job, click the three arrows icon next to the job’s status. This will run the job immediately. If you’ve selected multiple rows, click the Select a Bulk Action button at the bottom right of the window, then choose Run Now from the menu. Once the job(s) have been successfully submitted, a confirmation message will appear.

    Job Submission Job Submission Success

  8. To monitor the progress and status of the job, go to the Running Jobs section in the left-hand menu of the Jobs window.

  9. If the job completes successfully, you’ll see a checkmark in the State column. If a red X appears, check the Job Details section to find and resolve the error.

  10. You’ve successfully replicated the configuration of your object. Take a moment to relax and enjoy your accomplishment!

Failover Guide​

This section explains how to configure, initiate, and monitor a failover. There are three different scenarios where you might interact with the failover platform, and we will cover each one in detail:

  1. Regular Monitoring and Readiness Checking: Regularly check your failover status to ensure your system is ready for a failover.

  2. Planned Failover: Involves a pre-scheduled failover for regular testing or compliance, where both your source and target clusters are online and operational.

  3. Unplanned Failover: Occurs when your source cluster is offline or experiencing issues, requiring a failover to your Disaster Recovery (DR) site.

For this guide, both planned and unplanned failovers will be covered in the same sections.

Types of Failover​

There are two major types of failover:

  • Failover without Client Redirection: The failover occurs without redirecting clients to a new location.
  • Failover with Client Redirection: The failover redirects clients to a new location.

Whether or not client redirection is available depends on the type of failover object you are working with.

PowerScale OneFS Failover​

Failover objects that do NOT support client redirection:

  • Policy

Failover objects that DO support client redirection:

  • Access Zone
  • IP Pool

How-to: Monitoring Readiness​

In this section, we’ll walk you through how to monitor your system's readiness for a failover.

Prerequisites:
None

  1. Access the DR Dashboard: Start by selecting DR Dashboard from the Eyeglass dashboard.

  2. Review Available Failover Objects: The left-hand menu in the DR Dashboard window will display readiness information only for those failover objects that are available from your configured inventory. For example, if you’ve configured a PowerScale OneFS cluster, you will see options like Access Zone, IP Pool, DFS, and Policy Readiness in the navigation menu.

  3. Select the Relevant Failover Object: Choose the failover object that is relevant to your use case from the available options in the left-hand menu.

    Select Failover Object

  4. When monitoring the readiness of your failover objects, pay special attention to the DR Failover Status column in the table. This column is crucial for maintaining the readiness of your failover objects. Ideally, every important failover object should have a status other than ERROR.

    info

    The DR Failover Status is updated once every 24 hours, usually around midnight local time. If you suspect anything has changed in your readiness status since the last update, it's recommended to select the specific failover object and click Run Readiness in the bottom right to recheck the status.

    The possible statuses include:

    • OK: Indicates the related failover object is ready for failover.

    • ERROR: Indicates the related failover object has a blocking error that will prevent failover.

      • To investigate the blocking error:
        • Click on ERROR in the DR Failover Status column.
        • In the following window, expand the folder(s) marked with ERROR and then click the value(s) that appear below.
        • This will display the error details in the Additional Status Information section at the bottom of the window.

    • WARNING: Indicates the related failover object has an issue that could negatively impact failover, but it is not blocking.

      • To investigate the warning:
        • Click on WARNING in the DR Failover Status column.
        • In the following window, expand the folder(s) marked with WARNING and then click the value(s) that appear below.
        • This will display the warning details in the Additional Status Information section at the bottom of the window.

    • FAILED OVER: Indicates the related failover object is no longer the active cluster and is not available for failover.

    • INFO: Indicates the related failover object has a missing configuration that does not negatively impact failover.

    • DISABLED: Indicates the related failover object has been manually disabled.

      • To enable a disabled failover object:
        • Navigate to the Jobs icon on the Eyeglass dashboard.
        • In the Job Definitions section of the Jobs window, find your related failover object and click on the respective row.
        • Click Select a Bulk Action at the bottom right of the Jobs window and then choose Enable/Disable from the menu.
        • You should now be able to navigate back to the DR Dashboard to review the refreshed status of the related failover object.

How-to: Failover​

This section of the guide will cover the steps to start, monitor, and complete a failover.

Prerequisites:

  • A storage cluster failover candidate
  • A failover object candidate

Steps:

  1. Access DR Assistant: From the Eyeglass Dashboard, select DR Assistant.

  2. Select Storage Cluster: In the Failover Assistant section of DR Assistant, choose your storage cluster failover candidate from the Source Cluster dropdown menu.

  3. Choose Failover Object: Select the type of failover object you want to failover from the Failover Type dropdown menu.

  4. Enable/disable any applicable Failover Options. Not all options are available for all storage platforms. The available options are as follows:

    • Controlled Failover:

      • Only uncheck this option if the source cluster is unreachable. Using this option means you are failing away from the data and losing all changes at the moment the failover is started. If this is unchecked, all failover will occur from an older snapshot and will result in data loss.

    • Data Sync:

      • This option adds a step to the failover process to sync data between the source and target cluster before the failover begins. It’s recommended to keep this option enabled as it minimizes the amount of data that could be lost during a failover.

    • Config Sync:

      • Synchronizes the configuration between the source and target clusters during failover.

    • SMB Data Integrity Failover:

      • This option disconnects any active SMB sessions before the failover starts and ensures that no new sessions can be established on the failover source. This prevents data loss by ensuring no new data is written to the source cluster.

    • SyncIQ Resync Prep:

      • Disabling this option is not recommended as it will leave the system in a state where you cannot use Eyeglass to fail back. This option is used only when customers plan to failover in one direction and then recreate a new policy, or they know how to manually recover and create a mirror policy.

    • Disable SyncIQ Jobs on Failover Target:

      • Disabling on failover is optional if you don’t want to configure failback and execute sync jobs in the return direction. This is used when you want to verify systems before replicating data back to the source.

        warning

        Using this option will require manual steps to fail back.

    • Quota Sync:

      • This option will sync (i.e., copy the settings) quotas before failover on both the source and target.

    • Block Failover on Warnings:

      • This option will stop a failover from proceeding if a WARNING status exists.

    • Rollback Renamed Shares on Failure:

      • This option ensures that if the failover process fails, any shares that were renamed will be reverted to their original names.

  5. Proceed with Your Selected Options:

    • Once you have selected the failover option(s) you want, click the Next button in the bottom right corner to proceed.

  6. Review Failover Support Policies:

    • The next screen will display our failover support policies. Please read through them carefully, then select the checkbox and press Next to continue.

  7. PowerScale OneFS Cluster Best Practices:

    • If you selected a PowerScale OneFS cluster, you will see a Best Practices screen. Please review the information provided, then press Next to proceed.

  8. Select Failover Objects:

    • This screen will show the failover objects available to you based on the options you selected earlier (cluster and failover type).
    • Use the checkboxes on the left side of the table to select the failover object(s) you wish to include, then click the Next button to proceed.
    info

    If you believe your DR Failover Status has changed, you can select Run Readiness to update this status. The job usually takes up to 5 minutes to finish, but it may take longer depending on your configuration.

    Failover Object Selection

    Review Success Screen:

    • Assuming there are no errors, you should see a Success screen. Please review the failover release notes carefully, then click the checkbox to confirm you’ve read them, and press Next to continue.

  9. Summary and Run Failover:

    • This screen provides a summary overview of the selected failover object, including its DR Failover Status and the options that are enabled.
    • After reviewing all the settings and ensuring they are correct, click the checkbox at the bottom of the window to confirm, and then click the Run Failover button to initiate the failover process.

    Failover Summary Overview

  10. Success!

    • You have now successfully started a failover—congratulations! Next, we need to monitor the progress of the failover to ensure everything proceeds smoothly.

  11. Monitor Individual Operations:

    • While the failover is running, you can review the individual operations being executed in the Job Details section of the page.
    • For a more detailed view, click the Logs hyperlink within the running failovers table to monitor the actions at a more granular level.
    • We recommend opening the Failover Log Viewer and clicking the Watch button to stay up-to-date with the progress.

    Monitoring Failover Progress

  12. Handle Any Issues:

    • If your failover encounters any issues, you can view them in the Job Details section by clicking the INFO hyperlink next to the particular job name.

  13. Success!

    • You have now successfully completed a failover—congratulations!

  14. View Historical Failovers:

    • You can view historical failovers by navigating to the Failover History menu item within the left navigation of DR Assistant.