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
Virtualization workflow for virtual business service start operation
During the virtual business service start operation, Veritas InfoScale Operations Manager discovers any service group which contains only one system in its system list and it is a VMware virtual machine.
One example is ApplicationHA (single node cluster) service group where the service group's system list has only one virtual machine.
For the above-mentioned scenario, Veritas InfoScale Operations Manager selects a virtual machine from the service group's system list, and then starts the virtual machine using the VMware vCenter Server that is specified for that virtual machine. Make sure that vCenter and Veritas InfoScale Operations Manager is running for the VM to autostart. When this service group is successfully set to online, Veritas InfoScale Operations Manager starts to online other service groups in the virtual business service.
See Virtualization workflow for virtual business service stop operation.