Experiencing downtime is not something that companies wish for but as we
have seen lately it is something that we hear quite often about.
Interestingly enough very few enterprises, especially in the Small and
Medium Business area, spent enough time to work out good procedures for
recovery of their IT systems and applications. The recovery procedures
should always be driven by the business needs, and this is the part where lot
of IT departments are failing and as a result the recovery turns out to be
reactive procedure that is triggered by the issue, results in a chaotic
recovery activities and ends up with post-mortem but no improvements after
that. Putting more initial thought into the Business Impact Analysis (BIA)
is a prerequisite for a good recovery procedures and defining the two main
characteristics - RTO and RPO are crucial part of this process.
Let's star... (more)
Lately we have seen a lot of articles discussing how easy Disaster Recovery
in the cloud is but very few of those put the emphasis on talking about the
basics of Disaster Recovery and educating customers on why they should be
thinking about it. Mostly such articles concentrate on the technologies
that can be uses and how to do Disaster Recovery.
I would like to start with the basics and write about few Myths About
First, let's relate Disaster Recovery to something that is more close to us
in real life. The first thing that comes to mind as an analogy is the
insurance policies that we pay for our health or our home or our car.
Disaster Recovery is almost the same - we invest money in something that we
do not need immediately but that pays off when a disaster occurs. Well, I
write almost because there is a slight difference. Let's take for example ... (more)
Last week's Joyent outage brought us thinking how many IT teams make the
effort what is the meaningful downtime that will not have significant impact
on their business. In this post I will not discuss this particular outage
although it is a yet another good example for improving the IT practices and
processes but will concentrate on an important step in the Business Impact
Analysis (BIA) that is a prerequisite for Disaster Recovery - namely
the Cost of Downtime.
Very often because the lack of understanding of the overall IT application
portfolio the cost of downtime is calculated using made up numbers or
numbers for the whole company. Each application must be considered
separately and the analysis must be done per application - there is no one
size fits all. For now though let's take a simple example: company that has
a revenue of $5o0M and 1500 employees and exper... (more)
Quite often you will hear IT people say that they want the
ultimate automatic disaster recovery solution that you can buy. You can also
find some vendors who can sell you their solution as automatic disaster
recovery solution only because you asked for one. But do you really want
an automatic disaster recovery solution?
We are often victims of our bad understanding of the words but in technology
you need to be very careful what you ask for. If you ask for automatic
disaster recovery solution you may get something that you do not expect. Here
is the scenario.
An automatic disaster recovery solution will be a feature rich solution that
is able to recognize all kinds of "disaster" symptoms like bad weather,
increased humidity around the data center, low power voltage or increased
traffic, and it will trigger automatically the disaster recovery plan. There
are a few p... (more)