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

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: ambackupd reports missing data

Jon, Can you post the log..0 file? Jean-Louis On 24/09/17 05:59 PM, Jon LaBadie wrote: > When I request a backup of a client using ambackupd, the subsequent > report does not include most of the dump statistics (first line of > data). Some of them print out on the next regular amdump run when

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

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 error) problem is > an update of the Centos amanda packages. On tuesday we up

Release of Amanda-3.5

cancelling the shm_ring with a STRANGE result * fix chunker hang * Improve taperscan with chg-single and interactivity 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

Re: ambackupd reports missing data

:57:31AM -0400, Jean-Louis Martineau wrote: > > Jon, > > > > Can you post the log..0 file? > > > > Jean-Louis > > > > On 24/09/17 05:59 PM, Jon LaBadie wrote: > > > When I request a backup of a client using ambackupd, the subsequent > > >

Re: amanda-3.5 amanda-security.conf

schrieb Jean-Louis Martineau: The host reporting this error is an amanda 3.5. Do you added a tcp_port_range in the /usr/local/etc/amanda-security.conf file on that host (your server)? Jean-Louis On 02/10/17 05:10 AM, Dennis Benndorf wrote: Hi, might there be an issue with amanda-3.5

Re: amanda-3.5 amanda-security.conf

The host reporting this error is an amanda 3.5. Do you added a tcp_port_range in the /usr/local/etc/amanda-security.conf file on that host (your server)? Jean-Louis On 02/10/17 05:10 AM, Dennis Benndorf wrote: Hi, might there be an issue with amanda-3.5 and the new option tcp_port_range in

Re: Amcheck Fails on Amanda 3.5

On 29/09/17 12:08 PM, Steven Backus wrote: > Jean-Louis Martineau <jmartin...@carbonite.com> writes: > > > The error message is misleading. > > The problem is that you run it as root! > > > Amanda is not expected to be run as root, do you always run > > ama

Re: Amcheck Fails on Amanda 3.5

The error message is misleading. The problem is that you run it as root! Amanda is not expected to be run as root, do you always run amanda as root? Jean-Louis On 29/09/17 11:31 AM, Steven Backus wrote: > Trying amanda 3.5 on Centos 7.4.1708. Did: > > ./configure --with-user=root

Re: Amcheck Fails on Amanda 3.5

On 29/09/17 02:07 PM, Steven Backus wrote: > Jean-Louis Martineau <jmartin...@carbonite.com> writes: > > It will fail, there is similar code in planner.c, driver.c and > > amservice.c > > Found it in planner.c and amservice.c but not in driver.c. Sorry, it

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: 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: 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

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: 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

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: Using RAIT with vTapes and S3

Jose, What do you want to achieve? mirror? Using RAIT for mirroring is deprecated since we added vault functionality. It is better to write to vtape and then amvault to S3. In amanda-3.5, you can configure a dump to be flushed from holding disk to vtape and S3. Jean-Louis On 10/10/17 03:14

Re: property append IGNORE regex

Matthias, Which amanda version are you using? (client and server) Which application are you using? Is it amgtar? Post the application debug file Jean-Louis On 22/10/17 06:10 AM, Matthias Teege wrote: > Hello! > > I'm using > >property append "IGNORE" "file changed as we read it$" > > in my

Re: vault from aggregate changer to tape

Stefan, Which disk is UUID=5a5a9927-995f-4f0f-98ff-d222561f84ff, why amanda can't mount it? The 'No acceptable volumes found' message is from which storage? Are you sure you have a tape in band that amanda can use? You can run 'amcheck CONFIG -t -ostorage=band' to find it. Jean-Louis On

Re: amanda.conf.5 patch: expanded vault-storage description

Nathan, Thanks for the patch, I committed it Jean-Louis On 27/11/17 02:38 AM, Nathan Stratton Treadway wrote: > The attached patch against amanda.conf.5.xml tries to fill in some > specific details on the operation of the vault-storage parameter, and > also fixes a couple typos in other parts

Re: man page typos (amfetchdump, amanda-changers)

Nathan, Thanks for the patch, I committed it Jean-Louis On 27/11/17 09:33 AM, Nathan Stratton Treadway wrote: > Patch with minor fixes for amanda-changers.7.xml and amfetchdump.8.xml . > > Nathan > > > Nathan Stratton

