Skip to main content

Tech Refresh (Migration) Service

Overview​

This standalone remote service assists with Tech Refresh of data and configuration when one (1) or two (2) clusters are being refreshed to a new cluster or pair of clusters. This service includes planning, design and configuration assistance to enable migration from one cluster to another by using Superna Core Agent Appliance. Typical use cases include: data center move, hardware refresh, retiring old clusters.

One cluster migration Dell SKU: AB109746. Superna Product Code: eyeglass-P018
Two cluster migration Dell SKU: AB109747. Superna Product Code: eyeglass-P019

Exclusions​

  • Service delivery targeted to be completed within six (6) months. For longer migration projects additional fees might apply.
  • This service outlines the steps required to configure a one way failover of data from two existing clusters to two new clusters. It will only cover Superna related steps in detail and outline external steps that must be done to complete the overall migration.
  • The target clusters must have permanent DR licenses if future failover/fallback functionality is required.
  • Customers are responsible for making all changes to all third-party devices or software components and having expertise in AD, DNS, Networking and PowerScale to follow the directions provided by this service. All hands-on changes to third-party products MUST be done by the customer.
  • Superna will not support any non Superna software and hardware. This includes any technical / networking / data access issues on PowerScale. This will require Dell support to resolve.
  • Customers are expected to validate in advance any procedures that are applicable to their environment, network, applications and internal processes, maintenance windows.

Prerequisites​

  • Installed Superna™ Core Agent appliance
  • Access Requirements: PowerScale cluster login with admin and root access, Active Directory, DNS, DFS namespace
  • Customer IT admin knowledge and permissions to modify 3rd party solutions:
    • DNS
    • Active Directory
    • Microsoft DFS (if in use)
  • PowerScale hands on knowledge required:
    • SyncIQ policies
    • Advanced Pool License
    • Active Directory
    • Architectural network diagram
    • Identify SMB shares, NFS exports/aliases to protect

Service Methodology Flow​

Environment Readiness and Planning Phase​

  • Collect environment information (SyncIQ replication topology, access zones, network pools, DNS vendor, SMB shares & NFS exports/aliases).
  • Design failover topology (what will failover, where it will failover to).
  • Review, discuss and select DR failover mode option.
  • Supported configuration synced data is listed Configuration Replication. All configuration data not listed above is not supported or included, and will be manually recreated on the target cluster.

Configuration and Migration Readiness Phase​

  • Configure failover for data+config migration from source 1 to new cluster 1
  • Configure failover for data+config migration from source 2 to new cluster 2 (applies if two cluster migration was purchased).

Data Sync Phase (Source 1,2 ->New Cluster 1,2)​

  • Configure syncIQ policies to sync required data and configuration from source 1 and 2 clusters to New cluster 1 and 2
  • Start Data sync

Configuration sync activities (New Cluster 1 and 2) - pre failover​

Verification stage (participants: Superna + Customer)

  • Verify all config matches SyncIQ paths (only supported syncable objects)
  • Verify and audit configuration data for sync errors and correct as required
  • Objects synced shares, exports (single path exports only), NFS aliases, quotas , access zone user mappings, snapshot schedules

Failover (cutover) Configuration activities (participants: Superna + Customer)​

  • Validate DR Readiness
  • Execute planning guide steps pre-failover

Failover (cutover) Execution phase​

  • Failover #1 scheduled and executed (participants: Superna + Customer)
  • Failover #2 completed source 2 to new cluster 2 (2 active clusters use case only)

Post failover/cutover phase​

  • Re-Protect Data Sync from New Cluster 1 to New Cluster 2 and New Cluster 2 to New Cluster 1
  • Decommissioning of source clusters from Core Appliance; not the physical Powerscale(s)
  • Resync data with new SyncIQ policies
  • Decommission policies
  • If previous DR configuration existed on source clusters, reconfiguration of the same DR configuration will be applied to the new clusters.
  • NOTE: If no previous DR configuration existed, but is needed, the Customer will be required to purchase additional service hours to complete the DR configuration of the new cluster pair.

Service Complete: Superna Migration Document