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 unplanned failback process
After an unplanned failover, when the source cluster comes up, you can use the following unplanned failback process to return control to the original source cluster:
Make sure that you are logged into the source cluster.
Note:
Before starting the failback process, verify that the episodic replication service is running on the master node. If the service is not running on the master node, stop the service using the Replication> episodic service stop command and start it again using the Replication> episodic service start command.
Use the Replication> episodic job failover force=yes/no job_name current_cluster_link command to configure the current source cluster as a valid target to the new source cluster. This command should be executed from the old source cluster.
Use the Replication> episodic job sync job_name command from the new source cluster to synchronize file system data with the newly added destination cluster.
Use the Replication> episodic job failback force=yes/no job_name current_cluster_link command to move control of the episodic replication job from the destination cluster back to 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.
Note:
An administrator can use the Replication> episodic job destroy force command to clean up local job configuration. Configuration of the other clusters, which are part of the job, will not be modified and any episodic replication units will be disassociated from job. The Replication> episodic job destroy force and Replication> episodic repunit destroy force commands should be used in the event of an unrecoverable configuration or episodic replication direction mismatch.