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 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
- 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 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
- Configuring Veritas Access with the NetBackup client
- Section XI. 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. The continuous replication is supported for cluster file system as well as scale out file system.
To set up a continuous replication, enter the following:
Replication> continuous enable fs_name pool_name link_name [delayed=yes/delayed=no]
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. |
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.
It requires the pool on the destination cluster to have sufficient storage to create a file system and Storage Replicated Log (SRL) volume. The pool name should be same at the source and the destination cluster. The SRL volume size is one-fourth of the file system size.
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 an SRL volume. For the target cluster, 11 GB storage should be present in the pool to create the file system and SRL volume.
Note:
Continuous replication is not supported for file system with ecoded layout and 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 not supported on file systems which are configured under continuous replication. The mode of replication (synchronous or asynchronous) cannot be changed after configuring the replication.