Sponsored Content
Full Discussion: disaster recovery
Top Forums UNIX for Dummies Questions & Answers disaster recovery Post 50930 by RTM on Wednesday 5th of May 2004 03:10:35 PM
Old 05-05-2004
The quick and easy answer to what files and/or other information do I need to keep copies of to sucessfully restore my system from the ground up:

All of them!


Actually, it depends on what you are going to do - and what type of disaster you are looking to recover from.

Scenario 1 - stupid user removes files he/she needed = Recover from backup tapes

Scenario 2 - stupid System Admin removes files the system needed = Recover from backup and/or rebuild server from scratch and add changed system files from backup, rebuild data from backups.

Scenario 3 - server dies - all disks lost = rebuild from scratch - reload system and data files from backup.

Scenario 4 - natural disaster - fire, tornado... = get new hardware, build from scratch, get backups from off-site, restore system and data files.

Realize that the system files you need to restore are the ones you change - stuff like adding new startup scripts that won't be there after you rebuild from scratch (rebuilding from Solaris cd). Changes to /etc/inittab, /etc/services, specialty files such as DiskSuite config files, Veritas vxprint output, Database configuration files, output from df -k command (showing how things were set up as far as mount)... these type things you may not need if all your servers are built the same with NO deviations. Example - all servers built with same OS - patch level the same - no changes to default system - no application DATA on system drives.

The most important thing you should realize - you need to backup the system and data files so you have something if you do have a disaster to rebuild from.

This also goes for upgrades, adding new software - they don't have to complete sucessfully - the only thing that has to work is how you recover from it. That will save your job more than anything.

Last edited by RTM; 05-05-2004 at 04:18 PM..
 

9 More Discussions You Might Find Interesting

1. Cybersecurity

Please Tell Me About Disaster Recovery

please tell me if this thinkin is correct, if not, please corret me: disaster recovery means when something bad happens and you need to retrieved a backed up file, all you have to do is cd into the tape drive and then look for the file you want and extract it from the drive. is this... (3 Replies)
Discussion started by: TRUEST
3 Replies

2. 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

3. 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

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
XNBD-WATCHDOG(1)					      General Commands Manual						  XNBD-WATCHDOG(1)

NAME
xnbd-watchdog -- Watch a NBD device as started by xnbd-client(1) SYNOPSIS
xnbd-watchdog [--timeout SECONDS] [--interval SECONDS] [--recovery-command COMMAND] [--recovery-command-reboot] [NBD_DEVICE] DESCRIPTION
With the xnbd-watchdog, you can monitor a running nbd-client and trigger actions on failure. OPTIONS
The following options are supported: --timeout SECONDS Triggers the recovery command action if the watchdog process is unable to connect to the NBD_DEVICE within the given timeout. If not given, this defaults to 10 seconds. --interval SECONDS Specifies the polling interval between probes. If not given, this defaults to 10 seconds. --recovery-command COMMAND If given, the COMMAND is executed if the watchdog is unable to connect the NBD device after timeout exceeded. --recovery-command-reboot This argument is a shortcut for --recovery-command 'reboot now'. That is, it will reboot the server upon failure. POSITIONAL ARGUMENTS
The following positional options are supported: NBD_SERVER The local nbd-device to be associated with the remote xnbd-server. SEE ALSO
xnbd-server (8). AUTHOR
The NBD kernel module and the NBD tools have been written by Pavel Macheck (pavel@ucw.cz) and is now maintained by Paul Clements. (Paul.Clements@steeleye.com). The xNBD userland (client and server) have been written by Takahiro Hirofuchi (t.hirofuchi@aist.go.jp) This manual page was written by Arno Toell (debian@toell.net) for the Debian GNU/Linux system (but may be used by others). Permission is granted to copy, distribute and/or modify this document under the terms of the GNU General Public License, version 2, as published by the Free Software Foundation. XNBD-WATCHDOG(1)
All times are GMT -4. The time now is 11:22 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy