Veritas Access Appliance Administrator's Guide
- Section I. Introducing Access Appliance
- Section II. Configuring Access Appliance
- Managing users
- Configuring the network
- Configuring authentication services
- Configuring user authentication using digital certificates or smart cards
- Section III. Managing Access Appliance storage
- Configuring storage
- Managing disks
- Access Appliance as an iSCSI target
- Configuring storage
- Section IV. Managing Access Appliance file access services
- Configuring the NFS server
- Setting up Kerberos authentication for NFS clients
- Using Access Appliance as a CIFS server
- About configuring CIFS for Active Directory (AD) domain mode
- About setting trusted domains
- About managing home directories
- About CIFS clustering modes
- About migrating CIFS shares and home directories
- About managing local users and groups
- Using Access Appliance as an Object Store server
- Configuring the NFS server
- Section V. Managing Access Appliance security
- Section VI. Monitoring and troubleshooting
- Configuring event notifications and audit logs
- About alert management
- Appliance log files
- Configuring event notifications and audit logs
- Section VII. Provisioning and managing Access Appliance file systems
- Creating and maintaining file systems
- Considerations for creating a file system
- About managing application I/O workloads using maximum IOPS settings
- Modifying a file system
- Managing a file system
- Creating and maintaining file systems
- Section VIII. Provisioning and managing Access Appliance shares
- Creating shares for applications
- Creating and maintaining NFS shares
- About the NFS shares
- Creating and maintaining CIFS shares
- About the CIFS shares
- About managing CIFS shares for Enterprise Vault
- Integrating Access Appliance with Data Insight
- Section IX. Managing Access Appliance storage services
- Configuring episodic replication
- Episodic replication job failover and failback
- Configuring continuous replication
- How Access Appliance continuous replication works
- Continuous replication failover and failback
- Using snapshots
- Using instant rollbacks
- Configuring episodic replication
- Section X. Reference
Overview of the unplanned failback process
After an unplanned failover, when the source cluster (cluster A) comes up, you can use the following unplanned failback process to return control to the original source cluster (cluster A):
Make sure that you are logged into the source cluster.
Note:
Before starting the failback process, verify that the episodic replication service is running on the primary node. If the service is not running on the primary node, stop the service using the replication episodic service stop command and start it again using the Replication> episodic service start command.
Use the replication episodic job failover force=yes/no job_name current_cluster_link command to configure the current source cluster as a valid target to the new source cluster. This command should be run from the original source cluster (cluster A).
Use the replication episodic job sync job_name command from the new source cluster to synchronize file system data with the newly added destination cluster.
Use the replication episodic job failback force=yes/no job_name current_cluster_link command to move control of the episodic replication job from the destination cluster back to the source cluster. This command should be run from the original source cluster (cluster A).
Use the replication episodic job sync job_name command to ensure that the episodic replication job is in a well-defined state and incremental episodic replication can be resumed.
Once the unplanned failback is completed, cluster A becomes the source cluster again and cluster B becomes the destination cluster again.
Note:
An administrator can use the Replication> episodic job destroy force command to clean up local job configuration. Configuration of the other clusters, which are part of the job, are not modified and any episodic replication units are disassociated from job. The Replication> episodic job destroy force and Replication> episodic repunit destroy force commands should be used in the event of an unrecoverable configuration or episodic replication direction mismatch.