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
Overview of the planned failback process
After a job failover has been accomplished and the source cluster is ready to take back control of the episodic replication task, you can use the job failback feature to release control from the destination cluster and return it to the source cluster
From the destination cluster:
Stop all applications that access the replicated files. This step is recommended, but not required.
Use the Replication> episodic job sync job_name command to execute the job and make sure files on the source cluster and destination cluster are synchronized.
Use the Replication> episodic job disable job_name command to disable the job.
From the source cluster:
Use the Replication> episodic job failback force=yes/no job_name current_cluster_link command to move control of the job from the destination cluster back to the original source cluster.
Use the Replication> episodic job enable job_name command to enable the job or run a sync on the source cluster.
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.