Discussion Locked

Solve this disaster scenario

0 helpful
4 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Take a look at the scenario below and offer your best solution. The most innovative answers will be noted in the Disaster Recovery e-newsletter on July 1, 2003, along with Mike Talon's advice on this particular topic.

In this distributed office solution, the client in question has a series of five remote offices around a central site. Each remote office holds a file server with its own tape backup device that's capable of holding the entire server’s data on a single tape.

The backupsoftware is automated, so the remote offices only need to change the tapes on a regular basis. The technical staff is centered at the central office and only dispatched as needed.

Based on the information provided, what's the primary flaw in thissetup?

If you haven't subscribed to our free DR e-newsletter, be sure to do so today!

https://www.techrepublic.com/techmails.jhtml?repID=r001

4 replies

by hp

(1) The setup relies on remote office people to change tapes. It is very likely that one day somebody will just forget to insert a tape. Luck will have it that this is the very night disaster strikes.

(2) Who monitors the backup successes and failures? There is potential here for people making assumptions about each others' responsibilities.

(3) Is the tape at each remote site sent off-site or is an off-site duplicate produced? Without it, this is not a DR solution.

(4) What if the tape is faulty? If it is a single tape device, the backup system cannot move on to the next tape.

(5) If funds are available, a more automated solution would be better. There are two options:

- Change the backup strategy to backup the data to the central site. This will require network funding. However, depending on the type of data held at the remote sites, there are a number of tools which specialise in low-bandwith backups.

- Change the storage strategy to a central model and deliver the data to the remote sites using thin client technology, if possible, or deploy local caching servers.

by mrwizard10

Here are some other issues:

- There does not seem to be a discussion regarding off site storage of the media once it gets copied. This is a prime consideration should the facility "vanish".

- There was no mention made of a standardized backupmethodology or procedures. If that is not done, then you folks coming on site will have to resurrect what was done before being able to restore it.

- I agree with a centralized solution for at least mission critical data. That should always bebacked up redundantly.

by draco vulgaris

Is there a check in place to be certain that the tapes are actually being changed?

Is there a check in place to ensure that the backups are actually producing readable tapes?

Are the tapes being sent off site?

Is there a documented procedure for restoring these tapes?

Is there a server available to which the tapes can be restored? If not, how long will it take to obtain one in case of need?

If a tape is restored to another server at another site, will the users be able to accessthe data?

Is this "solution" only supposed to enable recovery of the data or must it recover the function of the remote office?

by swade2

The primary flaw is the apparant lack of true disaster recovery planning. Sure, this works great if the file server died, or the file system became corrupt, they could restore it from tape.

The problem is that if there's a disaster, generally that means that more than just the server is affected. The entire computer room, office, city, state, etc. could be affected.

Using the infrastructure in place, I could create a disaster recovery system that would insure maximium data recovery per site. However, this is assuming that each remote office is at least 300 miles away from one another. Have the remote offices send their backups to the central location. If there's a disaster at one of those sites, the technicians could get new hardware, restore the tape they received, and ship the server out to the affected remote site.

If the remote sites are closer, say various places within a city, I would set up a SAN backup, where each remote site might back up another remote site and the 5th site is backed up by the central site. Better yet, put all the backup drives in the central location and run the backups from there.

This discussion is closed to new replies.