Veritas Access Appliance 8.2 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
- Episodic replication job failover and failback
- Continuous replication failover and failback
- Configuring replication failover and exporting CIFS share from target cluster
- Troubleshooting
- Index
Overview of the planned failback process
After a planned failover has been accomplished and the original source cluster (cluster A) is ready to take back control of the replication task, you can use the failback feature to release control from the original destination cluster (cluster B) and return it to the original source cluster (cluster A).
For planned failback, run the following command:
Replication> continuous failback fs_name
Where fs_name is the name of the file system which is configured under continuous replication.
Once a planned failback happens, the roles of primary and secondary are switched back to the original state (the pre-failover state). Now, cluster A is the primary site again and cluster B is the secondary site again.
Note:
Planned failback command should be run when both the source and the destination clusters are reachable from each other. It should be run from the destination cluster (which was the original source cluster) and replication should be in progress.
While doing a planned replication continuous job failback from source to target, ensure that no NFS/CIFS shares are configured with the source file system.