Re: restoring from vtapes on client machine

[Debra S Baddorf]

Is this related to the  .amandahosts   file on the server,  which needs to have 
a line for each client,  allowing it to access the index-process
and maybe the tape-process?I have entries like this:

node.FQDN   root amindexd amidxtaped

I’m not certain that both of those are still needed, but there was at one time  
a reason I put them there.

Deb Baddorf


> On Oct 31, 2016, at 12:35 PM, John G Heim  wrote:
> 
> Well, that got me a lot closer. I gave user backup read permission to 
> /etc/amanda/DailySet1/amanda.conf on the "backup" backup server. Now when I 
> run amrecover, I can do a sethost and a setdisk. But after doing so, an ls 
> gives me an empty list. No error message. It's just that there are no files 
> listed. On the real backup server, where the backups are actually being made, 
> I do get a list of files, just as normal. I checked the permissions on the 
> index and info files. They look right.
> 
> 
> Actually, I moved the location of the indexdir and infofile to be on the same 
> remote nfs share as the virtual tapes themselves.  So when I run amrecover on 
> the backup backup server, it is reading the same files as it is when I run it 
> on the real backup server. I think moving those files to the remote nfs 
> server was a good thing, not just for this use but also, now amanda's index 
> and info files are in another building. I would still like to be able to use 
> amrecover on two different hosts in my buildijng though.
> 
> 
> 
> 
> 
> 
> 
> On 10/28/2016 10:52 AM, Jean-Louis Martineau wrote:
>> It is the amindexd process that report the error.
>> Look at its debug file.
>> It is run as your amanda user, did it have permission to read 
>> /etc/amanda/DailySet1/amanda.conf.
>> 
>> Jean-Louis
>> 
>> On 28/10/16 11:08 AM, John G Heim wrote:
>>> I am using the ubuntu amanda-server and amanda-client packages (3.3.6) on 
>>> ubuntu server 16.04 to backup to virtual tapes on an NFS mounted file 
>>> system. Everything is great on the backup server. I can run amrecover 
>>> locally and recover files. But I thought I'd try mounting the  NFS share on 
>>> a client machine to see if I could recover files that way. I thought if the 
>>> backup server ever goes down, I might still be able to recover files on the 
>>> client machine.
>>> 
>>> 
>>> So I installed amanda-server on the client machine and copied the contents 
>>> of /etc/amanda/DailySet1/ to the client. Then I ran:
>>> 
>>> 
>>> # amrecover DailySet1 -o auth=local -s localhost
>>> 
>>> That gives me the error message, ""501 Could not read config file for 
>>> DailySet1!". I amd doing this as root. Root does have permission to 
>>> open/read /etc/amanda/DailySet1/amanda.conf.
>>> 
>>> 
>>> 
>>> 
>>> 
>> 
> 
> -- 
> --
> John G. Heim; jh...@math.wisc.edu; sip://jh...@sip.linphone.org
> 

Re: Another 3.4 Issue

[Debra S Baddorf]

Hmm — Yes, I suppose. Though I’d prefer to get an email either way,
so that I know my batch job is actually running   (assuming I was doing the 
check
as a cronjob).But perhaps they have an option for my viewpoint too.
Deb Baddorf


> On Oct 31, 2016, at 1:08 PM, Steven Backus  wrote:
> 
> When I do amcheck -m -c  I get an email that says:
> 
> (brought to you by Amanda 3.4)
> 
> even though no problems are found.  From the amcheck man page:
> 
> -m
>   Nothing is printed, but mail is sent if any errors are detected.
>   The mail goes to the mailto address specified in the amanda.conf
>   file or the address value if -M is set.
> 
> So I'd consider this to be a bug, albeit a small one.
> 
> Steve
> -- 
> Steven J. BackusComputer Systems Manager
> University of Utah  E-Mail:  steven.bac...@utah.edu
> Genetic EpidemiologyAlternate:  bac...@math.utah.edu
> 391 Chipeta Way -- Suite D  Office:  801.587.9308
> Salt Lake City, UT 84108-1266   http://www.math.utah.edu/~backus

amrecover problems on compressed DLEs

[Ochressandro Rettinger]

I'm running Amanda 3.4 (3.4.1?) from the zmanda RPM, on an RHEL 
7.2 machine.  My client is an RHEL 6.8 machine, running the same generation of 
client, also from the zmanda RPM.

