InfoScale™ 9.0 Storage Foundation and High Availability Solutions HA and DR Solutions Guide for Enterprise Vault - Windows

Last Published:
Product(s): InfoScale & Storage Foundation (9.0)
Platform: Windows
  1. Introducing SFW HA for EV
    1.  
      About clustering solutions with InfoScale products
    2.  
      About high availability
    3.  
      How a high availability solution works
    4. How VCS monitors storage components
      1.  
        Shared storage - if you use NetApp filers
      2.  
        Shared storage - if you use SFW to manage cluster dynamic disk groups
      3.  
        Shared storage - if you use Windows LDM to manage shared disks
      4.  
        Non-shared storage - if you use SFW to manage dynamic disk groups
      5.  
        Non-shared storage - if you use Windows LDM to manage local disks
      6.  
        Non-shared storage - if you use VMware storage
    5.  
      About replication
    6.  
      About disaster recovery
    7.  
      What you can do with a disaster recovery solution
    8.  
      Typical disaster recovery configuration
  2. Configuring high availability for Enterprise Vault with InfoScale Enterprise
    1. Reviewing the HA configuration
      1. Active-Passive configuration
        1.  
          Sample Active-Passive configuration
        2.  
          IP addresses for sample Active-Passive configuration
    2. Reviewing the disaster recovery configuration
      1.  
        Sample disaster recovery configuration
      2.  
        IP addresses for disaster recovery configuration
      3.  
        Supported disaster recovery configurations for service group dependencies
    3.  
      High availability (HA) configuration (New Server)
    4.  
      Following the HA workflow in the Solutions Configuration Center
    5. Disaster recovery configuration
      1.  
        DR configuration tasks: Primary site
      2.  
        DR configuration tasks: Secondary site
    6. Notes and recommendations for cluster and application configuration
      1.  
        IPv6 support
    7.  
      Configuring the storage hardware and network
    8. Configuring cluster disk groups and volumes for Enterprise Vault
      1.  
        About cluster disk groups and volumes
      2.  
        Prerequisites for configuring cluster disk groups and volumes
      3.  
        Considerations for a fast failover configuration
      4.  
        Considerations for disks and volumes for campus clusters
      5.  
        Considerations for volumes for a Volume Replicator configuration
      6.  
        Sample disk group and volume configuration
      7.  
        Viewing the available disk storage
      8.  
        Creating a cluster disk group
      9.  
        Creating Volumes
      10.  
        About managing disk groups and volumes
      11.  
        Importing a disk group and mounting a volume
      12.  
        Unmounting a volume and deporting a disk group
      13.  
        Adding drive letters to mount the volumes
      14.  
        Deporting the cluster disk group
    9.  
      Configuring the cluster
    10.  
      Adding a node to an existing VCS cluster
    11.  
      Verifying your primary site configuration
    12.  
      Guidelines for installing InfoScale Enterprise and configuring the cluster on the secondary site
    13.  
      Setting up your replication environment
    14.  
      Setting up security for Volume Replicator
    15.  
      Assigning user privileges (secure clusters only)
    16.  
      Configuring disaster recovery with the DR wizard
    17.  
      Cloning the storage on the secondary site using the DR wizard (Volume Replicator replication option)
    18.  
      Installing and configuring Enterprise Vault on the secondary site
    19.  
      Configuring Volume Replicator replication and global clustering
    20.  
      Configuring global clustering only
    21.  
      Setting service group dependencies for disaster recovery
    22.  
      Verifying the disaster recovery configuration
    23.  
      Adding multiple DR sites (optional)
    24.  
      Recovery procedures for service group dependencies
  3. Using the Solutions Configuration Center
    1.  
      About the Solutions Configuration Center
    2.  
      Starting the Solutions Configuration Center
    3.  
      Options in the Solutions Configuration Center
    4.  
      About launching wizards from the Solutions Configuration Center
    5.  
      Remote and local access to Solutions wizards
    6.  
      Solutions wizards and logs
    7.  
      Workflows in the Solutions Configuration Center
  4. Installing and configuring Enterprise Vault for failover
    1.  
      Installing Enterprise Vault
    2. Configuring the Enterprise Vault service group
      1.  
        Before you configure an EV service group
      2.  
        Creating an EV service group
      3.  
        Enabling fast failover for disk groups (optional)
    3.  
      Modifying the Enterprise Vault service group attribute
    4.  
      Configuring Enterprise Vault Server in a cluster environment
    5.  
      Setting service group dependencies for high availability
    6.  
      Verifying the Enterprise Vault cluster configuration
    7.  
      Setting up Enterprise Vault
    8.  
      Considerations when modifying an EV service group

