Virtual Business Service-Availability User's Guide
- Overview of Virtual Business Services
- About Virtual Business Services
- Features of Virtual Business Services
- Sample virtual business service configuration
- Virtualization support in Virtual Business Services
- About the Veritas InfoScale Operations Manager policy checks for Virtual Business Services
- Supported operating systems for Virtual Business Services
- 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 Veritas 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
- Reconfiguring an ApplicationHA node
- 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
- Veritas InfoScale Operations Manager displays stale status for a virtual business service
- 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 ApplicationHA or SFWHA configured in a VBS [2832599]
- VBS start operation may fail from Veritas 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 2008 remains hidden behind other windows (2872716)
- Events generated for VBSD lack correct description (2833160)
- DR fails to start in VBS 7.3 or lower for VBS formed of global service groups [3240419]
- Installation or upgrade of VRTSsfmh or VRTSvbs package from Veritas 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
Upgrading the VRTSvbs package using Veritas InfoScale Operations Manager
Skip this section if you have installed or upgraded to VCS 7.3 or SFHA 7.3. Perform these steps if you have installed an earlier supported version of VCS or SFHA. You must upgrade the VRTSvbs package on each host of each cluster that you want to manage. VRTSvbs is not supported on the Management Server.
If you are upgrading an earlier supported version of VCS or SFHA (that has VRTSvbs installed) to VCS 7.3 or SFHA 7.3, you can use any of the upgrade procedures that are supported in VCS 7.3 or SFHA 7.3. For more information, see the installation guide for these products. If you want to remove VRTSvbs before upgrading, you must perform the steps in the procedure for uninstalling VRTSvbs.
Before you upgrade the VRTSvbs package to version 7.3 on a managed host, ensure that the VRTSsfmh package version 6.0 or later is installed on the host. If VRTSsfmh version 6.0 or later is not installed, the installation of VRTSvbs fails.
Note:
When you upgrade VRTSvbs to 7.3 through Management server, the vbsapp resource that is online on the managed host is brought offline and restarted after the upgrade is successfully completed. However, on Solaris 11 systems, the vbsapp resource is not taken offline and brought online automatically. Before you upgrade VRTSvbs on Solaris 11 systems, you must manually take the vbsapp resource on the managed hosts offline by using HA commands or through the Veritas InfoScale Operations Manager console. After the upgrade is complete, you must manually bring the vbsapp resource online.
To upgrade the VRTSvbs package using Veritas InfoScale Operations Manager
- Download the VRTSvbs package to a temporary directory on your computer from the following location:
The package is available for download from Veritas FileConnect and Trialware too.
- In the Veritas InfoScale Operations Manager console, select Home > Settings > Deployment.
- Click Upload Solutions on the Deployment Management view and upload the VRTSvbs package to the repository from the Upload Solutions to Repository wizard panel. You need to upload the VRTSvbs package for each platform that you want to deploy VBS on.
The uploaded package appears under Base Releases.
- Click Base Releases node and right-click on the VRTSvbs package under the Base Releases tab. This displays the Select hosts panel.
On the Select hosts panel perform the following steps as applicable:
Select Hosts or Platforms to display list of hosts and platforms respectively.
Select Hosts > Show all applicable hosts to overwrite existing installation on selected hosts.
Select Platforms > Force install to overwrite existing installation on selected platforms.
To upgrade the package on Hosts, select the hosts from the list.
To upgrade the package on Platforms, select the platforms from the list.
- Click Finish on the Select hosts panel.
Note:
VOM discovers the upgraded package version only via host family discovery, which is scheduled once in a day by default or is done manually. Hence, vbs - start and vbs -stop will not get invoked until the version upgrade is detected. You must refresh the hosts for which the VRTSvbs package was upgraded so that VOM can detect the upgraded package.