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)
Adding a new RVG resource to an existing replication Service group
This option is required when a disk group has multiple RVGs. Using this option you can add the resource for additional RVGs to an existing replication service group.
Note:
The systems that are selected for the replication service group must be a superset, and must have the same order, as those you had selected for the application service group.
To add a resource into an existing service group
- Verify that VCS is running. From the Java Console, logon to the Primary site.
- On a clustered node on the Primary site, launch the configuration wizard from Start > All Programs > Veritas > Veritas Cluster Server > Configuration Tools > Volume Replicator Agent Configuration Wizard or, on Windows 2012 operating systems, from the Apps menu in the Start screen.
- Read the information on the Welcome panel. Click Next.
- In the Wizard Options panel, click Add RVG resource to an existing replication service group. Select the replication service group to which you want to add an RVG resource, and click Next.
- In the Service Group Configuration panel, the appropriate replication service group name is selected.
The current system list is displayed. Select the nodes from the Available Cluster Systems list and click the appropriate arrow button to add them to the Systems in Priority Order list. Make sure that all the listed nodes on which the disk group can be imported must be selected. The nodes to be added to the service group system list are listed in priority order.
Use the up and down arrows to change the priority of the clustered nodes on which the service group needs to be brought online.
To enable the service group to automatically come online on one of the systems, select the Include selected systems in the service group's AutoStartList attribute check box. For information about the AutoStartList attribute, see the Cluster Server Administrator's Guide.
Click Next.
- Complete the Disk Group and Replicated Volume Group Configuration panel.
This can be done as follows:
Configure RVGPrimary resource for the selected RVG
Select this option, if you want to create an RVGPrimary resource for the selected RVG. This resource is required when you want to configure your setup to automatically enable takeover in case of a failure of the Primary cluster. The RVGPrimary resource is created in the application service group and replaces the VMDg resource.
Available Replicated Volume Groups
Select the RVG to which you want the new replication service group to be added. The Next option is enabled.
Click Next to display the IP Resource Options panel.
- When adding a new resource to an existing replication service group, the following options are enabled.
Complete the IP Resource panel as follows:
Create New IP resource
Select this option to create a new IP resource for the resource that you create.
Create a copy of an IP resource existing in another service group
Select this option to create a copy of an IP resource that already exists in another service group. When you select this option, the list of available IP resources are displayed in the Available IP Resources pane. Choose the required IP resource.
Link to an IP resource existing in the current service group
Select this option to use an IP resource that exists in the current service group.
This option cannot be used to choose an IP resource that lies outside the current service group.
Click Next to display the Network Configuration panel.
- Complete the Network Configuration panel as follows:
If you had chosen the Create New IP resource on the preceding panel, then complete the panel as follows:
Virtual IP address
Specify the virtual IP address in this field. Volume Replicator uses this address for replication.
Subnet Mask
Enter the subnet mask.
Adapter Display Name (Mac address)
Specify the correct adapter name (Mac address) of each system to which you want to assign the IP resource and the corresponding NIC resource, in the Adapter Display Name column.
If you had chosen the option to create a copy of an existing IP resource or to link to an existing IP resource, then the panel is filled up as described in the following table:
Virtual IP address
If the IP specified for replication has a resource that is created in the cluster, the wizard copies that IP and the corresponding NIC resource to the replication service group.
Subnet Mask
If the resource for the IP already exists then the wizard disables the Subnet Mask field and other inputs as these values are taken from the existing IP resource.
If no resource has been created for the specified IP then you can enter a subnet mask value and choose the proper adapter on each system.
Adapter Display Name (Mac address)
The appropriate adapter name (Mac address) is displayed for each system.
Verify that you have specified the correct IP and Subnet Mask information.
If you need to change this information later then you can do it by running the wizard in the modify mode.
Click Next.
- In the Service Group Summary panel you can modify the resource name for the new resource that you add. Click on the resource name in the left pane to modify the name. After you are done, click Next to proceed with creating the resources.
A warning informing you that the service group will be created is displayed. Click Yes to proceed.
- After the resource has been successfully created, the completion panel appears. Click Finish to complete the procedure and exit the wizard.
- Repeat the steps on one node of the Secondary cluster.