Re: Dump failed with data read: recv error: Resource temporarily unavailable after migration of some clients

The debug files are in the debug directory: amgetconf build.amanda_dbgdir Jean-Louis On 23/09/17 07:31 AM, Matthias Teege wrote: > On Fri, Sep 22, 2017 at 01:16:27PM -0400, Jean-Louis Martineau wrote: > > Hi, > > I have again looked more closely. Perhaps the (recv

Re: amvault - using vault-storage section

Gunnar, amanda can do automatic vault to the defined 'vault-storage' (during the amdump run), for that, you need to put a 'vault' in the source storage. Remove the vault-storage setting if you do not want this feature, and you run to run amvault manually. Jean-Louis On 19/09/17 04:02 PM,

Re: dump failed: [request failed: No route to host](too)

Tom, It is the system that return the "No route to host" error. You should check your system log (on server, client, router, firewall, nat, ...) for network error. Jean-Louis On 12/09/17 06:01 PM, Tom Robinson wrote: bump On 11/09/17 12:45, Tom Robinson wrote: > Hi, > > I've recently

Re: client-crc in header (01591e60:14438416) and client-crc in log (38e41ca3:40960) differ

On 12/09/17 01:32 PM, Charles Curley wrote: > On Fri, 8 Sep 2017 09:42:36 -0400 > Jean-Louis Martineau <jmartin...@carbonite.com> wrote: > > > Which version of amanda are you using? > > > > On 09/08/17 05:03 PM, Charles Curley wrote: > > > Does anyone k

Re: client-crc in header (01591e60:14438416) and client-crc in log (38e41ca3:40960) differ

What are the crc logged in the log file for that dump? Post the log.20170908000101.0 file On 12/09/17 03:10 PM, Charles Curley wrote: > On Tue, 12 Sep 2017 14:34:17 -0400 > Jean-Louis Martineau <jmartin...@carbonite.com> wrote: > >> On 12/09/17 01:32 PM, Charles Curley w

Re: client-crc in header (01591e60:14438416) and client-crc in log (38e41ca3:40960) differ

On 12/09/17 01:32 PM, Charles Curley wrote: > > > Can you post the dump header? > > Where do I find it? amfetchdump -p -h CONF HOST DISK DATESTAMP | dd bs=32k count=1 This message is the property of CARBONITE, INC. and may contain confidential or privileged information. If this message has been

Re: client-crc in header (01591e60:14438416) and client-crc in log (38e41ca3:40960) differ

Which version of amanda are you using? On 09/08/17 05:03 PM, Charles Curley wrote: > Does anyone know what this message from amrecover means? Is it a > problem? > > client-crc in header (01591e60:14438416) and client-crc in log > (38e41ca3:40960) differ They should be identical. Can you post

Re: Amanda 3.4.5 – failure dump summary – "shm_ring cancelled"

Are there any other error messages? There is nothing to say without more information. Post the amdump.TIMESTAMP and log.TIMESTAMP.0 files and the dumper, chunker and taper debug files. amanda use shared memory between dumper and chunker/taper, and one process cancelled it. Jean-Louis On

Re: working with storage definitions

orage still references it's own tpchanger and tapetype. On 9/1/17 2:31 PM, Jean-Louis Martineau wrote: > On 01/09/17 02:10 PM, Chris Hoogendyk wrote: > > OK. > > > > So, how does the planner plan for what goes on each storage? > It doesn't, it use the si

Re: working with storage definitions

On 01/09/17 02:10 PM, Chris Hoogendyk wrote: OK. So, how does the planner plan for what goes on each storage? It doesn't, it use the size and plan to dump less than that. That is, if I set up a pseudo tapetype for global and give it a length of, say, 12.5TB; how will it know that the

Re: working with storage definitions

uld add it in a dumptype inherited from all dles. Jean-Louis On 8/29/17 4:21 PM, Jean-Louis Martineau wrote: On 29/08/17 02:37 PM, Chris Hoogendyk wrote: Thank you! I've got that set up now. I tried labeling tapes. I thought it was working. e.g.: You should never use the '-o tpchanger

Re: working with storage definitions

same pool. Jean-Louis On 8/29/17 6:45 AM, Jean-Louis Martineau wrote: > Chris, > > Everything looks good except the 'define changer' should be before the > 'define storage'. > > define changer NEO200x48 { > tpchanger > "chg-robot:/dev/tape/by-id/scsi-1BDT_FlexSt

Re: amfetchdump: ERROR: Attempt to read past tape-end file on Amazon S3

don't how they got erased. Jean-Louis On 29/08/17 07:31 AM, Giorgio Valoti wrote: > Il giorno 29 ago 2017, alle ore 12:36, Jean-Louis Martineau <jmartin...@carbonite.com> ha scritto: > > This error often means that some s3 objects are missing. > > Do some of the data wa

Re: working with storage definitions

Chris, Everything looks good except the 'define changer' should be before the 'define storage'. define changer NEO200x48 { tpchanger "chg-robot:/dev/tape/by-id/scsi-1BDT_FlexStor_II_00MX64200626_LL0" # your changer device file (T48) property "tape-device"

Re: amfetchdump: ERROR: Attempt to read past tape-end file on Amazon S3

This error often means that some s3 objects are missing. Do some of the data was restored? Can you post the amfetchdump debug file? Can you get a list of all objects in the S3 bucket? Jean-Louis On 29/08/17 05:22 AM, Giorgio Valoti wrote: Hi all, I’m testing the restore process with Amanda

Re: chunkers die after update to 3.4.5

Can you post the chunker debug files? Look for error in amdump.1 log file Can you try to run the chunker from the command line? /path/to/chunker CONFIG --log-file /tmp/tmp-chunker-log Jean-Louis On 23/08/17 11:42 AM, Chris Hoogendyk wrote: I updated from Amanda 3.3.6 to Amanda 3.4.5 by

Re: Can't flush older dumps to a tape

Victor, Thanks for your good bug report!!! Try the attached patch, you can manually apply it to the amflush script. Jean-Louis On 16/08/17 09:56 AM, Victor Souza wrote: *Hi everyone!* I've upgraded my amanda version from 3.3.4 to 3.4.4 and I noticed that when I tried to flush older dumps

Re: Compiling 3.4.5 on OpenBSD 6.1

akes, I am new to git) > > ________ > From: Jean-Louis Martineau [jmartin...@carbonite.com] > Sent: Thursday, August 03, 2017 5:29 PM > To: Eric Lovelace; amanda-users@amanda.org > Subject: Re: Compiling 3.4.5 on OpenBSD 6.1 > > Use the attached patch instead of doing the include in

Re: Compiling 3.4.5 on OpenBSD 6.1

/amanda' gmake: *** [Makefile:1637: all] Error 2 From: Jean-Louis Martineau <jmartin...@carbonite.com <mailto:jmartin...@carbonite.com>> Date: Thursday, August 3, 2017 at 9:03 AM To: Eric Lovelace <elovel...@msddecatur.k12.in.us <mailto:elovel...@msddecatur.k12.in.us>>,

Re: Compiling 3.4.5 on OpenBSD 6.1

cros -I config/gnulib -I config/amanda -I config/macro-archive -I /usr/share/aclocal if WANT_CLIENT CLIENT_SUBDIRS = client-src application-src From: <owner-amanda-us...@amanda.org <mailto:owner-amanda-us...@amanda.org>> on behalf of Jean-Louis Martineau <jmartin...@carbonite.com

Re: Compiling 3.4.5 on OpenBSD 6.1

parameter call; I guess when I sit back down in > front of the system in question I will see if I can get enough of a > handle on the code to write the 4 parameter call. > ____ > From: Jean-Louis Martineau [jmartin...@carbonite.com] > Sent: Tuesda

Re: Compiling 3.4.5 on OpenBSD 6.1

How getservbyname_r is defined on OpenBSD 6.1 Jean-Louis On 01/08/17 04:28 PM, Eric Lovelace wrote: > Hello, > > I would like to run Amanda on OpenBSD (Ideally with current versions of > each). From what I have found online, this was possible in previous > versions of both softwares but I can¹t

Re: tcpm_recv_token: invalid size

): CRITICAL **: GLib version too old (micro mismatch): Amanda was compiled with glib-2.32.4, but linking with 2.32.3 Connection closed by foreign host. root@PCILNX01:~# I am using amanda version 3.4.1 on both client and server, what could be the reason? Regards, Dinesh *From:*Jean-Louis Martineau

Re: tcpm_recv_token: invalid size

Dinesh, It is often because amanda receive garbage from the socket. Do amandad was executed on pcilnx01? Check system log on pcilnx01? You can also try a 'telnet pcilnx01 10080' to see if a connection is successful. Jean-Louis On 31/07/17 09:41 AM, Dinesh Vashisht wrote: > > Hi Team, > >

Re: two tape libraries with one configuration

It can only be done with amanda 3.4, where you can define 2 storage and put on the dumptype on which storage you want the dump to go. Jean-Louis On 14/07/17 05:38 PM, Chris Hoogendyk wrote: I've just acquired and set up a new Overland T48 with two LTO7 tape drives. I already have an

Re: Amcheck fails for several clients if one of them is not reachable

This is a long standing bug and is not easy to fix. It is fixed in the not yet release 3.5 branch. All connect system call are done in different thread. All bind system call are done in separate processes. planner, dumper, amcheck, amservice do not require to be setuid root. Only the new ambind

Re: lots of level-0 backups

Amanda promote some dle to level-0 backup to try to balance the size of full done every days. The smaller dles sometime get over promoted. You can set the maxpromoteday to a smaller value for the dle that get over promoted. Jean-Louis On 15/06/17 06:06 AM, hy...@lactose.homelinux.net wrote: >

Release of Amanda-3.4.5

* fix config parser when -o option * fix compilation on FreeBSD * fix planner looping Jean-Louis Martineau This message is the property of CARBONITE, INC. and may contain confidential or privileged information. If this message has been delivered to you by mistake, then do not copy or deliver

Re: security.conf and FreeBSD jails

look for it? Because moving the file to /etc/ gives the following: ERROR: hostname: [Can't get realpath of the security file '/usr/local/etc/amanda/security.conf': No such file or directory] Ekki Am 07.06.2017 um 17:47 schrieb Jean-Louis Martineau: The complete path to security.conf must

Re: security.conf and FreeBSD jails

The complete path to security.conf must be owned and writable only by the root user $ man amanda-security.conf That's why it is by default in /etc and not in /etc/amanda which must be writable by the amanda user. Jean-Louis On 07/06/17 11:37 AM, Ekkehard 'Ekki' Gehm wrote: Ahoi! I ran

Re: Planner in loop, amanda-3.4.4

On 07/06/17 10:53 AM, Stefan G. Weichinger wrote: Am 2017-06-07 um 16:46 schrieb Jean-Louis Martineau: > On 07/06/17 10:43 AM, Stefan G. Weichinger wrote: >> Am 2017-06-07 um 14:08 schrieb Jean-Louis Martineau: >> >> > And please, learn to send good bug report, just

Re: Planner in loop, amanda-3.4.4

On 07/06/17 10:43 AM, Stefan G. Weichinger wrote: Am 2017-06-07 um 14:08 schrieb Jean-Louis Martineau: > And please, learn to send good bug report, just telling a process loop > is not enough.It <http://enough.It> is always better to send more information that nothing. su

Re: Planner in loop, amanda-3.4.4

On 07/06/17 02:59 AM, Stefan G. Weichinger wrote: > Am 2017-05-29 um 12:23 schrieb Jose M Calhariz: >> Hi, >> >> I have a private server of amanda. It is the second time that the >> planner enter in loop and I have to kill for the amdump to finish. >> >> What logs are relevant to help fix the

Re: Out of memory: Killed process 707, UID 0, (amrecover). / Amanda-3.4.4

Bernhard, Thanks for reporting this new issue. I committed the attached patch Jean-Louis On 04/06/17 07:45 AM, Bernhard Erdmann wrote: Hello, after an upgrade to Amanda-3.4.4, I discovered that amrecover eats too much memory. Trying to recover a single directory from a huge GNU tar image

Release of Amanda-3.4.4

(Juno and newer) * labelstr o fix matching a labelstr Jean-Louis Martineau This message is the property of CARBONITE, INC. and may contain confidential or privileged information. If this message has been delivered to you by mistake, then do not copy or deliver this message to anyone

Re: Labelstr issues with 3.4.3

Bonjour Luc, You found a bug, In 3.4, amanda automatically prepend a '^' and append a '$' to the labelstr, It should be done only when using the autolabel template. I applied the attached patch to fix the issue. The work around is to set labelstr to "000[0-9][0-9][0-9].*" Jean-Louis On

Re: amrecover isn't

:37:11 Jean-Louis Martineau wrote: Gene, Which version of tar are you using? 1.27.1 Read the thread at https://www.mail-archive.com/amanda-users@amanda.org/msg48929.html Jean-Louis Says 1.29 fixes this. I'll have to build it from the tarball, 1.27.1 is the newest in the wheezy repo's.

Re: amrecover isn't

Gene, Which version of tar are you using? Read the thread at https://www.mail-archive.com/amanda-users@amanda.org/msg48929.html Jean-Louis On 30/04/17 10:52 PM, Gene Heskett wrote: > Greetings all; > > The last time I used amrecover I had to make a tempdir on the same disk > as the stuff I

Re: strange initial backup - crc difference

On 24/04/17 06:29 PM, Jon LaBadie wrote: > I just added a new DLE to my disklist and ran a > "no-taper" dump of just the new DLE. The amdump > report listed it as "STRANGE" and showed an > error I do not recall seeing before: > >sendbackup: native-CRC 3faac26a:42524590080 >sendbackup:

Re: Ubuntu 16.04 amanda-client package

in the dumptype. At the moment, I'm getting "Permission denied (publickey,password)." during amcheck. Something is not correctly set for ssh, check ssh and sshd logs files. Run the ssh command from the command line Jean-Louis On 4/14/17 12:07 PM, Jean-Louis Martineau wrote: Chris,

Re: Ubuntu 16.04 amanda-client package

ackup"? I'd prefer to do it as intended rather than hacking. One would presume that should be smoother, assuming the intended setup is known (documented). On 4/14/17 8:29 AM, Jean-Louis Martineau wrote: Chris, We could help if you tell us what doesn't work. Jean-Louis On 13/04/17 03:53

Re: Ubuntu 16.04 amanda-client package

Chris, We could help if you tell us what doesn't work. Jean-Louis On 13/04/17 03:53 PM, Chris Hoogendyk wrote: I have a group of amanda servers and clients that are all Ubuntu 14.04 with amanda 3.3.6 installed from source with ssh config and user amanda. Now I'm trying to set up a new

Re: Ubuntu 16.04 amanda-client package

On 13/04/17 07:38 PM, Charles Curley wrote: > On Thu, 13 Apr 2017 22:42:06 + > Debra S Baddorf wrote: > >> Q to others: does the client have to have the same username and >> locations as the server? No, they do not need to be the same. Jean-Louis This message is the

Re: lots of level-0 backups

On 11/04/17 11:41 AM, hy...@lactose.homelinux.net wrote: > Jon LaBadie writes: >> On Mon, Apr 10, 2017 at 10:45:52PM -0400, hymie! wrote: >>> On Mon, Apr 10, 2017 at 04:14:25PM -0400, Jon LaBadie wrote: Do you mean you do not understand the mechanics of splitting a DLE or that you do not

Re: amflush

/CORE/libperl.so #7 0x7fcbe843c9a5 in perl_run () from /usr/lib64/perl5/CORE/libperl.so #8 0x00400d99 in main () -Sandro *From:*Jean-Louis Martineau [mailto:jmartin...@carbonite.com] *Sent:* Tuesday, April 11, 2017 9:00 AM *To:* Ochressandro Rettinger <orettin...@salud.unm.edu>;

Re: amflush

I want the stack trace of all threads,not only the main thread. in gdb for the taper process, do: thread apply all bt Jean-Louis This message is the property of CARBONITE, INC. and may contain confidential or privileged information. If this message has been delivered to you by mistake, then do

Re: amflush

It looks like the taper process is hang. Can you post the taper debug file? Can you get a gdb stacktrace of all threads? Jean-Louis On 11/04/17 10:12 AM, Ochressandro Rettinger wrote: > In fact, I am now sure that it's not doing anything. I ran amstatus > this morning and it looks

Re: force an estimate?

man amadmin: estimate [ hostname [ disks ]* ]* Print the server estimate for the dles ... The answer is NO, since 'amadmin estimate' only print the server estimate (based on history). The best tool is du. Jean-Louis On 10/04/17 07:06 AM, hy...@lactose.homelinux.net wrote: >

Re: how to change the amandad server (3.4.3) listening service port?

On 29/03/17 02:34 PM, Jean-Francois Malouin wrote: > Hi, > > For whatever reasons I'm stuck for a little while with an amanda server > with 2 different installations (one is community version 3.4.3 and the > other is a zmanda enterprise edition running 3.3.9). I'd like to have > them running

Re: change hostname of pre-existing backups?

Nothing can be done. The backup are done with the 'localhost' hostname You must use it when restoring. Jean-Louis On 23/03/17 09:50 AM, hy...@lactose.homelinux.net wrote: > Greetings. > > For the past couple of years, I've been using amanda to back up the > server amanda was running on, and I

Re: amlabel (v3.4.3) doesn't write tape line when first creating tapelist file

Nathan, Thanks for reporting the issue. I committed the attached patch. Jean-LouisOn 15/03/17 06:27 PM, Nathan Stratton Treadway wrote: > Summary: if the "tapelist" file doesn't exist, amlabel creates the file > but doesn't populate it. (Again, this is using Amanda 3.4.3.) > > (In the following

Re: labelstr check missing in amlabel (v3.4.3)?

Nathan, Thanks for reporting the issue. I committed the attached patch. Jean-Louis On 15/03/17 05:45 PM, Nathan Stratton Treadway wrote: > I'm running Amanda 3.4.3 (built under Ubuntu from Jose's Debian > "experimental" source package, v3.4.3-1). > > The man page for "amlabel" includes the

Re: AW: Released in Debian, on experimental, amanda-3.4.3

Why do you ran amcleanup? There is nothing to clean if the /var/lib/amanda/a2g-1/log/log symlink doesn't exists. Jean-Louis On 13/03/17 08:58 AM, Tobias Köck wrote: > Hi Jose, > > I get a while trying to cleanup > > backup@chronos:/u1/bin$ amcleanup -k a2g-1 > amcleanup: Can't open trace_log

Re: ambackup level 0 only

On 12/03/17 02:09 PM, Jon LaBadie wrote: > I've gotten a couple of DLEs to do a "backup on > demand" using ambackup. Two things I've noted: > > - each DLE is considered a separate backup and > thus generates a separate report for each yes, there is no fix yet. > > - so far (4 dumps of 3

Re: Errors when try to do backup.

for it to finish. Thanks! On 2017/3/10 21:03, Jean-Louis Martineau wrote: The patch fixed the dumper crash (fater the data timeout), but you must find why you get the data timeout. You must check the client debug file: amandad ,sendbackup, ... Jean-Louis On 09/03/17 11:10 PM, Yiyi Hu wrote

Re: Amanda Busy [revisited] -- now ambackupd

Jon, Another bogus check, it must be removed. Apply the attached patch. Jean-Louis On 09/03/17 02:35 PM, Jon LaBadie wrote: > On Thu, Mar 09, 2017 at 09:10:49AM -0500, Jean-Louis Martineau wrote: >> Jon, >> >> You can remove the faullty 4 lines. >> 3.4 can do

Re: Errors when try to do backup.

2:00, Jean-Louis Martineau wrote: Yiyi, Try the attached patch Jean-Louis On 09/03/17 04:27 AM, Yiyi Hu wrote: > Hi, > > After I upgraded to3.4.3 on my gentoo system, > > I get errors when I try to do the backup. > > The errors are > > FAILURE DUMP SUMMARY: > chu

Re: Amanda Busy [revisited]

Jon, You can remove the faullty 4 lines. 3.4 can do multiple backup in parallel. Instead of using amdump_client/amdumpd, you should use ambackup/ambackupd. amdump_client/amdumpd is the old protocol and is kept only for compatibility with 3.3 Jean-Louis On 08/03/17 02:19 PM, Jon LaBadie wrote:

Re: Errors when try to do backup.

Yiyi, Try the attached patch Jean-Louis On 09/03/17 04:27 AM, Yiyi Hu wrote: Hi, After I upgraded to3.4.3 on my gentoo system, I get errors when I try to do the backup. The errors are FAILURE DUMP SUMMARY: chunker: FATAL Can't use an undefined value as a subroutine reference at

Re: Errors when try to do backup.

Tiyi, Can youpost the complete chunker debug file? Jean-Louis On 09/03/17 04:27 AM, Yiyi Hu wrote: Hi, After I upgraded to3.4.3 on my gentoo system, I get errors when I try to do the backup. The errors are FAILURE DUMP SUMMARY: chunker: FATAL Can't use an undefined value as a subroutine

Re: Release of Amanda-3.4.3

On 03/03/17 11:30 AM, Gene Heskett wrote: > On Friday 03 March 2017 08:50:00 Jean-Louis Martineau wrote: > >> Hello, >> >> The Amanda core team is pleased to announce the release of Amanda >> 3.4.3 >> >> There is a major issue in 3.4, 3.4.1 and 3.4.2, al

Release of Amanda-3.4.3

-Louis Martineau

Re: tapelist format

Jon, Can you try the attached patch? On 25/02/17 01:58 PM, Jon LaBadie wrote: > I'm getting a lot of these messages in my nightly report > >planner: Last full dump of cyber.jgcomp.com:Home on tape DS1-084 > overwritten in 1 run. >planner: Last full dump of cyber.jgcomp.com:Vault on tape

Re: amanda-3.4.2: amrecover doesn't do recursive restores?

mcgill.ca> [20170222 > 12:09]: >> * Jean-Louis Martineau <jmartin...@carbonite.com> [20170222 11:02]: >>> Jean-Francois, >>> >>> Which application are you using? >> amgtar >> >>> Post the debug files, amrecover and th

Re: amanda-3.4.2: amrecover doesn't do recursive restores?

Jean-Francois, Which application are you using? Post the debug files, amrecover and the one for the application. Jean-Louis On 22/02/17 10:52 AM, Jean-Francois Malouin wrote: > Hi, > > I had this buried into another post... > > When using amrecover, 'add .' at the prompt of amrecover will not >

Re: A few minor fixups

On 21/02/17 05:28 PM, Charles Curley wrote: > While working on 1:3.4.2-1~rc2 for Debian: > > In the sample amanda.conf: > > define tapetype HARD-DISK { > global > comment "DAT tape drives" > # data provided by Rob Browning > length 1930 mbytes >

Re: amfetchdump returns 'Error writing to fd 7: Broken pipe'

On 20/02/17 11:47 AM, Jean-Francois Malouin wrote: > Hi, > > Attempting to restore a DLE with amfetchdump with: > > su amanda -c "~amanda/sbin/amfetchdump -p -d tape:/dev/nst0 top localhost > /data_/mica1 20170219 " | tar -xpGf - > > returns 'Error writing to fd 7: Broken pipe'. The logfile

Re: Result of backup is FLUSH from client with 3.4.1

? Where should I report a bug, amanda or Fedora? There are an installed amanda-policy: [root@uw000140 ~]# semodule -v -l | egrep amanda amanda Must I add the my-amandad policy after every reboot or when should I remove it? BR, Henrik On 2017-02-18 14:09, Jean-Louis Martineau wrote: Henrik

Re: segfault from planner (3.4.2-1)

Uwe, Thanks for your good bug report and patch. Can you tried the attached patch instead of yours? Jean-Louis On 18/02/17 06:31 PM, Uwe Menges wrote: Hi, Today I got a segfault from planner when I tried to run the weekly backup on my Fedora 24 workstation: Feb 18 12:16:26 lima audit[4905]:

Re: Result of backup is FLUSH from client with 3.4.1

From server /tmp/var_log_amanda_server_DailySet1_20170130.tgz From server /tmp/var_lib_amanda_DailySet1_20170130.tgz BR; Henrik On 2017-02-01 17:02, Jean-Louis Martineau wrote: Post more information. The amdump., log..0 and all debug files. Jean-Louis On 01/02/17 03:11 AM, Henrik Johansson wrote

Re: amsamba ignore property?

On 14/02/17 08:52 AM, Stefan G. Weichinger wrote: Am 2017-02-14 um 14:33 schrieb Jean-Louis Martineau: Stefan, Try this patch. JL, great, amcheck without error now. amdump later this evening, thanks. Stefan, Can you confirm the patch works? For backup and recovery? Jean-Louis

Re: how to use taper-parallel-write effectively?

On 14/02/17 12:51 PM, Jean-Francois Malouin wrote: > * Jean-Louis Martineau <jmartin...@carbonite.com> [20170214 12:39]: >> On 14/02/17 12:18 PM, Jean-Francois Malouin wrote: >>> Hi, >>> >>> I've never really understood how to make use of the amand

Re: how to use taper-parallel-write effectively?

On 14/02/17 12:18 PM, Jean-Francois Malouin wrote: > Hi, > > I've never really understood how to make use of the amanda.conf > parameter 'taper-parallel-write'. > > I have this tape library with 2 LTO6 tape drives and in the amanda > (3.4.2) config storage section I have set taper-parallel-write=2

Re: amsamba ignore property?

Stefan, Try this patch. Jean-Louis On 14/02/17 08:04 AM, Stefan G. Weichinger wrote: Am 2017-02-14 um 13:05 schrieb Jean-Louis Martineau: On 14/02/17 04:38 AM, Stefan G. Weichinger wrote: Is there a "ignore" for amsamba as well? no manpage doesn't tell. I have to ignore that

Re: amsamba ignore property?

On 14/02/17 04:38 AM, Stefan G. Weichinger wrote: > Is there a "ignore" for amsamba as well? no > manpage doesn't tell. > > I have to ignore that: > > > Amanda Backup Client Hosts Check > > ERROR: booze: smbclient: WARNING: The security=share option is deprecated

Re: 3.4: eject-volume=yes with interactivity keeps tape device open

to finish both tapes. Will try a real backup next week. Thanks alot, Thilo On 09/02/17 17:33, Jean-Louis Martineau wrote: This patch is also needed. Please try them and let me know if they works. Jean-Louis On 09/02/17 10:58 AM, Jean-Louis Martineau wrote: Hi, Can you try the attached patch

Re: recent amanda on Debian?

valgrind is a useful tool to find memory corruption. Try the attached patch. Jean-Louis On 10/02/17 09:35 AM, Jean-Francois Malouin wrote: > * Jean-Louis Martineau <jmartin...@carbonite.com> [20170210 07:54]: >> Jean-Francois, >> >> I was not able to find the

Re: recent amanda on Debian?

-resolution=high --track-origins=yes amadmin top tape And send me the resulting valgrind.amtape.output file. Jean-Louis On 09/02/17 02:19 PM, Jean-Francois Malouin wrote: > * Jean-Louis Martineau <jmartin...@carbonite.com> [20170209 14:09]: >> Jean-Francois, >> >>

Re: recent amanda on Debian?

Jean-Francois, Can you run amadmin in gdb and get a stacktrace? $ gdb ~amanda/sbin/amadmin (gdb) run top tape (gdb) bt (gdb) quit Jean-Louis On 09/02/17 01:56 PM, Jean-Francois Malouin wrote: > * Stefan G. Weichinger [20170209 13:36]: >> Does anyone use amanda 3.4.2 packages

Re: 3.4: eject-volume=yes with interactivity keeps tape device open

This patch is also needed. Please try them and let me know if they works. Jean-Louis On 09/02/17 10:58 AM, Jean-Louis Martineau wrote: Hi, Can you try the attached patch. Jean-Louis On 08/02/17 12:58 PM, ts...@portrix-systems.de <mailto:ts...@portrix-systems.de> wrote: > Hi,

Re: 3.4: eject-volume=yes with interactivity keeps tape device open

Hi, Can you try the attached patch. Jean-Louis On 08/02/17 12:58 PM, ts...@portrix-systems.de wrote: Hi, tried this with: http://www.zmanda.com/downloads/community/Amanda/3.4.2/Redhat_Enterprise_6.0/amanda-backup_server-3.4.2-1.rhel6.x86_64.rpm (and also 3.4.1) Oracle Linux Server release

Re: ERROR smbclient: NT_STATUS_ACCESS_DENIED on some files => Amanda doesn't backup anything on that share

The problem look to be that smbclient do not print the 'Total number of bytes' on it's stderr, so the estimate will never succeed. You can try to set: 'estimate server' for that dle. But you will probably get a similar error when doing the backup. What can we do if smbclient do not tell if the

Re: Build problem amanda-3.4.2 sparc Solaris 11

The attached get_sse42.diff patch is required. Jean-Louis On 06/02/17 08:14 AM, Gunnarsson, Gunnar wrote: > Hi > > I'm building amanda-3.4.2 on SunOS 5.11 11.2 sun4v sparc sun4v using gcc: > gcc --version > gcc (GCC) 4.5.2 > > cal/lib/amanda > Undefined first referenced >

Re: big update killed 1 host

Ask the amanda and systemd package maintainer for centos. Since your problem is to backup the amanda server,you can try to use the "local" auth. Jean-Louis On 02/02/17 04:04 PM, Jon LaBadie wrote: > On Sun, Jan 29, 2017 at 10:45:37PM -0500, Jon LaBadie wrote: >> I added updates to my CentOS

Re: FreeBSD client fails with 'error opening /usr/local/share/amanda/bsdtar'

You can't do a level 1 backup if there is no state file for the level 0 (full) backup. Force a full backup of the dle with amadmin CONF force HOST DISK Jean-Louis On 02/02/17 11:05 AM, Jean-Francois Malouin wrote: > * Jean-Louis Martineau <jmartin...@carbonite.com> [20170202 10:5

Re: FreeBSD client fails with 'error opening /usr/local/share/amanda/bsdtar'

Do amcheck reported an error? $ man ambsdtar STATE-DIR The directory where ambsdtar stores the database it uses to generate incremental dumps. The default is set when Amanda is built. Create the /usr/local/share/amanda/bsdtar directory of set the property

Re: amanda-3.3.9 : permission issues ?

On 02/02/17 04:34 AM, Stefan G. Weichinger wrote: > gentoo linux, amanda 3.3.9 > same installation worked for months > > now the tape isn't written anymore, amflush or amlabel fails. > > we cleaned the tape drive, reloaded st module > > $ amcheck daily > Amanda Tape Server Host Check >

Re: Result of backup is FLUSH from client with 3.4.1

Post more information. The amdump., log..0 and all debug files. Jean-Louis On 01/02/17 03:11 AM, Henrik Johansson wrote: Hi, I have a server with CentOS-7 and one client with Fedora-24. The server runs amanda 3.3.8, the backups of the client stopped working, when the client was upgraded to

Release of Amanda-3.4.2

* fix compilation without SSE4_2 when configure detect it * amtoc fix * amlabel -f fix * many more fixes Jean-Louis Martineau

Re: big update killed 1 host

Jon, Why systemd print the ExecStart on the socket? it's a systemd bug or a misconfiguration. Jean-Louis On 30/01/17 12:38 AM, Jon LaBadie wrote: > Follow-up, > > amrecover gives the same error whether run from the server/client > or from another client. > > On the server/client I also ran: >

Re: ./.libs/libamanda.so: undefined reference to `OPENSSL_init_ssl'

The command line do not include the required '-lssl -lcrypto' What is the output of: pkg-config openssl --libs Do you have the openssl.pc filerequired for pkg-config? Jean-Louis On 20/01/17 03:48 AM, Tobias Köck wrote: > > Hi, > > after trying to compile Amanda 3.4.1 on in Debian I get the

Re: GNUtar 1.29 on FreeBSD doesn't support --atime-preserve='system' option

On 19/01/17 12:36 PM, Jean-Francois Malouin wrote: > * Jean-Louis Martineau <jmartin...@carbonite.com> [20170119 10:29]: >> On 19/01/17 09:49 AM, Jean-Francois Malouin wrote: >>> Hi,, > ... >>> >>> Question: are they any drawbacks, performance, e

Re: GNUtar 1.29 on FreeBSD doesn't support --atime-preserve='system' option

On 19/01/17 09:49 AM, Jean-Francois Malouin wrote: > Hi,, > > I've got this FreeBSD 11.0 box (virtual at the moment but will become > real metal soon) for which I've installed an Amanda client (v3.3.6) and > while testing it, tar (GNU tar) 1.29 complains when the Amanda run is > started with

Re: AW: need to have samba-4.2.11 on amanda server

e? Isn't it supported anymore and/or won't be fixed? For the next round I'll try the amsamba dumptype. Greetings, Tobias *Von:*owner-amanda-us...@amanda.org [mailto:owner-amanda-us...@amanda.org] *Im Auftrag von *Jean-Louis Martineau *Gesendet:* Dienstag, 10. Januar 2017 15:00 *An:* Mike Höhn

Re: What is POOL and STORAGE?

On 17/01/17 10:11 AM, Stefan G. Weichinger wrote: Am 2017-01-17 um 15:33 schrieb Jean-Louis Martineau: The tapecycle is used to set the policy retention-days Each storage can have a different policy and each policy can have a different retention-days OK, so I created an extra policy-block

Re: Backup of Btrfs snapshots

On 18/01/17 05:43 AM, Jonas Hagen wrote: Hi We have an amanda server / client setup. Now one client has the root directory on a btrfs filesytem and we would like to back it up with the following procedure: 1) make a btrfs snapshot 2) mount this snapshot 3) make a backup of the snapshot using

Re: What is POOL and STORAGE?

On 17/01/17 07:30 AM, Stefan G. Weichinger wrote: Am 2017-01-13 um 11:13 schrieb Stefan G. Weichinger: As far as I understand so far now all the dumps should go to both the tapes and the vtapes. As soon as that works and looks good I will try to make up a more specific setup with defining

Re: Issues backing up very old (2.5 era) clients with 3.4

jason, Try the attached patch. Jean-Louis On 14/01/17 07:21 PM, Jason L Tibbitts III wrote: >>>>>> "JM" == Jean-Louis Martineau <jmartin...@carbonite.com> writes: > JM> Removing the leading semicolon was a mistake. Your patch looks > JM>

Re: Issues backing up very old (2.5 era) clients with 3.4

Removing the leading semicolon was a mistake. Your patch looks good. let me know if it works so I can commit it. I have no setup to test older version and they don't compile on newer distribution. I try to never break compatibility. Jean-Louis On 13/01/17 03:40 PM, Jason L Tibbitts III wrote:

Re: Amanda::Config::getconf($CNF_LABELSTR) now returns a ref to a hash in 3.4.1

On 10/01/17 11:55 AM, Jean-Francois Malouin wrote: > * Jean-Louis Martineau <jmartin...@carbonite.com> [20170110 09:31]: >> The labelstr setting changed in 3.4 >> $ man amanda.conf >> labelstr string | MATCH-AUTOLABEL >> Default: MATCH-AUT

<    1   2   3   4   5   6   7   8   9   10   >