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
Setting up the file systems to replicate
You need to set up the file systems you want to replicate using the Replication> repunit commands. The Replication> repunit commands let you define the type of data that you replicate from the source cluster to the destination cluster. All files and folders belonging to a replication unit are replicated together from the source cluster to the destination cluster.
Note:
The maximum number of replication units supported in Veritas Access Replication is 128.
Make sure that you already set up communication between your source and the destination clusters.
See Setting up communication between the source and the destination clusters.
A replication unit is defined as an ordered set of entries, where each entry is one of the following:
A single file system
A single subdirectory
A single file
Note:
The replication source has to be one of the entry types shown. It cannot be a snapshot or a Storage Checkpoint (ckpt).
Veritas Access Replication requires that the source and the destination replication units of a job definition have the same type of ordered entries, that is, every entry pair (one entry from the source and one entry from the destination replication unit) must be of a similar type.
Both can be files, or both can be directories, as shown in the following example:
Replication unit Name Replication unit Entries ===================== ======================== ru1 fs1,fs2/dir1,fs2/f1 ru2 fs4,fs6/dir2,fs5/f2
The entry is identified by the file system name, optionally followed by a slash '/', followed by the path of the directory or the file inside the file system. Member entries are ordered inside a replication unit and such ordering information is used to determine the replication entity pair mapping from the source replication unit to the destination replication unit.
Note:
Make sure that the paths in the destination replication unit exist in the destination cluster.
Note:
The commands in this section apply only to the source replication unit.
To create a replication unit
- From the source cluster, to create a replication unit, enter the following:
Replication> repunit create repunit_name repunit_entry[,repunit_entry,...]
repunit_name
The name of the replication unit you want to create.
repunit_entry
The file system file, file, folder, or directory.
Note:
Destination replication units should be created only at the source cluster using the Replication> repunit create command.
- To confirm the creation of the replication unit, enter the following:
Replication> repunit show verbose
You can use the Replication> repunit add_entry, Replication> repunit modify_entry, Replication> repunit remove_entry, and Replication> repunit destroy commands to manage your replication units.
Note:
The Replication> repunit modify_entry, Replication> repunit remove_entry, and Replication> repunit destroy operations are not allowed for the replication units that are included in any job definitions.