Enterprise Vault (EV) Agent backups of clustered EV database fail with "Unable to Attach to Resource".

Problem

When attempting to perform a backup of EV databases stored within a SQL cluster configured with a CNAME Alias record in DNS, the job fails with "Unable to attach to resource".

Error Message

V-79-57344-33932 - Unable to attach to a resource. Make sure that all selected resources exist and are online, and then try again. If the server or resource no longer exists, remove it from the selection list. Edit the selection list properties, click the View Selection Details tab, and then remove the resource.

Debug of beremote.exe with Enterprise Vault Agent logging set to maximum reveals:

---------------------------------
BEREMOTE: [02/13/12 16:07:56] [4424]     Failed to open VCS cluster (sqlclusteralias)
BEREMOTE: [02/13/12 16:07:56] [4424]     [fsys\ntfs]          -
NTFS_SurrogateCalling: sqlclusteralias
BEREMOTE: [02/13/12 16:07:56] [4424]     [fsys\ntfs]          - E: is NOT
owned, skipping logical drive
BEREMOTE: [02/13/12 16:07:56] [4424]     [fsys\ntfs]          - G: is NOT
owned, skipping logical drive
BEREMOTE: [02/13/12 16:07:56] [4424]     [fsys\ntfs]          - F: is NOT
owned, skipping logical drive
BEREMOTE: [02/13/12 16:07:56] [4424]     [fsys\ntfs]          - Not enumerating
local drives: this is not a node
------------------------------------
Further down, this information is passed to the agent:
--------------------------------------
BEREMOTE: [02/13/12 16:12:44] [2660]     [fsys\ev]            -
CStringHandler::GetEVVersionFromDevName - entering.
BEREMOTE: [02/13/12 16:12:44] [2660]     [fsys\ev]            -
CStringHandler::GetEVVersionFromDevName - Version information removed. Device
Name (EV-VDB::\\EV\sqlclusteralias\Vault Site\Vault Store Group\Vault Name
Vault\Vault Store DB@sqlclusteralias).
BEREMOTE: [02/13/12 16:12:44] [2660]     [fsys\ev]            -
CStringHandler::GetEVVersionFromDevName - exiting.
BEREMOTE: [02/13/12 16:12:44] [2660]     [fsys\ev]            -
FS_FshEV::AttachToDLE - Could not find/create DLE. Name = [sqlclusteralias]
BEREMOTE: [02/13/12 16:12:44] [2660]     [fsys\ev]            -
FS_FshEV::AttachToDLE - exiting.
BEREMOTE: [02/13/12 16:12:44] [2660]     [ndmp\ndmpsrvr]      - AttachToDLE(-
536836945)[EV-VDB::\\EV\sqlclusteralias\Vault Site\Vault Store Group\Vault Name
Vault\Vault Store DB@sqlclusteralias]
BEREMOTE: [02/13/12 16:12:44] [2660]     [ndmp\ndmpsrvr]      - startBackup:
CreateBSD() failed!
BEREMOTE: [02/13/12 16:12:44] [2660]     [ndmp\ndmpsrvr]      + ndmp_data.cpp
(12046):
-------------------



 

Cause

The Backup Exec cluster API does not perform name resolution when determining cluster resource ownership.  When attempting to locate resources for backup, the job will fail, as the SQL resources are owned by the virtual node name rather then the CNAME DNS alias.

Solution

This issue is resolved in Backup Exec 2014 or later versions. 


To resolve this issue and receive the new Backup Exec improvements please upgrade to the current version of Backup Exec.

 

NOTE: Symantec continues to focus on the current release and future releases, there are no plans to address this issue by way of a patch or hotfix in earlier versions of the software at the present time. Please contact your Symantec Sales representative or the Symantec Partner for upgrade information including upgrade eligibility to the release containing the resolution for this issue. For information on how to contact Symantec Sales, please see www.symantec.com 

 

Workaround:

Modify the EV configuration to use the SQL cluster virtual node name in place of the CNAME alias for the SQL cluster.

To achieve this, perform steps 2-8 in http://www.symantec.com/docs/TECH35744.  Please contact Enterprise Vault Support if assistance is required with this configuration change.
 

 

Applies To

Enterprise Vault Databases reside on a Microsoft Cluster with a CNAME record created which references the actual virtual node name of the cluster.  The EV Directory database is configured to point to CNAME alias instead of the virtual node name of the clustered resource.

Terms of use for this information are found in Legal Notices.

Search

Survey

Did this article answer your question or resolve your issue?

No
Yes

Did this article save you the trouble of contacting technical support?

No
Yes

How can we make this article more helpful?

Email Address (Optional)