Service - Superna ™ Eyeglass Isilon DR Design and Implementation Service Description

Superna Eyeglass Service Description

Part number SEL-EyeGlass DR Design-Implement-v1 - eyeglass-P013


Revision 1 Feb 11, 2018

Services - Superna ™ Eyeglass Isilon DR Design and Implementation


This service ensures  the highest level of DR readiness possible for Isilon customers with Superna Eyeglass. Recommended For: For customers that prefer to have Superna PS recommend and validate  customer implementation of cluster, DNS, AD changes and validate the end to end design and implementation to achieve high level of confidence the key business data is protected for all possible DR impacts.  Customers that view DR investments as a way to achieve continuous operations level of storage availability.

  1. Description:  This service is a stand alone service  that provides Isilon cluster remote implementation of cluster DR configuration  required for failover using one of the supported failover modes (Access Zone dual delegation, SyncIQ or DFS mode).  The  configuration changes will also address SyncIQ best practices to enable a robust DR solution with Isilon and Superna  ™ Eyeglass.   In addition, DR Readiness automation will be configured to ensure continuous DR testing is fully automated using the RunBook Robot feature in Superna ™ Eyeglass.



  1. Requirements to Engage Services - Mandatory to complete the service questionnaire before service team resources are assigned.  The link to service questionnaire.

  2. Access Requirements: Isilon cluster login with admin and root access

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

  4. Service Delivery: Remote WebEx, VPN or alternate remote access to customers Isilon equipment.  Approximately 8 days with dedicated customer technical resources.

    1. Exclusions:

      1. Service operates Monday to Friday 8:00 AM to 5:00 PM EDT excluding major holidays (Alternate schedules can be arranged on request)

      2. Failover knowledge transfer cannot use customer equipment or any type of customer data.

      3. Not a live DR service or support function for failover of production data

      4. Not a substitute for customer developed procedural run books, (runbooks are step by step, command level documents, and include external application procedures to validate DR end to end)

      5. Demonstration of configuration steps to be implemented will exclusively use Superna Data center resources to show procedures.   

        1. External component or software changes are excluded from all meetings including  AD, DNS, Isilon

        2. Only Isilon configuration will be implemented, external equipment DNS, Active Directory changes will be sent as instructions for customer to execute (with assistance via WebEx support)

      6. customer is responsible to make all changes to all 3rd party devices or software components and have expertise in AD, DNS, Isilon, Firewall, Windows, DFS, NFS sufficient to follow the directions provided by this service

      7. Exceptions: 2 Cluster design coverage, 4 block of additional hours (part eyeglass-b4-2)  added for each additional cluster requested as part of the service.


Prerequisites:

    • Installed Superna  Eyeglass appliance  

    • Customer SME (subject Matter expert) technical contact to to make changes to Isilon, AD, DNS, networking, host access to shares or exports

    • Customer IT admin knowledge of  DNS or Active Directory and DFS admin teams when required for DNS, AD and DFS configuration changes are required, NFS linux environment, Isilon hands on knowledge

Superna ™ Supplied Project Tools

  1. http://Basecamp.com dedicated Web based project management site for updates, status, document sharing and permanent archive of the project deliverables, shared by Superna and customer technical team at the customer site.

  2. Webex account for screen sharing



Service Flow


