IT lead does not have a backup, DR plan in writing [closed]

This is a general management question to IT managers out there.

We are a small firm with about 4 servers in our colo cabinent. No full time IT manager. But we do have one person on monthly contract and I am having a terrible time getting him to share what these plans actually are. I am sure he HAS a plan (and its probably in his head..) but that does us no good if he gets hit by a bus..

How would you guys handle this? He is a long time friend, but I fear this is dangerous for us long term..I have confronted him on several occasions about this, and he tells me not to worry, he has got it covered..

Thanks.

First, it's YOUR business and the first step is for YOU to determine what your business continuity and disaster recovery needs and objectives are. Have you defined and documented those? If not, do so. A BC/DR is NOT just about the technology and the data.

Once you've done that you can present them to this person and tell him you need him to provide documentation regarding the technical aspects of your BC/DR plan that supports your BC/DR objectives.

If he's unwilling or incapable of doing so, there's no need to damage or risk the friendship over it. Explain to him why you need this and why you'll need to get another party involved to handle it. If he's a friend and a professional he'll understand and be supportive of your decision.

I'd ask him why he doesn't have one in writing now, what he needs to get that done... and then give it to him and hold him accountable for delivering.

I've been in a number of small shops as the lead or only IT guy, and didn't have a written DR or backup plan because I never had time to write one up, or more than 5 minutes between firefighting excursions. (I've since moved onto consulting and bigger environments, thank God, but it's worth pointing out that you need to both provide him the resources and time to get it done, as well as give him the authority to make it a priority.) It's hard to prioritize documentation and planning over day-to-day firefighting, stupid user tricks and executive privilege requests, largely because everyone else puts a higher priority on their stupid issue than anything else, let alone something like a DR document that can be done "later."