Hi Dustin

You have to appreciate a lot of people have AMANDA in production
environments and it is working. We are very reluctant to change it in case
it breaks, we don't want the overhead of having to fix it.

Example we are deploying a 2.5.2 snapshot that has fixes in it that we
raised.

Speaking personally, I will not upgrade my AMANDA environment until I
absolutely have to, as it took quite a bit of effort to get it working
with our changer, kerberos auth and environment.

I am especially nervous to change since AMANDA has changed so much (read -
the change to PERL) and is no longer a straight upgrade with bugfixes and
new features
I personally think this is a failing of the AMANDA team to realise this,
and to see that a lot of sys admins are reluctant to upgrade for these
reasons.


Just my 2c

AlanP

-- 
AlanP

On Tue, August 11, 2009 2:57 pm, Dustin J. Mitchell wrote:
> I'm curious to know who out there is running the daily Amanda snapshots.
>
> A *lot* of new code has gone in since the 2.6.1 release, and I'd like
> to see it tested now, rather than waiting until the beta process
> begins.  We've rewritten the taper to use the transfer architecture;
> rewitten all uses of the old taperscan algorithm to use the simpler
> and more explicit Amanda::Taper::Scan::traditional; rewritten several
> other applications to use the new Changer API; and added a new
> chg-robot to replace the crusty old chg-zd-mtx.  I'm working on
> rewriting the restore/recover applications now.  The idea is to
> completely jettison the old Changer API before the next relase.
>
> So, please let me know if the snapshots are working for you!
>
> Dustin
>
> --
> Open Source Storage Engineer
> http://www.zmanda.com
>