Virtual Business Service-Availability User's Guide
- Overview of Virtual Business Services
- About Virtual Business Services
- Features of Virtual Business Services
- Sample virtual business service configuration
- Virtualization support in Virtual Business Services
- About the Veritas InfoScale Operations Manager policy checks for Virtual Business Services
- Supported operating systems for Virtual Business Services
- 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
- Reconfiguring an ApplicationHA node
- 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
- Veritas InfoScale Operations Manager displays stale status for a virtual business service
- 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 ApplicationHA or 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 2008 remains hidden behind other windows (2872716)
- Events generated for VBSD lack correct description (2833160)
- DR fails to start in VBS 7.3 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
When the you start a virtual business service, its associated service groups are brought online in a specified order. The order in which the service groups in a virtual business service come online is determined by the start order defined in Veritas InfoScale Operations Manager. You can define the start order of service groups using the option. You can specify one or more service groups as the child of another service group. Veritas InfoScale Operations Manager ensures that all child service groups are brought online before the parent service group. If two service groups are not related by the start order, they may come online at the same time. If a service group is configured on a VMware virtual machine, you can also set auto-start for that virtual machine.
The Start virtual business service operation does a quick pre-validation to verify if all tiers are reachable. This detects any unreachable tiers and prevents the operation from hanging. If the pre-validation check determines that any tier is unreachable, the operation fails and the tier state is correctly marked as UNKNOWN. This is useful in a disaster event in one tier, where you can continue to operate on the remaining tiers with a single click operation. If one or more tiers are not reachable and in UNKNOWN state, you can either stop the virtual business service or continue ignoring the unknown tiers
To perform this task your user group must be assigned:
Admin or Operator role on the service group or the Availability perspective.
Admin role on all tiers of the virtual business service in the Server perspective.
The permission on host of the tier may be explicitly assigned or inherited from a parent organization.
To start a virtual business service
- In the Management Server console, go to the Availability or Server perspective and expand Manage in the left pane.
- Do one of the following:
In the Availability perspective, select Data Center > Virtual Business Services in the navigation tree.
In the Server perspective, select Data Center. Expand Applications > Virtual Business Services to locate the required virtual business service.
- Right-click on the required virtual business service and select Start.
- On the Start Virtual Business Service wizard panel, click OK to confirm.
See Start Virtual Business Service panel options.
The progress of this operation can be viewed on the Dependency Graph.
See Stopping a virtual business service .
See Configuring dependencies for a virtual business service .