Veritas InfoScale™ 7.0 Replication Administrator's Guide - Linux
- Introducing Veritas Replicator Option
- Section I. Getting started with File Replicator
- Introducing File Replicator
- Administering File Replicator
- Displaying file replication job information
- About error recovery after a site disaster or network disruption using VFR
- Section II. Getting started with Volume Replicator
- Introducing Volume Replicator
- Understanding how Volume Replicator works
- Replication in a shared disk group environment
- Using SmartTier with VVR
- Understanding the VVR snapshot feature
- About VVR compression
- Planning and configuring replication
- Data flow in VVR
- Before you begin configuring
- Choosing the mode of volume replication
- Planning the network
- Sizing the SRL
- Understanding replication settings for a Secondary
- Configuring the agents for high availability
- Requirements for configuring VVR in a VCS environment
- Example setting up VVR in a VCS environment
- Configuring the agents for a bunker replication configuration
- About choosing the Primary site after a site disaster or network disruption
- Introducing Volume Replicator
- Section III. Analyzing your environment with Volume Replicator Advisor
- Introducing Volume Replicator Advisor (VRAdvisor)
- Collecting the sample of data
- About collecting the sample of data
- Collecting the sample of data on UNIX
- Collecting the sample of data on Windows
- Analyzing the sample of data
- About analyzing the sample of data
- Analyzing the collected data
- Understanding the results of the analysis
- Viewing the analysis results
- Recalculating the analysis results
- Installing Volume Replicator Advisor (VRAdvisor)
- Section IV. Setting up and administering VVR
- Setting up replication
- Creating a Replicated Data Set
- Creating a Primary RVG of an RDS
- Adding a Secondary to an RDS
- Changing the replication settings for a Secondary
- Synchronizing the Secondary and starting replication
- Starting replication when the data volumes are zero initialized
- Displaying configuration information
- Displaying RVG and RDS information
- Displaying information about data volumes and volume sets
- Displaying information about Secondaries
- Displaying statistics with the vrstat display commands
- Collecting consolidated statistics of the VVR components
- Displaying network performance data
- Administering Volume Replicator
- Administering data volumes
- Associating a volume to a Replicated Data Set
- Associating a volume set to an RDS
- Associating a Data Change Map to a data volume
- Resizing a data volume in a Replicated Data Set
- Administering the SRL
- Incrementally synchronizing the Secondary after SRL overflow
- Administering replication
- Administering the Replicated Data Set
- Administering Storage Checkpoints
- Creating RVG snapshots
- Using the instant snapshot feature
- About instant full snapshots
- Preparing the volumes prior to using the instant snapshot feature
- Creating instant full snapshots
- About instant space-optimized snapshots
- Creating instant space-optimized snapshots
- About instant plex-breakoff snapshots
- Administering snapshots
- Using the traditional snapshot feature
- Using Veritas Volume Manager FastResync
- Verifying the DR readiness of a VVR setup
- Backing up the Secondary
- Administering data volumes
- Using VVR for off-host processing
- Transferring the Primary role
- Migrating the Primary
- About taking over from an original Primary
- Failing back to the original Primary
- Choosing the Primary site after a site disaster or network disruption
- Troubleshooting the primary-elect feature
- Replication using a bunker site
- Introduction to replication using a bunker site
- Setting up replication using a bunker site
- Using a bunker for disaster recovery
- Replication using a bunker site in a VCS environment
- Troubleshooting VVR
- Recovery from configuration errors
- Errors during an RLINK attach
- Errors during modification of an RVG
- Recovery on the Primary or Secondary
- Recovering from Primary data volume error
- Primary SRL volume error cleanup and restart
- Primary SRL header error cleanup and recovery
- Secondary data volume error cleanup and recovery
- Tuning replication performance
- SRL layout
- Tuning Volume Replicator
- VVR buffer space
- Tuning VVR compression
- VVR buffer space
- Appendix A. VVR command reference
- Appendix B. Using the In-band Control Messaging utility vxibc and the IBC programming API
- Using the IBC messaging command-line utility
- Examples - Off-host processing
- In-band Control Messaging API
- Appendix C. Volume Replicator object states
- Appendix D. VVR task reference
- Appendix E. Alternate methods for synchronizing the Secondary
- Using the full synchronization feature
- Using block-level backup and Storage Checkpoint
- Using difference-based synchronization
- Examples for setting up a simple Volume Replicator configuration
- Appendix F. Migrating VVR from Internet Protocol version 4 to Internet Protocol version 6
- About migrating to IPv6 when VCS global clustering and VVR agents are not configured
- About migrating to IPv6 when VCS global clustering and VVR agents are configured
- About migrating to IPv6 when VCS global clustering and VVR agents are configured in the presence of a bunker
- Migrating to IPv6 when VCS global clustering and VVR agents are configured in the presence of a bunker
- Appendix G. Sample main.cf files
- Setting up replication
Managing a file replication job
You can manage a replication job from using the vfradmin job start, vfradmin job sync, vfradmin job stop, and vfradmin job abort commands. The commands are required only on the source system.
The vfradmin job start command starts replication immediately and initiates replication after every subsequent set frequency interval.
To start a replication job, type the following command:
# vfradmin job start job_name mntpt
where job_name is the name of the replication job you want to start and mntpt is the mount point on the source system.
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 vfradmin job start command on a previously aborted replication job will automatically restart the job.
The vfradmin 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 as a pre-defined time using a script or a cron job.
The vfradmin job stop command drops the replication job from the schedule and waits for any already running iterations to complete. This can take some time if the network is slow or if a large amount of data has changed since the last replication run. The -n option initiates the replication job stop without waiting for it to complete.
To stop a replication job, type the following command:
# vfradmin job stop [-n] job_name mntpt
where job_name is the name of the replication job you want to stop and mntpt is the mount point on the source system.
The vfradmin 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, type the following command:
# vfradmin job abort job_name mntpt
where job_name is the name of the replication job you want to abort and mntpt is the mount point on the source system.
The vfradmin job wait command will wait for the current iteration of a replication job to complete. This command can be used if a script requires the completion of the current replication cycle.