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
Preserving the file system on the destination cluster
When continuous replication is disabled, the target file system is deleted. When the same file system is enabled for replication again, a full sync happens. You have an option to preserve the file system and also re-use the file system that was created during the previous replication continuous enable operation using the destroy_target_fs=yes/no parameter.
If you disable the file system and set destroy_target_fs=no in the replication continuous disable, then the file system on the destination cluster will not be deleted. The default value of the destroy_target_fs parameter is yes and if you do not pass this parameter, the file system on the destination cluster is deleted.
replication> continuous disable fs_name link_name destroy_target_fs=yes/no
Later, if you want to re-use the file system created on the destination cluster, you can set create_target_fs=no in the replication continuous enable command.
replication> continuous enable fs_name link_name source delayed=yes rvg_test create_target_fs=yes srl_size
If there is a mismatch in any of the file system parameters, a failure message appears to inform the user that the file system on the destination cluster does not match with the source file system.