• Yes, have one.

    But seriously:

    Start with backups. Identify the Recovery Point Objective (RPO). That's the amount of data that the business is willing to lose. They'll say zero, but that's an impossible number to support. Get them to agree to five minutes worth or fifteen minutes worth, minimum. That will dictate the amount and type of backups you'll need to set up. Then, work out how long it's going to take you to restore your databases, the Recovery Time Objective (RTO) and communicate this to the business. It's largely a matter of the size of your databases, the speed and type of disks you're working with, and the types of backups you have available based on your RPO.

    Communicate all this with the business and ensure that they understand that much of this is dictated by physical laws of the universe, not wishful thinking.

    Then, figure out what they want for availability and uptime. This will lead you towards certain technologies, geographic distribution, web based solutions, etc.

    In short, this a giant topic with tens of thousands of variables. There isn't a "Generic DR Plan" that we can provide for you and you can implement. It completely depends on the needs of your business combined with their willingness to spend money to meet those needs. You'll meet somewhere in the middle, not supporting all their needs necessarily, but spending a lot more money than they wanted to.

    "The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
    - Theodore Roosevelt

    Author of:
    SQL Server Execution Plans
    SQL Server Query Performance Tuning