Error Code details
V-52410-49479-116
Severity: n/a 
Component: Cluster Server 
Message:
Could not connect to the cluster. The Veritas high-availability daemon (HAD) may not be running. Error code is 7. Failed to discover 'Veritas Cluster Server' on node '<server_name>'.

 

Veritas solutions
Solution 1 Vote: [Useful] [Not useful]
Last Modified: 2009-11-10 03:01:15 PST
Platform: Generic
Release: Generic
Content:


V-52410-49479-116 - Could not connect to the cluster. The Veritas high-availability daemon (HAD) may not be running. Error code is 7. Failed to discover 'Veritas Cluster Server' on node '<server_name>'.

Possible causes

This error message is displayed by the Disaster Recovery wizard when it fails to discover the Veritas high-availability daemon (HAD).

This may mean that HAD is not running on the secondary site system specified for the Disaster Recovery configuration.

Solution

The following actions may apply:
 

    Verify that the Veritas high-availability daemon (HAD) is running on the secondary site system specified for the Disaster Recovery configuration.
    If HAD is in a stopped state, start HAD on the system using the CLI ?hastart?. You may also start HAD using the CLI ?net start had?
    If HAD is in a disabled state, it means that the cluster is not yet configured and hence HAD will not be able to start. In this case, run the Cluster Configuration wizard (VCW) to configure a cluster and then proceed with the Disaster Recovery configuration.
Reference: http://entsupport.symantec.com/docs/306750
http://entsupport.symantec.com/docs/314098
Solution 2 Vote: [Useful] [Not useful]
Last Modified: 2009-11-10 05:56:51 PST
Platform: Generic
Release: Generic
Content:

The 'Disaster Recovery Configuration Wizard' fails with the error seen in Figure 1 below:

Figure1
 

The source of this issue has been identified and a private fix is available from Symantec Enterprise Technical Support. To obtain the private fix, contact Symantec Enterprise Technical Support and reference this article during the call. A support representative will be available to assist in troubleshooting this issue. If it is determined that the private fix addresses the problem the support representative will further assist in obtaining the private fix. Note: This fix specifically addresses the problem identified above. It has not been fully tested and should be applied in a test environment before placing into production. If the systems are not critically impaired, it is recommended to delay the installation of this private fix until the next scheduled maintenance release. Before applying this private fix, systems may be required to be upgraded to the latest code base. The support representative will help in determining the best course of action.

 

User solutions
No user solutions yet.

 

Read and accept Terms of Service