I need some help to understand the difference between Express full backup vs. syncronization for SQL protection. I have always thought that the SQL logs were truncated during a Express full backup, but have read several articles that claim the opposite. What is best practise in order to protect SQL DB's in general? And which recovery models should be used (full/simple)?

/Amir

Please read below

Backing up SQL with DPM

Why DPM 2010 and SQL are Better Together?

SQL Logs not getting truncated ? (comments)

SCDPM: Backup SQL and Truncate SQL Logs

Thank you Eugene!

I guess there is no significant changes in DPM 2012 R2 regarding SQL protection?

/Amir

Thank you Eugene!

I guess there is no significant changes in DPM 2012 R2 regarding SQL protection?

/Amir

Not at all!
Yes, you think right! :)

OK :) One last question: one of our customer's DB's are really large (700-800 GB). How many Express full backups are recommended on a daily basis? I guess 15 minutes syncronization schedule is quite natural in that case?

/Amir

OK :) One last question: one of our customer's DB's are really large (700-800 GB). How many Express full backups are recommended on a daily basis? I guess 15 minutes syncronization schedule is quite natural in that case?

/Amir

You are right again!

I recommend (from my experience) one night Express Full Backup (it give high load to SAN (or DAS), network and SQL server) and enable 30 (to begin) or 15 min (more faster copy changes at a block-level).

OK, but the number of syncronizations doesn't affect the max. no of 4200 RP's/week?

/Amir

OK, but the number of syncronizations doesn't affect the max. no of 4200 RP's/week?

/Amir

No, but i recommend to try first of all 30 min and see at load.

Also you must know that restore SQL database from DPM are dependent count of incremental backup. If you have more incr-l backup that and restore will be more longer.