Backups of Enterprise Vault databases fail if the databases are configured to listen on multiple TCP ports
|Article:TECH187959|||||Created: 2012-05-02|||||Updated: 2012-05-02|||||Article URL http://www.symantec.com/docs/TECH187959|
|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.|
When attempting a backup of Enterprise Vault databases, the Backup fails with "Unable to attach to resource" when protecting SQL databases configured to listen on multiple user-configured TCP ports.
Final error: 0xe000848c - 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.
Final error category: Resource Errors
For additional information regarding this error refer to link V-79-57344-33932
A BERemote debug from the Vault server reveals the following:
 04/18/12 10:35:48 [fsys\shared] - FS_BlowOutMachine: attached successfully
 04/18/12 10:35:48 [fsys\shared] - FS_BlowOutMachine: didn't find -->EV-MDB::\\EV\sqlsvr/EV,1111\SITE@sgsql2\sqlsvr/EV,1111<-- in DLE tree
 04/18/12 10:35:48 [fsys\shared] - FS_BlowOutMachine: detaching from newly created DLE
 04/18/12 10:35:48 [fsys\shared] - FS_FshGen: Failure to create debug trace object at line number 126
 04/18/12 10:35:48 [ndmp\ndmpsrvr] - AttachToDLE(-536836945)[EV-MDB::\\EV\sqlsvr/EV,1111\SITE@sqlsvr/EV,1111]
 04/18/12 10:35:48 [ndmp\ndmpsrvr] - startBackup: CreateBSD() failed!
The SQL Server hosting the Enterprise Vault Databases is configured to use multiple TCP ports, per http://msdn.microsoft.com/en-us/library/ms189310.aspx
The Backup Exec Enterprise Vault Agent does not recognize SQL server resource names that include a port number.
Manually modify the EVBackup.xml per http://www.symantec.com/docs/TECH174766
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.
There are no plans to address this issue by way of a patch or hotfix in the current or previous versions of the software at the present time. However, the issue is currently scheduled to be addressed in the next major revision of the product. Please be sure to refer back to this document periodically as any changes to the status of the defect will be reflected here. Please note that Symantec Corporation reserves the right to remove any fix from the targeted release if it does not pass quality assurance tests. Symantec's plans are subject to change and any action taken by you based on the above information or your reliance upon the above information is made at your own risk.
Please contact your Symantec Sales representative or the Symantec Sales group 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 http://www.symantec.com
EV: Backups of EV SQL databases fail when SQL database engine is configured to listen on specific, non-default port(s)
Article URL http://www.symantec.com/docs/TECH187959