11-07-2002
IT disaster recovery plans, programs and investments are directly proportional to the degree of risk when the IT systems are down.
Banks, brokers, insurance companies and other similar financial-releated firms tend to have very well financed and supported disaster recovery programs because their entire business is IT related (after all, money is simply numbers in computers, very little cash or other material is actually stored or transferred).
So, in a nutshell, disaster recovery is also known (in some circles) as business continuity planning (in the event of a disaster) and the metric is how fast business can continue in the event of a failure, series of failures, etc.
This can involve setting up IT computing and data centers in other parts of the world (in the event of nuclear attack on a nation!), setting up similar centers in cities a few miles away (in the event of fire or flood), or simply doing back ups on some reliable storage media.
The plans are completely dependent on the degree of risk to life or property (money) to the business (or mission) if the systems are lost.
Disaster recovery is a subset of the overall IT security umbrella known as 'operational risk managment'... where risks are managed with various compensating controls. The controls can be technical, but are also based on policy and business process, insuring insurance coverage, business continuity processes, etc.
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 OSF1
volrecover
volrecover(8) System Manager's Manual volrecover(8)
NAME
volrecover - Performs volume recovery operations
SYNOPSIS
/sbin/volrecover [-g diskgroup] [-sb] [-o options] [volume | medianame...]
OPTIONS
Options that can be specified to volrecover are: Starts disabled volumes that are selected by the operation. Volumes will be started
before any other recovery actions are taken. Volumes will be started with the -o delayrecover start option. This requests that any opera-
tions that can be delayed in starting a volume will be delayed. In other words, only those operations necessary to make a volume available
for use will occur. Other operations, such as mirror resynchronization, attaching of stale plexes and subdisks, and recovery of stale RAID5
parity will normally be delayed. Performs recovery operations in the background. With this option, volrecover will put itself in the back-
ground to attach stale plexes and subdisks, and to resynchronize mirrored volumes and RAID5 parity. If this is used with -s, volumes will
be started before recovery begins in the background. Performs no recovery operations. If used with -s, volumes will be started, but no
other actions will be taken. If used with -p, the only action of volrecover will be to print a list of startable volumes. Prints the list
of selected volumes that are startable. For each startable volume, a line is printed containing the following information: the volume name,
the disk group ID of the volume, the volume's usage type, and a list of state flags pertaining to mirrors of the volume.
State flags and their meanings are: One of the mirrors was detached by an I/O failure One of the mirrors needs recovery, but the
recovery is related to an administrative operation, not an I/O failure Neither kdetach nor stale is appropriate for the volume.
Displays information about each task started by volrecover. For recovery operations (as opposed to start operations), a completion
status is printed when each task completes. Displays commands that volrecover would execute without actually executing them. Lim-
its operation of the command to the given disk group, as specified by disk group ID or disk group name. If no volume or medianame
operands are given, all disks in this disk group will be recovered; otherwise, the volume and medianame operands will be evaluated
relative to the given disk group.
Without the -g option, if no operands are given, all volumes in all imported disk groups will be recovered; otherwise, the disk
group for each medianame operand will be determined based on name uniqueness within all disk groups. Passes the given option argu-
ments to the -o options for the volplex att and volume start operations generated by volrecover. An option argument of the form pre-
fix:options can be specified to restrict the set of commands that the -o option should be applied to.
Defined prefixes are: Applies to all invocations of the volume utility (volume starts, mirror resynchronizations, RAID5 partity
rebuilds, and RAID5 subdisk recoveries) Applies to all invocations of the volplex utility (currently used only for attaching plexes)
Applies specifically to plex attach operations applies specifically to volume start operations Applies to subdisk recoveries Applies
to mirror resynchronization and RAID5 parity recovery
DESCRIPTION
The volrecover program performs plex attach, RAID5 subdisk recovery, and resynchronize operations for the named volumes, or for volumes
residing on the named disks (medianame).
If no medianame or volume operands are specified, the operation applies to all volumes (or to all volumes in the specified disk group).
If -s is specified, disabled volumes will be started. With -s and -n, volumes are started, but no other recovery takes place.
Recovery operations will be started in an order that prevents two concurrent operations from involving the same disk. Operations that
involve unrelated disks will run in parallel.
EXAMPLES
To recover, in the background, any detached subdisks or plexes that resulted from replacement of a specified disk, use the command:
# volrecover -b medianame
If you want to monitor the operations, use the command:
# volrecover -v medianame
SEE ALSO
volintro(8), volplex(8), volume(8)
volrecover(8)