Veritas Access 7.3 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
- About Flexible Storage Sharing
- Configuring data integrity with I/O fencing
- Configuring ISCSI
- Configuring storage
- Section IV. Managing Veritas Access file access services
- Configuring your 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 Veritas Access to work with Oracle Direct NFS
- Configuring an FTP server
- Configuring your NFS server
- Section V. Managing the Veritas Access Object Store server
- Section VI. Monitoring and troubleshooting
- Section VII. 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 VIII. Configuring cloud storage
- Configuring the cloud gateway
- Configuring cloud as a tier
- About policies for scale-out file systems
- Section IX. 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
- Section X. Managing Veritas Access storage services
- Deduplicating data
- Compressing files
- About compressing files
- Compression tasks
- Configuring SmartTier
- Configuring SmartIO
- Configuring replication
- Replication job failover and failback
- Using snapshots
- Using instant rollbacks
- Configuring Veritas Access with the NetBackup client
- Section XI. Reference
Replication job 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 replication jobs. This feature enables control of 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 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 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> job failover command to move control from the source cluster to the destination cluster. You use the Replication> 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 replication unit definitions from the replication database on the source cluster and copies them to the replication database on the destination cluster.
Warning:
Job failover assumes that all replication job names and replication unit names are unique across all Veritas Access clusters on your network. Before you use the replication failover feature, make sure that these names are unique.
After a job failover or failback, you must manually start or enable the 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 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 |
---|---|
job failover | Transfer control of a replication job from the source cluster to the destination cluster. |
job failback | Return control of a replication job from the destination cluster to the source cluster. |