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 security model example
Consider two virtual business services:
VBS A that consists of cluster C1 and cluster C2
VBS B that consists of cluster C2 and cluster C3
Assume the following service groups for each cluster:
Service group SG1 for cluster C1
Service group SG2 for cluster C2
Service group SG3 for cluster C3
When you create a virtual business service from the Veritas InfoScale Operations Manager interface, Veritas InfoScale Operations Manager deploys a per-cluster credential (digital certificate) to each cluster. All hosts on the cluster get a credential that identifies them as belonging to that cluster. The cluster credential contains the cluster ID. Likewise, hosts on another cluster also get credentials that identify them as belonging to their respective cluster.
Additionally, the credential also has information about the Management Server that sent the credential. This information is required when one host is managed by multiple Management Servers.