NetWorker Blog

Commentary from a long term NetWorker consultant and Backup Theorist

  • This blog has moved!

    This blog has now moved to nsrd.info/blog. Please jump across to the new site for the latest articles (and all old archived articles).
  •  


     


     

  • Enterprise Systems Backup and Recovery

    If you find this blog interesting, and either have an interest in or work in data protection/backup and recovery environments, you should check out my book, Enterprise Systems Backup and Recovery: A Corporate Insurance Policy. Designed for system administrators and managers alike, it focuses on features, policies, procedures and the human element to ensuring that your company has a suitable and working backup system rather than just a bunch of copies made by unrelated software, hardware and processes.
  • This blog has moved!

    This blog has now moved to nsrd.info/blog. Please jump across to the new site for the latest articles (and all old archived articles).
  •  


     


     

  • Twitter

    Error: Twitter did not respond. Please wait a few minutes and refresh this page.

Posts Tagged ‘obligations’

The 5 Golden Rules of Recovery

Posted by Preston on 2009-11-10

You might think, given that I wrote an article awhile ago about the Procedural Obligations of Backup Administrators that it wouldn’t be necessary to explicitly spell out any recovery rules – but this isn’t quite the case. It’s handy to have a “must follow” list of rules for recovery as well.

In their simplest form, these rules are:

  1. How
  2. Why
  3. Where
  4. When
  5. Who

Let’s look at each one in more detail:

  1. How – Know how to do a recovery, before you need to do it. The worst forms of data loss typically occur when a backup routine is put in place that is untried on the assumption that it will work. If a new type of backup is added to an environment, it must be tested before it is relied on. In testing, it must be documented by those doing the recovery. In being documented, it must be referenced by operational procedures*.
  2. Why – Know why you are doing a recovery. This directly affects the required resources. Are you recovering a production system, or a test system? Is it for the purposes of legal discovery, or because a database collapsed?
  3. Where – Know where you are recovering from and to. If you don’t know this, don’t do the recovery. You do not make assumptions about data locality in recovery situations. Trust me, I know from personal experience.
  4. When – Know when the recovery needs to be completed by. This isn’t always answered by the why factor – you actually need to know both in order to fully schedule and prioritise recoveries.
  5. Who – Know who requested the recovery is authorised to do so. (In order to know this, there should be operational recovery procedures – forms and company policies – that indicate authorisation.)

If you know the how, why, where, when and who, you’re following the golden rules of recovery.


* Or to put it another way – documentation is useless if you don’t know it exists, or you can’t find it!

Posted in Backup theory, NetWorker, Policies | Tagged: , , , , | Comments Off

Obligations were popular in September

Posted by Preston on 2009-10-02

Looking back over September, the most read/visited article was “The 7 Procedural Obligations of Backup Administrators“. The goal of the article was to outline what functions should be at the absolute core of any backup administrators’ role. (This article beat out by a long margin both the long running frequently visited articles “Fixing ‘NSR peer information’” and “Carry a jukebox with you (if you’re using Linux)“.)

There’s a couple of reasons why I think this article was popular:

  • In IT we often work in roles that have informal definitions. While this can sometimes grant flexibility, it can also be a source of frustration for prioritising work or having a clear view of goals, both short-term and long-term.
  • The start of the article defines recoverability as meeting three critical facts. (A lot of the time one of those facts is forgotten when discussing “backup windows”.)

If you haven’t already checked out the article, the number of readers who already have would suggest it’s worth a read.

Posted in Aside | Tagged: , | Comments Off

The 7 procedural obligations of backup administrators

Posted by Preston on 2009-09-16

Hi!

Please read this article over at the NetWorker Information Hub, “The 7 procedural obligations of backup administrators“.

Posted in Backup theory, Ethics, NetWorker | Tagged: , , , , | 10 Comments »

 
Follow

Get every new post delivered to your Inbox.