Two new pieces of information to keep you informed on what is going on with SQL Server database protection and System Center Data Protection Manager 2007 SP1.
As part of Service Pack 1 for DPM, we now have official support for SQL Server 2005 Service Pack 3. This goes both for protected servers as well as the DPM server:
- Production Servers running SP3 for SQL 2005 are now "officially supported" (along with SQL 2008) - You can patch your DPM Server's SQL Server 2005 database to SP3, as well
- Production Servers running SP3 for SQL 2005 are now "officially supported" (along with SQL 2008)
- You can patch your DPM Server's SQL Server 2005 database to SP3, as well
In addition, in order to help folks get more experience with protecting SQL Server with DPM 2007 SP1, we just released a TechNet vLab (Virtual Lab) which is the same VHD environment that we use for all of our hands-on labs (HOL's) at TechEd and that our field uses for demonstrations of DPM 2007. All it takes is a web browser and you can spin up the virtual lab and play with SQL 2005 and SQL 2008 protection -- including recovering SQL 2005 data onto a SQL 2008 box for a very cool migration and test scenario.
We hope everyone, but particularly SQL database administrators and database-integrating channel partners, will come check out how easy it is to use Microsoft's backup and recovery solution that was built for your Microsoft environment
To try out SQL Server database protection, go to How to Protect SQL Server with DPM 2007 SP1
And for more information on SQL protection with DPM in general, including a review by SQL Server Magazine, click here for all of our SQL protection resources by DPM 2007 SP1.
Can you give us any information about the performance impact on SQL 2008 when using the DMP 2007 agent?
When using the DPM 2007 agent on a server running SQL Server 2005 SP3, what process truncates the log? Is the incremental log copy process? If so, can a separate script shrinking the log file be configured in DPM to run after the incremental backup?