February 24, 2011 at 2:54 am
You wont have any problem if it succeeds with you re chain. A "extra" full backup wont break the chain. you still can restore from youre own full backup and logs backups.
about the backup looks like you got some kind of agent/plugin running (commvault/legato ect) guess the trace will tell you more.
May 27, 2011 at 7:33 am
Did you find out any more info on this? The EXACT thing just showed up on our production SQL system. That is:
- we got a number of "BackupVirtualDeviceFile::SendFileInfoBegin: failure on backup device..." errors
- there were no SQL backups schedule (no SQL Agent jobs whatsoever, no other external apps, etc)
It is indeed disconcerting...
May 27, 2011 at 8:31 am
We finally tracked it down to the SAN. Our parent company has installed a network backup solution which scanned across the LAN and WAN for SQL Server databases and executed (or at least attempted to) a copy only backup which was to be stored off site. The idea, I discovered, was to ensure that all SQL Servers were backed up across different sites in case we lost one so completely as not to be able to recover. However this was only being done across the SAN drives, and one SQL Server I maintain that has it's own dedicated server was unaffected.
However it was misconfigured so that whilst it could issue the requests, it didn't have the specific privileges required by my SQL servers to perform the backup, and as such, it was failing.
I only discovered this when talking to a network team at another office who were aware of it, as our network team didn't seem to know what was going on either.
We still get hit with the error message once in a while, probably whilst they try to reconfigure the system to work properly. :w00t::hehe:
---------------------------------------
It is by caffeine alone I set my mind in motion.
It is by the Beans of Java that thoughts acquire speed,
the hands acquire shaking, the shaking becomes a warning.
It is by caffeine alone I set my mind in motion.
Viewing 3 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply