Veritas Access Appliance Administrator's Guide
- Section I. Introducing Access Appliance
- Section II. Configuring Access Appliance
- Managing users
- Configuring the network
- Configuring authentication services
- Section III. Managing Access Appliance storage
- Configuring storage
- Managing disks
- Configuring ISCSI
- 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
- Configuring an FTP server
- 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
- Using Access Appliance with OpenStack
- Integrating Access Appliance with Data Insight
- Section IX. Managing Access Appliance storage services
- Compressing files
- About compressing files
- Compression tasks
- 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
- Compressing files
- Section X. Reference
Continuous replication failover and failback
Typically, the source cluster drives a replication session. However, in some situations, it may be useful for the target cluster to drive the replication session. Access Appliance supports a failover and a failback feature for continuous replication. This feature enables control of replication to be temporarily relocated from the source cluster to the destination (target) cluster.
Continuous replication failover and failback is useful for:
Planned failover
In cases where the source cluster is taken down for routine maintenance or for moving applications to another cluster, a planned failover procedure is available for moving replication from the source cluster to the target cluster.
Disaster recovery
In cases where the source cluster fails unexpectedly, an unplanned failover procedure is available for moving replication to the target cluster.
With failover and failback, you can use the replication continuous failover command to move control from the source cluster to the target cluster. You use the replication continuous failback to restore control to the source cluster.
Continuous replication failover does not automatically move the NFS or the CIFS share information that is associated with file system from the source cluster to the target cluster. Share information has to be done manually.
CIFS shares should be removed before failover and failback operations. After failover and failback operation are complete, add the CIFS shares again.