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 systems to replicate
You need to set up the file systems you want to replicate using the Replication> episodic repunit commands. The Replication> episodic 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 an episodic replication unit are replicated together from the source cluster to the destination cluster.
Note:
The maximum number of episodic replication units supported in Access Appliance episodic 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.
An episodic 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 episodic replication source has to be one of the entry types shown. It cannot be a snapshot or a Storage Checkpoint (ckpt).
Access Appliance episodic replication requires that the source and the destination episodic 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 episodic 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/dir1, fs1/dir1 ru2 fs2/f1, fs2/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 an episodic replication unit and such ordering information is used to determine the episodic replication entity pair mapping from the source episodic replication unit to the destination episodic replication unit.
Note:
Make sure that the paths in the destination episodic replication unit exist in the destination cluster.
Note:
The commands in this section apply only to the source episodic replication unit.
To create an episodic replication unit
- From the source cluster, to create an episodic replication unit, enter the following:
Replication> episodic repunit create repunit_name repunit_entry[,repunit_entry,...]
repunit_name
The name of the episodic replication unit you want to create.
repunit_entry
The file system file, file, folder, or directory.
Note:
Destination episodic replication units should be created only at the source cluster using the replication episodic repunit create command.
- To confirm the creation of the episodic replication unit, enter the following:
Replication> episodic repunit show verbose
You can use the replication episodic repunit add_entry, replication episodic repunit modify_entry, replication episodic repunit remove_entry, and replication episodic repunit destroy commands to manage your episodic replication units.
Note:
The above-mentioned commands are restricted for a job that is enabled with a replication unit containing a WORM-enabled file system with user-defined data.
Note:
The replication episodic repunit destroy operation is not allowed for the episodic replication units that are included in any job definitions.