Troubleshooting Just In Time Availability
Prev Appendix A. Using Veritas AppProtect for vSphere

Troubleshooting Just In Time Availability

Table: Issues and the corresponding resolutions lists the issues and the recommended solutions.

Table: Issues and the corresponding resolutions

Issue

Recommended Solution

When setting up a maintenance plan, the registered virtual machine is not listed on the wizard.

To troubleshoot the issue, make sure the following:

  • ESX host on which the virtual machine resides, is connected to the vCenter.

  • The virtual machine is added as a managed host to Management Server.

  • On the virtual machine, at least one application is configured for monitoring, along with VCS.

  • The virtual machine is registered in VIOM.

  • VCS is configured on the virtual machine.

  • The virtual machine does not contain RHEL7 and SUSE 12, which are not supported.

    Note:

    Windows 2012 R2 and 2008 R2 are supported.

  • VCS is configured with the service groups.

When setting up a maintenance plan, the listed virtual machine is not available for selection.

To troubleshoot the issue, make sure the following:

  • The virtual machine is not configured for Global Cluster option (GCO).

  • Agents that support SAN are configured.

When Veritas AppProtect executes an operation, the timeout message is reported.

To troubleshoot the issue, perform the following:

  • If the failover or the failback operation fails, then click Planned Maintenance > Revert icon. Retry the operation.

  • If the delete plan or the delete clone operation fails, then retry the operation.

The revert operation failed.

Manually revert the virtual machine to its original state.
Prev Up
Plan states Home