Veritas InfoScale™ 8.0.2 Replication Administrator's Guide - Linux
- Section I. Getting started with Volume Replicator
- Introducing Volume Replicator
- Understanding how Volume Replicator works
- How VVR uses kernel buffers for replication
- Replication in a shared disk group environment
- Using SmartTier with VVR
- Understanding the VVR snapshot feature
- About VVR compression
- Planning and configuring replication
- Before you begin configuring
- Choosing the mode of volume replication
- Planning the network
- Sizing the SRL
- Understanding replication settings for a Secondary
- Configuring VVR in a VCS environment
- Using the primary-elect feature to choose the primary site after a site disaster or network disruption
- Requirements for configuring VVR in a VCS environment
- Example setting up VVR in a VCS environment
- Configuring the agents for a bunker replication configuration
- Section II. 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
- VVR event notification
- 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 as a log plex
- 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
- Setting up replication
- Section III. Getting started with File Replicator
- Introducing File Replicator
- Administering File Replicator
- Displaying file replication job information
- Section IV. 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 V. VVR reference
- 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. 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 E. Migrating VVR from IPv4 to IPv6
- Migrating VVR to support IPv6 or dual stack
- 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 F. Sample main.cf files
Modifying a file replication job
Some configuration parameters including the source mount point, the target mount point, the host, and the job direction can not be changed if a replication job is currently scheduled. All other configuration changes including the source and the target IP address, replication frequency, the target port, and the debugging level can be changed when a replication job is scheduled. Unless otherwise specified, all replication job modification commands must be run on both the source and the target systems to maintain replication job configuration consistency, otherwise the replication job will fail with a job configuration mismatch error.
To update the frequency at which file system data is replicated, type the following command:
# vfradmin job set freq job_name mntpt freq
where job_name is the name of the replication job you want to modify, mntpt is the mount point of the source or the target system, and freq is the new frequency in minutes at which the replication job will run.
To update the source address of the replication job, type the following command:
# vfradmin job set srcaddr job_name mntpt src_addr
where job_name is the name of the replication job you want to modify, mntpt is the mount point of the source or the target file system, and src_addr is the new source address for the replication job.
To update the target address of the replication job, type the following command:
# vfradmin job set tgtaddr job_name mntpt tgt_addr
where job_name is the name of the replication job you want to modify, mntpt is the mount point of the source or the target file system, and tgt_addr is the new target address for the replication job.
To update the host name where the replication job can come online, type the following command:
# vfradmin job set host job_name mntpt host
where job_name is the name of the replication job you want to modify, mntpt is the mount point of the source or the target system, and host is the updated host name.
The host must be the same host name as returned by the uname -n command. You must update the host name to manually failover the replication job from one cluster system to another. This command is only required on the source system if a new system will become the source for the replication job. Similarly, this command is only required on the target system if a new system will become the target for the replication job.
To update the target port of the replication job, type the following command:
# vfradmin job set port -p tgt_port job_name mntpt
where tgt_port is the target port you want to use, job_name is the name of the replication job you want to modify, and mntpt is the mount point of the source or the target system.
If you run this command, the vxfsrepld daemon on the target system must be started with the updated port.
To update the replication job source mount point, type the following command:
# vfradmin job set srcmntpt [-t tgt_mntpt] job_name newsrc_mntpt
where job_name is the name of the replication job you want to modify and tgt_mntpt is the mount point of the target file system. To change the source mount point on target system, the target mount point must be specified using the -t tgt_mntpt option. The file system must be mounted on newsrc_mntpt on the source system for the command to succeed. On the source system, the replication job must not be associated with a consistency group.
To update the replication job target mount point, type the following command:
# vfradmin job set tgtmntpt [-s src_mntpt] job_name newtgt_mntpt
where job_name is the name of the replication job you want to modify and src_mntpt is the mount point of the source file system. To change the target mount point on source system, the source mount point must be specified using the -s src_mntpt option. The file system must be mounted on newtgt_mntpt on the target system for this command to succeed. On the target system, the replication job must not be associated with a consistency group.
To update the replication job direction on the source or the target, type the following command:
# vfradmin job set mode [-s|-t] job_name mntpt
where job_name is the name of the replication job you want to modify and mntpt is the mount point on the source or the target system. You must specify the -s option when updating the replication job mode on the old target system. This specifies that the current machine should now behave as the source system for the replication job. You must specify the -t option when updating the replication job mode on the old source system. This specifies that the current machine should behave as the target system for the replication job. This command swaps the source and the target mount points and IP addresses in the replication job configuration.
Changing the replication job mode can be used with other commands in disaster recovery scenarios.
Note:
For a given replication job, when a previous source machine becomes the target machine, statistics information is deleted from the source machine. New source will build the statistics information from the next replication iteration.
To set the debug level of the replication job, type the following command:
# vfradmin job set dbg -d [0|1] job_name mntpt
where job_name is the name of the replication job you want to modify and mntpt is the mount point on the source or the target system. By default, the debug level is set to 0. Setting the debug level to 1 adds diagnostic information in the job log file. The diagnostic information can provide useful information for debugging any errors. Setting the debug level to 0 will turn off logging of diagnostic information.
To turn the File Change Log (FCL) feature on or off for a replication job, type the following command:
# vfradmin job set fcl job_name mntpt [on|off]
When used with "on" option, the command modifies the replication job to use the FCL feature to detect changes in the file system. When used with "off" option the replication job will not use the FCL feature to detect changes in the file system.
To configure or tune the threads using the vfradmin for a replication job, type the following command:
/opt/VRTS/bin/vfradmin job set thread <nthreads> <job-name> <mount-point>
To update the number of sockets using the vfradmin for a replication job, type the following command:
/opt/VRTS/bin/vfradmin job set socket <nsockets> <job-name> <mount-point>
Note:
If a job is in the Failed state, you can change the number of threads connections and use it for next iteration.