Archive for the ‘Disaster Recovery’ Category



Worse Than Failure

Friday, June 12th, 2009

Whether you have your own shop or host your gear somewhere else, this week’s horror story at VAserv should serve as a wake-up call if you’re responsible for safeguarding vital company data, especially your customer’s data.

To briefly sum up the story, hackers took out 100,000, (yes 100,000) web sites, many of them permanently, in an evening’s worth of work.   Just restore the backup, you say?  Not so fast.

VAserv basically offers low-cost Web hosting services using virtualized private servers based on HyperVM. As of Wednesday morning, it was not clear how many of its customers — many of them based in the U.S — had irretrievably lost data in the attack. That number could be high, though, because half of those affected had apparently signed up for an unmanaged service that doesn’t include backups, according to the Register. [emphasis added]

 
And for those customers that did sign up for backup?

A note on VAserv’s Web site, which is now just a text document with details on the company’s restoration efforts, claimed its staff had been working “tirelessly” over the last 48 hours. “However, we have now reached the end of all of our servers, and as such, if your server is not currently up, or not partly up, then it is unfortunate that you will have lost your data due to this third-party attack,” the note said.

Oh the humanity, indeed. ComputerWorld’s Jaikumar Vijayan receives this week’s Master of the Understatement award:

The continuing fallout from a hacking incident at U.K.-based Web hosting company VAserv should serve as a powerful reminder that companies need proper data backup and disaster recovery procedures. The incident, which could result in a fire sale of VAserv to another hosting provider, is also an especially stark example of the kind of havoc that a malicious attacker can wreak on businesses.  [more emphasis added]

 
Can you say ‘class action lawsuit?’

Attempts to reach Rus Foster, VAserve’s director via e-mail and phone were unsuccessful. But the terse updates on the company’s Web site and the thousands of customer posts on a discussion forum painted a picture of total chaos.

I’ve personally reached the end of my physical and emotional tether” Foster wrote in one post on the discussion forum late Tuesday evening. “We have worked pretty much continuously for the last few days firefighting.”

Foster wrote in a post that suggested he was putting the company up for sale. In his note, Foster said he had two options: Do what’s best for the customer base by getting “some big boys in behind” to help get things back up and running. The other he said was to simply “Run away and hide and just say to everyone “good bye”"

 
Run away and hide?  When did that become a viable option for gross negligence?  No one can outrun the long arm of the Bar Association.

matrix42

I’m reminded of a line from The Architect’s classic speech: “There are levels of survival we are prepared to accept.”   There are clearly plenty of folks that seem comfortable managing their IT shops that way.  We see it all the time when we look at their backup strategies and disaster plans, if they have any.  It seems to me that being totally wiped out or having to sell our companies because of something so easily preventable as failed backups is not one of those acceptable levels. But wait, it was those scoundrels the hackers, wasn’t it?  They caused the problem, and they killed the company.  No they didn’t. To be sure, the hackers wreaked havoc, but what they really did was expose the ultimate game-ending event: no backups. Had proper backup procedures been in place and restores regularly tested, the incident would have been merely one of  downtime and possibly SLA penalties. (Yes. I know credit card data was also stolen, but that’s not necessarily a game-ender.)

Being an infrastructure company, we routinely preach about the need for proper backup and restore procedures, and the need to test them.  Sadly, it often falls on deaf ears, and while we do occasionally read an obituary like VAserv’s,  death-by-no-backups is happening all the time in companies you’ll never hear about.

There’s another quote I like from the Matrix: “You hear that Mr. Anderson?  That is the sound of inevitability…it is the sound of your death…”   If you aren’t testing your ability to restore your backups (you do have them don’t you?) , the sound of inevitability may be tolling for you.

Hope is not a strategy.  If backups and restores stress you out, or you’re just hoping they’ll be there when you need them, consider handing it all over to a group of people who live and breathe it. They actually enjoy backups, and they’ll take good care of your gear too.

//spk

Post to Twitter Tweet This Post to Delicious Delicious Post to Digg Digg This Post Post to StumbleUpon Stumble This Post

Hog Wild

Thursday, April 30th, 2009

Try as you might, your IT department won’t be allowed to ignore the current drama surrounding the swine flu outbreak south of the border. While the number of confirmed swine flu deaths is one (yes one) as of this writing, the 7/24 news cycle is in full Doom’s Day mode. Your customers may soon be asking what your plans are because they are just in the process of making their own plans. Unlike “normal” data center disasters like fire or flood, a pandemic scenario is just not on most people’s planning radar.

So what are we in IT do? Chances are you’ve already taken care of it. If you have remote access technology in place for your employees, and you’ve already planned for a building disaster, you’ve probably done as much as you can do unless you can find staff who are impervious to the flu.

Commander Data

The rest is really a matter of business continuity, not disaster recovery.

A relevant article appeared on processor.com a few years ago that stated as much:

A major part of an IT admin’s job during a pandemic will involve remote IT administration. Unlike disaster planning for acts of God, such as floods, fire, or earthquakes, staffers during a pandemic will not immediately seek to relocate.

“One interesting difference between [a pandemic] and another disaster is how everybody cannot just go and work at a different data center. You don’t want to take everybody and put them all in one place,” notes James Governor, an analyst for Redmonk, an analyst firm built on open source. “You do need a distributed and potentially home-working strategy because this is not the same as your [average disaster].”

Enabling staffers to access and perform networking tasks remotely is crucial in the event of a pandemic. “Any establishment worth its salt has good access tools to use the network from wherever they are on the planet. That is just good practice in any case,” Governor says. “And certainly, it is good practice if one is concerned about any potential issues where you might not be able to access the network in a way that you normally would.”

And as Bob DeCoufle pointed out on Tuesday, there is only a remote possibility of needing to invoke your disaster plan, assuming you had a recovery facility “outside of the epidemic region.” How one would anticipate where that would be is another matter, but in any case, few of us have the resources to relocate around a pandemic.

Unless we’re hosting hospital applications or other life support systems, asking our employees to do more than work remotely is probably unrealistic. In a genuine crisis, they will likely be home with their families, and Uncle Sam will probably be calling the shots regardless of our plans.

If by chance you are also required to cover the continuity aspect of your company, Forrester Research offers the following planning tips for a pandemic:

Preparing for a pandemic involves collaboration between all the departments in an enterprise, Forrester Research says. If an outbreak of a contagious virus or disease keeps more than half of all employees from showing up for work, some of the things an organization must do include:

Maintaining inventory and supplier relationships

Providing systematic communications about the outbreak for employees

Making vaccines and medical support for employees available (if possible)

Offering means of transportation to and from work in case public transit systems fail

Providing tools and resources to enable employees to work from home

The phrase “this too shall pass” brings me peace of mind. The swine flu will pass. In the meantime here at DSS, we’ll be making sure our remote access systems are up to snuff and reviewing our staffing plans for the data center. An emergency IT staffing plan should reflect the kind of business you’re in. If your IT systems support the lives of others, you obviously have a greater ethical responsibility than those who are running online shopping sites. For the crisis du jour, you will want to have an appropriate plan for on-site data center support.

And if you put your gear in a facility like this, you’ll have even less to worry about the next time the flu bug oinks in our direction.

That's all Folks!

Post to Twitter Tweet This Post to Delicious Delicious Post to Digg Digg This Post Post to StumbleUpon Stumble This Post


Twitter links powered by Tweet This v1.6.1, a WordPress plugin for Twitter.