Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 20 Aug 2001 17:14:19 -0400
From:      Bill Moran <wmoran@iowna.com>
To:        joe@jwebmedia.com
Cc:        freebsd-questions@FreeBSD.ORG
Subject:   Re: Unix Backup Options
Message-ID:  <3B817DAB.689A522C@iowna.com>
References:  <3B817889.681AC1C5@jwebmedia.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Joseph Koenig wrote:
> 
> I've been reading about backup options for Unix, and have found the
> standard dump, dd, tar and cpio options. Just wondering if these were
> the commonly used methods, or if there were better methods out there?
> Dump looks pretty useful, but it apparently works best when set up to
> follow an algorithm, which to me, looks difficult to implement via cron.
> Any opinions? Thanks,

I generally use dump as a cron job to do full backups every day (during
off-peak hours) For this, it works great.
If you're filesystem won't fit on a single tape and/or there is some
other reason you can't take this approach, dump does offer options for
incremental backups, I assume this is the "algorithm" you're talking
about. It can be a little confusing.
Also, dump handles multi-tape backups well. I have one client with a
HUGE filesystem setup to rsync to a staging (backup) server during off-
peak hours. The sysadmin can then backup to tape at his leasure during
the day. The backup always comprises at least 2 25G DATs, and sometimes
three.
amanda is a possible option if you have more complex needs. It's in the
ports. I haven't used it so I can't really vouch for it or not.
There is also a commercial product available called BRU. I've not used
it either (so I can't give an opinion) but you can find out more by 
searching http://mall.daemonnews.org

Hope this helps,
Bill

-- 
"Where's the robot to pat you on the back?"

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3B817DAB.689A522C>