Virtual Business Services - Availability User's Guide
- Overview of Virtual Business Services
- About Virtual Business Services
- Features of Virtual Business Services
- Sample virtual business service configuration
- VMware virtualization support prerequisites for Veritas InfoScale Operations Manager Virtual Business Services
- About the Veritas InfoScale Operations Manager policy checks for Virtual Business Services
- Supported operating systems for Virtual Business Services
- Internationalization (I18N) support
- Installing and configuring Virtual Business Services
- About Virtual Business Services components
- Virtual Business Services workflow
- Support matrix for VBS
- Prerequisites for Configuring VBS
- Installing the Virtual Business Services package using Veritas InfoScale Operations Manager
- Configuring a virtual business service
- Considerations for creating a virtual business service
- Creating virtual business services
- Editing virtual business services
- Deleting virtual business services
- Virtual Business Services daemon
- Communication among VBS daemons
- Auto discovery of VBS Daemon on each cluster
- Configuring auto discovery for each cluster in VBS
- Configuring dependencies for a virtual business service
- Configure Virtual Business Service dependencies - Specify service group dependencies panel options
- Link Service Groups panel options
- Unlink Service Groups panel options
- Specify Script Execution details panel options
- Configure Virtual Business Service dependencies - Specify VMs start or stop panel options
- Managing Microsoft Failover Clustering from VBS
- Uninstalling the VRTSvbs package
- Uninstalling VBS from Microsoft Failover Clusters
- Virtual Business Services operations
- Starting and stopping Virtual Business Services
- Viewing the information on a Virtual Business Service
- Viewing Virtual Business Services in the data center
- Viewing the service groups associated with Virtual Business Services
- Viewing the clusters associated with virtual business services
- Viewing the virtual business services status from the command line
- Viewing the information on a virtual business service in the Server perspective
- Viewing the dependency associated with Virtual Business Services in the Server perspective
- Viewing the dependency associated with Virtual Business Services
- Viewing the properties of a virtual business service
- Viewing application recovery point and startup time of a VBS
- Tracking VBS operations
- Logs of a virtual business service
- Fault management for a virtual business service
- Virtual Business Services security
- Fault management in Virtual Business Services
- Disaster recovery in Virtual Business Services
- About disaster recovery for Virtual Business Services
- Prerequisites
- Sample disaster recovery configuration
- Disaster recovery alerts
- Disaster recovery limitations
- About the disaster recovery plan
- Bringing up Virtual Business Services at the DR site
- Performing planned migration of virtual business services
- Concurrency violation
- Upgrading Virtual Business Services
- Appendix A. Command reference
- Appendix B. Troubleshooting and recovery
- Appendix C. Known issues and limitations
- Known issues and limitations
- Complete cluster fault is not handled
- Fault propagation for shared service groups
- Propagation of multiple child fault or recovery events may be missed if fault action on parent service group is in progress (2745323)
- ClusterService group having vbsapp resource does not link vbsapp to newly created gcoip (2713002)
- CLI command returns incorrect state of the virtual machine in VBS (2789621)
- VBS dependencies get deleted during the upgrade of SFWHA configured in a VBS [2832599]
- VBS start operation may fail from Veritas InfoScale Operations Manager when VM start/stop is enabled [2848118]
- Clusters running on SFWHA 5.1SP1 or 5.1SP2 configured with virtual IP addresses cannot migrate to VIP-less communication (2845412)
- Pop up showing error message during VBS uninstallation on Windows remains hidden behind other windows (2872716)
- Events generated for VBSD lack correct description (2833160)
- DR fails to start in VBS 8.0.2 or lower for VBS formed of global service groups [3240419]
- Installation or upgrade of VRTSsfmh or VRTSvbs package from Veritas InfoScale Operations Manager may fail if publisher is set (3306997)
- Operation performed on service groups with disabled resources remains stuck or fails by timing out [3280718, 3288725]
- Recover and takeover messages are not displayed during DR of a VBS with a global service group [3315435]
- Known issues and limitations
Starting a virtual business service from the command line
To start a virtual business service, use the following command from a host on any of the clusters that are part of the virtual business service. The command brings the service groups online in the required order.
UNIX systems:
# /opt/VRTSvbs/bin/vbssvc -start vbs_name
Windows systems:
"C:\Program Files\VERITAS\VRTSvbs\bin\vbssvc.exe" -start vbs_name
The start operation on a VBS brings online all the children of a service group present in the same VBS before bringing online the service group itself. It does not take into account child service groups that are outside the VBS in question. Any local VCS dependencies of a service group are still honored, whether or not they are a part of the same VBS.
If any tier is in UNKNOWN state, the CLI prompts you to choose whether the start operation must proceed after ignoring the tiers in UNKNOWN state. If you enter Y, the tiers in UNKNOWN state are ignored from the VBS. This is useful when you want to start a VBS when some of its tiers are down.
Note that any dependencies associated with the tier in UNKNOWN state are ignored if you choose to continue with the operation ignoring the tiers in UNKNOWN state. The ignored tiers are not considered as members of the VBS for the start operation.
A task ID is displayed when you run the start command. You can optionally associate a user-defined tag name with the operation by specifying it in the vbssvc -start command with the -tag <tag_name> option. You can use the tag_name or the task ID to track the progress of the of the operation.
The vbssvc -start command supports automatic starting of VMware virtual machines before it brings the service groups on the virtual machines online. However, you must enable the Start VM option on the Configure Dependencies - Specify VM start/stop panel in Veritas InfoScale Operations Manager.
Note:
In the case of disaster recovery or planned migration of VBS, you can use the command line to automatically start the VMware machines before the service groups are brought online.
A virtual machine start operation through the vbssvc -start command is supported only for single node VCS clusters.
To terminate the start operation from the command line (for example, if the command becomes unresponsive), use the vbssvc -flush command.
UNIX systems:
# /opt/VRTSvbs/bin/vbssvc -flush vbs_name
Windows systems:
"C:\Program Files\VERITAS\VRTSvbs\bin\vbssvc.exe" -flush vbs_name