Backups are only half the story. The real important part of DR is how fast can you get the databases back to point in time and operational once you have all the backups covered? Your user could care less about your backups. They are however, concerned about your restore process though because that directly affects their downtime. So, automate your restore process by building a job that nightly scripts out and saves all your users database restores (FULL,DIFF,T-Log) right up to point in time including the stop at clause, so that all you have to do is bring the script up in in the Query Analyzer in case of emergency and plug in the stop at time and you are ready to go. This front work will definitely cut your down time drastically and you will sleep much better knowing that those scripts are there everyday. I have this stored procedure/job on every production SQL Server we have. Always remember this, no one appreciates what a DBA does until they cant get to their data!!!!!!!:-D