Eric Wadsworth wrote:
>
> My queries about two of my problems (backing up partial shares in Windows
> boxes, and preventing monstrous report emails which include the list of
> files of windows boxes backed up) have resulted in the same solution:
> install 2.4.2-beta2.
>
> I have some questions:
>
> 1. I generally avoid beta products when working with critical projects.
> The company's backup is considered critical. Just how risky is this beta?
> Worst case scenario: A machine crashes, and I can't restore the data. How
In case of Amanda in order not to be able to restore the data you should
burn down your tape drive and all your tapes :)).
One of the major advantages of Amanda is that it uses standard
utilities.
All you need is dd + tar (or dump).
> unlikely might this be? Other risk: I spend extra time trying to get it to
> work right, but for some reason it's broken, and I have to revert back to
> the release version. I'm interested to hear from those using the beta on
> it's stability.
Yes, it takes some time to learn all the features to tune it up.
But after that it can work in "unattended" mode.
>
> 2. How do I get it? I ftp'd into ftp.amanda.org/pub/amanda and the latest
> there is amanda-2.4.1p1.tar.gz. There is a 'new' subdirectory, but access
> is denied.
cvs
look for "cvs" in Faq-O-Matic page (there is a link on amanda
web-page).
>
> 3. My FreeBSD lets me use the FreeBSD Ports system to install and manage
> software applications. By installing the beta, I suppose I must abandon
> using ports for this app?
I'd not recommend using Amanda neither form from ports nor from
packages.
Personally I run Amanda 2.4.2 form the latest CVS tree on FreeBSD 4.1S
for long time
and I never had any problems with that.
>
> Thanks in advance for your comments.
>
> --- Eric
--
Yuri Pismerov, TUCOWS.COM INC. (416) 535-0123 ext. 352
S/MIME Cryptographic Signature
