Search <book_title>...

Veritas Access 7.3 Administrator's Guide

Last Published: 2019-04-04

Product(s): Access (7.3)

Platform: Linux

Section I. Introducing Veritas Access
1. Introducing Veritas Access
Section II. Configuring Veritas Access
Section III. Managing Veritas Access storage
Section IV. Managing Veritas Access file access services
Section V. Managing the Veritas Access Object Store server
1. Using Veritas Access as an Object Store server
Section VI. Monitoring and troubleshooting
1. Monitoring events and audit logs
Section VII. Provisioning and managing Veritas Access file systems
1. Creating and maintaining file systems
Section VIII. Configuring cloud storage
1. Configuring the cloud gateway
  1. About the cloud gateway
  2. Configuring the cloud gateway
2. Configuring cloud as a tier
Section IX. Provisioning and managing Veritas Access shares
Section X. Managing Veritas Access storage services
Section XI. Reference
1. Appendix A. Veritas Access documentation
  1. Using the Veritas Access product documentation
  2. About accessing the online man pages
2. Appendix B. Veritas Access tuning
  1. File system mount-time memory usage

Managing a replication job

You can manage a replication job using the Replication> job commands. The commands are required only on the source system.

The Replication> job enable, Replication> job sync, Replication> job disable, Replication> job abort, Replication> job pause, and Replication> job resume commands change the status of an existing replication job.

You can use the Replication> job modify, and Replication> job destroy commands to modify or destroy a replication job definition.

The Replication> job enable command starts replication immediately and initiates replication after every subsequent set frequency interval. When a replication job is created it is disabled by default, and you must enable the job to start replication.

To enable a replication job

To enable a replication job, type the following command:
```
Replication> job enable job_name
```
job_name
Specify the name of the replication job you want to enable.

At each frequency interval, a fresh file system Storage Checkpoint is taken and replication is started against the new Storage Checkpoint. If a previous replication run has not completed, a new Storage Checkpoint is not taken and the current run is skipped.

Note:

Running the Replication> job enable command on a previously aborted replication job automatically restarts the job.

The Replication> job sync command lets you start a replication job, but then stops the 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 a replication job at a predefined time using a script or a cron job.

See Synchronizing a replication job.

The Replication> job disable command drops the replication job from the schedule and waits for any already running iterations to complete. The Replication> 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 replication run.

To disable a replication job

To disable a replication job, type the following command:
```
Replication> job disable job_name
```
job_name
Specify the name of the replication job you want to stop.

The Replication> job abort command forcefully cancels a replication job even if it is in progress. Aborting a 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 a replication job

To abort a replication job, type the following command:
```
Replication> job abort job_name
```
job_name
Specify the name of the replication job you want to abort.

The Replication> job pause command immediately stops the replication job. You must use the Replication> job resume command to resume the replication job from where it was paused. When replication is resumed, the 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 replication job is paused, the replication frequency option is disabled. Once the replication job is resumed, the frequency option resumes for subsequent iterations. The pause and the resume functions let you manage the replication job based on workload requirements.

To pause and resume a replication job

To pause a replication job, type the following command:
```
Replication> job pause job_name
```
where job_name is the name of the replication job you want to pause.
To resume a replication job, type the following command:
```
Replication> job resume job_name
```
where job_name is the name of the 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> job modify command lets you modify debugging or setting tubnables on a replication job definition.

The addition or removal of a filesystem from the source replication unit or the destination replication unit is not supported. To remove a specific filesystem from the replication unit you must destroy the replication job and recreate the replication job with the new set of file systems in the replication unit. To add a specific filesystem from an existing replication unit, you can either create a new replication job with a new source replication unit and target replication unit, or destroy the replication job and recreate it with the new set of file systems in the replication unit to use the same job name

The Replication> job modify debug command lets you enable or disable debugging on a given job.

To modify debugging on a replication job

To modify debugging on a replication job definition, enter the following command:
```
Replication> job modify debug job_name on|off
```
job_name
Specify the replication job name you want to modify.

The Replication> job modify tunables command allows you to 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 a replication job

To modify tunables on a replication job definition, enter the following command:
```
Replication> job modify tunables job_name netconn rw_count
```
job_name
Specify the 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> 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 replication job must be disabled before the job definition can be destroyed.

To destroy a replication job definition

To destroy a job definition, enter the following command:
```
Replication> 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> job destroy command with the force option removes the local job irrespective of the job state, and all replication units are disassociated from the job. Cluster configurations, which are part of the job, are not modified.

Note:

When setting up 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 replication job from the source cluster to resume replication services

To re-create a replication job

To re-create a replication job, you must first delete the job definition. Enter the following command on the source cluster:
```
Replication> 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> job create job_name src_repunit tgt_repunit
link_name schedule_name
```
You can reuse the source replication unit, target replication unit, link, and schedule names.