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

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

Re: Amrecover Issue in 3.4

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

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

* 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

Re: restoring from vtapes on client machine

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

Another 3.4 Issue

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

Re: Another 3.4 Issue

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 Epidemiology

amrecover problems on compressed DLEs

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/ {

Re: Another 3.4 Issue

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

Re: restoring from vtapes on client machine

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