Storage Foundation and High Availability Solutions 7.4 HA and DR Solutions Guide for Enterprise Vault - Windows

Last Published:
Product(s): InfoScale & Storage Foundation (7.4)
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.  
      Establishing secure communication within the global cluster (optional)
    24.  
      Adding multiple DR sites (optional)
    25.  
      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.  
      Configuring Enterprise Vault Server in a cluster environment
    4.  
      Setting service group dependencies for high availability
    5.  
      Verifying the Enterprise Vault cluster configuration
    6.  
      Setting up Enterprise Vault
    7.  
      Considerations when modifying an EV service group
  5. Appendix A. Using Veritas AppProtect for vSphere
    1.  
      About Just In Time Availability
    2.  
      Prerequisites
    3.  
      Setting up a plan
    4.  
      Deleting a plan
    5.  
      Managing a plan
    6.  
      Viewing the history tab
    7.  
      Limitations of Just In Time Availability
    8.  
      Getting started with Just In Time Availability
    9.  
      Supported operating systems and configurations
    10.  
      Viewing the properties
    11.  
      Log files
    12.  
      Plan states
    13.  
      Troubleshooting Just In Time Availability

Establishing secure communication within the global cluster (optional)

A global cluster is created in non-secure mode by default. You may continue to allow the global cluster to run in non-secure mode or choose to establish secure communication between clusters.

The following prerequisites are required for establishing secure communication within a global cluster:

  • The clusters within the global cluster must be running in secure mode.

  • You must have Administrator privileges for the domain.

The following information is required for adding secure communication to a global cluster:

  • The active host name or IP address of each cluster in the global configuration.

  • The user name and password of the administrator for each cluster in the configuration.

  • If the local clusters do not point to the same root broker, the host name and port address of each root broker.

Adding secure communication involves the following tasks:

  • Taking the ClusterService-Proc (wac) resource in the ClusterService group offline on the clusters in the global environment.

  • Adding the -secure option to the StartProgram attribute on each node.

  • Establishing trust between root brokers if the local clusters do not point to the same root broker.

  • Bringing the ClusterService-Proc (wac) resource online on the clusters in the global cluster.

To take the ClusterService-Proc (wac) resource offline on all clusters

  1. From Cluster Monitor, log on to a cluster in the global cluster.
  2. In the Service Groups tab of the Cluster Explorer configuration tree, expand the ClusterService group and the Process agent.
  3. Right-click the ClusterService-Proc resource, click Offline, and click the appropriate system from the menu.
  4. Repeat all the previous steps for the additional clusters in the global cluster.

To add the -secure option to the StartProgram resource

  1. In the Service Groups tab of the Cluster Explorer configuration tree, right-click the ClusterService-Proc resource under the Process type in the ClusterService group.
  2. Click View > Properties view.
  3. Click the Edit icon to edit the StartProgram attribute.
  4. In the Edit Attribute dialog box, add -secure switch to the path of the executable Scalar Value.

    For example:

    "C:\Program Files\Veritas\Cluster Server\bin\wac.exe" -secure
  5. Repeat the previous step for each system in the cluster.
  6. Click OK to close the Edit Attribute dialog box.
  7. Click the Save and Close Configuration icon in the tool bar.
  8. Repeat all the previous steps for each cluster in the global cluster.

To establish trust between root brokers if there is more than one root broker

  • Establishing trust between root brokers is only required if the local clusters do not point to the same root broker.

    Log on to the root broker for each cluster and set up trust to the other root brokers in the global cluster.

    The complete syntax of the command is:

    vssat setuptrust --broker host:port --securitylevel [low|medium|high] 
[--hashfile fileName | --hash rootHashInHex]

    For example, to establish trust with a low security level in a global cluster comprised of Cluster1 pointing to RB1 and Cluster2 pointing to RB2 use the following commands:

    From RB1, type:

    vssat setuptrust --broker RB2:14141 --securitylevel low

    From RB2, type:

    vssat setuptrust --broker RB1:14141 --securitylevel low

To bring the ClusterService-Proc (wac) resource online on all clusters

  1. In the Service Groups tab of the Cluster Explorer configuration tree, expand the ClusterService group and the Process agent.
  2. Right-click the ClusterService-Proc resource, click Online, and click the appropriate system from the menu.
  3. Repeat all the previous steps for the additional clusters in the global cluster.