Barracuda backup solution and MS SQL 2005

[davetherave2]

Our company has just changed from using an older version of Backup Exec 11D I think and installed a couple of Barracuda storage devices but since having these installed it seems to be breaking log shipping for one our critical databases on a SQL 2005 Win 2K3 box.

The reason for the log shipping is for a reports server (which is in read only-standby mode) but every other day this seems to be breaking the log shipping processes.

From reading around the internet I gather this is due to something other than the normal log shipping routines which are created as part of the log shipping routines backing up the transaction logs.

So is there anything that needs to be changed within the backup policies to prevent the backup device from interfering with this database as it means our reporting system is down for an hour or two while I have to reset everything backup again which means no one can pull reports while this process is being done.

I am sure it is this solution as up until now the log shipping has been working fine for 6 years with the various forms of Backup Exec we used to have and nothing has changed on the server to my knowledge.

I just want to point our support team in the right direction on how to cure this issue as I don't fancy having to restore the report server every morning because of this issue. (As I am currently doing now for the 4th time in just over a week)

Thanks in advance.

 

[davetherave2]

ok update from me. Turns out it was a simple change that needed to be done rather than backing up the sql db's we excluded it and left it to do a normal file system backup. Touch wood this is will work.

Mod's - feel free to lock/close this thread.

 

[masterk]

Am I right in presuming that as your new backup devices were doing full SQL backups they were truncating the transaction logs and breaking log shipping?

If so that explains why not backing up SQL fixes this, I just worry that you don't have a good backup of SQL. Do the new backup devices have an ability to just do a copy backup of SQL as opposed to a "Full" backup which will truncate the logs?

Either that or are you dumping the DB to disk to back up the flat file?

 

[davetherave2]

we dump the db to a .bak file that is done on a nightly basis and backed up that way. this is how it has always been set up fwith backup exec. But took some time to try and explain this to the support team and show them the error of their ways . Even before I had looked into this in any great depth I would have suspected something similar.

From speaking to the support team it just does a full backup of the db and not a copy hence the .bak file being created.

Oh well hopefully tomorrow everything will be working tomorrow morning.