Volume Replicator 7.4.2 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
- 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
- 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 memory monitoring and control support
- About Volume Replicator Graphs
- Setting up replication
- Security considerations for Volume Replicator
- Setting up replication using the Setup Replicated Data Set wizard
- Setting up the Bunker RVG for replication
- Using the VEA Console for Volume Replication Operations
- Monitoring replication
- Interpreting the information in the Volume Replicator views
- Monitoring replication using the VEA console
- Checking replication performance using vxrlink stats
- Administering Volume Replicator
- Adding volumes
- Administering the RVG
- Administering replication
- Managing checkpoints
- Pausing replication using Volume Replicator
- Creating snapshots for the data volumes
- Creating synchronized snapshots using the VSS Snapshot wizard
- 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
- Administering the RDS using the vxrds command
- Resizing the data volumes
- Displaying the network statistics for the RLINK
- Administering the RVGs using the vxrvg command
- Displaying information using the vxprint command
- Creating snapshots using the vxsnap 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
- Example 1: Setting up replication using the command line interface
- Example 3: Using Bunker node for disaster recovery
- Example 4: Using synchronized snapshots to restore data
- 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
- Recommendations and checks
- Recovering from problems in a firewall or NAT setup
- Recovering from problems during replication
- Error when configuring the VxSAS Service
- Operation time-out errors
- Problems when configuring Volume Replicator in a VCS environment
- Problems when setting performance counters
- Appendix A. Services and ports
- Appendix B. Using the vxrsync utility
- Appendix C. VR Advisor (VRAdvisor)
Permission denied errors when performing Volume Replicator Operations
You may get permission denied errors while Volume Replicator operations are carried out:
Failed to authenticate user credentials. Please verify the vxsasservice is running in proper account on all hosts in RDS.
This error can occur if the VxSAS service is not started, or, if it has been started using a logon account that is not valid as a local administrator on some of the Volume Replicator hosts, participating in the command.
An RDS is the logical unit that groups the RVGs present on different (local and remote) hosts. Volume Replicator uses the VxSAS service logon account as the account to be authenticated while performing remote RDS configuration operations. Volume Replicator provides many RDS-wide operations that can perform simultaneous updates of Volume Replicator configuration on multiple hosts. These operations can be initiated from the Primary or the Secondary, and can be successful only when the logon account(s) of the local host's VxSAS service and Primary host's VxSAS service (if that is not the local host) has administrative privileges on all the remote participating hosts, failing which you may get this error.
To fix the problem, use the Volume Replicator Security Service Configuration Wizard to configure the VxSAS service remotely on multiple hosts from a single host.
Launch the Apps menu on the screen.
from theOptionally, run vxsascfg.exe from the command prompt.
Veritas recommends that you configure the VxSAS service now. Once correctly configured, it is not necessary to reconfigure a host unless you want to change the account name or the password.
When configuring the VxSAS service account make sure that all the hosts participating or being added in the RDS are configured, using an account that has administrative rights on all the other hosts. Another way to configure the vxsas service is through the Service Control Manager.
To configure the VxSAS service directly from the Service Control Manager
- Open Administrative Tools > Services from the Start screen, and click Control Panel.
Select VxSAS service and right-click. Choose the Properties option from the menu that appears.
- Click on the Log On tab and select the This account option. Specify your administrative password in the This account field and your password if any in the password field. Click OK to effect these changes.
- Restart the VxSAS service.
- Perform these steps for each host that is intended to be a part of the replication configuration.
For cluster setups, Veritas recommends that each node of the cluster should share the same VxSAS logon account. This can either be a domain account that has been configured as a member of the local administrators group in the local security policy of each node, or a local administrative account that is configured with the same name and password on each node.