Discussion Locked

Chief disaster recovery officer

0 helpful
21 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
Tell us what you think about the value of having a CDRO to coordinate recovery efforts, as featured in the May 28th Disaster Recovery e-newsletter. What other roles and responsibilities are required of this position?

21 replies

by jklein

Does a large organization really need a CDRO? The duties of a CDRO should fall under the CIO's job. You have to have a disaster recovery plan but does that need to be a full time job even for the biggest organizations? IF your big enough to have a CDRO then your big enough to have built in redundancies so that your organization will not skip a beat. The CIO should look at disaster recovery planning as a project for someone not a career. If you have a CDRO does it not mean that you expect a disaster. If so how would you want to work at what your boss thinks will be the next ground zero?

by nettek

A agree that disaster recovery should be the ultimate responsibility of the CIO, in coordination with a Facilities Manager. After all, once a plan is developed and in place, what would a CDRO do? Sit around and wait for a disaster, I suppose. But ifhe did his job right, he wouldn't be needed in that case either.

What's next, a Chief Electronics Recycling Officer? How about a Chief Microsoft Licensing Officer? Or a Vice President of Inappropriate Internet Usage Monitoring?

by admin

The CDRO could run a lot of simulated exercices or respond to a lot of potential disasters and report heavily on what "could have happened" or perhaps even figure out how to punish people responsible for allowing the possibility of disaster to occurinstead of sitting around "waiting for a disaster" :)

by prefbid ii

A CDRO sounds like the career progression job for the Y2K coordinator. It may be hot on the list of things to do this year, but after it runs its course, what is the poor person going to do? What type of personality does it take to have a full time job of preparing for the next disaster?

Most companies manage to make disaster recovery a part of every job. That is the only realistic way to spread the boredom. If a hundred person organization has enough DR work for one person, splitting the work evenly among 100 is much more realistic. If you need to get started on a DR plan, assign it to a PM and get the ball rolling. However, do the poor PM a favor and keep it a project and let him leave the job after six months to a year.

by miketalonnyc

DR planning can *never* stop, so in six months to a year when the PM leaves, who takes over?

Mike Talon

by prefbid ii

Unless someone just loves that type of punishment, I would recommend rotating the job. It should be one of the those skills that many people get to "taste" in their careers.

by rafiqul.islam

It will be quite apt to play the role of a CDRO by the data centre or infratructure manager. For organisational units or divisions of large MNCs whose earnings fall between 200-250 million US dollars this will be a viable option instead of a new post creation. However for large organizations and particularly for financial institutions the idea of a separate headcount as CDRO merits consideration.

by lafarr

As the "poor person" responsible for planning for my company's four location's next disaster I am appalled at the lack of awareness of the previous responses to the CDRO article. Though I do not have the same title, my job description is essentialy the same - to assess the risk of our sites and implement strategies to reduce them. Whether it be evacuation plans, adjusting our data storage policy, creating a confidential document destruction policy or negotiating a hot site contract, I have the big picture of the company to look at and am not blinded by the sole desire to just recreate the data center. Business continuity is not a project that will "run its course." We have small disasters regularly that cause fines, bad press, etc. and hardware and software upgrades that change your recovery strategy. These situations need to be managed and procedures udpated to reduce the risk and impact of any issues, from negligent third party vendors to internet hackers. Though compelled to "spread the boredom" of my career (yes, it is a career with certifications, associations and master degrees) I believe that I have more than enough work to attend to as well as having it as each associate's objective. Having a coordinator merely ensures that every aspect can be touched upon and every business unit given proper analysis. A project manager working for 6 months will not be able to identify and monitor the workflow and dependancies of the company's critical functions. Morose? A company creating a plan that lays on a shelf is just as sullen as not implementing any measures to provide for the safety of its associates and the well-being of its clients and shareholders. It's not just about earthquakes and planes crashing into buildings anymore. Step into the future of business survival.

by jklein

The duties you seem to be describing would be that of the VP of Corporate Security or Risk Management, which is fine. CDRO sounds like a combat position. Getting a paper cut or stopping a hacker does not warrant the CIB. Business culture tends to label its activities with military or combat connotations. This practice is uncalled for. Lets not over exaggerate what we are doing here. We?re only making money. Leave the Chief Disaster Recovery Officer titles to someone who is actually involved in a real disaster. Losing a directory or have the LA office go down for 2 hours is a problem not a disaster. Disasters are for life risking events not dollar risking events.

A business with the ability to hire a CDRO aught to have enough redundant capability built into their IT infrastructure to make the job moot.

