Veritas Access Appliance Administrator's Guide
- Section I. Introducing Access Appliance
- Section II. Configuring Access Appliance
- Managing users
- Configuring the network
- Configuring authentication services
- Configuring user authentication using digital certificates or smart cards
- Section III. Managing Access Appliance storage
- Configuring storage
- Managing disks
- Access Appliance as an iSCSI target
- Configuring storage
- Section IV. Managing Access Appliance file access services
- Configuring the NFS server
- Setting up Kerberos authentication for NFS clients
- Using Access Appliance as a CIFS server
- 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
- Using Access Appliance as an Object Store server
- Configuring the NFS server
- Section V. Managing Access Appliance security
- Section VI. Monitoring and troubleshooting
- Configuring event notifications and audit logs
- About alert management
- Appliance log files
- Configuring event notifications and audit logs
- Section VII. Provisioning and managing Access Appliance file systems
- Creating and maintaining file systems
- Considerations for creating a file system
- About managing application I/O workloads using maximum IOPS settings
- Modifying a file system
- Managing a file system
- Creating and maintaining file systems
- Section VIII. Provisioning and managing Access Appliance shares
- Creating shares for applications
- Creating and maintaining NFS shares
- About the NFS shares
- Creating and maintaining CIFS shares
- About the CIFS shares
- About managing CIFS shares for Enterprise Vault
- Integrating Access Appliance with Data Insight
- Section IX. Managing Access Appliance storage services
- Configuring episodic replication
- Episodic replication job failover and failback
- Configuring continuous replication
- How Access Appliance continuous replication works
- Continuous replication failover and failback
- Using snapshots
- Using instant rollbacks
- Configuring episodic replication
- Section X. Reference
Unconfiguring continuous replication
You can unconfigure continuous replication.
To unconfigure continuous replication
- Stop the replication. Before you disable continuous replication, you have to stop replication using the following command.
Replication> continuous stop <fs_name>
fs_name
Specify the file system name.
Note:
This command should be run from the source cluster.
- Check the replication status.
Replication> continuous status <fs_name>
fs_name
Specify the file system name.
- Disable continuous replication. All the configuration which was done for replication configuration when you enabled continuous replication from the source and the destination cluster is destroyed.
Replication> continuous disable <fs_name> <link_name>
fs_name
Specify the file system name.
link_name
Specify the link name.
Note:
This command should be run from the source cluster.
The RVG continues to exist until the last file system in the RVG is disabled. Once the last file system in the RVG is disabled, the RVG is deleted.
If a file system is WORM-enabled and contains data, the replication continuous disable <fs_name> <link_name> command fails because the default value of the destroy_target_fs parameter is yes. To disable replication, set destroy_target_fs=no.
You have an option to preserve the file system and also re-use the file system that was created.
For more details, See Preserving the file system on the destination cluster.
- Delete the authentication links.
Replication> continuous config deauth <link_name>
link_name
Specify the link name.
Note:
The Replication> continuous config deauth command should be run from the source cluster. The command deletes the link from the destination to the source cluster.
- Delete the keys from the source and the destination clusters.
Replication> continuous config del_keys <remote_console_ip>
remote_console_ip
Specify the remote console IP address.
- Stop the continuous service from the source and the destination clusters.
Replication> continuous service stop
- Unbind the replication IP from the source and the destination clusters.
Replication> continuous config unbind <replication_ip>
replication_ip
Specify the replication IP address.