Veritas Access Administrator's Guide
- Section I. Introducing Veritas Access
- Section II. Configuring Veritas Access
- Adding users or roles
- Configuring the network
- Configuring authentication services
- Section III. Managing Veritas Access storage
- Configuring storage
- Configuring data integrity with I/O fencing
- Configuring ISCSI
- Veritas Access as an iSCSI target
- Configuring storage
- Section IV. Managing Veritas Access file access services
- Configuring the NFS server
- Setting up Kerberos authentication for NFS clients
- Using Veritas Access as a CIFS server
- About Active Directory (AD)
- 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 Veritas Access as an Object Store server
- Configuring the NFS server
- Section V. Monitoring and troubleshooting
- Section VI. Provisioning and managing Veritas Access file systems
- Creating and maintaining file systems
- Considerations for creating a file system
- Modifying a file system
- Managing a file system
- Creating and maintaining file systems
- Section VII. Configuring cloud storage
- Section VIII. Provisioning and managing Veritas Access shares
- Creating shares for applications
- Creating and maintaining NFS shares
- Creating and maintaining CIFS shares
- Using Veritas Access with OpenStack
- Integrating Veritas Access with Data Insight
- Section IX. Managing Veritas Access storage services
- Compressing files
- About compressing files
- Compression tasks
- Configuring SmartTier
- Configuring SmartIO
- Configuring episodic replication
- Episodic replication job failover and failback
- Configuring continuous replication
- How Veritas Access 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 destination cluster to drive the replication session. Veritas Access 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 destination cluster.
Disaster recovery
In cases where the source cluster fails unexpectedly, an unplanned failover procedure is available for moving replication to the destination cluster.
With failover and failback, you can use the Replication> continuous failover command to move control from the source cluster to the destination 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 destination 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.