Bill Carlson <[EMAIL PROTECTED]> wrote:

> [...]
> I think amanda falls under the qmail/smtpd category. If you have trouble
> installing it, maybe you should rethink whether you are qualified to 
> implement the backup procedure.

Well... I think if you don't have trouble installing amanda for the
first time, you are either using very good step by step instructions
stating how it is done within your organization... or you are God :)

> I'm not trying to be rude or take the "elite attitude", but there are some 
> systems that should only be admined by qualified individuals; to do 
> otherwise is to create an environment for disaster.

Totally agreed. I also agree backups are a key element not only of
networks, but of corporations. But this does not qualify as a reason
why amanda installation must be complicated and can't be done using
RPM.

It is also true that the (approx.) month of work time that passes
before your amanda backups are safe and in production in a let's say
10 client environment is valuable for the person who does it. You are
getting very good knowledge of the internal processes of amanda almost
automatically by studying the /tmp/amanda/* and amdump files. However,
this will not help your organization when you are gone. Another guy
will start learning it (installing, supervising, restoring) all over
unless you have written the detailed step by step instructions
mentioned above.

But if you *have* written these instructions for all amanda tasks for
your organization so you are replaceable, they will certainly contain
shell scripts which install etc. - close to the same scripts that are
in the RPM package.

By the way, I do not believe in "every network is different". Every
network is similar. There are many more common things in all networks
than differences.

Greetings,
Moritz

Reply via email to