Service - Superna ™ Eyeglass 1 Cluster Migration Service Description

Eyeglass Service Description - 1 Cluster Migration

Part number eyeglass-p018 “SEL-EyeGlass 1 Cluster Migration Service”

Revision 1 Dec 28, 2017


This service assists with migration of data and configuration from one cluster in a hot\cold configuration to a new pair of clusters.  This service offers expertise, planning, design and configuration assistance to enable migration from one cluster to another.  Typical use cases are:  data center move, hardware refresh, retiring an older cluster.

The service provides the following:

  1. Rental Eyeglass licenses for the duration of the project.  During the project more clusters exist than will be required in the final location.  This provides fully supported license keys during this time for all clusters added to eyeglass during the service.  

    1. Limited to 6 months.    

    2. For longer migration projects additional fees are required.

  2. Design, planning, Configuration of migration to leveraging Eyeglass features to enable:

    1. 1 x one way failover for hot\cold clusters

    2. Data migration with Access Zone migration feature as required

  3. Planning assistance before scheduled cut over event

  4. Actual cut over uses standard Eyeglass support process for the day of the event

Terms of Service

  1. Service Delivery: Remote webex

    1. Service operates Monday to Friday 8:00 AM to 6:00 PM EDT excluding major holidays

  2. Availability: Monday to Friday 8:00 AM EDT to 6:00 PM EDT, excluding holidays And weekends

  3. Terms and Conditions of task covered in product maintenance agreement Exhibit A  section 4.0  

  4. Service Description:  This service will assist in outline of steps required to configure a one way failover of data from 1 existing cluster to 1 existing new cluster and OR how to migrate data + configuration to new target cluster.  It will only cover Eyeglass related steps in detail and outline external steps that must be done to complete the overall migration.  

    1. NOTE: The destination clusters must have permanent eyeglass licenses.

    2. NOTE: The destination clusters require a design service to assess, implement a DR design.  The migration service does not cover the target cluster configuration for DR.  


  • Eyeglass is installed (install SOW required and offered free of charge)

  • Supported Onefs Release or later

   Exceptions excluded from hours usage:

  • Outage or issue resolution, recovery of any kind for execution day tasks

  • NOTE: Design and implementation service OR DR Quick start Service will be required to cover the scope of DR design and implementation for the final cluster Configuration.  This is not included in this service.

  • Customers are expected to dry run any procedures that are applicable to their environment, network, applications and internal processes, maintenance windows

  • Assisted DR hands on or remote or procedural assistance of any kind in a production environment

  • This is a planning and design service not an assisted migration service which means monitoring of migration of data, data access validation (security access, networking, firewall, permissions testing, lan or wan changes) , data sync confirmation and completeness, assessment of application health pre and post migration are customer responsibilities.

  • Assisted migration steps are not included.  Customer is expected to test all procedures in documents provided to ensure they understand how to execute all steps.

    • Example host mount testing

    • DNS and AD changes are documented but applied by customer IT teams

  1. Project summary :

  1. Scope of activity

Objective: Swing 1 cluster  over to a new cluster.  Phased project that will address hot\cold cluster pair migrated to new cluster as production cluster.   The scope covers the configuration and design and planning of the 1 phase cutover.  

  1. Plan Overall Migration and Cutover

    1. Supported configuration synced data is listed here

    2. All configuration data not listed above is not supported or included via Eyeglass and will be manually recreated on target cluster.

  2. Migration Document deliverable that covers the configuration required for one way failover, data sync, config sync, planning of failover execution.

    1. Configure failover for data+config migration from source 1 to new cluster 1

      1. Who participates: Superna + Customer -->  AD , DNS, Isilon configuration, Eyeglass

    2. Data Sync Phase (Source 1  and New Cluster 1)

      1. Who participates: Superna + Customer -->  Data and Path assessment to failover to new clusters.

      2. Configure syncIQ policies to sync required data and configuration from source 1  cluster to New cluster 1

      3. Start Data sync

      4. Note:  Requires dedicated IP pool and smartconnect names for SyncIQ.  Best practices followed.

    3. Configuration sync phase (New Cluster 1) - pre failover

      1. Who participates: Superna + Customer

      2. Verify all config matches synciq paths (only supported syncable objects)

      3. Verify - audit configuration data for sync errors and correct as required

        1. Compare config counts on both clusters as an audit of configuration data

      4. Objects synced shares, exports (single path exports only), nfs aliases, quotas , access zone user mappings (note local users not supported), snapshot schedules  

        1. Note: only config that matches synciq paths

        2. Plan for any unprotected configuration data audited using Eyeglass cluster report and log parsing tools

        3. Report to Customer exposed data for decision on how to migrate with access Zone migration feature or manual migration.

    4. Eyeglass Failover Mode Configuration

      1. Who participates: Superna + Customer

      2. Configure appropriate failover mode from source 1 to new cluster 1

      3. Validate DR Readiness

    5. Execute planning guide steps pre-failover

      1. Who participates: Customer

      2. Customer will be responsible for running through planning guide and providing updates on status to support - Customer + Superna Support

      3. Audit checklist steps - Superna Support

    6. Failover #1 - completed for source 1 to new cluster 1

      1. Who participates: Customer

      2. Failover scheduled and executed - Customer

        1. Normal Support process for failover

        2. Test Data Access Procedure completed

        3. Failover Completed

    7. Post Failover - Re-Protect Data Sync from New Cluster 1 to Target 1

      1. This step will cut over data replication services to allow decommissioning of source cluster 1

      2. Resync data with new SyncIQ policies from New cluster 1 to Target 1.

        1. Data sync complete

      3. Decommission policies from New Cluster 1 to Source 1

      4. Decommission Source 1  cluster - Not included in scope, Customer responsibility.  Documented here for completeness.

      5. NOTE: At this point data is DR protected but DR Readiness requires DR design implemented from New Cluster 1 to Target 2  for failover and failback.  

        1. Additional services required for DR Design eyeglass-p013 or eyeglass-p15.

This Service Description is an agreement between the company receiving the Service identified below (“you or “Company”) and Superna, LLC (“Superna”), pursuant to which Superna agrees to provide certain professional services in connection with your use of the Superna Eyeglass® software (the “Licensed Product”).  This Service Description is subject to the terms of the Superna Eyeglass Software License and Support Agreement , and Exhibit B attached thereto (the “Agreement”) the terms of which are incorporated herein by reference.  

Company Name _____________

Signed: ____________________

Name (PRINT):______________



Telephone: ________________