InfoScale™ 9.0 Storage Foundation and High Availability Solutions 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
- Modifying the Enterprise Vault service group attribute
- 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
Non-shared storage - if you use SFW to manage dynamic disk groups
VCS introduces the Volume Manager Non-Shared Diskgroup (VMNSDg) agent to support local non-shared storage configurations that are managed using SFW. The VMNSDg agent works without SCSI reservations and is designed for locally attached storage devices that do not support SCSI.
The VMNSDg agent monitors and manages the import and deport of dynamic disk groups created on local storage. The only difference between the VMDg agent and the VMNSDg agent is that the VMDg agent is designed for shared cluster dynamic disk groups and uses SCSI reservations, whereas the VMNSDg agent supports only non-shared local dynamic disk groups and works without SCSI reservations.
The VMNSDg agent can be used to set up single-node Replicated Data Clusters (RDC) or Disaster Recovery (DR) configurations with replication set up between the sites.
During a failover, the VCS MountV and VMNSDg agents deport the locally attached storage from the affected node and then import the locally attached storage of the target node. Replication ensures that the data is consistent and the application is up and running successfully.
Note:
The VMNSDg agent does not support fast failover and Intelligent Monitoring Framework (IMF).