Re: Is there a write-up on using amvault with an archive config?
I use amvault to tertiarary media (LTO-2, I am just a casual home user)
while my main archive is VTL on a slow NAS. I use cron, but obviously I
could just run as-needed from the command line.
You're right, it is a bit hard to intuit, and I had to get some help
from the community here as it is using overrides.
The command line I use is as follows:
/usr/sbin/amvault -q --latest-fulls --dest-storage "tape_storage" vtl
Where vtl is the config. The key part is the "tape_storage" which
refers to the appropriate vault-storage template in the amanda conf
file. E.g.
storage "vtl"
vault-storage "tape_storage"
define storage "tape_storage" {
erase-on-failure yes
policy "HP_Robot"
runtapes 1
set-no-reuse no
tapedev "LTO-2"
tapetype "LTO2"
tapepool "$r"
tpchanger "LTO-2"
labelstr "Vault-[1-7]"
autolabel "Vault-%" any
}
define changer LTO-2 {
tpchanger "chg-single:/dev/nst0"
device-property "LEOM" "TRUE"
}
define tapetype LTO2 {
comment "HP Ultrium 448, hardware compression off"
length 193024 mbytes
filemark 0 kbytes
speed 20355 kps
}
Obviously for you it will be simpler since you don't have to engage the
SCSI subsystem and define actual tapetype parameters or fiddle with
blocksizes. And you're not limited to a single "tape".
On 2022-03-21 15:46, Jon LaBadie wrote:
*** Apologies if a near duplicate has been posted ***
*** I initially submitted it with the wrong email ***
Amazing, I've used amanda for about 25 years and never set up
an archive config nor used amvault. No time like the present
as I setup a new server with increased capacity.
I don't want an archive config that does periodic massive
dumps. Instead I'd prefer that on-demand I could copy a
level 0 DLE to the archive in such a way that amrecover/
amrestore could use the archive config. Both the source
and the archive destination would be vtapes but on
different drives in different housings.
I "think" that amvault would be the appropriate tool.
If not, correct my error please.
Has anyone done a write-up on setting up and using such
a scheme?
Thanks,
Jon
Is there a write-up on using amvault with an archive config?
*** Apologies if a near duplicate has been posted *** *** I initially submitted it with the wrong email *** Amazing, I've used amanda for about 25 years and never set up an archive config nor used amvault. No time like the present as I setup a new server with increased capacity. I don't want an archive config that does periodic massive dumps. Instead I'd prefer that on-demand I could copy a level 0 DLE to the archive in such a way that amrecover/ amrestore could use the archive config. Both the source and the archive destination would be vtapes but on different drives in different housings. I "think" that amvault would be the appropriate tool. If not, correct my error please. Has anyone done a write-up on setting up and using such a scheme? Thanks, Jon -- Jon H. LaBadie j...@jgcomp.com 154 Milkweed Dr (540) 868-8052 (H) Lake Frederick, VA 22630(703) 935-6720 (M)
RE: Sent out a pull-request to upgrade the packaging system....
Info for Solaris in specific …. The Solaris 10 build needs a lot of downloads from "pkgutil", but folks may be used to these distributed packages. SUNWgcc SUNWhea SUNWlibstdcxx4 SUNWarc SUNWzlib SUNWlibm SUNWcsu SUNWlxml SUNWgnu-gettext SUNWgnome-common-devel SUNWgnome-common-devel-share SUNWgnome-base-libs SUNWgnome-base-libs-devel SUNWgnome-base-libs-devel-share SUNWlxsl SUNWgmake SUNWopenssl-include SUNWgnutls-devel SUNWlibgcrypt-devel SUNWsmbac SUNWsmbau CSWlibtool CSWgmake CSWflex CSWbison CSWautoconf CSWautomake CSWcurl CSWlibcurl-dev CSWlibssl1-0-0 CSWlibncurses5 CSWlibreadline_dev CSWdocbooksxsl CSWlibxsl CSWfakeroot CSWgit CSWlibtool CSWswig CSWgnuplot CSWmtx CSWpkgutil CSWbash CSWggrep CSWgsed Solaris 11 requires (from a while ago??) at least these using “pkg install” (maybe more likely to be installed already) and their depends: gcc-c gnu-binutils gnu-gettext gnu-make gnu-m4 gnu-tar libtool autoconf automake bison flex swig glib2 json-glib readline curl openssl ncurses perl-common mtx libsmbclient gnuplot CSWcoreutils CSWfindutils CSWbash CSWfakeroot CSWgmake I haven’t de-installed everything CSW from Solaris 11, as their “pkgs” repos have become much stronger over the last two years. I’m pretty sure most of the above is correct.. at least to use fakeroot. > -Original Message- > From: Stefan G. Weichinger > Sent: Friday, March 18, 2022 3:31 AM > To: Chris Hassell ; ? amanda users us...@amanda.org> > Subject: Re: Sent out a pull-request to upgrade the packaging system > > WARNING: This email originated from outside of BETSOL. Do not click links or > open attachments unless you recognize the sender and know the content is safe. > > > Am 17.03.22 um 22:28 schrieb Chris Hassell: > > First of many. It is not configured-and-tested as is but it is very > > close to our working version. > > > > -Versioning based on tags from git > > > > -An in-directory build as well as below-directory package build > > > > -Solaris 10 and Solaris 11 packages > > > > -Better handling of pre/post scripts (may need to update Debian > > ones??) > > > > -Systemd services are included as well. > > > > If I can get someone to look over it and give it a spin I’d really > > appreciate it. > > > > I have more fixes for the installcheck directory to allow some good > > and solid self-tests. > > Nice to see progress. > > I assume you want us to try to build the code in that PR? > > pls point to some howto, I can't remember the procedure anymore (autoconf? > etc) > > I can test on Debian 11, for example. Confidentiality Notice | The information transmitted by this email is intended only for the person or entity to which it is addressed. This email may contain proprietary, business-confidential and/or privileged material. If you are not the intended recipient of this message, be aware that any use, review, re-transmission, distribution, reproduction or any action taken in reliance upon this message is strictly prohibited. If you received this in error, please contact the sender and delete the material from all computers.
RE: Sent out a pull-request to upgrade the packaging system....
NOTE: it seems at least gcc 7 is a good idea for the Solaris build. Autoconf 2.69 seems to be the minimal level. To start from a clean set of source. % git clean -dfx % ./autogen ( Not sure if autogen is necessary any more. It can be done automatically in the scripts. ) To build binaries and packages in the top directory (where the source is) ... depending what you are running on. [Same dir setup as old]. % ./packaging/rpm/build client % ./packaging/deb/build client % ./packaging/sun-pkg/build client To build current working dirs in a subdirectory (rpmbuild, debbuild or pkgbuild) and keep the top clear. % ./packaging/rpm/buildpkg client % ./packaging/rpm/buildpkg client % ./packaging/sun-pkg/buildpkg client The Solaris 11 wasn't fully going until today when I adjusted where the license is installed. > -Original Message- > From: Stefan G. Weichinger > Sent: Friday, March 18, 2022 3:31 AM > To: Chris Hassell ; ? amanda users us...@amanda.org> > Subject: Re: Sent out a pull-request to upgrade the packaging system > > WARNING: This email originated from outside of BETSOL. Do not click links or > open attachments unless you recognize the sender and know the content is safe. > > > Am 17.03.22 um 22:28 schrieb Chris Hassell: > > First of many. It is not configured-and-tested as is but it is very > > close to our working version. > > > > -Versioning based on tags from git > > > > -An in-directory build as well as below-directory package build > > > > -Solaris 10 and Solaris 11 packages > > > > -Better handling of pre/post scripts (may need to update Debian > > ones??) > > > > -Systemd services are included as well. > > > > If I can get someone to look over it and give it a spin I’d really > > appreciate it. > > > > I have more fixes for the installcheck directory to allow some good > > and solid self-tests. > > Nice to see progress. > > I assume you want us to try to build the code in that PR? > > pls point to some howto, I can't remember the procedure anymore (autoconf? > etc) > > I can test on Debian 11, for example. Confidentiality Notice | The information transmitted by this email is intended only for the person or entity to which it is addressed. This email may contain proprietary, business-confidential and/or privileged material. If you are not the intended recipient of this message, be aware that any use, review, re-transmission, distribution, reproduction or any action taken in reliance upon this message is strictly prohibited. If you received this in error, please contact the sender and delete the material from all computers.
SV: Sent out a pull-request to upgrade the packaging system....
Hi, I had missed some packets but know autogen works. I'm getting this error. Thanks Gunnar libtool: link: gcc -Wall -Wextra -Wparentheses -Wdeclaration-after-statement -Wmissing-prototypes -Wstrict-prototypes -Wmissing-declarations -Wformat -Wformat-security -Wsign-compare -Wfloat-equal -Wold-style-definition -Wno-strict-aliasing -Wno-unknown-pragmas -Wno-deprecated-declarations "-DAMANDA_FILE=\"amflock-test.o\"" -g -O2 -fno-strict-aliasing -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -o .libs/amflock-test amflock-test.o -L/usr/lib/64 ./.libs/libamanda.so -L/usr/lib/sparcv9 ./.libs/libtestutils.a -lgobject-2.0 -lgthread-2.0 -lglib-2.0 -lsocket -lnsl -lresolv -lintl -lssl -lcrypto -R/opt/lib/amanda ld: fatal: symbol 'tu_debugging_enabled' is multiply-defined: (file amflock-test.o type=OBJT; file ./.libs/libtestutils.a(testutils.o) type=OBJT); collect2: error: ld returned 1 exit status gmake[3]: *** [Makefile:2371: amflock-test] Error 1 gmake[3]: Leaving directory '/root/amanda_compile/amanda-3_5-packaging-upgrade-wip/amanda/common-src' gmake[2]: *** [Makefile:2171: all] Error 2 gmake[2]: Leaving directory '/root/amanda_compile/amanda-3_5-packaging-upgrade-wip/amanda/common-src' gmake[1]: *** [Makefile:1737: all-recursive] Error 1 gmake[1]: Leaving directory '/root/amanda_compile/amanda-3_5-packaging-upgrade-wip/amanda' gmake: *** [Makefile:1661: all] Error 2 -Ursprungligt meddelande- Från: owner-amanda-us...@amanda.org För Gunnarsson, Gunnar Skickat: den 19 mars 2022 11:58 Till: li...@xunil.at; Chris Hassell ; ? amanda users Ämne: SV: Sent out a pull-request to upgrade the packaging system Hi, git clone -b 3_5-packaging-upgrade-wip https://github.com/zmanda/amanda.git git branch * 3_5-packaging-upgrade-wip On solaris these packages are needed pkg install git automake autoconf pkg:/developer/build/libtool gcc cd Amanda ./autogen + set -x + /usr/bin/autoconf configure.ac:25: error: possibly undefined macro: AC_DEFINE If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation. + die 'autoconf [default autoconf version] failed' + echo 'autoconf [default autoconf version] failed' autoconf [default autoconf version] failed + exit 1 This works on the master branch ? Thanks Gunnar -Ursprungligt meddelande- Från: owner-amanda-us...@amanda.org För Stefan G. Weichinger Skickat: den 18 mars 2022 10:31 Till: Chris Hassell ; ? amanda users Ämne: Re: Sent out a pull-request to upgrade the packaging system Am 17.03.22 um 22:28 schrieb Chris Hassell: > First of many. It is not configured-and-tested as is but it is very > close to our working version. > > -Versioning based on tags from git > > -An in-directory build as well as below-directory package build > > -Solaris 10 and Solaris 11 packages > > -Better handling of pre/post scripts (may need to update Debian > ones??) > > -Systemd services are included as well. > > If I can get someone to look over it and give it a spin I’d really > appreciate it. > > I have more fixes for the installcheck directory to allow some good > and solid self-tests. Nice to see progress. I assume you want us to try to build the code in that PR? pls point to some howto, I can't remember the procedure anymore (autoconf? etc) I can test on Debian 11, for example.
