Skip to main content
Version: 4.4.0

Superna for Qumulo DR Design and Implementation Service

Superna Product Code (SKU): EYEGLASS-P015

Overview​

This service provides the remote implementation of DR configurations for Qumulo clusters, enabling failover through one of the supported failover modes. The configuration changes address replication relationship best practices to enable a robust DR solution with Qumulo and Superna.

Service delivery: Remote sessions for audio, video, and screen sharing via Zoom, VPN, or alternate remote access to customer Qumulo equipment. Estimated 5–8 hours over a span of 6–8 days with dedicated customer technical resources.

Operating hours: Monday to Friday, 9 am–4 pm in your local time zone, excluding major holidays.

Terms and conditions: Subscription EULA

Exclusions​

  • Customers are responsible for making all changes to all third-party devices or software components, and for having expertise in AD, DNS, Firewall, and NFS sufficient to follow the directions provided by this service. All hands-on changes to third-party products must be done by the customer.
  • Two-cluster design coverage is included in the scope of service.
note

For three or more clusters, an additional purchase of DR Implementation Services or service hours is required.

  • Superna Services failover and failback implementation activities cannot use any type of production data.
  • Superna Services are not a substitute for customer-developed procedural runbooks (step-by-step, command-level documents that include external application procedures to validate DR end to end).

Prerequisites​

  • Installed Superna Core Agent Appliance.
  • Qumulo cluster login with admin and root access.
  • Customer SME (Subject Matter Expert) technical contact to make changes to Qumulo, AD, DNS, NFS, networking, host access to shares or exports, and Linux environment.

Service Methodology​

Environment Readiness Phase​

DR Design and Implementation questionnaire/kickoff:

  • Review DR mode choices with the customer.
  • Collect cluster replication topology (Hot/Cold or Hot/Hot).
  • Collect SMB and NFS mounts from the cluster configuration via Superna report: SMB mounts and NFS mounts.
  • Update the summary in the Design document.
  • Collect configuration reports from the Superna appliance for each cluster.
  • Set Cluster RPO value to the customer objective for Replication Relationship data loss exposure in minutes/hours per cluster — via reports to validate Replication Relationship schedules.
  • Demonstrate to the customer the RPO report and how to run and review the report that measures RPO compliance percentage in reports on demand.
  • Collect current Replication Relationship configuration: Replication Relationship configuration schedules (on change detection) report, and best practice review versus current Replication Relationship configuration.
  • Collect Active Directory information (domain name, machine account names) report.
  • Demonstrate AD delegation using the documentation link "How to Configure Delegation of Cluster Machine Accounts with Active Directory Users and Computers Snap-in."
  • Customer to complete delegation steps with AD administrator.
  • Test that AD delegation is completed correctly.

Deployment Readiness Activities​

DR Design Phase:

  • Recommend failover solution to the customer based on the Collection Phase.
  • Cover all configuration changes on the cluster in this section and document them in the design document: AD delegation, configuration sync issue resolution, Replication Relationship configuration changes, and additional configuration changes.
  • Build Cluster Change Management Plan, including order and CLI commands to be executed by the customer and validated by Superna.
  • Build the plan in two phases: online changes and maintenance window changes.
  • Review the design document with the customer. Obtain sign-off on the design and configuration change plan before proceeding to the next phase.
  • In collaboration with the customer, apply configuration changes defined in the Design document following the execution plan.
  • Customer applies changes, coordinating with SME within the customer organization.
  • Submit support logs for validation of correct configuration.

Knowledge Transfer Phase​

  • Review failover planning guide on how to plan a failover.
  • Review best practices guide on how to execute steps pre-failover and verify the cluster environment before any failover.
  • Review failover release notes for last-minute release-specific steps or instructions.
  • Review DR Assistant validation screen warnings and process for open files.
  • Review failover logs in detail to explain how to read them and diagnose successful vs. unsuccessful steps.
  • Review failover recovery guide and how to use it to recover from failed steps.
  • Review the process to raise a support request correctly to get failover log analysis completed.

Service Complete​

Review and deliver final DR Design document.