You've put time into implementing a DR solution, performing daily backups and you should. Your organisation will call on you for data recovery when it goes tits up. So, when was the last time you performed a full DR test, restoring all your data back to another server/disk and tried restoring a few files? DR implementation is nothing if it doesn't work when required. It's as important, if not more important to perform quarterly DR tests. You may think you don't have the time, but once you've ran through this exercise a number of times you'll end up with a procedure which can be followed quickly and efficiently. Questions you want to be able to answer once you're happy with the restore procedure.

What is the recovery point? How old will the data been once restored, 24 hours maybe? Assuming you have a full backup off site each day.

What is the recovery time? How long until you can start restoring data on specific servers? If using TSM you may need to restore everything to disk first?

Once you have these answers and experience ask the business what their business continuity plan is, how do they prepare for a disaster. What site do we have on standby, where will we purchase computers and servers from? What services and data are most important to the business. This is the kind of information that until required appears unimportant. If your organisation does not prepare for a disaster it's possible you'll be out of business sooner rather than never.

It's not about backup, it'd about recovery

Cheers
Ryan Partington