My disklist file was as follows:

backuptest /slash/ {
comp-gnutar-ssh
exclude append "./boot"
exclude append "./var"
}
backuptest /bootgnutar-ssh
backuptest /varcomp-gnutar-ssh-full

with the thought that everything in /boot is compressed already 
anyway, and wanting to test the idea of splitting DLEs up and use different 
backup methods and the like.

Well, the backup went OK, and running amcheckdump on the backup 
showed as OK, but when I went to recover, attempting to recover /slash for 
example, it would start trying to extract the files, and then just hang 
forever.  (Forever in this case being defined as 24 hours.)  However, when I 
tried to recover the /boot DLE, that actually worked.  So, I changed my DLEs to 
all be just plain "gnutar-ssh" type, re-ran the backup, and then attempted to 
recover again, and was successful recovering.

I ran "ps -ef" while the amrecover process was hung, and saw 
that it had spawned a "gzip -dc" process.  So, I presume it was trying to pipe 
compressed data to that process, but somehow, either before or afterwards, it 
was getting lost on its way to the tar process.  Indeed, looking at the debug 
file, I see "amrecover: Spawning "/usr/bin/gzip /usr/bin/gzip -dc" in pipeline".

The last thing in the debug file is "amrecover: 
send_to_tape_server: DATA-READY" until I hit ctrl-C in the amrecover window, at 
which point a "QUIT" was sent by amrecover, presumably to the amandad process 
that it was connected to.

Any thoughts on why this wouldn't be working?  Any thoughts on 
other things I can look at?

-Sandro

Re: Another 3.4 Issue

[Steven Backus]

Jean-Louis Martineau  wties:

> I committed the attached patch to fix the bug.

Thank you Jean-Louis.

Steve
-- 
Steven J. BackusComputer Systems Manager
University of Utah  E-Mail:  steven.bac...@utah.edu
Genetic EpidemiologyAlternate:  bac...@math.utah.edu
391 Chipeta Way -- Suite D  Office:  801.587.9308
Salt Lake City, UT 84108-1266   http://www.math.utah.edu/~backus

Re: amanda-3.4 fails to compile on Debian/Jessie with SSL errors

[Jean-Francois Malouin]

* Jean-Louis Martineau <jmartin...@carbonite.com> [20161031 12:16]:
> How do you configured amanda? Post the complete command line.
> Post the complete ./configure output
> Post the config.log file
> Post the common-src/Makefile file


The config file is very simple and specific to our environment:

./configure \
--prefix=/opt/amanda\
--mandir=/opt/man   \
--with-tmpdir=/var/tmp/amanda   \
--with-amperldir=/opt/amanda/perl   \
--with-config=strange   \
--with-user=amanda  \
--with-group=disk   \
--with-security-file=/etc/amanda/amanda-security.conf \
--with-bsdtcp-security  \
--with-amandahosts  \
--with-tape-device=tape:/dev/nst0   \
--with-tape-server=dow  \
--with-index-server=dow  

Turns out that the package libcurl4-openssl-dev wasn't installed on my
Debian/Jessie host: doing so makes 'make' happy. I tried a few
combinations with '--without-ssl-security'' and '--without-ssh-security'
with no luck.  Maybe those configure flags do nothing.

Somehow libssl-dev is required but not libssh2-1-dev.

thanks,
jf

