SQL Server Backup Best Practices and Articles
- SQL Server Backup Best Practices – my own best practices for backing up databases from the 10+ years I’ve been doing it.
- Back Up To The Network, Not Local Disk – I explain why you shouldn’t write your SQL Server backups to the same disks your data lives on.
- Carbonite Failures – I talked about the problems with Carbonite, and what DBAs can learn from them. I also followed up on the Carbonite issues after David Friend (their CEO) commented on the blog.
- Journalspace Failure – another dot-com bites the dust because they didn’t have good database backups.
- Ma.gnolia Backup Failures – online bookmark sharing service couldn’t restore from backups, and went under.
- Browse All Posts Tagged “Backup”
Multi-Part Backup Blog Series
I work for Quest Software, the company that makes LiteSpeed, but long before I came to Quest, I lived and breathed backups. I wrote up a 5-part series about what DBAs need to know about picking the best backup software for SQL Server 2005:
- Backup Software Part 1 – why native SQL Server backups suck.
- Backup Software Part 2 – how quad-core CPUs are changing the game.
- Backup Software Part 3 – new features for backup and restore.
- Backup Software Part 4 – features missing from SQL Server backup software as of 2008.
- Backup Software Part 5 – justifying the cost of third-party backup compression tools.
SQL Server Backup Software Reviews
I work for Quest, so take what I say with a grain of salt. This isn’t marketing, though – this is just my experiences. Some of these were written before I came to work for Quest.
- Microsoft DPM 2007 Review – this backup software is radically different, and there’s some things you want to know when you evaluate it.
- Idera SQLSafe Review – of version 4.5 before I came to work for Quest.
- Idera SQLSafe Followup – I had problems restoring my larger databases, and I discussed the issues I had with support & development.
