Veritas Access Appliance 8.3 Solutions Guide for Enterprise Vault
- Introduction
- System Requirements
- Installing and configuring Enterprise Vault with Access Appliance
- Access Appliance features for Enterprise Vault archival storage
- Access Appliance archival policy configuration for Enterprise Vault
- Configuring CIFS for the Active Directory domain mode
- Access Appliance GUI policies for archival storage
- Configuring the replication job
- Activating the archival policy using GUI
- Configuration of CIFS shares for archival using Veritas Access CLISH
- Storage provisioning using policies
- Configuring Access Appliance storage with Enterprise Vault store partition
- Continuous replication failover and failback
- Configuring replication failover and exporting CIFS share from target cluster
- Troubleshooting
- Index
Overview of the planned failover process
Consider two Access Appliance clusters, cluster A and cluster B. Here, cluster A is the original source cluster that replicates data to cluster B which is the original destination cluster. If the source cluster A is taken down for routine maintenance or for moving applications to cluster B, you can use a planned failover operation so that the replication direction switches from cluster B (new source) to cluster A (new destination). You should perform the planned failover before cluster A is taken down.
For planned failover, run the following command on the source cluster (cluster A):
Replication> continuous failover fs_name
Where fs_name is the name of the file system which is configured under continuous replication.
Once a planned failover happens, the roles of primary and secondary are switched. It will online the file system at new primary site and offline the file system at new secondary site. Now, cluster B is the primary site and cluster A is the secondary site. The file systems come online at the new primary site (cluster B) and the file systems at new secondary site (cluster A) are offline.
Note:
Planned failover command should be run when both the source and the destination clusters are reachable from each other. It should be run from the source cluster and replication should be in progress.
While doing a planned replication continuous job failover from source to target, ensure that no NFS/CIFS shares are configured with the source file system.