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)
Configuring the VxSAS Service
Volume Replicator provides you with a VxSAS Wizard that enables you to configure the VxSAS service across multiple hosts at the same time. Many of the Volume Replicator commands require the VxSAS service logon account to be the same across different hosts, for the commands to run successfully. This wizard enables you to configure the same user name and password for the VxSAS service on multiple hosts, with ease. This wizard can also configure the VxSAS service logon account for all the hosts in a Cluster Server (VCS) or Microsoft Cluster as a group. This means that if a single node in a cluster is selected then all the nodes that are part of that cluster gets selected automatically.
Certain considerations should be taken into account before configuration of VxSAS.
They are as follows:
For a VCS cluster setup, the hosts are displayed as a part of the VCS cluster setup on the Host Selection panel, if the local host on which you have invoked the VxSAS wizard belongs to the VCS cluster.
If the local host on which you have invoked the VxSAS wizard and the secure remote cluster, are part of the same domain.
For any other VCS cluster, if it is configured as a non-secure cluster, then that cluster does not show up in the Host Selection panel and the hosts under the cluster are shown as independent hosts.
If you have a Microsoft Cluster setup, then, the host display may not indicate that it is a part of a cluster if:
The host on which you invoke VxSAS is not a part of the same domain as the Microsoft Cluster nodes.
You have not logged on as domain administrator on the host from which the VxSAS service configuration wizard is invoked.
The host on which the VxSAS service configuration wizard is invoked is not part of the same subnet on which the cluster nodes are present.
Note:
If you have chosen Japanese as the language of installation, the VxSAS wizard does not launch automatically, after the first restart post-installation. In this case, you must launch the wizard manually.
To configure the VxSAS service
- Launch the VVR Security Service Configuration Wizard manually from Start > All Programs > Veritas > Veritas Storage Foundation > Configuration Wizards > VVR Security Service Configuration Wizard or, on Windows 2012 operating systems, from the Apps menu in the Start screen.
Optionally, run vxsascfg.exe from the command prompt.
- The Welcome panel appears.
This panel displays important information that is useful as you configure the VxSAS service. Read the information that is provided on the Welcome panel and click Next.
- The Account Information panel appears.
Complete this panel as follows:
Account name (domain\account)
Enter the administrative account name in the Account name field.
Password
Specify a password in the Password field.
If you have already configured the VxSAS service for one host that is intended to be a part of the RDS, then make sure that you specify the same user name and password when configuring the VxSAS service on the other hosts.
After providing the required information, click Next.
- Select the required domain to which the hosts that you want to configure belong, from the Domain Selection panel.
Selecting Domains
The Available Domains pane lists all the domains that are present in the Windows network neighborhood.
Select the required domain by moving the appropriate name from the Available Domains pane to the Selected Domains pane, either by double-clicking it or using the arrow button.
Adding a Domain
If the domain name that you require is not displayed, then add it by using the Add Domain button. This displays a dialog that lets you specify the domain name. Click Add to add the name to the Selected Domains list.
After specifying the domain click Next.
- Select the required hosts from the Host Selection panel.
Complete this panel as follows:
Selecting Hosts
The Available Hosts pane lists the hosts that are present in the specified domain.
Select the required host by moving the appropriate name from the Available Hosts list to the Selected Hosts list, either by double-clicking it or using the arrow button. Use the Shift key with the up or down arrow keys to select multiple hosts.
Adding a Host
If the host name you require is not displayed, then add it using Add Host option. In the Add Host dialog specify the required host name or IP in the Host Name field. Click Add to add the name to the Selected Hosts list.
After you select the host name, click Configure to proceed with configuring the VxSAS service.
- After the configuration completes, the Configuration Results panel is displayed. If the operation is successful then the Status column displays the appropriate message to indicate that the operation was successful.
If the operation was not successful then the Status column displays the appropriate message along with the error message.
This panel displays the status as failed and the corresponding details on why the account update failed. It also displays the possible reasons for failure and recommendations on getting over the failure.
Click Back to change any information you had provided earlier.
When you configure the VxSAS service for Volume Replicator in a firewall setup, the VxSAS wizard may not be able to configure the computers that are across the firewall, although the Host Selection dialog may list these nodes. In this case, configure the VxSAS service locally on the computers that are across the firewall.
Click Finish to exit the wizard.