Re: amflush and .tmp files in holding directory

20, 2017 at 14:42:01 -0500, Jean-Louis Martineau wrote: > > Each process should take a lock on the holding directory (a pid file), > > In my original amflush-during-amdump test the specific error I noticed > was that amflush attempted to flush .tmp files out of the holding > disk

Re: amflush run while amdump underway tries to flush .tmp files

Nathan, search_holding_disk should not take the pid file. Jean-Louis On 21/11/17 06:49 PM, Nathan Stratton Treadway wrote: > On Tue, Nov 21, 2017 at 12:57:00 -0500, Nathan Stratton Treadway wrote: > > > I do not see how Amanda::Util::setup_application call code in > holding.c > > > > To be

Re: amflush run while amdump underway tries to flush .tmp files

are right, it should check for ppid Jean-Louis On 21/11/17 08:13 PM, Nathan Stratton Treadway wrote: > On Mon, Nov 20, 2017 at 15:09:25 -0500, Jean-Louis Martineau wrote: > > perl automatically close it when it come out of scope. > > The close should before the 'if (kill' line. &g

Re: "vaulting run" amdump email report issues -- driver.c "nodump" option

On 23/11/17 02:00 PM, Nathan Stratton Treadway wrote: > On Wed, Nov 22, 2017 at 11:58:12 -0500, Jean-Louis Martineau wrote: > > On 22/11/17 12:56 AM, Nathan Stratton Treadway wrote: > > > On Mon, Nov 20, 2017 at 11:45:07 -0500, Jean-Louis Martineau wrote: > > > > Nat

Re: amflush run while amdump underway tries to flush .tmp files

Treadway wrote: > On Mon, Nov 20, 2017 at 15:09:25 -0500, Jean-Louis Martineau wrote: > > perl automatically close it when it come out of scope. > > The close should before the 'if (kill' line. > > Okay, I moved the close() line up to that spot as I applied the patch. > > I can c

Re: "vaulting run" amdump email report issues -- driver.c "nodump" option

On 22/11/17 12:56 AM, Nathan Stratton Treadway wrote: > On Mon, Nov 20, 2017 at 11:45:07 -0500, Jean-Louis Martineau wrote: > > Nathan, > > > > I was too fast to write the first patch, and you are completely right. > > > > I committed the attached patch,now a

Release of Amanda-3.5.1

of 'no such parameter' * amdump o new --no-dump, --no-flush and --no-vault argument * amstatus fix * lock holding disk to protect multiple parallel access Jean-Louis Martineau This message is the property of CARBONITE, INC. and may contain confidential or privileged information

Re: "vaulting run" amdump email report issues

Nathan, Try this patch. run: amdump --no-dump --no-flush CONFIG Will do all scheduled vault to the vault-storage Jean-Louis On 16/11/17 08:31 AM, Nathan Stratton Treadway wrote: > On Thu, Oct 19, 2017 at 11:06:40 -0400, Jean-Louis Martineau wrote: > > Since you want to vault all full

Re: "vaulting run" amdump email report issues

On 16/11/17 08:31 AM, Nathan Stratton Treadway wrote: > On Thu, Oct 19, 2017 at 11:06:40 -0400, Jean-Louis Martineau wrote: > > Since you want to vault all full, I would set 'vault' in the local > > storage, set 'dump-selection' in the cloud storage, but will not set >

Re: "vaulting run" amdump email report issues

Thanks, I committed the attached patch to fix the issue. Jean-Louis On 16/11/17 11:08 AM, Nathan Stratton Treadway wrote: > On Thu, Nov 16, 2017 at 09:43:15 -0500, Jean-Louis Martineau wrote: > > On 16/11/17 08:31 AM, Nathan Stratton Treadway wrote: > > > DUMP SUMMARY: > &

Re: approaches to Amanda vaulting?

Stefan, Post all debug files and log generated while running amflush. Jean-Louis On 10/11/17 08:45 AM, Stefan G. Weichinger wrote: Am 2017-11-08 um 18:57 schrieb Jean-Louis Martineau: On 28/10/17 12:37 PM, Stefan G. Weichinger wrote: Is it possible to amflush dumps from holdingdisk to tape

Re: approaches to Amanda vaulting?