by miketalonnyc

Take a look at a representative sample of companies, and you'll see they do not have the required redundancy to properly and continualy manage Business Continuity Planning.

by prefbid ii

My point was that there is no need for the DR coordinator to be an officer of the company. It trivializes the CIO position and makes the CIO job harder if he/she has to plan for DR, but has no power over DR.

DR is a part of the overall IT job. If it is made a separate "office", then the politics of upper management will take over in the budget wars, etc. and DR will not get done. The person who needs to be part of the DR plan is the technology people who put the working system together. Everyone of them needs to know how to recreate their piece of the system and not some special office that specializes in it.

by tomsal

While I respect Leah's job duties and I know what she is saying (basically that DR is a serious topic to be handled in a professional manner, by a like-minded professional) - I agree with the previous two posters in that a "CDRO" position is not needed.

I really like what Prefbid II had to say...If your IT infrastructure is done right and your CIO is doing his/her job correctly - all the things that Leah points out should be inherently done in the process of daily operations to begin with!
That is part of what a CIO does!

Part of my reaction is that although I'm a team player and I respect those appointed/hire above me, I'm not a very big fan of politics.

I'm the last person who thinks the FIRST answer to a solution is "hey let's make a new position to take care of that, what the heck let's make a whole new department"...

Each executive is akin to a member of congress, the more execs you have the more bickering (in one form or another) you have to get bills passed (ie.get things done).

So, in summation - the idea of DR planning as a monumental task and important...true. But unless you work for an organization where downtime means lives are at stake (not dollars at stake) - there's no need to create dedicate staff and executive positions solely for the purpose of DR planning.

(Btw, it seems to me that some of the most important concepts of DR planning are little more than common sense...like emergency plans for evacuation, redundancy in your data center, off-site storeage of archival files - insurance policies, etc....certainly existing IT management can plan this!)

by generalist

This should be one of the tasks for the CSO, IF the CSO is responsible for all forms of security, not just the IT side.

The CSO should be able to identify the operational weaknesses of an organization and make sure that disasters are self limiting through various techniques. In theory, the CSO knows the core elements of the organization's business functions because those elements are also the ones that must be secured.

With this multi-function knowledge, the CSO should be able to replicate the needed business functions in the event of a disaster. The security 'blueprints' the CSO uses for monitoring can be turned into recovery 'blueprints' for disaster recovery. And security 'tests' could easily include disaster recovery elements.

Of course, in a larger organization, the CSO may have a disaster recovery team composed of experts in the CSO's department and critical end users.

by clinton goveas

I would suggest a DRO post, functionally reporting to the organisation's Business Continuity functional leader.

Then again, the guy could just be a network management specialist with a specific mandate!

by davisda

IT dept. currently implementing detailed drp for all Servers, UPS, PBX. Trying to find software or templates that could greatly reduce the time involved. Any suggestions. We are trying to document every detail for worse case scenario in the event of server crashes or disaster recovery.

by jklein

99% of all companies, mine included cant afford a CDRO no less a redundant system. Management has an understanding that if anything disasterous happens we are gonna be down for a couple of days.
They are unwilling to pay for redundant systems. Its all in the backups basically.

Hell if something like that happens I'm sure the #1 priority would be to find new office space and get a new phone system up.

Fortune 500/1000 companies are another story. They can afford robust redundant systems but as you correctly pointed out most dont. I would think that if your company was going to appoint someone to organize and manage disaster recovery full time then management has recognized a need and should be willing to provide some redundancy. I would think.

by terlajep

A real nice IT coverage however, I think it would have been more informative if a few well known "Proven & Tested" software, hardware and Training locations towards implementing such a rounded out team in this function.
Got any more info to add to this.

by miketalonnyc

I'm not sure what you are asking for here, but I'd like to provide you with whatever information I can give.

We don't mention specific products in this column in order to avoid favoritism, however if you clarify what types of things you are seeking I'd be happy to point out where you can find that type of information, and from there you can get specifics on a wide range of brand names for that type of product and/or service.

Mike Talon

by miketalonnyc

While all of your opinions are both correct and well-rounded, we're leaving out one thing:

The CIO cannot cover all points of Disaster Recovery and Business Continuity Planning, because two-thirds of a BCP are not handled by Technology departments.

Facilities and Human Resources must also be considered as part of a BCP or DR plan, and therefore my suggestion of a single point of contact (who can be an exisiting officer, perhaps the COO) who is responsible for culling information from all these disparate sources.

Mike Talon

This discussion is closed to new replies.