Managing an episodic replication job
You can manage an episodic replication job using the replication episodic job commands. The commands are required only on the source system.
The replication episodic job enable, replication episodic job sync, replication episodic job disable, replication episodic job abort, replication episodic job pause, and replication episodic job resume commands change the status of an existing episodic replication job.
You can use the replication episodic job modify, and replication episodic job destroy commands to modify or destroy an episodic replication job definition.
The replication episodic job enable command starts episodic replication immediately and initiates episodic replication after every subsequent set frequency interval. When an episodic replication job is created it is disabled by default, and you must enable the job to start episodic replication.
To enable an episodic replication job
- To enable an episodic replication job, type the following command:
Replication> episodic job enable job_name
job_name
Specify the name of the episodic replication job you want to enable.
At each frequency interval, a fresh file system Storage Checkpoint is taken and episodic replication is started against the new Storage Checkpoint. If a previous episodic replication run has not completed, a new Storage Checkpoint is not taken and the current run is skipped.
Note:
Running the replication episodic job enable command on a previously aborted episodic replication job automatically restarts the job.
The Replication episodic job sync command lets you start an episodic replication job, but then stops the episodic replication job after one iteration (full or incremental) is complete. You can use this command to recover from the secondary site in the event that the primary file system is completely destroyed. This command can also be used if you want to run an episodic replication job at a predefined time using a script or a cron job.
See Synchronizing an episodic replication job .
The Replication> episodic job disable command drops the episodic replication job from the schedule and waits for any already running iterations to complete. The Replication> episodic job disable command disables a job definition which is in one of these states: ENABLED, PAUSED, or FAILED. This process can take some time if the network is slow or if a large amount of data has changed since the last episodic replication run.
To disable an episodic replication job
- To disable an episodic replication job, type the following command:
Replication> episodic job disable job_name
job_name
Specify the name of the episodic replication job you want to stop.
Note:
If episodic replication has been configured on a WORM-enabled file system, the replication episodic job disable command is restricted unless all the user data on the file system is deleted.
The replication episodic job abort command forcefully cancels an episodic replication job even if it is in progress. Aborting an episodic replication job may leave Storage Checkpoints mounted on the source system and the target file system may be left in an intermediate state.
To abort an episodic replication job
- To abort an episodic replication job, type the following command:
Replication> episodic job abort job_name
job_name
Specify the name of the episodic replication job you want to abort.
Note:
If episodic replication has been configured on a WORM-enabled file system, the replication episodic job abort command is restricted unless all the user data on the file system is deleted.
The Replication> episodic job pause command immediately stops the episodic replication job. You must use the Replication> episodic job resume command to resume the episodic replication job from where it was paused. When episodic replication is resumed, the episodic replication job replicates the set of selected files before pausing the job, and attempts to replicate as much of the latest data as possible. This action allows the customer to have two recovery point objectives (RPO). When the episodic replication job is paused, the episodic replication frequency option is disabled. Once the episodic replication job is resumed, the frequency option resumes for subsequent iterations. The pause and the resume functions let you manage the episodic replication job based on workload requirements.
To pause and resume an episodic replication job
- To pause an episodic replication job, type the following command:
Replication> episodic job pause job_name
Where job_name is the name of the episodic replication job you want to pause.
- To resume an episodic replication job, type the following command:
Replication> episodic job resume job_name
Where job_name is the name of the episodic replication job you want to resume.
Note:
You cannot start or sync a paused job. You can abort a paused job. However, if synchronization is performed on a paused job that has been aborted, the last RPO for the paused job is not available.
The replication episodic job modify command lets you modify debugging or setting tunables on an episodic replication job definition.
The addition or removal of a file system from the source episodic replication unit or the destination episodic replication unit is not supported. To remove a specific file system from the episodic replication unit you must destroy the episodic replication job and recreate the episodic replication job with the new set of file systems in the episodic replication unit. To add a specific file system from an existing episodic replication unit, you can either create a new episodic replication job with a new source episodic replication unit and target episodic replication unit, or destroy the episodic replication job and recreate it with the new set of file systems in the episodic replication unit to use the same job name.
The replication episodic job modify debug command lets you enable or disable debugging on a given job.
To modify debugging on an episodic replication job
- To modify debugging on an episodic replication job definition, enter the following command:
Replication> episodic job modify debug job_name on|off
job_name
Specify the episodic replication job name you want to modify.
The replication episodic job modify tunables command lets you modify the job configuration to use multiple network connections (sockets) for replicating data from source to target. In configurations where WAN latency is high, it is recommended to use multiple connections for significantly increased throughput. After the tunables are set for a job, only one job is supported.
To modify tunables on an episodic replication job
- To modify tunables on an episodic replication job definition, enter the following command:
Replication> episodic job modify tunables job_name netconn rw_count
job_name
Specify the episodic replication job name you want to modify.
netconn
Specify the number of connections.
rw_count
Specify the number of threads.
The increased number of connections is effective in case of a relatively small number of large files. For large number of small files, full sync performance may be slower with increased number of connections.
The replication episodic job destroy command destroys a job definition. This command completely removes the specified job from the configuration, cleans up any saved job-related statistics, and removes any Storage Checkpoints. The episodic replication job must be disabled before the job definition can be destroyed.
To destroy an episodic replication job definition
- To destroy a job definition, enter the following command:
Replication> episodic job destroy job_name
Where job_name is the name of the job definition you want to delete. Make sure that the job is not enabled.
Using the replication episodic job destroy command with the force option removes the local job irrespective of the job state, and all episodic replication units are disassociated from the job. Cluster configurations, which are part of the job, are not modified.
Note:
If episodic replication has been configured on a WORM-enabled file system, the replication episodic job destroy and replication episodic job destroy force commands are restricted unless all the user data on the file system is deleted.
Note:
When setting up episodic replication, Veritas does not advise you to make any modifications or deletions on the target side of the file system. In the event that some or all of the target data is modified or deleted, you must re-create the episodic replication job from the source cluster to resume episodic replication services.
To re-create an episodic replication job
- To re-create an episodic replication job, you must first delete the job definition. Enter the following command on the source cluster:
Replication> episodic job destroy job_name
Where job_name is the name of the job definition you want to delete. Make sure that the job is not enabled.
- Re-create the job definition:
Replication> episodic job create job_name src_repunit tgt_repunit link_name schedule_name [evpsn] [metadata_only]
You can reuse the source episodic replication unit, target episodic replication unit, link, and schedule names.