I am having some trouble with BackupExec 2010. The media server is v.13.0 Rev. 2896 (64-bit).
We have 8 servers we back up- one is a SQL server, one is a Hyper-V server, one is an Exchange server, then there are a few file servers and a couple of VM's.
Everything is updated to the latest (As of 7/6) according to LiveUpdate.
The problems seem to stem from connectivity. The admin console will randomly drop the connection ot he BE database- Sometimes once in 2 hours, sometimes several times in a minute. Then I have to click the OK button and put in the password to reconnect. I have one job in particular that runs daily on the non-database information on our SQL server- sometimes it runs, and sometimes it will back up a few GB then throw an error E000846B which is a generic "lost connectivity" error. It succeeds about 2-3 out of six times a week. The backup target is a disk local to the media server, which is on a separate drive-based array from anything else (Except other backup jobs). I have since tried adding a separate network dedicated to the backups- Each server being backed up has a hardware port assigned to this backup network, which has no route to the Internet- Basically a simple LAN on a dedicated switch in which all members have static IP's and can ping each other.
In BE I have the job set to use the network connection for the backup network, and the SQL server has the remote agent set only to publish to the backup network IP address of the media server.
I have a second job that runs on this server as well- it is dedicated to backing up the MSSQL databases on the server. When I run it, it runs for less than a second and fails with an error E0000F02. The only way to get it to run is to allow it to use any network adapter it wants, which will push unwanted traffic over the production network, but does allow it to success most of the times it runs.
We never run more than two backup jobs at the same time as a tape backup, and one of those must be a local backup- This is for the sake of network communications and reducing unexpected errors. We run a B2D2T scenario, where the tape backup runs starting at 3am each day, database backups run at 12am and hyperV/fileserver backups start at 6PM.
I think the common theme here is a network connectivity issue- Our production network uses Cisco Catalyst 2960's @ 100MBPS, and the backup network uses a Netgear GS724T-300 (Chosen for solid history in data streaming applications, such as ghosting.... Any ideas why we are having these issues?
Thanks!