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 Services daemon
An instance of the Virtual Business Services daemon runs on each cluster over which a VBS is configured. This daemon is made highly available using the local high availability solution deployed on that cluster. For VCS clusters and ApplicationHA nodes, the VBS daemon is configured as a resource called vbsapp inside a service group called ClusterService. For such clusters that are already running a GCO configuration, ClusterService would already be present and is reused.
On non-Veritas clusters (Microsoft Failover Clustering in VBS 6.1 or later), the VBS daemon is made highly available and failover-capable by making it a resource (called vbsapp) inside a resource group or application role called VBSHAService.
You must ensure that the ClusterService or VBSHAService group is not in FAULTED or FAILED state across all nodes of the cluster. Otherwise, VBS does not function correctly.