D&I Service Flowchart.png


  1. Collection Phase - DR Design and Implementation - Interview

    1. Review DR mode choices with customer from the Start Here Guide.

        1. Collect cluster replication topology (Hot/Cold or Hot/Hot)

    2. Collect SMB and NFS  mounts from the cluster configuration - via Eyeglass Report

      1. SMB mounts

      2. current DFS usage and configuration - Get screenshot

      3. NFS mounts

      4. Update summary in Design document.

    3. Collect configuration reports from Superna ™ Eyeglass for each cluster

    4. Set Cluster RPO value in Eyeglass to customer objective for SyncIQ  data loss exposure in minutes/hours per cluster)- via Eyeglass reports to validate SyncIQ schedules

        1. Demonstrate to customer the RPO report and how to run and review the report that measures RPO compliance percentage in reports on demand.   

    5. Collect current SyncIQ  configuration

        1. SyncIQ configuration schedules (on change detection)  Eyeglass report

        2. subnet and IP used for replication, restrict at source, DNS target host using smartconnect  Eyeglass report

        3. Best practice review versus current syncIQ configuration

    6. Collect SmartConnect Zones configuration and usage - Eyeglass report

      1. Include in Design document summary

    7. Collect Access zone usage - Eyeglass report

        1. Include in Design document summary

    8. Collect DNS  resolution of Smartconnect names  - nslookup

        1. Verify nameservers returned are Subnet service ip from each cluster.

        2. Include in Design document summary

    9. Design SmartConnect failover mappings for Pool to Pool mappings between sites - Eyeglass report

        1. Requires IP pool to IP pool mapping between cluster sites

        2. Update design document mapping table aliases for each pool that is recommended.  Customer to make these changes to the environment.

    10. Collect Active Directory information (domain name, machine account names) - Eyeglass report

        1. Demonstrate AD delegation using documentation link here.  

        2. Customer to complete delegation steps with AD administrator

        3. Test AD delegation is completed correctly using document here.

    11. Customer sign off on phase completed - Email or Basecamp post to acknowledge

  2. Design Phase - DR configuration

    1. Recommend failover solution presented to customer based on Collection Phase

      1. All Access Zone changes on the cluster are covered in this section and documented in the design document.

      2. Includes AD delegation SPN failover

      3. Smartconnect name changes and DNS delegation changes

      4. configuration sync issue resolution

      5. syncIQ policy configuration changes

      6. Eyeglass configuration changes

      7. DFS (if used) changes

      8. pool mapping aliases for failover (access zone or pool failover)

    2. Build Cluster Change Management plan including order and CLI commands needed to be executed by customer and validated by Superna - Customer Deliverable document

    3. Build the plan in two phases online changes and maintenance window changes  - Customer Deliverable document

    4. Review design document with customer (webex) sign off on design and configuration change plan before proceeding to next phase

    5. Customer sign off on phase completed - Email or basecamp post to acknowledge

  3. Continuous DR Automation Design and Configure Phase -  RunBook Robot Access Zone Failover Automation

    1. Design an Access Zone for Run Book Robot feature to implement daily failover and failover for DR Readiness

      1. Review Runbook robot configuration requirements (guide here)

      2. Configure Robot access zone, ip pools, DNS delegation - Requires customer administrators.  

      3. Execute Robot Access Zone failover - Via Webex

      1. Verify successful failover and failback

      2. Review success and failover of robot policies and how to check completion

      3. Review how to change schedule

      4. Review how to run manually for DR testing

      5. Review how to customize with test data and additional shares, exports and quotas

    1. Customer sign off on phase completed - Email or basecamp post to acknowledge

  1. Knowledge Transfer phase: - Via Webex 1-2 hours

    1. Review failover planning guide on how to plan a failover

    2. Review best practices guide on how to execute steps pre-failover and verify the cluster environment before any failover

    3. Review failover release notes document on last minute release specific steps or instructions

    4. Review DR assistant validation screen warnings and process for open files

    5. Review failover logs in detail to explain how to read them and diagnose successful vs unsuccessful steps

    6. Review failover recovery guide and how to use this to recovery from failed steps

    7. Review process to raise support request correctly to get failover log analysis completed.

    8. Customer sign off on phase completed - Email or basecamp post to acknowledge

  2. Implementation phase:

    1. In collaboration with customer apply configuration changes defined in the build design document following execution plan.

      1. Customer applies changes coordinating with SME within customer organization to apply changes from the design guide document.

      2. Superna validates DNS and SmartConnect dual delegation (if implemented), DFS configuration, Active Directory SPN configuration, SyncIQ policy updates, IP pools mapping (if implemented), Eyeglass configuration and job definitions and DR dashboard.

      3. Submit support logs for validation of correct configuration.

      4. Scheduled via multiple webex sessions with customer technical resources based on change management requirements

    2. Customer sign off on phase completed - Email or basecamp post to acknowledge

  3. Validation phase: via Webex

    1. Checklist validation on design with Eyeglass UI and support log analysis

    2. Customer sign off on phase completed - Email or basecamp post to acknowledge