SQL Server 2005 Backup Scenario question

[jlancton]

Hello,

I've recently started at a new company, and have inherited a SQL server.

It is a Windows Server 2003 box with SQL Server 2005 installed. The entire server is backed up to tape using Backup Exec, with full backups done daily.

There are also jobs set up in SQL Server to perform daily backups of the databases to devices which point to files on the same server.

Is there a sound reason for this type of backup strategy that I just don't see? Its seems redundant and needlessly taking up space on the hard drive/tape.

Your thoughts are greatly appreciated.

-Jeff

 

[mrdenny]

Is there a backup exec agent for the SQL Server, or is Backup Exec only taking file system backups? If Backup Exec is only taking file system backups then it can't backup the SQL Server databases, and can only backup the backups which the SQL Server creates.

Denny
MVP
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / SQL 2008 Implementation and Maintenance / Microsoft Windows SharePoint Services 3.0: Configuration / Microsoft Office SharePoint Server 2007: Configuration)
MCITP Database Admin (SQL 2005/2008) / Database Dev (SQL 2005)

My Blog

 

[jlancton]

That's it exactly. No agent for the SQL server in Backup Exec. Makes sense now. Time to buy the Agent.

Thanks!!

 

[mrdenny]

That or have the SQL Server backup the databases to disk, then use Backup Exec to backup the file backups. It adds an extra step to the process, but it will save you some cash.

Denny
MVP
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / SQL 2008 Implementation and Maintenance / Microsoft Windows SharePoint Services 3.0: Configuration / Microsoft Office SharePoint Server 2007: Configuration)
MCITP Database Admin (SQL 2005/2008) / Database Dev (SQL 2005)

My Blog