> 
> Jean-Louis
> 
> On 31/10/16 11:48 AM, Jean-Francois Malouin wrote:
> >Hi,
> >
> >Trying to compile amanda-3.4 on Debian/Jessie leads to this error:
> >
> >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\" -m64 -fno-strict-aliasing -o 
> >.libs/amflock-test amflock-test.o -Wl,--export-dynamic -pthread -pthread 
> >./.libs/libamanda.so ./.libs/libtestutils.a -lrt -lm -lgmodule-2.0 
> >-lgobject-2.0 -lgthread-2.0 -lglib-2.0 -lnsl -lresolv -lcrypto -pthread 
> >-Wl,-rpath -Wl,/opt/amanda-3.4/lib/amanda
> >./.libs/libamanda.so: undefined reference to `SSL_connect'
> >./.libs/libamanda.so: undefined reference to `SSL_CTX_set_verify'
> >./.libs/libamanda.so: undefined reference to `SSL_load_error_strings'
> >./.libs/libamanda.so: undefined reference to `SSL_CTX_check_private_key'
> >./.libs/libamanda.so: undefined reference to `SSL_get_peer_certificate'
> >./.libs/libamanda.so: undefined reference to `SSLv3_server_method'
> >./.libs/libamanda.so: undefined reference to `SSLv3_client_method'
> >./.libs/libamanda.so: undefined reference to `SSL_set_connect_state'
> >./.libs/libamanda.so: undefined reference to `SSL_CTX_new'
> >./.libs/libamanda.so: undefined reference to `SSL_set_accept_state'
> >./.libs/libamanda.so: undefined reference to `SSL_read'
> >./.libs/libamanda.so: undefined reference to `SSL_set_fd'
> >./.libs/libamanda.so: undefined reference to `SSL_get_current_cipher'
> >./.libs/libamanda.so: undefined reference to `SSL_CTX_load_verify_locations'
> >./.libs/libamanda.so: undefined reference to `SSL_CIPHER_get_name'
> >./.libs/libamanda.so: undefined reference to `SSL_CTX_set_verify_depth'
> >./.libs/libamanda.so: undefined reference to `SSL_CTX_use_PrivateKey_file'
> >./.libs/libamanda.so: undefined reference to `SSL_library_init'
> >./.libs/libamanda.so: undefined reference to `SSL_CTX_use_certificate_file'
> >./.libs/libamanda.so: undefined reference to `SSL_CTX_set_cipher_list'
> >./.libs/libamanda.so: undefined reference to `SSL_new'
> >./.libs/libamanda.so: undefined reference to `SSL_write'
> >./.libs/libamanda.so: undefined reference to `SSL_accept'
> >./.libs/libamanda.so: undefined reference to `SSL_CTX_ctrl'
> >collect2: error: ld returned 1 exit status
> >Makefile:2266: recipe for target 'amflock-test' failed
> >make[3]: *** [amflock-test] Error 1
> >
> >What am I missing?
> >
> >thanks,
> >jf
> 

-- 
Jean-Francois Malouin | IT Operations and Infrastructure
McConnell Brain Imaging Centre | MNI | McGill University

Another 3.4 Issue

[Steven Backus]

When I do amcheck -m -c  I get an email that says:

(brought to you by Amanda 3.4)

even though no problems are found.  From the amcheck man page:

 -m
   Nothing is printed, but mail is sent if any errors are detected.
   The mail goes to the mailto address specified in the amanda.conf
   file or the address value if -M is set.

So I'd consider this to be a bug, albeit a small one.

Steve
-- 
Steven J. BackusComputer Systems Manager
University of Utah  E-Mail:  steven.bac...@utah.edu
Genetic EpidemiologyAlternate:  bac...@math.utah.edu
391 Chipeta Way -- Suite D  Office:  801.587.9308
Salt Lake City, UT 84108-1266   http://www.math.utah.edu/~backus

Re: restoring from vtapes on client machine

[John G Heim]

Well, that got me a lot closer. I gave user backup read permission to 
/etc/amanda/DailySet1/amanda.conf on the "backup" backup server. Now 
when I run amrecover, I can do a sethost and a setdisk. But after doing 
so, an ls gives me an empty list. No error message. It's just that there 
are no files listed. On the real backup server, where the backups are 
actually being made, I do get a list of files, just as normal. I checked 
the permissions on the index and info files. They look right.



Actually, I moved the location of the indexdir and infofile to be on the 
same remote nfs share as the virtual tapes themselves.  So when I run 
amrecover on the backup backup server, it is reading the same files as 
it is when I run it on the real backup server. I think moving those 
files to the remote nfs server was a good thing, not just for this use 
but also, now amanda's index and info files are in another building. I 
would still like to be able to use amrecover on two different hosts in 
my buildijng though.








On 10/28/2016 10:52 AM, Jean-Louis Martineau wrote:

It is the amindexd process that report the error.
Look at its debug file.
It is run as your amanda user, did it have permission to read 
/etc/amanda/DailySet1/amanda.conf.


Jean-Louis

On 28/10/16 11:08 AM, John G Heim wrote:
I am using the ubuntu amanda-server and amanda-client packages 
(3.3.6) on ubuntu server 16.04 to backup to virtual tapes on an NFS 
mounted file system. Everything is great on the backup server. I can 
run amrecover locally and recover files. But I thought I'd try 
mounting the  NFS share on a client machine to see if I could recover 
files that way. I thought if the backup server ever goes down, I 
might still be able to recover files on the client machine.



