Volume Replicator 7.4.1 Administrator's Guide - Windows
- Understanding Volume Replicator
- About Volume Replicator
- Basic Volume Replicator terms
- Building blocks of Volume Replicator
- Understanding replication in the Volume Replicator environment
- Modes of replication
- Understanding data flow in Volume Replicator asynchronous mode
- Understanding data flow in an RDS that contains multiple Secondary hosts
- Managing data during failure and recovery
- Replication concepts
- About using Volume Replicator as a disaster recovery tool
- Understanding how Volume Replicator logs writes to the Replicator Log
- Understanding replication settings for a Secondary
- Measures to protect log overflow and replication latency
- Pausing the replication
- Understanding checkpoints
- Synchronizing the Secondary
- Understanding Volume Replicator support for FlashSnap
- About Synchronized Snapshots
- Understanding Bunker replication
- Understanding Volume Replicator Support for TCP Multi-Connection
- About Volume Replicator compression
- About Volume Replicator memory monitoring and control support
- About Volume Replicator Graphs
- Setting up replication
- About setting up replication
- Best practices for setting up replication
- Security considerations for Volume Replicator
- Setting up replication using the Setup Replicated Data Set wizard
- Creating a Replicated Data Set (RDS)
- Replication failover considerations with diverse network configurations
- Setting up the Bunker RVG for replication
- Using the VEA Console for Volume Replication Operations
- Monitoring replication
- About monitoring replication
- Interpreting the information in the Volume Replicator views
- Monitoring replication using the VEA console
- Checking replication performance using vxrlink stats
- Analyzing Volume Replicator performance
- Monitoring alerts to interpret error conditions
- Handling Volume Replicator events
- Administering Volume Replicator
- About administering Volume Replicator
- Modifying the configuration
- Adding volumes
- Adding a Secondary host
- Administering the RVG
- Administering replication
- Disabling the SwiftSync feature
- Starting replication through the VEA console
- Stopping replication using the VEA console
- Changing replication settings for an RDS
- Managing checkpoints
- Pausing replication using Volume Replicator
- Converting the Primary to a Secondary
- Migrating the Primary role within an RDS
- Creating snapshots for the data volumes
- Creating synchronized snapshots using the VSS Snapshot wizard
- About snapshot naming convention on the Secondary
- Creating synchronized snapshot sets
- Prerequisites for creating synchronized snapshot sets
- Creating schedules for synchronized snapshots
- Displaying the status of the scheduled synchronized snapshot
- Reattaching synchronized snapshots
- Deleting a synchronized snapshot schedule
- Recovering the RVG
- Restoring the Secondary
- Migrating VVR to support IPv6 or dual stack
- Administering Bunker replication
- Performing disaster recovery operation
- Deleting Volume Replicator objects
- Accessing data on Secondary host
- Performing automated system recovery (ASR)
- Alternative methods to synchronize the Secondary faster
- Obtaining statistical information through Volume Replicator Graphs
- Using the command line interface
- About using the command line interface
- Conventions for command line syntax
- Administering the RDS using the vxrds command
- Activating the Bunker RVG
- Creating and adding a Secondary RVG
- Adding an existing volume to the RDS
- Adding a Bunker node
- Changing the host name or IP
- Creating the Primary RVG
- Deactivating the Bunker RVG
- Deleting the Bunker node
- Deleting the Secondary
- Deleting the Primary
- Dissociating data volumes
- Resynchronizing a failed Primary with the new Primary
- Converting a Primary to a Secondary
- Migrating the Primary to a Secondary
- Pausing replication using the vxrds pauserep command
- Displaying the RDS
- Resizing the data volumes
- Growing the Replicator Log volume
- Resuming replication after pausing
- Resynchronizing the Secondary
- Setting replication attributes
- Starting replication using the vxrds startrep command
- Stopping replication using the vxrds stoprep command
- Taking over the Primary role using the vxrds takeover command
- Performing RLINK Operations using the vxrlink command
- Associating a Secondary
- Attaching a Secondary
- Displaying the list of Secondary checkpoints
- Deleting the Secondary checkpoint
- Detaching an RLINK
- Dissociating an RLINK
- Creating new RLINK
- Pausing the RLINK
- Recovering the RLINK
- Restoring the RLINK
- Resuming the RLINK
- Removing the RLINK
- Setting the RLINK attributes
- Displaying the network statistics for the RLINK
- Displaying the RLINK status
- Identifying the most up-to-date Secondary
- Verifying the RLINK
- Starting the Historic Bandwidth Data Collection using the CLI
- Stopping the Historic Bandwidth Data Collection using the CLI
- Administering the RVGs using the vxrvg command
- Adding DCM log
- Associating the Replicator Log volume to an RVG
- Associating data volume with the RVG
- Ending checkpoint
- Starting the checkpoint
- Deleting the RVG checkpoint
- Displaying RVG checkpoints
- Dissociating volumes from RVG
- Dismounting data volumes
- Creating new RVG
- Converting a Secondary RVG to Primary RVG
- Converting a Primary RVG to Secondary RVG
- Recovering the RVG
- Removing an RVG
- Resynchronizing the RVG
- Setting RVG attributes
- Creating snapshots for data volumes in an RVG
- Reattaching the snapshot volumes back to the data volumes in an RVG
- Enabling data access (Starting the RVG)
- Generating application statistics
- Disabling data access (stopping the RVG)
- Displaying information using the vxprint command
- Creating snapshots using the vxsnap command
- Displaying memory statistics using the vxmemstat command
- Administering replicated volumes using the vxvol command
- Displaying and changing replication ports using the vrport command
- Administering the RVG using the vxedit
- Administering the RVG using the vxassist command
- Tuning Volume Replicator
- Examples: Using the command line
- Sample setup using the command line
- Example 1: Setting up replication using the command line interface
- Creating the RLINK on the Primary system VVRPRI
- Creating the Primary RVG on the Primary system VVRPRI
- Creating the RLINK on the Secondary system VVRSEC
- Creating the Secondary RVG on Secondary system VVRSEC
- Attaching the RLINKs and starting replication on the Secondary
- Attaching the RLINKs and starting replication on the Primary
- Example 2: Setting up Bunker replication
- Example 3: Using Bunker node for disaster recovery
- Updating the Secondary from the Bunker
- Transferring the Primary role
- Restoring the original Primary in a Bunker setup
- Migrating the Primary role back to the original Primary
- Recovering the original Primary during Bunker replay
- Failing back to the original Primary
- Restoring the Bunker setup after failback to original Primary
- Example 4: Using synchronized snapshots to restore data
- Sample setup showing how to restore data using synchronized snapshots
- Configuration Details
- Preparing the Volumes
- Creating snapshot volumes
- Using the snapshots to recover the corrupted volumes
- Restoring the original Primary
- Migrating the Primary role back to the original Primary (failing back to the original Primary)
- Configuring Volume Replicator in a VCS environment
- About configuring Volume Replicator in a VCS environment
- Components of a VCS cluster
- Illustrating a highly available Volume Replicator setup
- How the agents work
- Configuring the agents
- Working with existing replication service groups
- Configuring Volume Replicator with Hyper-V
- Advanced settings in Volume Replicator
- Troubleshooting Volume Replicator
- About troubleshooting Volume Replicator
- Recommendations and checks
- Encrypted files on replicated volumes
- Selecting the mode of replication
- Volume Replicator issues when Norton AntiVirus scan is performed
- Monitor view does not display the RDS information
- Preventing the connect problems
- Configuration checks for RLINKS
- Network, process, and operating system checks
- Configuration checks for volume mappings
- Troubleshooting Volume Replicator performance
- Other information and checks
- Recovering from problems in a firewall or NAT setup
- Recovering from problems during replication
- Permission denied errors when performing Volume Replicator Operations
- Error when configuring the VxSAS Service
- VEA Service is not started
- Connecting to cluster having multiple IP addresses
- Error when disabling data access to the RVG, creating Secondary RVG, adding volumes
- Error when resizing volumes
- Replica link already exists
- Unable to perform delete RDS, add volume, delete volume
- Removing the Replicator Log volume mirror
- Pausing when writes are in progress
- Unable to see volume name for associating Replicator Log
- Unable to see the volume names for adding volumes to RDS
- Adding logs to dissociated volumes
- Using two commands in succession
- Renaming dynamic disk group while importing
- Problems when performing the snapshot operation
- Operation time-out errors
- Problems when configuring Volume Replicator in a VCS environment
- Problems when setting performance counters
- Ignore error when adding secondary using VEA
- Appendix A. Services and ports
- Appendix B. Using the vxrsync utility
- Appendix C. VR Advisor (VRAdvisor)
vxrclient
The vxrsync utility contains the vxrclient component.
This component of the vxrsync utility can be used to:
Synchronize the remote systems with the source on which the vxrclient is running
Verify the data on the volumes between the source and the target.
The command syntax varies depending on the options that it is used with. To perform full synchronization you must use the -full option. To verify the data between the source and the target systems, use the -verify option. Using the command without either of these options, which is the default, results in difference-based synchronization.
The vxrclient command, by default, does not lock all the volumes before synchronizing or verifying the volumes. If you choose to proceed with the default, a warning message is displayed.
Note:
Veritas recommends that you use the command with the -x option to make sure that the all volumes in the RDS are locked before performing any operation on them.
Syntax for the vxrclient command:
vxrclient [-noreport] [-reportinterval <secs>]
[-full|-swiftsync] [-blocksize|-bs <blksize_KB>]
[-blockgroupcount|-bc <numblocks>] [-x]will be
[-use <host>] -to <host> [[<host>]...] [-port
<serverportnumber>]
{-for | -g} <groupname> | -r <rvgname> | -vol
<volumename>[[,<volumename>] ...][-dg <diskgroupname>]Note:
You can use the swiftsync option to leverage the NTFS or ReFS file systems.
Syntax for verifying the vrclient command against remote or target host:
vxrclient -verify|-quick[verify] [-noreport]
[-reportinterval <secs>] [-blocksize|-bs <blksize_KB>]
[-blockgroupcount|-bc <numblocks>] [-x]
[-use <host>] -with <host> [[<host>]...] [-port
<serverportnumber>]
{-for | -g} <groupname> | -r <rvgname> | -vol
<volumename>[[,<volumename>] ...]
[-dg <diskgroupname>]The following table describes the vxrclient command usage with the basic options to perform the required operations:
Table: Command usage for vxrclient
Operation | Command | Description |
|---|---|---|
Full synchronization | vxrclient -full -use <host> -to <host> -r <rvgname> | This command enables you to perform full synchronization between the source and target volumes. The RVG name is used as input by the command. The -x parameter can be optionally specified if you want all the volumes in the RDS to be locked. |
vxrclient -full -use <host> -to <host> -vol <vol1>, <vol2> | This command enables you to perform a full synchronization between the source and target volumes. A comma-separated list of volumes is used as input to the command. | |
vxrclient -full -use <host> -to <host> -g <groupname> | This command enables you to perform a full synchronization between the source and target volumes. A configuration file is used as input to the command. | |
Difference-based synchronization | vxrclient -use <host> -to <host> -r <rvgname> | This command enables you to perform a difference-based synchronization between the source and target volumes. The RVG name is used as input to the command. |
vxrclient -use <host> -to <host> -vol <vol1>, <vol2> | This command enables you to perform a difference-based synchronization between the source and target volumes. A comma-separated list of volumes is used as input to the command. | |
vxrclient -use <host> -to <host> -g <groupname> | This command enables you to perform a difference-based synchronization between the source and target volumes. A configuration file is used as input to the command. | |
Swiftsync synchronization | vxrclient swiftsync -use <host> -to <host> -r <rvgname> | This command enables you to perform a swiftsync synchronization between the source and target volumes. The RVG name is used as input to the command. Note: If you use this option with an NTFS or ReFS file system, only the used blocks are synced between the source and target volumes. |
Data Verification | vxrclient -verify -use <host> -with <host> -r <rvgname> | This command enables you to perform data verification between the source and target volumes. The RVG name is used as input to the command. |
vxrclient -verify -use <host> -with <host> -vol <vol1>, <vol2> | This command enables you to perform data verification between the source and target volumes. A comma-separated list of volumes is used as input to the command. | |
vxrclient -verify <host> -with <host> -g <groupname> | This command enables you to perform data verification between the source and target volumes. A configuration file is used as input to the command. |
The following table lists the command options available with vxrclient.
Table: Command options for vxrclient
Option | Description |
|---|---|
-v|-version | Prints the version number of vxrclient command. |
-?|/?|-h|-help | Prints a brief summary of command line options. |
-longhelp | Prints a detailed summary of command line options and an explanation of the operation of vxrclient command. |
-noreport | Specifies that the performance and progress information does not require to be printed. |
-reportinterval <secs> | Updates the performance and progress information every <secs> seconds where you can specify the value for the report interval. The default value is 10 seconds. |
-full | Copies all the data, and not just differences from the source volume to the target volume. This option is useful to create the initial volume copies. The default is to transfer only data differences. |
-swiftsync | Acts like -full option, if the volume is not an NTFS or ReFS volume. For NTFS or ReFS volumes, only the blocks that are used by these volumes are transferred. This option is useful for creating the initial volume copies. |
-blocksize|-bs <KB> | Sets the size of the block of data to be examined, and then transfers it as a unit. The default is 8 KB. |
-blockgroupcount|-bc <numblocks> | Sets the number of blocks of size that is specified in -blocksize|-bs option, that are sent in one network message. The default is 200 blocks. |
-x | Specifies that all the volumes on the client system are locked. |
-use <hostname_or_ip> | If the client system has more than one network interface card (NICs), specifies which interface to use when connecting to the required server systems either by providing the host name or IP address of the local network connection to use. |
-to <host> [[<host]...] | Synchronizes one or more remote host systems from this client system. All the host names with the corresponding information must be found in the configuration file. |
-port | Specifies the port number on which the server listens for requests from the client. This parameter does not need to be specified if the configuration file is used as input. |
-verify | Verifies the client's volumes with one or more remote host systems and lists any differences that are found. |
-quick[verify] | Verifies the client's volumes with one or more remote host systems. Halt this operation upon detection of any difference. This option does not perform any synchronization. |
-with <host> [[<host>]...] | Specifies the host name or IP of the remote host system(s) with which this client system's volumes should be verified. |
-for|-g <groupname> | Identifies the group of volumes for this operation. The group name corresponds to an ASCII configuration file that describes all possible host systems and the relationship and paths of the volumes that should be synchronized or verified together as a unit. |
-dg <disk group name> | Identifies the SFW disk group name. The disk group name is used to uniquely identify the specified RVG or volumes. |
-r <rvgname> | Identifies the RVG whose volumes are used for the required operation. |
-vol <volumename> [[,volumename].....] | Identifies the volumes that are used for the required operation. If there is more than one volume, they are indicated by a comma-separated list. Note: A volume or a set of volumes that are synchronized using swiftsync option, when verified through vxrclient and vxrserver, would show differences. This is because the swiftsync option has synchronized only the NTFS or ReFS used blocks, it has ignored the rest of the blocks, even though they may be different between source and destination volumes. See vxrserver. |