11-07-2002
Disaster recovery can be anything from rebuilding a single server to rebuilding a complete data center or business. The biggest part of it (IMO) is the planning of what you will do.
Most IT folks know or have planned how to rebuild a server lost due to any number of reasons (fire, storm, electrical outage). D/R is knowing what you will do if a particular server is down, a particular network is down, a particular site is down....on and on until you know what you are doing from the smallest problem to the biggest (like the WTC).
I don't think many IT folks really had planned for a WTC type disaster. I think it was a great effort by those involved to get the services back SO fast.
Do a search on D/R on the web - there is loads of information to learn more.
9 More Discussions You Might Find Interesting
1. Cybersecurity
Hello,
I am trying to make a disaster recovery of my Unix System.
Is there a site where I can find template from Disaster Recovery Domain. So this can help me to have the principals chapter to make a good report.
Thanks a lot ........ (5 Replies)
Discussion started by: steiner
5 Replies
2. UNIX for Advanced & Expert Users
Can anyone tell me of what to expect? I've been nominated to join a team of unix admins to do a DR testing. we already have the guys who are gono be doing the restores. besides the restore, anybody know what else to look forward to?? (2 Replies)
Discussion started by: TRUEST
2 Replies
3. UNIX for Dummies Questions & Answers
I am looking into disaster recovery and I wanted to know what files and/or other information do I need to keep copies of to sucessfully restore my system from the ground up..... Any help is greatly appreciated. I am running Solaris 8 on an Ultra 60. (5 Replies)
Discussion started by: rod23
5 Replies
4. Solaris
Recovering Solaris to an alternate server
I was just wondering if anyone could give me some points on restoring a Solaris 9 backup to an alternate server. Basically, we use netbackup 6 and I was wondering what the best procedures are for doing this? What things do we need to take into... (3 Replies)
Discussion started by: aaron2k
3 Replies
5. AIX
Are there any products out there that provide a disk imaging solution for AIX (and HPUX and Solaris for that matter)? In a development environment where users are looking to restore an OS quickly back to a certain point in time, what is there available for this besides opening up the system,... (7 Replies)
Discussion started by: tb0ne
7 Replies
6. Solaris
Hello everyone I am Kevin and new to this forum.
I have encounter an issue I can't seem to resolve. I am currently using Solaris 8 02/04 on Sun V240 servers. I know how to create a flar image of the server and restore it using NFS (network server) or Local Tape (tape drive). What I need to do... (2 Replies)
Discussion started by: Kevin1166
2 Replies
7. AIX
Hi Guys,
is it possible to failover a hacmp cluster in one datacentre via SRDF to a single node in another datacentre, or do I need a cluster there in any case? This is only meant as worst case scenario and my company doesn't want to spend more money than absolutely necessary.
I know the... (3 Replies)
Discussion started by: zxmaus
3 Replies
8. UNIX for Dummies Questions & Answers
We have a SCO OpenServer Unix server that has been damaged. Fortunately we have a good backup of the entire system (using BackupEdge.) On a new server, if we install SCO from original SCO CD's (we have all necessary activation codes) then drop the tape (we can restore with tar), will the... (3 Replies)
Discussion started by: jmhohne
3 Replies
9. Red Hat
Hi,
I just want to throw something out there for opinions and viewpoints relating to a Disaster Recovery site.
Besides the live production environment, do you think a DR environment should include:
- pre-production environment
- QA Environment
......or would this be considered to be OTT... (3 Replies)
Discussion started by: Duffs22
3 Replies
LEARN ABOUT DEBIAN
bup-damage
bup-damage(1) General Commands Manual bup-damage(1)
NAME
bup-damage - randomly destroy blocks of a file
SYNOPSIS
bup damage [-n count] [-s maxsize] [--percent pct] [-S seed] [--equal]
DESCRIPTION
Use bup damage to deliberately destroy blocks in a .pack or .idx file (from .bup/objects/pack) to test the recovery features of bup-fsck(1)
or other programs.
THIS PROGRAM IS EXTREMELY DANGEROUS AND WILL DESTROY YOUR DATA
bup damage is primarily useful for automated or manual tests of data recovery tools, to reassure yourself that the tools actually work.
OPTIONS
-n, --num=numblocks
the number of separate blocks to damage in each file (default 10). Note that it's possible for more than one damaged segment to
fall in the same bup-fsck(1) recovery block, so you might not damage as many recovery blocks as you expect. If this is a problem,
use --equal.
-s, --size=maxblocksize
the maximum size, in bytes, of each damaged block (default 1 unless --percent is specified). Note that because of the way bup-
fsck(1) works, a multi-byte block could fall on the boundary between two recovery blocks, and thus damaging two separate recovery
blocks. In small files, it's also possible for a damaged block to be larger than a recovery block. If these issues might be a
problem, you should use the default damage size of one byte.
--percent=maxblockpercent
the maximum size, in percent of the original file, of each damaged block. If both --size and --percent are given, the maximum block
size is the minimum of the two restrictions. You can use this to ensure that a given block will never damage more than one or two
git-fsck(1) recovery blocks.
-S, --seed=randomseed
seed the random number generator with the given value. If you use this option, your tests will be repeatable, since the damaged
block offsets, sizes, and contents will be the same every time. By default, the random numbers are different every time (so you can
run tests in a loop and repeatedly test with different damage each time).
--equal
instead of choosing random offsets for each damaged block, space the blocks equally throughout the file, starting at offset 0. If
you also choose a correct maximum block size, this can guarantee that any given damage block never damages more than one git-fsck(1)
recovery block. (This is also guaranteed if you use -s 1.)
EXAMPLE
# make a backup in case things go horribly wrong
cp -a ~/.bup/objects/pack ~/bup-packs.bak
# generate recovery blocks for all packs
bup fsck -g
# deliberately damage the packs
bup damage -n 10 -s 1 -S 0 ~/.bup/objects/pack/*.{pack,idx}
# recover from the damage
bup fsck -r
SEE ALSO
bup-fsck(1), par2(1)
BUP
Part of the bup(1) suite.
AUTHORS
Avery Pennarun <apenwarr@gmail.com>.
Bup unknown- bup-damage(1)