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
Episodic replication job failover and failback
Typically, the source cluster drives a episodic replication session. However, in some situations, it may be useful for the destination cluster to drive the episodic replication session. Veritas Access supports a failover and a failback feature for episodic replication jobs. This feature enables control of episodic replication jobs to be temporarily relocated from the source cluster to the destination (target) cluster.
Job 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 episodic replication jobs 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 episodic replication jobs to the destination cluster.
Note:
In the event of a planned or unplanned failover from the source cluster to the destination cluster, there should be at least one successful sync attempt. The successful sync ensures that a consistent point in time image is present on the destination cluster that can be used for the failover.
With job failover and failback, you use the Replication> episodic job failover command to move control from the source cluster to the destination cluster. You use the Replication> episodic job failback to restore control to the source cluster. The link_name is the link of one of the destination clusters. The link_name argument can be empty when the source cluster is not available, in which case the job failover can be executed from one of the destination clusters.
Essentially, job failover takes job and episodic replication unit definitions from the episodic replication database on the source cluster and copies them to the episodic replication database on the destination cluster.
Warning:
Job failover assumes that all episodic replication job names and episodic replication unit names are unique across all Veritas Access clusters on your network. Before you use the episodic replication failover feature, make sure that these names are unique.
After a job failover or failback, you must manually start or enable the episodic replication job to start pre-configured schedules. Link throttle information should be reconfigured after the job failover or failback.
Job failover does not automatically move the NFS or the CIFS share information that is associated with job failover episodic replication units from the source cluster to the destination cluster. Share information has to be done manually.
Table: Job failover and failback commands
Command | Definition |
---|---|
episodic job failover | Transfer control of an episodic replication job from the source cluster to the destination cluster. |
episodic job failback | Return control of an episodic replication job from the destination cluster to the source cluster. |