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)
Creating schedules for synchronized snapshots
You can use the VSS Snapshot Scheduler wizard to add a snapshot schedule. The scheduling capability automates the process of refreshing snapshot sets simultaneously on the Primary and Secondary nodes. At the time that is scheduled for the snapshot, the snapshot volumes are automatically reattached, resynchronized, and then split again. Once configured and applied, a scheduler service VxSchedService.exe maintains the schedule.
If the Secondary host initially satisfies the required conditions but during execution of the synchronized snapshot operation some of the checks fail, then the command does not fail, but proceeds with creating the snapshots on the Primary host.
The wizard then logs an event with an appropriate error code, which can be viewed through the Event Viewer.
Note:
The VSS Snapshot Scheduler wizard does not prepare the snapshot mirror. Prepare the snapshot mirror on the Primary and Secondary hosts with the prepare command before running the VSS Snapshot Scheduler wizard.
To schedule a snapshot for a selected component
- From the VEA console URL bar, select the <host name> which is the system where the production volumes and snapshot mirrors are located, as the active host.
- In the tree view expand the system node, the Storage Agent node, and the VSS Writers node.
Select one of the following depending on the application for which you want to create the snapshot:
For Exchange, right-click Microsoft Exchange Writer and click VSS Exchange Snapshot.
For SQL, right-click Microsoft SQL Writer and click VSS SQL Snapshot.
- In the Welcome panel, review the information and click Next.
- On the Select Component panel, specify the snapshot set parameters as follows and then click Next.
Complete this panel as follows:
Select component for snapshot operation
Select the component for the snapshot set.
To create snapshots for Exchange, select the appropriate storage group.
To create snapshots for SQL, select the appropriate database.
Snapshot set
Enter a name for the snapshot set. The snapshot set metadata XML file is stored under this name, with the prefix "VM_".
The XML file is stored by default in the directory that is shown on the screen.
To change the XML file location, use a text editor to create a text file named redirect.txt. This text file should contain a single text line specifying the full path to the location of the XML file, for example, G:\BackupSets. Save the redirect.txt file in the default directory C:\Program Files\Veritas\Veritas Volume Manager\VSSXML.
Select snapshot type
Select the snapshot type.
Full Backup is typically used for backup to tape or other storage media. It does the following:
Creates a copy of the selected component
Only for Exchange, runs Eseutil to check for consistency before you truncate the logs
Truncates the transaction logs
Copy is typically used for Quick Recovery. It creates a copy of the storage group, but does not truncate the transaction logs.
For Exchange: optionally check Run Eseutil with the Copy option to check the snapshot for consistency.
For SQL: Either type can be used to restore a database. However, if you want to replay logs in SQL Server as part of restoring a database, a Full backup needs to have been created earlier. When replaying logs, you can replay from the time of the last Full backup. A Copy backup does not affect this sequence of log replay and therefore is often used as an "out of band" copy for purposes such as testing or data mining.
- In the Change Attributes panel, optionally change the attributes for the snapshot volumes and click Next.
Complete this panel as follows:
Snapshot Volume Label
Displays the read-only label for the snapshot volume.
Drive Letter
Optionally, click a drive letter and select a new choice from the drop-down menu.
The drive letters that are specified may not be available when the snapshot is taken. When this occurs, the snapshot operation is performed, but no drive letters are assigned.
Plex
Optionally, click a plex and select a new choice from the drop-down menu.
- On the Synchronized Snapshot panel, select the Secondary hosts for which you want to create synchronized snapshots. Either double-click on the host name or click the Add option to move the host into the Selected Secondary Hosts pane. To select all the available hosts, click the Add All option. The VSS wizard creates synchronized snapshots on all the selected Secondary hosts.
This panel is displayed only in an environment using Volume Replicator. Otherwise, you are directly taken to the Schedule Information panel.
- In the Schedule Information panel, on the General Options tab, you need to the following.
Complete the information as:
Name of this schedule
Enter a unique name for the snapshot set schedule. This name identifies the snapshot schedule if you later want to view information about the snapshot status. A default name consists of the VSS writer name, the component name, and a numbered suffix that increments with each schedule.
Description of this schedule
Optionally, enter a description to help you identify the schedule when you view information about the snapshot status.
Start Time
The time of the day to begin taking snapshots
End Time
The time of day to end taking snapshots.
If a snapshot is in progress it is completed but a new one is not started after the end time.
Schedule takes effect on
The date on which the specified schedule takes effect. The default is the current date.
Restart task every
The interval between snapshots, in minutes.
For example, if the interval is 360 minutes and you schedule a snapshot start time of 12:00 P.M. and an end time of 7:00 P.M., the snapshot occurs twice. If no interval is specified the snapshot occurs once.
Every
Enable the Every option to have the snapshot schedule continue to occur. Otherwise the schedule applies only for one day.
Specify the number of days before restarting the snapshot schedule.
For example, 1 day would mean that the schedule takes effect daily, 2 days would mean every other day.
Start On
If you enable the Every option, specify the starting date.
Pre Command
Optionally, specify the full path of a command script to run before the scheduled snapshot occurs.
Post Command
Optionally, specify the full path of a command script to run after the snapshot is complete.
- To specify additional schedule days or dates, make selections on the following tabs:
Days of Week
Select one or more days on one or more weeks of the month.
You can click a button at the top of the column to select the entire column or a button to the left of a row to select the entire row. For example, clicking First schedules the snapshots to occur on the first occurrence of all the week days for the month.
Days of Month
Select one or more days of the month. You can also check the Last Day check box to schedule the snapshot for the last day of each month.
Specific Dates
Select one or more specific dates to include in or to exclude from the schedule.
Excluding a date takes precedence over days scheduled on the other tabs. For example, if you schedule every Monday on the Days of Week tab, and you exclude Monday October 9 on the Specific Dates tab, the snapshots are not taken on October 9.
If two schedules overlap for the same snapshot set, only one snapshot is taken. For example, if you select every Thursday plus the last day of the month, and the last day of the month occurs on Thursday, then only one snapshot is taken on Thursday.
- Click Next.
- Review the snapshot set and schedule details and click Finish.