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

Article:TECH182020  |  Created: 2012-02-22  |  Updated: 2012-02-22  |  Article URL http://www.symantec.com/docs/TECH182020
NOTE: If you are experiencing this particular known issue, we recommend that you Subscribe to receive email notification each time this article is updated. Subscribers will be the first to learn about any releases, status changes, workarounds or decisions made.
Article Type
Technical Solution


Issue



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



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):
-------------------



 


Environment



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.


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



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.
 

-------
 
Symantec Corporation has acknowledged that the above-mentioned issue is present in the current version(s) of the product(s) mentioned at the end of this article. Symantec Corporation is committed to product quality and satisfied customers.
 
This issue is currently under investigation by Symantec Corporation. Pending the outcome of the investigation, this issue may be resolved by way of a patch or hotfix in current or future revisions of the software. However, this particular issue is not currently scheduled for any release.  If you feel this issue has a direct business impact for you and your continued use of the product, please contact your Symantec Sales representative or the Symantec Sales group to discuss these concerns.  For information on how to contact Symantec Sales, please see  http://www.symantec.com Please be sure to refer back to this document periodically as any changes to the status of the issue will be reflected here.
 


Supplemental Materials

ValueV-79-57344-33932
Description

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.


SourceETrack
Value2698788
Description

EV: Unable to resolve clustered SQL resources configured with a CNAME record using EV Agent.




Article URL http://www.symantec.com/docs/TECH182020


Terms of use for this information are found in Legal Notices