Hi Folks,
I'm working carefully though " [ https://www.zmanda.com/quick-backup-setup.html
| The 15-Minute Backup Solution ] " It is pretty good, but it confuses me a bit
and it has raised questions.
I am in the first client setup section, "Iron". I'm configuring a "tapedev".
The pdf version references this as Section 5.1 and the HTML version doesn't
mention it at all. I am instructed to edit /etc/amanda/amanda-client.conf, in
particular I need to define "tapedev".When I was also told to do this on the
server for the time when I need to backup elements of the server. I have the
same questions in that context.
So, I have a few questions:
* Why is this definition of "tapedev" in /etc/amanda/amanda-client.conf
mentioned in the PDF version, but not in the HTML version? Do I not need to do
this yet, or is this an oversight in the HTML version?
* Assuming that I do have to do this, am I designating capacity to stage
backups, or am I designating an interface of some kind through which backups
will flow?
Now I'm confused about the behavior of AMANDA . I've read about "staging"
backups and how this is a good architecture, and to that end I have installed a
big disk in the AMANDA server, but it is not clear to me if this is a benefit
to me. I will be backing up to NAS, so if I stage my backups on the server, I
need to put everything on the net twice -- once from client to server, and once
from server to NAS. Couldn't I just tell the client, "Put your backup there."
and designate the appropriate NAS?
I'm sure my questions are answered somewhere in some explanation of AMANDA
operations, but I haven't stumbled across this explanation yet, so if you have
one, I'd be most appreciative.
Thanks for the help,
--
Chris.
V:916.974.0424
F:916.974.0428