Recovery procedures for service group dependencies

Service group dependencies have special requirements and limitations for disaster recovery configuration and for actions to be taken in a disaster recovery scenario.

See Supported disaster recovery configurations for service group dependencies.

The procedure and requirements for bringing service group dependencies online at the secondary site depends on their configuration: soft, firm, or hard.

In general, if a child or parent remains online at the primary site, you take it offline before you bring the child and parent service groups online in the correct order on the secondary site.

An exception is the RVG service group, used for Volume Replicator replication, which the wizard creates with an online, local, hard dependency. The RVG group remains online at the primary site in all cases and should be left online at the primary site.

The following tables show the recovery requirements if a child or parent service group fails at the primary site and is unable to fail over on the primary site, thus requiring the secondary site to be brought online.

Using a scenario of a parent and one child, the following table shows the expected results and necessary actions you must take for an online, local, soft dependency link.

Table: Online, local, soft dependency link

Failure condition

Result

Action required (sequentially)

The child service group fails

  • The parent remains online on the primary site.

  • An alert notification at the secondary site occurs for the child service group only.

  • The RVG group remains online.

  • Primary site: Manually take the parent service group offline at the primary site. Leave the RVG group online.

  • Secondary site: Bring the parent and child service groups online in the appropriate order (child first, then parent).

The parent service group fails

  • The child remains online on the primary site.

  • An alert notification at the secondary site occurs for the parent only.

  • The RVG group remains online.

  • Primary site: Manually take the child service group offline at the primary site. Leave the RVG group online.

  • Secondary site: Bring the service groups online in the appropriate order (child first, then parent).

Using a scenario of a parent and one child, the following table shows the expected results and necessary actions you must take for an online, local, firm dependency link.

Table: Online, local, firm dependency link

Failure condition

Result

Action required (sequentially)

The child service group fails

  • The parent goes offline on the primary site.

  • An alert notification at the secondary site occurs for the child service group only.

  • The RVG group remains online.

Secondary site: Bring the service groups online in the appropriate order (child first, then parent).

Leave the RVG group online at the primary site.

The parent service group fails

  • The child remains online on the primary site.

  • An alert notification at the secondary site occurs for the parent only.

  • The RVG group remains online.

  • Primary site: Manually take the child service group offline at the primary site. Leave the RVG group online.

  • Secondary site: Bring the service groups online in the appropriate order (child first, then parent).

Using a scenario of a parent and one child, the following table shows the expected results and necessary actions you must take for an online, local, hard dependency link.

Table: Online, local, hard dependency link

Failure condition

Result

Action required (sequentially)

The child service group fails

  • The parent goes offline on the primary site.

  • An alert notification at the secondary site occurs for the child service group only.

  • The RVG group remains online.

Secondary site: Bring the service groups online in the appropriate order (child first, then parent).

Do not take the RVG group offline at the primary site.

The parent service group fails

  • The child remains online on the primary site.

  • An alert notification at the secondary site occurs for the parent only.

  • The RVG group remains online.

  • Primary site: Manually take the child service group offline at the primary site. Leave the RVG group online.

  • Secondary site: Bring the service groups online in the appropriate order (child first, then parent).