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 unplanned failback process
After an unplanned failover, when the original source cluster (cluster A) comes up, you can use the following unplanned failback process to retain the replication between source and destination cluster.
When the original source cluster (cluster A) comes up, it still acts as the primary cluster. At this time, both the source and the destination clusters show the same status.
For unplanned failback, run the following command from the original source cluster (cluster A):
Replication> continuous failback fs_name
Where fs_name is the name of the file system which is configured under continuous replication.
Once, an unplanned failback happens, the original source cluster (cluster A) becomes the new destination cluster. The file system is still online at new source cluster (cluster B).
Note:
Unplanned failback command should be run from the original source cluster. If you have NFS/CIFS shares on the original source cluster, it is recommended that you stop the NFS/CIFS server before unplanned failback.