Veritas InfoScale™ Operations Manager 7.3.1 Frequently Asked Questions

Last Published:
Product(s): InfoScale & Storage Foundation (7.3.1, 7.3, 7.2, 7.1, 7.0.1, 7.0)

Virtual Business Services

How are the Virtual Business Services back-end components deployed?

The VRTSvbs package contains the Virtual Business Services back-end components. This package is available by default with SFHA 6.0, SFWHA 6.0, and ApplicationHA 6.0 (UNIX) versions and later. For earlier releases of SFHA and ApplicationHA, do the following:

  • Download the VRTSvbs packages for all required platforms from the Veritas website to a temporary directory on a local computer.

  • Log in to the Management Server console from that computer. Upload all the packages for the relevant cluster platforms using the Deployment Manager.

  • Select all the applicable hosts and install the packages using the Management Server console.

Is Veritas InfoScale Operations Manager Management Server in the critical path and a single point of failure?

Veritas InfoScale Operations Manager Management Server is critical from the point of view of Virtual Business Services configuration, but not for its operation. A virtual business service cannot be created or edited without Veritas InfoScale Operations Manager. After a virtual business service is created, it continues to operate even if the Management Server is down. The Virtual Business Services back-end CLIs can be used for performing the operations and finding status. Veritas InfoScale Operations Manager also has its own high availability and disaster recovery provision to handle its failure.

How often does the configurator run?

The configurator runs under two circumstances:

  • Scheduled: Once every 5 minutes. This scheduled run pushes out any changes that have not yet been sent to one or more virtual business services that have fault management configured.

  • Unscheduled: Any configuration changes made in the Management Server console to an existing virtual business service has fault management enabled by default.

How can I know if all the nodes have been properly configured for Virtual Business Services to work?

There are several ways:

  • You can view the "Fault Management Status" in the Management Server console for any virtual business service. This tab has an entry for each host in the virtual business service, and the configuration status on it. You can right-click on the a virtual business service in the tree panel and click on Properties from the menu to see the "Fault Management Status". For each host, there is a "Configured status" column that shows whether fault management is enabled on that host. Also, there is a "VBS package version" column that shows the version of the Virtual Business Services package installed on that host.

  • You can create a policy check using the new signature added for a virtual business service. Run it for the selected a virtual business services and see if there are any violations reported. If any violation is reported, the virtual business service may not work properly and it should be fixed.

  • You can use the new fault that has been added for the Virtual Business Services. The topic ID is event.alert.vom.vcs. vbs.package.notinstalled, which stands for "VRTSvbs package is not installed". Create a rule that acts on this alert. Choose the notification type that you want. This rule helps in reducing one of the factors that can affect the proper functioning of Virtual Business Services.

It is recommended that you use a combination of all of the above.

If the Virtual Business Services configuration goes out of synch, how does one correct it?

Run the following command on VOM Management Server:<sfmh_bin_dir>/xprtlc -l https://localhost:5634/admin/cgi-bin/vbs_configurator.pl -d rescan=all

For example:

UNIX systems:

# /opt/VRTSsfmh/bin/xprtlc -l https://localhost:5634/admin/cgi-bin/vbs_configurator.pl -d rescan=cred

Windows systems:

"C:\Program Files\Veritas\VRTSsfmh\bin\xprtlc.exe" -l https://localhost:5634/admin/cgi-bin/vbs_configurator.pl -d rescan=cred

What happens to the Virtual Business Services definitions if Veritas InfoScale Operations Manager Management Server is reinstalled?

All the Virtual Business Services definitions are lost and you have to re-create them. It is recommended that you back up the Veritas InfoScale Operations Manager database before uninstalling Veritas InfoScale Operations Manager, and restore it after reinstall to retain the old Virtual Business Services definitions.

How is data passed from Veritas InfoScale Operations Manager Management Server to the cluster nodes?

Veritas InfoScale Operations Manager uses XDist to push the data from Management Server to the cluster nodes. XDist has an in-built retry mechanism that sends the data even if the target host is down, and comes back up later.

Where are the various log files stored for this feature?

The log files can be found at the following locations:

  • <sfmcs_var_dir>/logs/vbs_configurator.log (on Management Server)

  • <sfmh_var_dir>/logs/ (on managed host)

  • <vbs_var_dir>/log/ (on managed host)

Which virtualization technologies are supported for starting or stopping virtual machines?

Currently, Veritas InfoScale Operations Manager supports only VMware ESX for starting or stopping virtual machines. For this, Virtual Center/vSphere must be configured in Veritas InfoScale Operations Manager. The virtual machine start and stop operation from the command line is supported only for ApplicationHA or single node VCS clusters.

What is the port used by the Virtual Business Services daemon?

2410

How is the Virtual Business Services daemon made HA?

The Virtual Business Services daemon is configured as a resource (vbsapp) in the ClusterService group on all the participating clusters in the virtual business Service.