On 10/11/17 09:14 AM, Stefan G. Weichinger wrote: Am 2017-11-10 um 14:59 schrieb Jean-Louis Martineau: > Stefan, > > Post all debug files and log generated while running amflush. will try that server doesn't write debugfiles now, I raised the debug-* parameters in amanda.conf but c

Re: Odd non-fatal errors in amdump reports.

On 10/11/17 07:57 AM, Austin S. Hemmelgarn wrote: On 2017-11-08 08:03, Jean-Louis Martineau wrote: On 07/11/17 02:58 PM, Austin S. Hemmelgarn wrote: > On 2017-11-07 10:22, Jean-Louis Martineau wrote: >> Austin, >> >> It's hard to say something with only the error mes

Re: Odd non-fatal errors in amdump reports.

On 10/11/17 10:10 AM, Austin S. Hemmelgarn wrote: On 2017-11-10 10:00, Jean-Louis Martineau wrote: Austin, Can you try the attached patch, I think it could fix the set1 and set2 errors. Yes, but I won't be able to log in this weekend to revert it if it doesn't work, so I won't be able

Re: Odd non-fatal errors in amdump reports.

Austin, Can you try the attached patch, I think it could fix the set1 and set2 errors. Jean-Louis On 07/11/17 02:58 PM, Austin S. Hemmelgarn wrote: On 2017-11-07 10:22, Jean-Louis Martineau wrote: Austin, It's hard to say something with only the error message. Can you post the amdump

Re: Odd non-fatal errors in amdump reports.

The previous patch broke something. Try this new set2-r2.diff patch Jean-Louis On 10/11/17 10:40 AM, Austin S. Hemmelgarn wrote: On 2017-11-10 08:27, Jean-Louis Martineau wrote: On 10/11/17 07:57 AM, Austin S. Hemmelgarn wrote: On 2017-11-08 08:03, Jean-Louis Martineau wrote: On 07/11/17 02

Re: amcheck -m DailySet does not display, sends mail only

The -m flag should print nothing on stdout Do not use the -m flag if you want something displayed. Jean-Louis On 12/11/17 11:19 PM, Jobst Schmalenbach wrote: > Hi > > running amcheck-3.4.1, server and clients all run same software (3.4.1) and > only linux stations. > > On the tape server when

Re: "vaulting run" amdump email report issues -- driver.c "nodump" option

:15:28 -0500, Jean-Louis Martineau wrote: > > Nathan, > > > > Try this patch. > > > > run: amdump --no-dump --no-flush CONFIG > > Will do all scheduled vault to the vault-storage > > [...] > > > diff --git a/server-src/driver.c b/server-src/drive

Re: amvault and label problem as of 3.4.5

On 20/11/17 10:54 AM, Winston Sorfleet wrote: Thanks Nathan... I have tried the command line without any -o options: |/usr/sbin/amvault --latest-fulls --dest-storage "HP G2 Robot" vtl | Now the response is "FATAL amvault no 'tape-device' property specified" which doesn't make sense

Re: amflush run while amdump underway tries to flush .tmp files

