Sponsored Content
Special Forums Cybersecurity Please Tell Me About Disaster Recovery Post 31420 by Neo on Thursday 7th of November 2002 11:47:48 AM
Old 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

Template for Disaster Recovery

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

Disaster Recovery

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

disaster recovery

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

Disaster Recovery

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

AIX disaster recovery

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

Solaris 8 using Flash Archive for Disaster Recovery

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

hacmp and disaster recovery question

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

Disaster Recovery - Help needed

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

Disaster Recovery

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
vxrecover(1M)															     vxrecover(1M)

NAME
vxrecover - perform volume recovery operations SYNOPSIS
vxrecover [-bcEmnpsvV] [-d defaults_file] [-g diskgroup] [-o options] [-t tasktag] [volume | volume_set | medianame...] DESCRIPTION
The vxrecover utility performs plex attach, RAID-5 subdisk recovery, and resynchronize operations for the specified volumes, for all vol- umes under the specified volume sets, or for volumes residing on the disks specified by medianame. If no medianame, volume or volume_set is specified, the operation applies to all volumes, or to all volumes in the specified disk group. If -s is specified, disabled volumes are started. With -s and -n, volumes are started, but no other recovery takes place. Recovery operations are started in an order that prevents two concurrent operations on the same disk. Operations that involve unrelated disks run in parallel. OPTIONS
-b Performs recovery operations in the background. With this option, vxrecover runs in the background to attach stale plexes and subdisks, and to resynchronize mirrored volumes and RAID-5 parity. If this is used with -s, volumes are started before recovery begins in the background. -c Operates on cluster-sharable disk groups. This option is used by the cluster reconfiguration utility to effect recovery on vol- umes in shared disk groups after the failure of a node in the cluster. Do not use -c as a command-line option. Available only if the Veritas Volume Manager (VxVM) cluster feature is enabled and a license is installed. -d defaults_file Specifies the absolute pathname of a defaults file to use instead of /etc/default/vxrecover. The defaults file can be used to define new values for the I/O region size and delay time when reattaching plexes. The following attributes may be defined in this file: iosize=size Specifies the size (in standard length units as defined in vxintro(1M)) of the regions that are used to perform recovery operations. Specifying a larger size typically causes the operation to complete sooner, but with greater impact on other processes using the volume. The default I/O size is 2048 sectors (1 megabyte). slow=iodelay Allows the impact on system performance of copy operations to be reduced. Plex recovery operations usually consist of a number of short operations on small regions of the volume. This attribute inserts a delay between the recovery of each such region. A specific delay is specified as a number of milliseconds. The default value is 250 milliseconds. The following settings are suggested for a clustered environment with a large number of mirrored volumes: iosize=4m slow=1000 corresponding to an I/O size of 4 megabytes, and an I/O delay of 1000 milliseconds. -E Starts disabled volumes or plexes even when they are in the EMPTY state. This is useful for starting up volumes restored by the vxmake utility when specified along with the -s option. -g diskgroup Limits operation of the command to the given disk group, as specified by disk group ID or disk group name. If no volume or medi- aname is specified, all disks in this disk group are recovered, otherwise, the volume and medianame are evaluated relative to the given disk group. Without the -g option, if no volume and medianame is specified, all volumes in all imported disk groups are recovered; otherwise, the disk group for each medianame specified is determined based on name uniqueness within all disk groups. -m Recognizes and enables volumes that were moved as a result of a disk group move, split or join operation. -n Does not perform any recovery operations. If used with -s, volumes are started, but no other actions are taken. If used with -p, vxrecover only prints a list of startable volumes. -o options Passes the given option arguments to the -o options for the vxplex att and vxvol start operations generated by vxrecover. You can specify an option argument in the form prefix:options to restrict the set of commands that the -o option is applied to. Defined prefixes are: o vol applies to all invocations of the vxvol utility (volume starts, mirror resynchronizations, RAID-5 partity rebuilds, and RAID-5 subdisk recoveries) o plex, applies to all invocations of the vxplex utility (used only for attaching plexes) o attach applies specifically to plex attach operations o start applies specifically to volume start operations o recover applies to subdisk recoveries o resync applies to mirror resynchronization and RAID-5 parity recovery. -p Prints the list of selected volumes that are startable. For each startable volume, a line is printed containing 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 include: o kdetach indicates that one of the mirrors was detached by an I/O failure o stale means that one of the mirrors needs recovery, but that the recovery is related to an administrative operation, not an I/O failure o stopped prints if neither kdetach nor stale is appropriate for the volume. -s Starts disabled volumes that are selected by the operation. Volumes are started before any other recovery actions are taken. Volumes are started with the -o delayrecover start option. This requests that any operations that can be delayed in starting a volume are delayed. That is, only those operations necessary to make a volume available for use occur. Other operations, such as mirror resynchronization, attaching of stale plexes and subdisks, and recovery of stale RAID-5 parity, are typically delayed. -t tasktag If any tasks are registered to track the progress of the operation, marks them with the tag tasktag. This option is also passed to any utilities called to perform recoveries, so all tasks registered by any utility to perform the recoveries are also tagged with tasktag. -v Displays information about each task started by vxrecover. For recovery operations (as opposed to start operations), prints a completion status when each task completes. -V Displays each command executed by vxrecover. The ouput generated is more verbose than the job descriptions printed with the -v option. EXAMPLES
To recover, in the background, any detached subdisks or plexes that resulted from replacement of a specified disk, use the command: vxrecover -b medianame To monitor the operations, use the command: vxrecover -v medianame FILES
/etc/default/vxplex Standard defaults file for vxplex that determines whether FastResync is used when attaching plexes. See vxplex(1M) for details. /etc/default/vxrecover Standard defaults file for vxrecover that is used to set the I/O size and I/O delay values for recovery operations. SEE ALSO
vxintro(1M), vxmake(1M), vxplex(1M), vxvol(1M), vxvset(1M) VxVM 5.0.31.1 24 Mar 2008 vxrecover(1M)
All times are GMT -4. The time now is 09:41 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy