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
Configuring dependencies for a virtual business service
For a selected virtual business service, you can configure the order in which its constituent service groups are brought online (during virtual business service start operation) and taken offline (during virtual business service stop operation).
You can establish a service group's relationships with its child service groups. For the service groups that are configured on virtual machines, you can also enable virtual machine auto-start and auto-stop options. It ensures that if the virtual machine is detected as turned off during virtual business service start operation, Veritas InfoScale Operations Manager turns it on, and brings the service group online on that virtual machine. Similarly, if you have selected virtual machine auto-stop option, after the service group is taken offline, Veritas InfoScale Operations Manager turns off that virtual machine. The start and stop operations apply only to the single node clusters that are part of the selected virtual business service.
Note:
Virtual business service does not alter the dependencies that are set through Cluster Server.
To perform this task, your user group must be assigned the Admin role on the service group or the Availability perspective. The permission on the service group may be explicitly assigned or inherited from a parent Organization or cluster.
Caution:
Do not create cyclic dependencies across clusters in a virtual business service, as it is not supported in VBS.
To configure dependencies in a virtual business service
- In the Management Server console, go to the Availability perspective and expand Manage in the left pane.
- Select Data Center in the navigation tree.
- Select the Virtual Business Services node.
- In the virtual business services list, right-click on the required virtual business service and select Configure dependencies.
- In the Configure Virtual Business Service dependencies - Specify service group dependencies panel options wizard panel, under Parent, select the parent service group from the drop-down list. Under Child, select the child service group that you want to associate with the selected parent service group. Select the type of dependency from the drop-down list and click Link. Click OK. By default, the type of dependency is set to soft.
See Configure Virtual Business Service dependencies - Specify service group dependencies panel options.
- In the Configure Virtual Business Service dependencies - Specify VMs start or stop wizard panel, select the service group for which you want to enable virtual machine auto-start and auto-stop option.
See Configure Virtual Business Service dependencies - Specify VMs start or stop panel options.
- Use the Specify Script Execution details wizard panel to define and execute custom scripts. Custom scripts can be defined only if the dependency type is Soft.
- In the Result wizard panel, verify the configuration that you have made for selected virtual business service.
Note:
In a VBS that has one of the tier configured for a global service group, VBS daemons across tiers communicate using the virtual IP address set in the ClusterAddress attribute of the global service group tier.
- Click Finish.
Note:
If the virtual business service contains a mix of local and global service groups, and one or more global service groups are in online or partial state on a remote reachable cluster (which is in running state), then virtual business service start operation is rejected. For such a virtual business service, you need to manually take all the global service groups on the remote clusters offline, and then bring virtual business service at the local site online.