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
Defining what to replicate
You use the Replication> episodic job commands to set up a job definition. This defined job determines what to replicate and when, using the settings from the previous commands.
Make sure that you created a schedule for replicating files from the source to the destination cluster.
See Scheduling the episodic replication.
To set up the episodic replication job
- To create an episodic replication job, enter the following:
Replication> episodic job create job_name src_repunit tgt_repunit link_name schedule_name [evpsn] [metadata_only]
job_name
Specify a name for the episodic replication job you want to create.
src_repunit
Specify the source episodic replication unit. The episodic replication unit determines the exact item (such as a file system) that you want to replicate.
tgt_repunit
Specify target episodic replication units.
link_name
Specify the link name used when you ran the Replication> episodic config auth command between the local cluster and the remote cluster. Both the source cluster and the destination cluster need to be assigned a unique identifier (name). This identifier is used to identify the link that is established between the source and the destination clusters. You can use the link name instead of the virtual IP addresses of the source and the destination clusters when using the other episodic replication commands.
schedule_name
Specify the name of the episodic replication schedule you want to apply to the episodic replication job.
evpsn
Enable or disable Enterprise Vault partition secure notifications.
metadata_only
Enable or disable metadata-only episodic replication. This feature is not supported with consistency groups and tunables.
Note:
If you configure episodic replication on a WORM-enabled file system, the job configuration 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.
- To add an excluding unit to the job, enter the following command. This step is optional.
Replication> episodic job exclude job_name exclunit_name
- By default, the job is disabled. To enable the job, enter the following:
Replication> episodic job enable job_name
- To check if the job was enabled, enter the following:
Replication> episodic job show [job_name]