On 20/11/17 02:56 PM, Nathan Stratton Treadway wrote: > On Mon, Nov 20, 2017 at 14:42:01 -0500, Jean-Louis Martineau wrote: > > Each process should take a lock on the holding directory (a pid file), > > Okay, makes sense. > > > > + my $pidfn = File::Spec->catfile($di

Re: amflush run while amdump underway tries to flush .tmp files

Each process should take a lock on the holding directory (a pid file), The attached path fix it. Please try it. On 17/11/17 12:38 AM, Nathan Stratton Treadway wrote: > (Amanda v3.5) > > I noticed that Amanda 3.5 no longer aborts amflush if amdump is > currently running (as older versions of

Re: amflush run while amdump underway tries to flush .tmp files

at 14:42:01 -0500, Jean-Louis Martineau wrote: > > > + if (open(my $pidh, $pidfn)) { > > > + my $pid = <$pidh>; > > > + if (kill($pid, 0) == 0) { > > > + # pid is alive, skip this directory > > > + next; > > > + } > > > > look

Re: Odd non-fatal errors in amdump reports.

On 13/11/17 02:53 PM, Austin S. Hemmelgarn wrote: driver: send-cmd time 9300.326 to taper1: VAULT-WRITE worker1-0 00-00120 local-vtl local-vtl Home-0001 client0 /home/1D 0 20171113073255 "" "" "" "" 1073741824 memory "" "" 0 FAIL taper "ST:cloud" "POOL:cloud" client0 /home/1D 20171113073255 0

Re: DLE stuck on holdingdisk and being flushed on every dump

Jose, The report should report the error. The attached patch fix it. Jean-Louis On 01/11/17 12:18 PM, Jose M Calhariz wrote: On Wed, Nov 01, 2017 at 10:47:10AM -0400, Jean-Louis Martineau wrote: Jose, When amanda did the backup, it computed a crc of 6828c030. But it compute b8d66d3d when

Re: DLE stuck on holdingdisk and being flushed on every dump

Jose, When amanda did the backup, it computed a crc of 6828c030. But it compute b8d66d3d when it read it from holding disk to flush it. Do you see that error in the report for all flush attempt? The holding disk file is not erase because of the crc mismatch. You can manually remove it (amadmin

Re: Odd non-fatal errors in amdump reports.

On 07/11/17 02:58 PM, Austin S. Hemmelgarn wrote: On 2017-11-07 10:22, Jean-Louis Martineau wrote: Austin, It's hard to say something with only the error message. Can you post the amdump. and log..0 for the 2 backup set that fail. I've attached the files (I would put them inline, but one

Re: Continuing after "No acceptable volumes found"

On 08/11/17 09:17 AM, Greg Dickie wrote: running 3.4.5 and interactivity is set up but whatever I do to the /tmp/email_input file just recreates the message. I'm pretty sure if I put abort in there it will abort but I don't want to abort unless there is no choice. How the interactivity is

Re: amreport: ERROR error: the mailer '/bin/Mail': No such file or directory

The mailer is set when amanda is configured (./configure). The machine where amanda was build have a /bin/Mail and amanda is configured to use it. Either install the package with /bin/Mail or set the mailer in amanda.conf, or remove it if it set to '/bin/Mail' Jean-Louis On 08/11/17 10:21

Re: Continuing after "No acceptable volumes found"

barcode 000118L7 [retention-no] slot 19: label 000119L7 barcode 000119L7 [retention-no] slot 20: label 000120L7 barcode 000120L7 [retention-no] slot 21: label 000121L7 barcode 000121L7 [retention-no] slot 22: empty slot 23: empty slot 24: empty Cannot find any taperscan logs, I guess I need to enable

Re: Continuing after "No acceptable volumes found"

On 08/11/17 10:07 AM, Greg Dickie wrote: So in /var/lib/amanda/CONFIG I do not see taper logs. I'll figure out why.. run: amgetconf build.amanda_dbgdir Go in the resulting directory /server/WeeklySet1 Jean-Louis This message is the property of CARBONITE, INC. and may contain confidential or

Re: approaches to Amanda vaulting?

On 04/11/17 09:55 PM, Nathan Stratton Treadway wrote: > On Mon, Oct 16, 2017 at 09:20:16 -0400, Jean-Louis Martineau wrote: > > Amanda 3.5 can do everything you want only by running the amdump > command. > > > > Using an holding disk: > > > > * You confi

Re: Continuing after "No acceptable volumes found"

='000114L7' disk='' dumplevel=0 and blocksize=2097152 Rolling again, Thank you very much for the help, Greg On Wed, Nov 8, 2017 at 11:57 AM, Jean-Louis Martineau <jmartin...@carbonite.com <mailto:jmartin...@carbonite.com>> wrote: I do not understand why it doesn't want to u

Re: Continuing after "No acceptable volumes found"

state Wed Nov 08 11:43:16.029230821 2017: pid 23508: thd-0x18fd200: taper: new Amanda::Changer::Error: type='failed', reason='notfound', message='No acceptable volumes found' On Wed, Nov 8, 2017 at 10:15 AM, Jean-Louis Martineau <jmartin...@carbonite.com <mailto:jmartin...@carbonite.com&g

Re: approaches to Amanda vaulting?

On 28/10/17 12:37 PM, Stefan G. Weichinger wrote: Is it possible to amflush dumps from holdingdisk to tape while keeping the dump files in the holdingdisk (for flushing them to a second set of tapes later or just restore purposes) ? It's not possible to flush them again. Keeping them for

Re: Continuing after "No acceptable volumes found"

On 07/11/17 06:23 PM, Greg Dickie wrote: Hi, After 32TB of 48TB backed up I suddenly get a "No acceptable volumes found". Is there a way to continue the backup rather than aborting and restarting? I have ensured there are valid tape loaded. There is no way to continue the current run.

Re: approaches to Amanda vaulting?

On 08/11/17 03:40 PM, Nathan Stratton Treadway wrote: > On Wed, Nov 08, 2017 at 12:50:12 -0500, Jean-Louis Martineau wrote: > > YES > > Great, thanks for confirming my understanding. > > A few clarifications: > > > > > > 2) the "without holding dis

Re: Odd non-fatal errors in amdump reports.

Austin, It's hard to say something with only the error message. Can you post the amdump. and log..0 for the 2 backup set that fail. The tapedev of the aws changer can be written like: tapedev "chg-multi:s3:/slot-{0..127} Jean-Louis On 07/11/17 09:17 AM, Austin S.

Re: amanda 3.5 (debian) - multiple instances - is it normal?

amanda-3.5 allow to run multiple backup in parallel. This to allow to run different amdump on different host/dle at the same time and to allow client initiated backup to run at the same time. Jean-Louis On 07/12/17 08:28 PM, Kamil Jońca wrote: So far amanda was unable to run multiple

Re: application amgtar ignore messages

On 09/12/17 02:11 PM, Jon LaBadie wrote: > On Fri, Dec 08, 2017 at 07:14:54AM -0500, Austin S. Hemmelgarn wrote: >> On 2017-12-07 22:26, Jon LaBadie wrote: >>> If I want amgtar to ignore certain messages, is it >>> sufficient to list the message on the amanda server >>> or must the ignored message

Re: approaches to Amanda vaulting?

On 24/10/17 02:07 PM, Stefan G. Weichinger wrote: I was able to label the vtapes in storage "daily" but can't figure out why this command accesses changer "disk1" instead of "disk2" -> $ /usr/sbin/amlabel --storage vault --pool vault daily vault01 slot 1 Reading label... Found label 'daily01'

Re: approaches to Amanda vaulting?

On 24/10/17 02:45 PM, Jean-Louis Martineau wrote: On 24/10/17 02:29 PM, Stefan G. Weichinger wrote: Am 2017-10-24 um 20:25 schrieb Jean-Louis Martineau: This is not what you want. You want amlabel to do its operation on the vault storage. amlabel operate on the first configured storage, so

Re: approaches to Amanda vaulting?

On 24/10/17 02:29 PM, Stefan G. Weichinger wrote: Am 2017-10-24 um 20:25 schrieb Jean-Louis Martineau: This is not what you want. You want amlabel to do its operation on the vault storage. amlabel operate on the first configured storage, so this is what you must change. $ amlabel -ostorage

Re: approaches to Amanda vaulting?

Stefan, can you try the attached patch? Jean-Louis On 24/10/17 03:00 PM, Jean-Louis Martineau wrote: On 24/10/17 02:45 PM, Jean-Louis Martineau wrote: On 24/10/17 02:29 PM, Stefan G. Weichinger wrote: Am 2017-10-24 um 20:25 schrieb Jean-Louis Martineau: This is not what you want. You want

Re: temporarily remove a system

The --exclude-host option is a good idea. Jean-Louis 2018-05-20 16:41 GMT-04:00 C. Chan : > It would be nice if amdump had some kind of --exclude-host flag > which would skip over that host even if it is in the disklist > file. > > Also Sprach Jon LaBadie: > > On Sun, May

Re: temporarily remove a system

Jon, Set the strategy to skip. Jean-Louis 2018-05-20 2:55 GMT-04:00 Jon LaBadie : > I have one system that will be down for an unknown time. > > How best to stop amanda from trying, and failing, to > back up the DLEs of that system. Is it as simple as > commenting out the

Re: approaches to Amanda vaulting?

On 19/10/17 08:48 AM, Austin S. Hemmelgarn wrote: On 2017-10-18 15:45, Stefan G. Weichinger wrote: Am 2017-10-16 um 20:47 schrieb Austin S. Hemmelgarn: While it's not official documentation, I've got a working configuration with Amanda 3.5.0 on my personal systems, using locally accessible

Re: Problem backing up: "no backup size line"

Jobst, Every good bug report should include the version of the software you are using. Which amanda version are you using? On amanda server an client? Also tell us more information, you just tell us 'no backup size line"' on nothing more. Which program or application are you using to do the

Re: First run...

On 05/01/18 01:35 PM, Chris Miller wrote: Now, I recognize that the simple answer is I have made my vtapes too small, but there is a larger confusion. Why didn't the backup use as many vtapes as necessary? Somewhere there must be a good discussion of how vtapes work and what Amanda does in

Re: Serious tape error

This is an issue in 3.4, 3.4.1 and 3.4.2 It is fixed in 3.4.3 Jean-Louis On 04/01/18 06:37 PM, Jon LaBadie wrote: > On Thu, Jan 04, 2018 at 05:12:27PM -0500, Jon LaBadie wrote: >> I use vtapes of 100GB and runtapes == 3. Most days only >> one tape is used. About once every 2 or 3 weeks a

Re: amanda tape algorithm

On 04/01/18 12:59 PM, Ned Danieley wrote: > > I'm using > > taperalgo largestfit > > which I assume means that amanda will write to tape the largest DLE > available. I have 'runtapes' set to 2, and occasionally I'll see amanda > move on to the second tape when the first tape is reporting around

Re: ambackup -- usage message error

Thanks Jon, I committed the attached path Jean-Louis On 08/01/18 02:08 AM, Jon LaBadie wrote: > The usage message of ambackup(8) shows "dump" as a > valid command. It should show "backup" instead. > > Jon This message is the property of CARBONITE, INC. and may contain confidential or

Re: tape device order in amanda.conf

Luc, The assignment of 'Data Transfer Element 0' to '/dev/nst1' and 'Data Transfer Element 1' to '/dev/nst0' is done by the kernel. You can use the 'amtape CONF verify' command to check if you correctly configured amanda. Jean-Louis On 13/01/18 06:40 PM, Luc Lalonde wrote: Hello Folks,

Re: Amtapetype wrongly reporting compression?

Luc, You should keep the driver in variable block size: eg . /usr/bin/mt -f /dev/st0 setblk 0 Jean-Louis On 12/01/18 03:20 PM, Luc Lalonde wrote: Hello Gene, Would a variant like this: /usr/sbin/mtx load 1 0; /usr/bin/mt -f /dev/st0 compression 0; /usr/bin/mt -f

Re: Amtapetype wrongly reporting compression?

’ capacity of the LTO7 tapes. Can you confirm this? Best regards, Luc. On Jan 11, 2018, at 3:09 PM, Jean-Louis Martineau <jmartin...@carbonite.com <mailto:jmartin...@carbonite.com>> wrote: Luc, amtapetype use speed heuristic to detect if the drive is in compressed mode, it might

Re: reconstructing file hierarchy from indecies

On 19/01/18 12:51 PM, Michael Stauffer wrote: amanda 3.3.9 Hi, I've got a large xfs filesystem that had trouble and has undergone repair. Some inodes were disconnected from filenames. I've mostly been able to identify what's what from contents of the dir trees now named as inodes in

Re: Amtapetype wrongly reporting compression?

Luc, amtapetype use speed heuristic to detect if the drive is in compressed mode, it might not be good for newer drives. Why you didn't post the complete amtapetype output? I can't tell you why the heuristic is bad without those numbers. The default block size of 32k was good 15 years ago,

Re: Regression in 3.5.1 or a broken compilation for Debian stretch

add: debug-auth 9 to amanda.conf and retry Post the planner debug file. For the failing client, do amandad is executed, post the amandad debug files. Jean-Louis From: owner-amanda-us...@amanda.org on behalf of Jose M

Re: again level 1 backup problems.

Charles, It looks to be a bug in gnutar, I sent a bug report to bug-...@gnu.org but I got no reply. http://lists.gnu.org/archive/html/bug-tar/2018-02/msg0.html You could try an older version 1.12, 1.13, 1.14 Or the patch I posted to bug-...@gnu.org Jean-Louis

Re: again level 1 backup problems.

You didn't say how you do the backup, you are using the GNUTAR program or the amgtar application? or ... ? Read https://marc.info/?l=amanda-users=2=1=GNU+tar+estimates+for+vfat+filesystems=b Try to set gnutar-list-dir to the empty string in /etc/amanda/$CONF/amanda-client.conf eg.

Re: More problems with a big installation of amanda 3.5.1 on Debian stretch, v9

The driver process crashed. Can you post the driver debug file and the amdump.TIMESTAMP file? After you start the next backup. Attach gdb to the driver process (gdb -p PID). If it crash, get the stack trace in gdb (bt command). Jean-Louis From:

Re: server 3.5.1 - issue backing up localhost

Joe, Do amandad is executed? It should create debug files in /var/log/amanda/amandad If not, check xinetd configuration and system log to find why. If amandad is executed, check its debug file Jean-Louis From: owner-amanda-us...@amanda.org

Re: amanda is skipping over available tapes

Jon, 'amadmin tape' list the oldest reusable label, it doesn't use the taperscan algorithm and it doesn't check what is currently loaded in the changer. 'amcheck' and 'amtape' run the taperscan algorithm and verify they are in the changer. Which taperscan are you using? Jean-Louis On

Re: VTape configuration

A vtape do not reserve the space, it only use the space of the dump you put on it. The vtape size should be the maximum size of any days or larger, they could be 120GB or 2TG, the result will be the same. Some vtape will use 5GB, some will use 120GB. Jean-Louis On 03/01/18 04:08 PM, Chris

Re: Another problem with smbclient for Samba 4

Olivier, Do not use the 'GNUTAR' program. Use the amsamaba application. Jean-Louis 2018-07-04 5:51 GMT-04:00 Olivier : > Hi, > > I noticed that the command >smbclient olivier\\drivec -U on\%password -E -W samba -d0 -Tqca - > does not behave the same with Samba 3 and Samba 4. The

Re: Restoring files from amanda in a script

You can't restore in a unique tree of files. I do not understand why you want to do that. To do it: - patch amgtar to remove the -G flag ("-xpGvf" to "-xpvf"), otherwise extracting a DLE will remove what was extracted from another DLE, but file erase before the backup will not be erased - run

Re: sendbackup deadlock for my direct-to-tape dump

Ian, Can you try to use the "amgtar" application instead of the GNUTAR program? Jean-Louis From: owner-amanda-us...@amanda.org on behalf of Ian Turner Sent: April 12, 2018 5:13 PM To:

Re: tape pools, wrapping my mind around them

You want 3 storage A vtape can only contains backup from one storage. You use the storage 'dump_selection' and the dumptype 'tag' to specify which dle go to that storage You could use a different pool for each storage. But using the same pool for all storage have a big benefits: - no need to

Re: Zmanda acquired from Carbonite by BETSOL -- future of Amanda development?

Don't fork. I can give write access to the SVN repository to people that ask for. Jean-Louis Le mer. 26 sept. 2018, à 13 h 39, Chris Nighswonger < cnighswon...@foundations.edu> a écrit : > On Wed, Sep 26, 2018 at 1:31 PM Gene Heskett wrote: > >> >> Fork it if someone has a long term interest

Re: Fw: amanda backup fails, because of wrong suid settings

Read the ReleaseNotes and we will find that suid have changed in 3.5 Le lun. 10 déc. 2018, à 16 h 35, Charles Stroom a écrit : > Sorry, but below replace "sticky bit" by "suid bit". > > Charles > > Begin forwarded message: > > Date: Mon, 10 Dec 2018 21:10:36 +0100 > From: Charles Stroom > To:

Re: Reusable

Use the amraw application to backup a single file. it backup on;y the data, not the meta-data: filename permission, stat, ... man amraw Le mer. 21 nov. 2018, à 15 h 01, Chris Miller a écrit : > Hi Folks, > > I have written some very small DLEs so I can rip through weeks of backups > in minutes.

Re: amanda-client: HOST localhost ERROR: //192.168.0.250/ftp: Application 'amsamba': exited with status 1

Add the same pattern near line 757: return if $line =~ /^Unable to initialize messaging context/; From: owner-amanda-us...@amanda.org on behalf of Stefan G. Weichinger Sent: July 17, 2019 12:52 PM To: Diego Zuccato; AMANDA users Subject: Re:

<    12   13   14   15   16   17