![how to keep backup exec 2010 from ejecting tapes how to keep backup exec 2010 from ejecting tapes](https://myitknowledgebase.files.wordpress.com/2012/08/12.jpg)
- #How to keep backup exec 2010 from ejecting tapes install#
- #How to keep backup exec 2010 from ejecting tapes update#
- #How to keep backup exec 2010 from ejecting tapes full#
Figured that they must be fine anyway since the job would fail far sooner in the process if they weren't correct.Īfter a few hours of poking around by myself and eliminating a few things (redirected the job target to local storage rather than the usual NAS box, started a whole new test job on a spare VM, re-ran the installer for Update 2a, rescanned the source and targets, and even moved the SQL database off to our central SQL2012 server) had no success.
![how to keep backup exec 2010 from ejecting tapes how to keep backup exec 2010 from ejecting tapes](https://i.stack.imgur.com/7hgfa.png)
Checked the credentials being used by the proxy, no joy, checked the permissions on VCSA, all fine.
#How to keep backup exec 2010 from ejecting tapes full#
Error Client error: ChannelError: ConnectionReset (System.Exception)Ĭlearly the disk isn't full but it suggests something wrong. Error at .ProcessDiskFromVmToBackupVi(CViDiskBackupObject diskBackupObject, CBackupDiskTarget diskTarget, COibEx prevOib, IDiskInfo prevDiskInfo) Error at .SrcBackupDiskFull(String pathToDesc, IFileVfsLink vbkLink, ICTAgentSpec ctkSpec, Boolean dedupEnabled) Error SrcBackupDiskFull failed (System.Exception)
![how to keep backup exec 2010 from ejecting tapes how to keep backup exec 2010 from ejecting tapes](https://www.helpowl.com/manualimages/u/v/dell-powervault-tl2000-manual-f385160_16_6cfa.png)
Left Support with a copy of the logs to dig through. The jobs were failing immediately at the 'Hard Disk 1' action, apparently not even starting. nvram files were copying OK, so figured it must be working at some level. On the phone to Veeam Support (Case Ref#: 00549248) digging through a few logs didn't give anything obvious besides the fact that the agent was shutting down the connection for some reason.
#How to keep backup exec 2010 from ejecting tapes install#
Uninstalled BE2012, rebooted, installed BE2010 (eventually, after convincing it that the local install of SQL2008R2 Express is a valid instance!) and ran a test tape job, all working fine until the scheduled Veeam jobs ran later in the day, throwing the error above. After finding that BE2012 has removed the concept of Selection Lists (Which I use heavily) and a few other reasons, decided to roll back to the tried and tested BE2010 that we've been using for years. Took the opportunity to update to BE2012 (bit of a mistake but I won't go into that here) and had it all working fine, Veeam jobs working OK on ESXi 5.5 and a test tape job working OK in BE2012. Needs to be physycal since we run BE2010 to tape for offsite copies using a Quantum Tape Loader over SCSI. Time for a core hardware upgrade, 3 new VMWare hosts, and at the same time, updated to ESXi 5.5.Īlong wih the hosts, updated the backup box hardware. Jobs now running as normal (although I don't know which one actually solved it since I did them both at the same time, sorry, not helpful) My (eventual) solution: from C:\Program Files\Veeam\Backup and Replication\Backup\Packages ran the VeeamTransport.msi and vPowerNFS.msi installers. 20:42:24 :: Error: Client error: ChannelError: ConnectionReset Uninstalled Backup Exec 2012, Veeam jobs then failed at next run giving the error: Apologies if this is covered elsewhere, I've had a bit of a dig and haven't found anything myself. Just spent a weekend battling with this one and thought it might be of some use to someone in a similar position.