I just had a curious question as to how other companies plan their DR in regards to recovering failed servers.  What are the best practices when it comes to this?

Example: a server is backed up to hard drive on another server on-site (copy #1).  This backup server then archives copies of all the backups to a hard drive that can be taken off-site (copy #2).  Then this backup server also syncs to another server at a remote location (copy #3).  The idea of creating another backup that can be taken off-site (just in case the hard drive that was archived to fails) is being tossed around now.

That's one backup on-site, 2 copies that are physically walked out of the building, and one synced to a remote location.  Where does one draw the line?

This is what risk assessments are for. It doesn't sound like there is really a plan, course of action, or any formalized process. What are your ultimately trying to achieve? What is the impact of lost data and/or downtime? You're just going to be grasping at straws if you don't sit down and figure out what you're really trying to achieve. Who knows, you may even find a better way of doing what you need to when you start brainstorming...

Thanks for the tips guys.  Some great questions that I need to be thinking about.  To do list: risk assessment.