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
VCS dependencies in Virtual Business Services
If two service groups in a virtual business service have a VCS-level dependency set between them, this dependency is represented as VCS type dependency in the virtual business service. VCS-level dependencies between two participating service groups are visible in a virtual business service, but there is no action taken on the dependency by the VBS daemon. The dependency is used by the VBS daemon only to determining the start or stop order. Therefore, the behavior for this dependency is identical to that of the SOFT dependency type.
Note that the custom script execution feature is not supported for VCS-level dependency child tiers.
VBS configuration does not allow you to change VCS-level dependencies from Veritas InfoScale Operations Manager. When VCS-level dependencies exist, they are given higher precedence than VBS-type dependencies.