Re: moving to amanda 3.3.7p1
On Thu, Feb 26, 2015 at 8:37 AM, Toomas Aas wrote: > Wed, 25 Feb 2015 kirjutas Michael Stauffer : > > >> Directories: >> Application: /usr/local/libexec/amanda/application >> Configuration: /usr/local/etc/amanda >> GNU Tar lists: /usr/local/var/amanda/gnutar-lists >> Perl modules (amperldir): /usr/local/share/perl5 >> Template and example data files (amdatadir): /usr/local/share/amanda >> Temporary: /tmp/amanda >> WARNINGS: >> no user specified (--with-user) -- using 'amanda' >> no group specified (--with-group) -- using 'backup' >> >> >> These are different dir locations than amanda 3.3.4 which I've been using >> until now. Is this b/c I've built from source or is that a change >> effecting >> rpm's too (not that it seems likely they'd be different I figure). >> > > As you deduced, this is probably because of different installation method > (source vs rpm). Whoever supplied the RPMs that you previously used, had > them set up with different configuration settings. > > >> The default user and group is now amanda:backup instead of >> amandabackup:disk. If I want to use this server with existing clients >> running 3.3.4 is this ok? Or should I rebuild with user amandabackup:disk? >> Or upgrade clients to 3.3.7? >> > > The user and group used on the server do not need to be the same as on > clients. You can continue using the existing clients. > > Thanks everyone for the replies. I'll probably just go with what I have since it doesn't seem to matter. -M
Re: moving to amanda 3.3.7p1
> Wed, 25 Feb 2015 kirjutas Michael Stauffer : > >> >> Directories: >> Application: /usr/local/libexec/amanda/application >> Configuration: /usr/local/etc/amanda >> GNU Tar lists: /usr/local/var/amanda/gnutar-lists >> Perl modules (amperldir): /usr/local/share/perl5 >> Template and example data files (amdatadir): /usr/local/share/amanda >> Temporary: /tmp/amanda >> WARNINGS: >> no user specified (--with-user) -- using 'amanda' >> no group specified (--with-group) -- using 'backup' >> >> >> These are different dir locations than amanda 3.3.4 which I've been using >> until now. Is this b/c I've built from source or is that a change effecting >> rpm's too (not that it seems likely they'd be different I figure). > > As you deduced, this is probably because of different installation method > (source vs rpm). Whoever supplied the RPMs that you previously used, had them > set up with different configuration settings. > >> >> The default user and group is now amanda:backup instead of >> amandabackup:disk. If I want to use this server with existing clients >> running 3.3.4 is this ok? Or should I rebuild with user amandabackup:disk? >> Or upgrade clients to 3.3.7? > > The user and group used on the server do not need to be the same as on > clients. You can continue using the existing clients. > > -- > Toomas Aas > If you are more comfortable using the user and group that you USED to use, then start over, and do the configure with —with-user = yourPreferredUser —with-group = yourUsualGroup The user and group you mentioned from the rpms aren’t familiar to me; I’ve always installed from source. It sounds like source and rpms have been different for a long while. You can also specify what directory things should be placed in, if you are used to looking for them there. Deb Baddorf Fermilab smime.p7s Description: S/MIME cryptographic signature
Re: moving to amanda 3.3.7p1
Wed, 25 Feb 2015 kirjutas Michael Stauffer : Directories: Application: /usr/local/libexec/amanda/application Configuration: /usr/local/etc/amanda GNU Tar lists: /usr/local/var/amanda/gnutar-lists Perl modules (amperldir): /usr/local/share/perl5 Template and example data files (amdatadir): /usr/local/share/amanda Temporary: /tmp/amanda WARNINGS: no user specified (--with-user) -- using 'amanda' no group specified (--with-group) -- using 'backup' These are different dir locations than amanda 3.3.4 which I've been using until now. Is this b/c I've built from source or is that a change effecting rpm's too (not that it seems likely they'd be different I figure). As you deduced, this is probably because of different installation method (source vs rpm). Whoever supplied the RPMs that you previously used, had them set up with different configuration settings. The default user and group is now amanda:backup instead of amandabackup:disk. If I want to use this server with existing clients running 3.3.4 is this ok? Or should I rebuild with user amandabackup:disk? Or upgrade clients to 3.3.7? The user and group used on the server do not need to be the same as on clients. You can continue using the existing clients. -- Toomas Aas
Re: moving to amanda 3.3.7p1
>
> These are different dir locations than amanda 3.3.4 which I've been using
> until now. Is this b/c I've built from source or is that a change effecting
> rpm's too (not that it seems likely they'd be different I figure).
>
> The default user and group is now amanda:backup instead of amandabackup:disk.
> If I want to use this server with existing clients running 3.3.4 is this ok?
> Or should I rebuild with user amandabackup:disk? Or upgrade clients to 3.3.7?
>
We have been rebuilding the RPMs from the SRPM (with some minor changes) for
RHEL7 (and CentOS6 and RHEL6). The spec file that ships with the source RPM
specifically creates two variables:
%define amanda_user amandabackup
%define amanda_group disk
In the build section it then defines:
%build
%define config_user %{amanda_user}
%define config_group %{amanda_group}
The configure then specifically calls out those users:
--with-user=%{config_user} \
--with-group=%{config_group} \
So, RPM versions use amandabackup:disk. I would think that’s the ‘official’
default?
Directories are also specifically defined but we make some changes but the only
difference for us is that we change:
-%define PERLSITELIB %(eval "`perl -V:installsitelib`"; echo
$installsitelib)
+%define PERLSITELIB %perl_privlib
This keeps amanda from installing anything into /usr/local.
# Configure directories:
%define PREFIX /usr
%define EPREFIX %{PREFIX}
%define BINDIR %{EPREFIX}/bin
%define SBINDIR %{EPREFIX}/sbin
%define LIBEXECDIR %{EPREFIX}/libexec
%define AMLIBEXECDIR%{LIBEXECDIR}/amanda
%define DATADIR %{PREFIX}/share
%define SYSCONFDIR /etc
%define LOCALSTATEDIR /var
%define AMANDATES %{AMANDAHOMEDIR}/amandates
%define AMANDAHOMEDIR %{LOCALSTATEDIR}/lib/amanda
%ifarch x86_64
%define LIBDIR %{EPREFIX}/lib64
%else
%define LIBDIR %{EPREFIX}/lib
%endif
%define AMLIBDIR%{LIBDIR}/amanda
%define INCLUDEDIR %{PREFIX}/include
%define MANDIR %{DATADIR}/man
%define LOGDIR /var/log/amanda
%define PERLSITELIB %perl_privlib
%define AMDATADIR /var/lib/amanda
# Installation directories:
%define ROOT_SBINDIR%{buildroot}/%{SBINDIR}
%define ROOT_LIBEXECDIR %{buildroot}/%{LIBEXECDIR}
%define ROOT_DATADIR%{buildroot}/%{DATADIR}
%define ROOT_LOCALSTATEDIR %{buildroot}/%{LOCALSTATEDIR}
%define ROOT_SYSCONFDIR %{buildroot}/%{SYSCONFDIR}
%define ROOT_AMANDAHOMEDIR %{buildroot}/%{AMANDAHOMEDIR}
%define ROOT_LIBDIR %{buildroot}/%{LIBDIR}
%define ROOT_MANDIR %{buildroot}/%{MANDIR}
%define ROOT_LOGDIR %{buildroot}/%{LOGDIR}
%define ROOT_AMDATADIR %{buildroot}/%{AMDATADIR}
The fact that these are called out may mean that the ‘official’ directories are
different from the autoconf/configure defaults.
By the way, 3.3.37p1’s spec file doesn’t “natively” compile on RHEL7 (it does
on CentOS7), but you can fix that easily.
Does that help any?
Markus
---
Markus A. Iturriaga Woelfel, IT Administrator
Department of Electrical Engineering and Computer Science
University of Tennessee
Min H. Kao Building, Suite 424 / 1520 Middle Drive
Knoxville, TN 37996-2250
mitur...@eecs.utk.edu / (865) 974-3837
http://twitter.com/UTKEECSIT
moving to amanda 3.3.7p1
Hi, I just built amanda 3.3.7p1 on a CentOS 7 box, to be used as our new backup server with a new tape robot. The config step output this: Directories: Application: /usr/local/libexec/amanda/application Configuration: /usr/local/etc/amanda GNU Tar lists: /usr/local/var/amanda/gnutar-lists Perl modules (amperldir): /usr/local/share/perl5 Template and example data files (amdatadir): /usr/local/share/amanda Temporary: /tmp/amanda WARNINGS: no user specified (--with-user) -- using 'amanda' no group specified (--with-group) -- using 'backup' Two things: These are different dir locations than amanda 3.3.4 which I've been using until now. Is this b/c I've built from source or is that a change effecting rpm's too (not that it seems likely they'd be different I figure). The default user and group is now amanda:backup instead of amandabackup:disk. If I want to use this server with existing clients running 3.3.4 is this ok? Or should I rebuild with user amandabackup:disk? Or upgrade clients to 3.3.7? Thanks. -M
