InfoScale™ Virtual Business Services - Availability User's Guide
- Overview of Virtual Business Services
- About Virtual Business Services
- Features of Virtual Business Services
- Sample virtual business service configuration
- VMware virtualization support prerequisites for InfoScale Operations Manager Virtual Business Services
- About the InfoScale Operations Manager policy checks for Virtual Business Services
- Supported operating systems for Virtual Business Services
- Internationalization (I18N) support
- 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 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
- 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
- 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 SFWHA configured in a VBS [2832599]
- VBS start operation may fail from 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 remains hidden behind other windows (2872716)
- Events generated for VBSD lack correct description (2833160)
- DR fails to start in VBS 9.0 or lower for VBS formed of global service groups [3240419]
- Installation or upgrade of VRTSsfmh or VRTSvbs package from 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
About the disaster recovery plan
The disaster recovery plan (DR plan) provides the sequence of operations that will be performed at the DR site, in the event of a disaster. To view the Virtual Business Services DR plan, use the vbssvc -showplan command. You can run this command from the production site or from the DR site.
The command output might resemble the following:
# vbssvc -showplan FinanceVBS
Name | Global | CanBeOnline | Reason |
PuneWeb:FinanceApacheWeb | No | Yes | Already online |
PuneWSphere:FinanceWebSphere | No | Yes | Already online |
PuneDB:FinanceDB | Yes | No | Online on remote cluster MtViewVBS. At least one service group in virtual business service is not global |
VCS NOTICE V-16-25-40234 virtual business service FinanceVBS cannot be started.
Note:
This prediction is based on the last discovered state of the service groups. The actual start operation can still fail if the underlying high availability technology is not available or due to external factors like network outages.
Table: DR plan examples lists a few scenarios and possible DR plan command outputs.
Table: DR plan examples
Scenario | DR plan output |
|---|---|
Global service group is faulted. | The plan shows that the global service group at the production site is FAULTED. The -force option will be used to bring the global service group online at the DR site. |
Global service group is offline. | The plan shows that the global service group is offline at the production site. You can start the virtual business service at the DR site. |
Production cluster is faulted. | The plan shows that the service group is global and that the production cluster is FAULTED or DOWN. When you start the virtual business service on the DR site, the -force option will be used to bring the global service group online at the DR site. |
Global service group is online at the production site and there are one or more non-global service groups in the virtual business service. | The plan shows that the production cluster is up and the global service group is online on the production cluster. You cannot start the virtual business service at the DR site. |
Global service group is online at the production site and all service groups are global. | The plan shows the status of each service group on the production site. The -switch option will be used to bring the global service groups online at the DR site for the global service groups that are online at the production site. |