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
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.
Use the Replication> 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> job sync job_name command from the new source cluster to synchronize file system data with the newly added destination cluster.
Use the Replication> job failback force=yes/no job_name current_cluster_link command to move control of the replication job from the destination cluster back to the source cluster.
Use the Replication> job sync job_name command to ensure that the replication job is in a well-defined state and incremental replication can be resumed.
Note:
An administrator can use the Replication> 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 replication units will be disassociated from job. The Replication> job destroy force and Replication> repunit destroy force commands should be used in the event of an unrecoverable configuration or replication direction mismatch.