Live recovery CD
Hi, I wonder if anyone ever put together an Amanda live recovery CD. There are many Linux distro that have a live CD, it woul donly nned to add amrecover to that live CD to be up and running. Booting the live CD, one can repartition/reformat his disk, and amrecover will allow to restore the data. Best regards, Olivier
chg-rait error messages and amvault problems
Hello @all,
I get the following error messages if I run amcheck:
slot {11,11}: Can't read label: Inconsistent volume labels/datestamps:
Got D0/20110604180123 on tape:/dev/L700/MRU-LW-1 against
D10020/20110601081910 on tape:/dev/L700/MRO-LW-1.
amcheck-device: Can't call method "make_new_tape_label" on an undefined
value at /usr/local/share/perl/5.10.1/Amanda/Changer.pm line 1582.
I have two robots, in the first one there are tapes labeled starting
with D0 and in the second starting with D1. The thing I am wondering
about is that if I use the normal chg-robot amcheck checks slot 88 in
the first robot, which is a new tape. But if I use chg-rait around the
chg-robot it wants to check slot 11 which is far too new to override!
Before trying this (chg-rait) I used amvault, but this is unusefull if
you want to use "taperflush 100", so only writing full tapes. It will
not vault all dumps then.
Any idea how to get chg-rait working without relabeling all tapes or how
to get amvault to vault all dumps when using taperflush?
--
Mit freundlichem Gruß
Dennis Benndorf
<>
chg-rait error messages and amvault problems
Hello @all,
I get the following error messages if I run amcheck:
slot {11,11}: Can't read label: Inconsistent volume labels/datestamps:
Got D0/20110604180123 on tape:/dev/L700/MRU-LW-1 against
D10020/20110601081910 on tape:/dev/L700/MRO-LW-1.
amcheck-device: Can't call method "make_new_tape_label" on an undefined
value at /usr/local/share/perl/5.10.1/Amanda/Changer.pm line 1582.
I have two robots, in the first one there are tapes labeled starting
with D0 and in the second starting with D1. The thing I am wondering
about is that if I use the normal chg-robot amcheck checks slot 88 in
the first robot, which is a new tape. But if I use chg-rait around the
chg-robot it wants to check slot 11 which is far too new to override!
Before trying this (chg-rait) I used amvault, but this is unusefull if
you want to use "taperflush 100", so only writing full tapes. It will
not vault all dumps then.
Any idea how to get chg-rait working without relabeling all tapes or how
to get amvault to vault all dumps when using taperflush?
--
Mit freundlichem Gruß
Dennis Benndorf
Re: creating a solaris package
On 09/17/2011 02:46 PM, Klas Heggemann wrote: I would split this, to make it possible to share the package between machines sharing /opt perhaps read only (NFS shared or in zones). # Shared binaries and libraries and documentation: /opt/amanada/bin /opt/amanada/sbin /opt/amanda/lib /opt/amanda/share # per host directories /etc/amada # local config files /var/amanda # local machine specific files ? My 5 cents. Klas Heggemann You'd essentially only move the contents of /usr to /opt/amanda/. It's a reasonable suggestion, and is similar to Sun's original intended usage pattern. Klas, have you used sparse-root zones in production? I just want to make sure your suggestion comes from a bit more than glancing over Sun's documentation. That's as much as I did, and I feel a tad uninformed. The opinions don't seem particularly strong here. Since I debated Klas' suggestion myself before sending my original message, I think I'll go with that for the package, unless of course there's some pressing reasons *not* to do it. The build scripts will be in SVN and included in the distribution tarball and I'll try to make it easy to change file locations by just tweaking some variables. Anyone who needs other locations should be able to build a package fairly painlessly. Dan On Sep 16, 2011, at 23:32 , Dan Locks wrote: Hi all, I'm in the process of creating a Solaris package designed to install in a sparse-root zone. Solaris sparse-root zones mount /usr/* read only, so the package can't put files in /usr at all. My first instinct is to use a file-layout which puts *everything* amanda installs in /opt/amanda/. That mean we would have something like: /opt/amanda/bin /opt/amanda/sbin /opt/amanda/lib/amanda /opt/amanda/var/lib/ /opt/amanda/etc/ /opt/amanda/share I'm really not a Solaris admin, so I don't the have experience to know The Right Way to do a sparse-root install. I'd like some input from any Solaris admins or users that either know, or have (non-local-config-dependent) ideas. The source will end up in amanda's SourceForge repository, and the binary package will be on download.zmanda.com. Thanks for any help! Dan Locks
