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
Setting up the file system to replicate
You need to set up the file systems you want to replicate. The file system which you are going to replicate should be in online state.
To set up a continuous replication, enter the following:
Replication> continuous enable fs_name pool_name link_name delayed=yes/delayed=no rvg_name create_target_fs srl_size
fs_name | The name of the file system that you want to replicate from source to destination cluster. |
pool_name | The name of the pool. |
link_name | The link name which was created during authentication time. |
delayed=yes/delayed=no | The delayed parameter value is yes if you want to set up continuous asynchronous replication. By default, its value is no. |
rvg_name | RVG name at primary site. |
create_target_fs | The value is yes if you want to create file system on secondary cluster. Else, the value is set to no. |
srl_size | Specify the SRL size for the file system. |
The command configures the continuous replication between the source and the destination cluster. A file system is created with the same name and same size on the destination cluster. The file system is in offline state at the secondary site to maintain a consistent copy of data. You can enable continuous replication using the same RVG on multiple file systems.
It requires the pool on the destination cluster to have sufficient storage to create a file system, the Storage Replicator Log (SRL) volume and the DCM logs. The pool name must be same at the source and the destination cluster. If delayed mode is enabled, there can be a non-zero RPO. For asynchronous continuous replication, the SRL volume size is 20% of the file system size. For synchronous continuous replication, the SRL volume size is 5% of the file system size. By default, the number of DCM logs is 2 but for a mirrored file system, the number of DCM logs is equal to the number of mirrors.
For example, if the file system size on the source cluster is 8 GB, then at least 3 GB storage should be present in the pool at the source cluster to create the SRL volume and the DCM logs in case of asynchronous replication. For the destination cluster, 11 GB storage should be present in the pool to create the file system, the SRL volume, and the DCM logs.
Note:
If you configure continuous replication on a WORM-enabled file system, the replication continuous enable command fails if either the source or destination clusters are configured with Normal lockdown mode. It is recommended that the source and destination clusters should be configured with the same lockdown modes.
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.
Note:
Continuous replication is not supported for a file system with encrypted volume. When setting up replication, Veritas recommends that you do not make any modifications or deletions on the target side of the file system. File system grow and shrink operations are supported on file systems which are configured under continuous replication. The mode of replication (synchronous or asynchronous) cannot be changed after configuring the replication.