So I installed amanda-server on the client machine and copied the 
contents of /etc/amanda/DailySet1/ to the client. Then I ran:



# amrecover DailySet1 -o auth=local -s localhost

That gives me the error message, ""501 Could not read config file for 
DailySet1!". I amd doing this as root. Root does have permission to 
open/read /etc/amanda/DailySet1/amanda.conf.










--
--
John G. Heim; jh...@math.wisc.edu; sip://jh...@sip.linphone.org

Re: Amrecover Issue in 3.4

[Steven Backus]

Debra S Baddorf  wrote to me:

> When somebody in charge finally reads your notes, I'm sure
> they'll agree.

Not sure if that's what's slowing down amrecover but the 3.4
version is much slower than the 3.3.9 one I was using.  Maybe that
problem will go away when all my backups are done with 3.4.

> I've never seen those numbers. (I'm only at 3.3.8)   

There seems to be no auth = bsd (only auth = bsdtcp) in 3.4 so be
prepared to change that if you decide to upgrade.

Steve
-- 
Steven J. BackusComputer Systems Manager
University of Utah  E-Mail:  steven.bac...@utah.edu
Genetic EpidemiologyAlternate:  bac...@math.utah.edu
391 Chipeta Way -- Suite D  Office:  801.587.9308
Salt Lake City, UT 84108-1266   http://www.math.utah.edu/~backus

amanda-3.4 fails to compile on Debian/Jessie with SSL errors

[Jean-Francois Malouin]

Hi,

Trying to compile amanda-3.4 on Debian/Jessie leads to this error:

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\" -m64 -fno-strict-aliasing -o 
.libs/amflock-test amflock-test.o -Wl,--export-dynamic -pthread -pthread 
./.libs/libamanda.so ./.libs/libtestutils.a -lrt -lm -lgmodule-2.0 
-lgobject-2.0 -lgthread-2.0 -lglib-2.0 -lnsl -lresolv -lcrypto -pthread 
-Wl,-rpath -Wl,/opt/amanda-3.4/lib/amanda
./.libs/libamanda.so: undefined reference to `SSL_connect'
./.libs/libamanda.so: undefined reference to `SSL_CTX_set_verify'
./.libs/libamanda.so: undefined reference to `SSL_load_error_strings'
./.libs/libamanda.so: undefined reference to `SSL_CTX_check_private_key'
./.libs/libamanda.so: undefined reference to `SSL_get_peer_certificate'
./.libs/libamanda.so: undefined reference to `SSLv3_server_method'
./.libs/libamanda.so: undefined reference to `SSLv3_client_method'
./.libs/libamanda.so: undefined reference to `SSL_set_connect_state'
./.libs/libamanda.so: undefined reference to `SSL_CTX_new'
./.libs/libamanda.so: undefined reference to `SSL_set_accept_state'
./.libs/libamanda.so: undefined reference to `SSL_read'
./.libs/libamanda.so: undefined reference to `SSL_set_fd'
./.libs/libamanda.so: undefined reference to `SSL_get_current_cipher'
./.libs/libamanda.so: undefined reference to `SSL_CTX_load_verify_locations'
./.libs/libamanda.so: undefined reference to `SSL_CIPHER_get_name'
./.libs/libamanda.so: undefined reference to `SSL_CTX_set_verify_depth'
./.libs/libamanda.so: undefined reference to `SSL_CTX_use_PrivateKey_file'
./.libs/libamanda.so: undefined reference to `SSL_library_init'
./.libs/libamanda.so: undefined reference to `SSL_CTX_use_certificate_file'
./.libs/libamanda.so: undefined reference to `SSL_CTX_set_cipher_list'
./.libs/libamanda.so: undefined reference to `SSL_new'
./.libs/libamanda.so: undefined reference to `SSL_write'
./.libs/libamanda.so: undefined reference to `SSL_accept'
./.libs/libamanda.so: undefined reference to `SSL_CTX_ctrl'
collect2: error: ld returned 1 exit status
Makefile:2266: recipe for target 'amflock-test' failed
make[3]: *** [amflock-test] Error 1

What am I missing?

thanks,
jf