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
Custom script execution
VBS can execute scripts on parent tiers that have one or more child tiers with soft dependency configured. The custom script is associated with a parent tier and not specific to a given VBS. It is executed whenever any Soft dependency child tier recovers from a fault. The script runs in the background on all nodes where the parent service group is online or partial. There is no time-out on the script execution and the VBS daemon does not wait for the script execution to complete. The exit code is captured in VBS daemon log on the tier where the script is executed. It is the script writer's responsibility to log the information and exit code as required.
You can configure the custom script from the Veritas InfoScale Operations Manager management console. The script can optionally take arguments. The script must already exist on the nodes before you configure this feature and its path must be same across all the nodes on the tier. On UNIX, you can run the script optionally in the context of a user present on the system. By default, it runs with root privileges. On Windows, the script always runs as SYSTEM user.
The following environment variables are made available to the script:
VBS_SCRIPT_PARENT_TIER: This is the fully qualified parent tier name which is represented as Cluster name:group name.
For example: "DB_cluster1:OracleSG"
VBS_SCRIPT_CHILD_TIER: This is the fully qualified name of the child tier which has recovered from a fault.
For example: "App_cluster1:CustomAppSG"