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)
RVGPrimary agent-specific functions, state definitions, and attributes
This section provides information about RVGPrimary agent and state definitions.
The following table provides the RVGPrimary agent-specific information with agent and state definitions.
Table: RVG Primary agent-specific information
Description | Agent Functions(Entry Points) | State Definitions |
|---|---|---|
Enables taking over of the Primary role by the Secondary if the Primary becomes unavailable. Enables the migration of the Primary role to the Secondary. |
|
|
Review the following information to become familiar with the agent attributes required for an RVGPrimary resource type. This information assists you during the agent configuration.
The following table describes the agent attributes for the RVGPrimary resource.
Table: Agent attributes for RVGPrimary resource type
Attribute | Type and Dimension | Definition |
|---|---|---|
RvgResourceName | string-scalar | The name of the VvrRvg resource in the replication group on which the application group depends. |
AutoTakeover | int | If set to 1, the agent automatically enables the Secondary to take over the Primary role when it detects that the Primary has become unavailable. If set to 0, no automatic takeover is performed. In that case you must manually perform the takeover operation on the Secondary |
AutoResync | int | If set to 1, the agent automatically performs a resynchronization operation to synchronize the failed Primary with the new Primary when it becomes available after a takeover operation with fast-failback. If set to 0, manually resynchronize the original Primary with the new Primary, after it becomes available again. |
BunkerSyncTimeout | int | If set to Null (no value), the RVGPrimary agent considers this as infinite time-out value. It replays all the writes on the Bunker Replicator Log to the Secondary and only after all the writes are sent the takeover is performed on the Secondary. If set to 0 indicating a zero RTO, the RVGPrimary agent immediately performs a take over on the Secondary and no pending writes from the Bunker are sent to the Secondary. If the value is set to a specific integer, <T> seconds, then the RVGPrimary agent makes sure that writes for <T> seconds are sent to the Secondary before performing a takeover on the Secondary. Thus, the RTO in this case is equal to <T> seconds. |
The following table describes the factors affecting the RVGPrimary resource on the Primary and Secondary nodes.
Table: Factors affecting the RVGPrimary resource on Primary and Secondary nodes
Node on which RVGPrimary is online | Factors affecting the RVGPrimary resource actions | Action that the RVGPrimary agent performs during online operation |
|---|---|---|
Primary | None | The resource is online. |
Secondary | The Secondary is connected and is up-to-date. | The resource performs a migrate operation and the RVGPrimary resource becomes online. If there are multiple Secondaries in the RDS, and RLINKs between the Secondaries have been created, then, the RVGPrimary agent adds these Secondaries back into the RDS and synchronizes them with the new Primary. This happens in the background once the resource has come online. |
Secondary | The Secondary is connected but is not up-to-date. | The resource waits until the online time-out period is reached, for the Secondary to become up-to-date. If the Secondary becomes up-to-date then the resource performs a migrate operation and the RVGPrimary resource is brought ONLINE, else it will fault. If there are multiple secondaries in the RDS, and RLINKs between the secondaries are created, then, the RVGPrimary agent adds these secondaries back into the RDS and synchronizes them with the new Primary. |
Secondary | The Secondary is not connected, and the following attributes are set: AutoTakeover=1 AutoResync=1 | If the original primary node has a bunker RVG associated with it, then the resource first synchronizes the secondary node from the Bunker before performing a takeover with fast-failback logging. When the original Primary becomes accessible, it is converted to a secondary and is automatically synchronized with the new Primary. If there are multiple secondaries in the RDS, and RLINKs between the secondaries are created, then, the RVGPrimary agent adds these secondaries back into the RDS and synchronizes them with the new Primary. |
Secondary | The Secondary is not connected, and the following attributes are set: AutoTakeover=1 AutoResync=0 | The resource performs a takeover with fast-failback, but without performing the automatic synchronization. In the case of a Bunker setup, the resource first synchronizes the secondary node from the Bunker node before performing a takeover with fast-failback logging. You need to manually resynchronize the original Primary when it becomes available again using:
The fbsync action is very useful as it enables you to perform synchronization from the VCS console itself without having to switch to the VEA console. If there are multiple secondaries in the RDS, and RLINKs between the secondaries are created, then, the RVGPrimary agent adds these secondaries back into the RDS and synchronizes them with the new Primary. |
Secondary | The Secondary is not connected and the Primary cluster state has been declared as disaster or replica. For more information, see Cluster Server Administrator's Guide. In this you have set the following attributes: AutoTakeover=1 AutoResync=0 | The resource performs a takeover without fast-failback. If there are multiple secondaries in the RDS, and RLINKs between the secondaries are created, then, the RVGPrimary agent adds these secondaries back into the RDS and synchronizes them with the new Primary |
Secondary | The Secondary is inconsistent. | The resource fails to come online. |
Acting Secondary | The resource fails to come online. |