February 25, 2008 at 5:54 am
Hi All,
Yesterday one of our SQL Server started throwing strange Errors in the Log.
"BACKUP failed to complete the command BACKUP log [Master] TO VIRTUAL_DEVICE="
And provides a Virtual Device ID. I am not sure what happened. We have transaction Log shipping set up for every 5 minues and we use LiteSpeed backups.
Have anyone heard of this issue? After this happened, the server started responding very very slow. After half an hour, the system stopped responding.
We also saw somewhere around 8000 SPIDS on the Activity Monitor after an hour. We solved this by Failing over to the other Cluster. But I dont like it. I dodnt know if it will repeat again or not.
Any Ideas about this issue?
Thanks
Roy
-Roy
February 25, 2008 at 8:21 am
No one has seen this error? That is not good for us then
-Roy
February 25, 2008 at 9:06 am
Roy,
Probably just something you did 🙂
All backups run through VIDs. What probably happened is that something failed in the litespeed backup. Maybe a disk issue, server bogged, etc.
I'd start with Litespeed support and complain loudly that this is an issue.
February 25, 2008 at 9:12 am
Thx Steve. I am going get on at the Litespeed guys and find out what the heck happened.
-Roy
February 26, 2008 at 4:53 am
Hi there,
It seems like an hardware issue on your backup device. The fact the server stoped should be related to the fact the the transaction log is growing until the server falls on hard disk sapce.
February 26, 2008 at 5:04 am
Hi
It is an issue with your backup device (most likely). Check with the litespee customer support. They may give you some light on this.
February 26, 2008 at 5:49 am
Whic version of lite speed you are using. Earlier versions of lite speed had these issues but it has been resolved in the latest version. Also what is the value of -g parameter set to for the sql server?
February 26, 2008 at 6:07 am
Thx for all the input guys. I did some more digging and figured out what was wrong. Basically 15 minutes back, there was a sudden surge of data request from the web site. Around 8000 connection per minute. There were lots of blocking. This basically caused the Back up to fail like this.
Our cluster had a small issue. (Actually stupid mistake). One of the systems in our cluster had just half the horse power of the other and it was running on it. Our high config server is a 8 CPU, 16 Gig RAM and our lower config is 4 CPU, 8 Gig RAM. Once we did a fail over to the other server in our cluster, everything worked like a charm.
-Roy
February 26, 2008 at 6:10 am
I have seen this error before and it was because of other activity on the server at the time the backup was run, it could not find enough virtual memory to be able to create the backup file. I rescheduled to a time where there would be less likelihood of conflict.
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply