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
Typical disaster recovery configuration
A disaster recovery (DR) configuration enables you to restore application data and services in the event of a catastrophic failure. A typical DR solution requires primary and secondary sites, and clusters within those sites. The cluster at the primary site provides data and services during normal operation, and the cluster at the secondary site provides data and services if the primary site fails.
The following figure illustrates a typical DR configuration.
The illustration displays an environment with a DR solution that is prepared for a disaster. In this case, the primary site consists of two nodes, System1 and System2. Similarly the secondary setup consists of two nodes, System3 and System4. Each site has a clustered setup with the nodes set up appropriately for failover within the site.
Data is replicated from the primary site to the secondary site. Replication between the storage is set up using a replication software. If the application on System1 fails, the application comes online on node System2 and begins servicing requests. From the user's perspective there might be a small delay as the backup node comes online, but the interruption in effective service is minimal.
When a failure occurs, such as an earthquake that destroys the data center in which the primary site resides, the DR solution is activated. System3 at the secondary site takes over, and the data that was replicated to the secondary site is used to restore the application services to clients.