Thanks Gavin and Jon,
Wow that was great help.
Regarding my first question, what should I do with the 'old' labels (the
hard disk) can I delete them?
if not how Amanda knows to write on the new tape drive and not on the hard
disk.
Sincerely,
gil
-----Original Message-----
From: owner-amanda-users AT amanda DOT org
[mailto:owner-amanda-users AT amanda DOT org]On Behalf Of Jon LaBadie
Sent: Friday, February 04, 2005 3:46 PM
To: Amanda-Users
Subject: Re: Getting Amanda to production
On Fri, Feb 04, 2005 at 02:43:55PM -0500, Gil Naveh wrote:
> hello,
>
> I have a few question in mind so I'll be able to better configure it.
> 1) So far I tested Amanda and backed up data on a hard drive and am quit
> happy with the results. Recently we got a new tape drive and I need to
start
> backing up our data into taps. I am going to use the same Amanda server
and
> clients. Should and if so how do I initialize Amanda so it won't care
about
> previous backups? Additionally I'll probably have to do some more testing
in
> order to see how much time/bandwidth Amanda uses when it backup to our
tape
> drive. But after doing those tests - can I delete those files from the
tape?
I'd start a different config for the tape. Currently you probably
do a cronjob with amdump vtapeconfig, simply comment that out entry and
add an amdump realtapeconfig. That way, if you ever need to do vtape
backups again, you can just uncomment it.
>
> 2) I understand that Amanda has its algorithm that decides when do to a
full
> backup, or an incremental one.
> But I am a little confused with labeling tapes. (amlabel)
> When I used the hard-disk I define each hard-drive 'partition' as 4GB
and
> then amlabel each disk e.g.
> #/usr/sbin/amlabel DailySet1 HISS01 slot 1
> #/usr/sbin/amlabel DailySet1 HISS02 slot 2 ...
> However, I have tapes that each can store 400 compress data, and we
have
> to store about 30GB - am I domed to use each tape for one backup
yes
> - or can I 'partition' those tapes?
no
What some who have a large holding disk(s) space is to let several dump runs
collect on the holding disk(s) by not putting a tape in the drive.
Amrecover,
I'm pretty sure, works with the taped or holding disk dumps. Then insert a
tape and amflush them to tape.
> Do I have to put each tape in the tape drive and run amlabel?
yes
>
> 3) We have a local and remote sites that we have to backup any thoughts,
> comments on what should I keep in mine before doing so. Additionally any
> recommendation for what to use to secure our data when backing up
remotely?
> I read that I can use TCP wrappers but how do I implement it with Amanda?
Don't bring them all on line at the same time. Make all your disklist
entries
but put a # sign to comment them out. Uncomment a couple each dump. Run
amcheck
with several from each client uncommented BEFORE even thinking about a dump.
Maybe use your vtape config to test drive a client before moving them to the
big show.
>
> 4) Finally, we have one tape drive and about 20 servers that we need to
> backup from. Some of those servers run on Solaris, some on Windows. Can I
> back all servers on the same tape, or do I need to set separate tapes for
> Win machines?
>
Both can share a config. Lots of ways to do the M$ machines, none fully
satisfactory. Samba clients to one or several of your unix hosts, nfs
shares if your M$ boxes are nfs servers (possibly from M$'s free Services
For Unix product - SFU), some windows backup program that writes to a file
and backup that single file/directory with amanda, install cygwin on each
box and install amanda so it looks like a unix host. Many limitations to
backing up M$ boxes, set your expectations low and you won't be unhappy.
--
Jon H. LaBadie jon AT jgcomp DOT com
JG Computing
4455 Province Line Road (609) 252-0159
Princeton, NJ 08540-4322 (609) 683-7220 (fax)
|
