Virtual Business Service-Availability User's Guide
- Overview of Virtual Business Services
- Virtualization support in Virtual Business Services
- Supported operating systems for Virtual Business Services
- Installing and configuring Virtual Business Services
- Configuring a virtual business service
- Creating virtual business services
- Editing virtual business services
- Configuring dependencies for a virtual business service
- Managing Microsoft Failover Clustering from VBS
- Virtual Business Services operations
- Starting and stopping Virtual Business Services
- Tracking VBS operations
- Logs of a virtual business service
- Virtual Business Services security
- Fault management in Virtual Business Services
- Disaster recovery in Virtual Business Services
- Upgrading Virtual Business Services
- Appendix A. Command reference
- Appendix B. Troubleshooting and recovery
- Appendix C. Known issues and limitations
- Known issues and limitations
- Known issues and limitations
Virtual business service state is unknown
If a virtual business service goes into an unknown state, perform the following tasks in sequence till the issue is resolved.
Run the Veritas InfoScale Operations Manager Policy Check with the VBS Availability Configuration signature. Verify whether your configuration conforms to predefined standards and take appropriate corrective action. For more information on running Policy Check, refer to Veritas InfoScale Operations Manager Management Server User Guide.
See About the Veritas InfoScale Operations Manager policy checks for Virtual Business Services .
Check states of the individual service groups from the VBS command line. If some of the remote clusters are not reachable, perform the corrective actions, such as rectifying cluster or node failures, network communication failure, firewall issues, or configuration issues.
See Viewing the virtual business services status from the command line.
Refresh the hosts of the cluster whose service groups are in unknown state. You can refresh the hosts from the Management Server or by running the following command from a managed host.
UNIX:
# /opt/VRTSsfmh/bin/mh_ctl.pl --family VCS --refresh
Windows:
cd C:\Program Files\Veritas\VRTSsfmh\bin perl.exe mh_ctl.pl --family VCS --refresh
If you reinstalled only the Management Server and did not reinstall the managed hosts, re-create the virtual business service and rescan by running the following command from the Management Server.
UNIX:
# /opt/VRTSsfmh/bin/xprtlc -l \ https://localhost:5634/admin/cgi-bin/vbs_configurator.pl -d \ rescan=all
Windows:
"C:\Program Files\Veritas\VRTSsfmh\bin\xprtlc.exe" -l https://localhost:5634/admin/cgi-bin/vbs_configurator.pl -d rescan=all
If you moved a managed host from one Management Server to another Management Server, run the following command from the new Management Server. The command makes the credentials available to the managed host.
UNIX:
# /opt/VRTSsfmh/bin/xprtlc -l \ https://localhost:5634/admin/cgi-bin/vbs_configurator.pl -d \ rescan=cred
Windows:
"C:\Program Files\Veritas\VRTSsfmh\bin\xprtlc.exe" -l https://localhost:5634/admin/cgi-bin/vbs_configurator.pl -d rescan=cred
If the ClusterAddress of any of the tiers is not set, ensure that all the tiers are upgraded to VBS version 7.3 and the hosts in the participating clusters can communicate with one another.