Linux-admin Development Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Scott Taylor <scott@mustang.dctchambers.com>
To: linux-admin <linux-admin@vger.kernel.org>
Subject: Re: system backups with zip disks
Date: Mon, 20 Jan 2003 13:43:25 -0800	[thread overview]
Message-ID: <5.1.1.6.0.20030120133124.01c70b08@mustang> (raw)
In-Reply-To: <3E2C58C5.4040707@imagelinks.com>

At 12:15 PM 1/20/03, Jeff Largent wrote:
>Backing up and entire system is a complete waste of time.

I have to disagree with you there Jeff.  I see at least 2-4 updates on 
software packages every week, sure a lot of them are for the same package 
numerous times.

On any *nix system, it's a good idea to backup the entire file system at 
least once a week; who wants to go do all that work again.  And all good 
SysAdmins have a recovery tool, such as BRU, that they can fit onto one 
diskette, boot from it (or a second diskette, or even CD today) and restore 
the entire tape, then a few tweaks and you are back up again.

>The install media is the backup for your programs.
>Back up your configs and data, The progs themseleves can
>be reinstalled faster than you read all of that off of tape.

<snip>

>This should only take you less than an hour and your system will
>be exactly like it was on the date of your last backup.

I doubt any safe, secure,  production system could be restored in even a 
couple of hours just by having all the configs in place.

Jude has the right idea, just the wrong material.

>Jude DaShiell wrote:
>>I was trying to backup the entire contents of the slackware 8.0 system.
>>I didn't figure to have to do this all that regularly but even with cdrw
>>drives that would have used 6 disks by now.  As things stand, everything
>>new I've downloaded I've got backed up.  After that, I'll probably end up
>>backing up /home and /etc directory trees and leave it at that.

BTW Jude,
Don't forget to back up your databases, web pages and other oddball configs 
you might find in /var, /usr/libexec, /usr/share et al.  Never assume all 
configs are where they are supposed to be (/etc), unless you put them there 
yourself. :)

Scott.

This e-mail was scanned by RAV Antivirus. (www.ravantivirus.com)

  parent reply	other threads:[~2003-01-20 21:43 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.33.0301191012210.1273-100000@athame.gmpexpress. net>
2003-01-19 16:11 ` system backups with zip disks Scott Taylor
2003-01-20  2:09   ` terry white
2003-01-20  6:47     ` Jude DaShiell
     [not found]     ` <Pine.LNX.4.33.0301200140550.344-100000@athame.gmpexpress.n et>
2003-01-20 16:39       ` Scott Taylor
2003-01-20 19:25         ` Jude DaShiell
2003-01-20 20:15           ` Jeff Largent
2003-01-20 21:09             ` terry white
2003-01-20 21:28               ` Jeff Largent
2003-01-20 22:14                 ` Scott Taylor
2003-01-20 21:43             ` Scott Taylor [this message]
2003-01-23  0:13             ` Jude DaShiell
2003-01-20  8:32   ` Toby Fisher
     [not found]   ` <Pine.LNX.4.50.0301191800520.1018-100000@yossarian.aniota.n et>
2003-01-20 17:31     ` Scott Taylor
2003-01-19 15:18 Jude DaShiell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5.1.1.6.0.20030120133124.01c70b08@mustang \
    --to=scott@mustang.dctchambers.com \
    --cc=linux-admin@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox