About 3 weeks ago, my customer began a migration of their core application to another vendor. During the migration, Symantec Backup Exec has been failing on the database backups with the following error:
BackupUnable to attach to server2.SORD.LOCAL\MSSQLSERVER.
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.
I’ve verified I can create a local SQL backup with the same account that Backup Exec is using (and even tried the sa credentials), and I’ve verified TCP/IP (Port 1433) and Named Pipes are enabled in the configuration manager. Actually, the order is 1) Shared Memory , 2) TCP/IP, and 3) Named Pipes. The firewall service is enabled, but the firewall configuration is set to permit all traffic. IPv6 is enabled on both systems, and I’ve verified IPv6 connectivity.
Can you think of anything else? I’ve tried to get the vendors involved, but they have been directed internally not to help for liability reasons.
Thank you.