Storage Foundation and High Availability Solutions 8.0.1 HA and DR Solutions Guide for Enterprise Vault - Windows
- Introducing SFW HA for EV
- About clustering solutions with InfoScale products
- About high availability
- How a high availability solution works
- How VCS monitors storage components
- Shared storage - if you use NetApp filers
- Shared storage - if you use SFW to manage cluster dynamic disk groups
- Shared storage - if you use Windows LDM to manage shared disks
- Non-shared storage - if you use SFW to manage dynamic disk groups
- Non-shared storage - if you use Windows LDM to manage local disks
- Non-shared storage - if you use VMware storage
- About replication
- About disaster recovery
- What you can do with a disaster recovery solution
- Typical disaster recovery configuration
- Configuring high availability for Enterprise Vault with InfoScale Enterprise
- Reviewing the HA configuration
- Reviewing the disaster recovery configuration
- High availability (HA) configuration (New Server)
- Following the HA workflow in the Solutions Configuration Center
- Disaster recovery configuration
- Notes and recommendations for cluster and application configuration
- Configuring the storage hardware and network
- Configuring cluster disk groups and volumes for Enterprise Vault
- About cluster disk groups and volumes
- Prerequisites for configuring cluster disk groups and volumes
- Considerations for a fast failover configuration
- Considerations for disks and volumes for campus clusters
- Considerations for volumes for a Volume Replicator configuration
- Sample disk group and volume configuration
- Viewing the available disk storage
- Creating a cluster disk group
- Creating Volumes
- About managing disk groups and volumes
- Importing a disk group and mounting a volume
- Unmounting a volume and deporting a disk group
- Adding drive letters to mount the volumes
- Deporting the cluster disk group
- Configuring the cluster
- Adding a node to an existing VCS cluster
- Verifying your primary site configuration
- Guidelines for installing InfoScale Enterprise and configuring the cluster on the secondary site
- Setting up your replication environment
- Setting up security for Volume Replicator
- Assigning user privileges (secure clusters only)
- Configuring disaster recovery with the DR wizard
- Cloning the storage on the secondary site using the DR wizard (Volume Replicator replication option)
- Installing and configuring Enterprise Vault on the secondary site
- Configuring Volume Replicator replication and global clustering
- Configuring global clustering only
- Setting service group dependencies for disaster recovery
- Verifying the disaster recovery configuration
- Adding multiple DR sites (optional)
- Recovery procedures for service group dependencies
- Using the Solutions Configuration Center
- About the Solutions Configuration Center
- Starting the Solutions Configuration Center
- Options in the Solutions Configuration Center
- About launching wizards from the Solutions Configuration Center
- Remote and local access to Solutions wizards
- Solutions wizards and logs
- Workflows in the Solutions Configuration Center
- Installing and configuring Enterprise Vault for failover
- Installing Enterprise Vault
- Configuring the Enterprise Vault service group
- Configuring Enterprise Vault Server in a cluster environment
- Setting service group dependencies for high availability
- Verifying the Enterprise Vault cluster configuration
- Setting up Enterprise Vault
- Considerations when modifying an EV service group
Verifying the disaster recovery configuration
After the DR wizard has completed, you can confirm the following to verify the DR configuration:
Confirm that the configuration of disk groups and volumes at the DR site have been created by the DR wizard storage cloning.
Confirm that the application VCS service group has been created in the DR cluster including the same service group name, same resources, and same dependency structure as the primary site's application VCS service group.
Confirm that the application service group is online at the primary site. The application service group should remain offline at the DR site.
Ensure Volume Replicator replication configuration. This includes ensuring that the RVGs have been created at primary and secondary with the correct volume inclusion, replication mode, Replicator Log configuration, and any specified advanced options.
Confirm that the replication state matches what was specified during configuration. If specified to start immediately, ensure that it is started. If specified to start later, ensure that it is stopped.
specified to start later, ensure that it is stopped. Ensure that the Volume Replicator RVG VCS service group is configured on the primary and secondary clusters, including the correct dependency to the application service group, the specified IP for replication, and the correct disk group and RVG objects within the RVG VCS service group.
See Setting service group dependencies for disaster recovery.
Confirm that the RVG service groups are online at the primary and secondary sites.
Confirm that the RVG Primary resources are online in the primary cluster's application service group. If they are offline, then bring them online in the primary site's cluster's application service group. Do not bring them online in the secondary site application service group.
Ensure that the application service groups are configured as global.
Check to ensure that the two clusters are communicating and that the status of communication between the two clusters has a state of Alive.
If you are using Volume Replicator for replication and configuring an additional DR site, verify the heartbeat and replication configuration between all sites.
If you are using Volume Replicator for replication and chose to start replication manually in the DR wizard, to avoid replicating large amounts of data over the network the first time, then you will need to start the process necessary to synchronize from checkpoint. This typically consists of
starting a Volume Replicator replication checkpoint
performing a block level backup
ending the Volume Replicator replication checkpoint
restoring the block level backup at the DR site
starting replication from the Volume Replicator replication checkpoint
To learn more about the process of starting replication from a checkpoint, refer to the Volume Replicator Administrator's Guide.
Do not attempt a wide area failover until data has been replicated and the state is consistent and up to date.