Amanda compatible with Fujitsu Eternus LT20 tape library

We have a customer request to implement a backup system which incorporates a Fujitsu eternus lt20 tape library. Is there any experience on operating this tape library with amanda? Any help would be greatly appreciated. -- Volker Jahns, vol...@thalreit.de

Re: tape device order in amanda.conf

Ok, thanks for the tip: [root@ulysses ~]# su amandabackup -c '/usr/sbin/amtape Mensuel-LTO7 verify' GOOD : Drive 0 is device tape:/dev/nst1 GOOD : Drive 1 is device tape:/dev/nst0 property "TAPE-DEVICE" "0=tape:/dev/nst1" "1=tape:/dev/nst0" Best regards, Luc.

Re: tape device order in amanda.conf

, I’m getting a strange result when I do an ‘amcheck’: slot 3: Tape device /dev/nst1 is not ready or is empty slot 4:Slot 4, label '000279L7', mismatch barcode between changer '000280L7' and tapelist file '000279L7' ERROR: Slot 4, label '000279L7', mismatch barcode between changer '000280L7

tape device order in amanda.conf

Hello Folks, I’m getting a strange result when I do an ‘amcheck’: slot 3: Tape device /dev/nst1 is not ready or is empty slot 4:Slot 4, label '000279L7', mismatch barcode between changer '000280L7' and tapelist file '000279L7' ERROR: Slot 4, label '000279L7', mismatch barcode between changer

amcheckdump and a tape changer

Hello! I'm using amanda 3.3 with a tape changer. It works as expected. There is only one problem with amcheckdump. On startup amcheckdumps tells me, which tape is needed and stops then, waiting for "enter". Is it possible to let amcheckdump load the correct tape? Many thanks! Matthias

Re: Serious tape error

On Fri, Jan 05, 2018 at 08:54:36AM -0500, Jean-Louis Martineau wrote: > This is an issue in 3.4, 3.4.1 and 3.4.2 > > It is fixed in 3.4.3 Ahh yes, I do [now] recall that fix being reported. Thanks, I will look for an available update. > > Jean-Louis > jl -- Jon H. LaBadie

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 tap

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 eve

Re: amanda tape algorithm

> > > the rated capacity would be accurate. I'll give it a try; in the meantime, > > > has anyone run 'amtapetype' on an LTO6 tape? I have an HP Ultrium 6 drive. > > > > I did and got: > > > > define tapetype LTO6 { > > comment "Created by amtapety

Re: amanda tape algorithm

time, > > has anyone run 'amtapetype' on an LTO6 tape? I have an HP Ultrium 6 drive. > > I did and got: > > define tapetype LTO6 { > comment "Created by amtapetype; compression disabled" > length 2442954880 kbytes > filemark 7456397 kbytes > speed 15

Re: amanda tape algorithm

Ned Danieley <ned.danie...@duke.edu> wrote: > ah, that makes sense. no, I haven't run 'amtapetype'; I just assumed that > the rated capacity would be accurate. I'll give it a try; in the meantime, > has anyone run 'amtapetype' on an LTO6 tape? I have an HP Ultrium 6 drive. I did a

Re: Serious tape error

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 second > tape is needed. Yesterday was one of those days. But > amanda chose the same vtape for the second t

Re: amanda tape algorithm

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

Serious tape error

I use vtapes of 100GB and runtapes == 3. Most days only one tape is used. About once every 2 or 3 weeks a second tape is needed. Yesterday was one of those days. But amanda chose the same vtape for the second tape and over wrote the data it had just written to the "first" ta

Re: amanda tape algorithm

On Thu, Jan 04, 2018 at 09:43:35PM +, Debra S Baddorf wrote: > > > On Jan 4, 2018, at 11:59 AM, Ned Danieley <ned.danie...@duke.edu> wrote: > > > > > > I'm using > > > > taperalgo largestfit > > > > which I assume means that amanda

Re: amanda tape algorithm

> On Jan 4, 2018, at 11:59 AM, Ned Danieley <ned.danie...@duke.edu> 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 am

amanda tape algorithm

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 80% full. I'm dumping almost 200 DLE, so it seems like

Re: vault from aggregate changer to tape

Am 2017-11-27 um 14:43 schrieb Winston Sorfleet: I've been having a devil of a time trying to get a similar configuration working since 3.4.5. Could you post a copy of your working config? I could but I would prefer to maybe start some kind of howto or collection of examples that might go

Re: vault from aggregate changer to tape

agree: if I want to vault all FULLs from storage "vtape" I have to >attach both drives at the same time ... for now it's testing and I play >with only subsets (single servers/DLEs). > >> The 'No acceptable volumes found' message is from which storage? Are >you >> s

Re: vault from aggregate changer to tape

off-site. I agree: if I want to vault all FULLs from storage "vtape" I have to attach both drives at the same time ... for now it's testing and I play with only subsets (single servers/DLEs). > The 'No acceptable volumes found' message is from which storage? Are you > sure you hav

Re: vault from aggregate changer to tape

On Mon, Nov 27, 2017 at 12:20:59 +0100, Stefan G. Weichinger wrote: > $ amvault --fulls-only --src-storage vtape --dest-storage band vtape > --src-timestamp 20171110231503 server > mount: can't find UUID=5a5a9927-995f-4f0f-98ff-d222561f84ff > No acceptable volumes found Off hand (without

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 27

vault from aggregate changer to tape

I try to set up this: 1) storage "vtape" : an aggregate changer running 2 external disks plus : allow-missing-changer yes -> one external disk is out of the building ... 2) storage "band" : a tapedrive I want to transfer fulls from vtapes to tape, dryrun shows DLEs

Re: manual updating tapelist and tape headers after disk crash

the currently highest numbered vtape. > >>>> > >>>> I.e. I am succumbing to that human fraility of wanting > >>>> things to run in numerical order when it really doesn't > >>>> matter. > >>> > >> > >> I hav

Re: manual updating tapelist and tape headers after disk crash

;> order they would have been used. >>>> >>>> Also, I would like to add vtapes and have them used >>>> after the currently highest numbered vtape. >>>> >>>> I.e. I am succumbing to that human fraility of wanting >>>> things

Re: manual updating tapelist and tape headers after disk crash

used > >> after the currently highest numbered vtape. > >> > >> I.e. I am succumbing to that human fraility of wanting > >> things to run in numerical order when it really doesn't > >> matter. > > > > I haven’t tried this with vtapes

Re: manual updating tapelist and tape headers after disk crash

est numbered vtape. >> >> I.e. I am succumbing to that human fraility of wanting >> things to run in numerical order when it really doesn't >> matter. > > A quick idea (no big solution): use "amadmin no-reuse" (or edit the > reuse "flag" in tapel

Re: manual updating tapelist and tape headers after disk crash

ly doesn't > matter. A quick idea (no big solution): use "amadmin no-reuse" (or edit the reuse "flag" in tapelist) to temporarily disable all the tapes except the one freshly labelled vtape. By doing that you force amanda to use *this* tape with *this* label. Do so until you h

manual updating tapelist and tape headers after disk crash

still use the "new" tape over the one at the bottom of the list? For those already existing vtapes lost in the crash, can I create the directory and hand craft the tape header. Then just leave those tapelist entries alone. Considering the unlikely possibility that I will attemp

Re: Problem backing up the tape host.

On Fri, Oct 20, 2017 at 08:45:11AM -0600, Steven Backus (bac...@whimsy.med.utah.edu) wrote: > Did you put auth "local" in your dumptype? Here's mine: > > define dumptype comp-integ-root-tar { > global > program "GNUTAR" > comment "root partitions with compression" > compress

Re: Problem backing up the tape host.

Did you put auth "local" in your dumptype? Here's mine: define dumptype comp-integ-root-tar { global program "GNUTAR" comment "root partitions with compression" compress client fast priority low auth "local" } Steve -- Steven J. BackusComputer

Problem backing up the tape host.

The HOSTNAME is bound to the ip address in the disklist file. I really do not know what is wrong. HELP, please! Symptoms: ~ Hostname: THEHOSTNAME Org : DailySet1 Config : DailySet1 Date: October 19, 2017 These dumps were to tape DailySet1-11. The next tape Amanda e

Re: no tape device(s) under Debian Stretch

00:00:01.1/:02:00.0': > KERNELS==":02:00.0" > SUBSYSTEMS=="pci" > DRIVERS=="megaraid_sas" [...] > --- so only megaraid_sas involved here, as it seems. Well, the other part I was interested to see is what driver actually provided th

Re: no tape device(s) under Debian Stretch

Am 2017-09-20 um 21:58 schrieb Nathan Stratton Treadway: > On Wed, Sep 20, 2017 at 20:56:22 +0200, Stefan G. Weichinger wrote: >> >> put the controller + drive back into the gentoo server >> > [...] >> Maybe someone on the list with similar hardware could compare "dmesg" ? > > Does Gentoo have

Re: no tape device(s) under Debian Stretch

On Wed, Sep 20, 2017 at 20:56:22 +0200, Stefan G. Weichinger wrote: > > put the controller + drive back into the gentoo server > [...] > Maybe someone on the list with similar hardware could compare "dmesg" ? Does Gentoo have the "udevadm" command installed? If so, what does $ udevadm info

Re: no tape device(s) under Debian Stretch

put the controller + drive back into the gentoo server seems it loads one more module: # dmesg | grep mega [2.119694] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013 [2.119708] megasas: 0x1000:0x0073:0x1734:0x1177: bus 2:slot 0:func 0 [2.119821] megasas: FW now in Ready

Re: no tape device(s) under Debian Stretch

Am 2017-09-20 um 00:27 schrieb Nathan Stratton Treadway: > I don't know the specifics for a SAS-based tape drive, but in general my > impression is that (on modern Debian Linux systems) all device files > should be aotmatically created (via udev) when the related kernel module &g

Re: no tape device(s) under Debian Stretch

On Tue, Sep 19, 2017 at 18:44:35 +0200, Stefan G. Weichinger wrote: > Problem: > > even after installing mt-st, scsiutils etc and repeated reboots I > don't get any device files (/dev/nst? /dev/st? /dev/tape* etc) > > Even a mknod or modprobe st does not help: > >

no tape device(s) under Debian Stretch

Masked- Capabilities: [100] Advanced Error Reporting Capabilities: [138] Power Budgeting Kernel modules: megaraid_sas Problem: even after installing mt-st, scsiutils etc and repeated reboots I don't get any device files (/dev/nst? /dev/st? /dev/tape* etc) Even a mknod

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

use BLOCKSIZE:10240 >> 2017082317 slot-7 reuse BLOCKSIZE:10240 >> 2017082217 slot-6 reuse BLOCKSIZE:10240 >> 2017082117 slot-5 reuse BLOCKSIZE:10240 >> 2017082017 slot-4 reuse BLOCKSIZE:10240 >> 2017081917 slot-3 reuse BLOCKSIZE:10240 >> 2017081

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

7082017 slot-4 reuse BLOCKSIZE:10240 > 2017081917 slot-3 reuse BLOCKSIZE:10240 > 2017081817 slot-2 reuse BLOCKSIZE:10240 > 2017081717 slot-1 reuse BLOCKSIZE:10240 > 2017081617 slot-15 reuse BLOCKSIZE:10240 > 2017081517 slot-14 reuse BLOCKSIZE:1024 &g

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

The list of files with the 'slot-bb2e601e63b3408bb6a865e442a28366-6' prefix (slot-6) show there is no data in the slot, only the tape label. There is data only on slot-10,11,12 and 13. I have no idea why there is no data in the others slots. I assume the data was there after the backup, but I

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

admin.s3.amazonaws.com/slot-bb2e601e63b3408bb6a865e442a28366-6f0002-filestart failed with 404/NoSuchKey Tue Aug 29 08:27:19 2017: thd-0x1a8a600: amfetchdump: Device s3:onebip-backups-admin/slot-bb2e601e63b3408bb6a865e442a28366-6 error = 'Attempt to read past tape-end file' Tue Aug 29 08:27:19 2017: thd-0x1a

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

> > >> 1 volume(s) needed for restoration > >> The following volumes are needed: slot-6 > >> ERROR: Attempt to read past tape-end file > > And here is the list of the relevant backups: > > > >> backup@backup-server:~$ amadmin zfs-dataset find --so

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

and I’m getting this error with amfetchdump: amfetchdump -p -a zfs-dataset ci-master rpool/jenkins 2017082217 1 volume(s) needed for restoration The following volumes are needed: slot-6 ERROR: Attempt to read past tape-end file And here is the list of the relevant backups: backup@backup

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

-a zfs-dataset ci-master rpool/jenkins 2017082217 > >> 1 volume(s) needed for restoration >> The following volumes are needed: slot-6 >> ERROR: Attempt to read past tape-end file > > And here is the list of the relevant backups: > >> backup@backup-server:~$ amadmi

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

Hi all, I’m testing the restore process with Amanda and I’m getting this error with amfetchdump: amfetchdump -p -a zfs-dataset ci-master rpool/jenkins 2017082217 > 1 volume(s) needed for restoration > The following volumes are needed: slot-6 > ERROR: Attempt to read past tape

Re: Can't flush older dumps to a tape

6 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 to a tape I just can choose ALL or the > most recent. When I try to add a old one, amanda chooses the last one. > Follow exam

Re: Can't flush older dumps to a tape

to a tape I just can choose ALL or the most recent. When I try to add a old one, amanda chooses the last one. Follow example: *Tried to add 3 dumps, amanda choose the last one 3 times

Can't flush older dumps to a tape

*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 to a tape I just can choose ALL or the most recent. When I try to add a old one, amanda chooses the last one. Follow example: *Tried to add 3 dumps, amanda choose the last one

Re: two tape libraries with one configuration

Martineau wrote: 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.

Re: two tape libraries with one configuration

OK. So, for a more general question, how do people configure and use multiple drives in a tape library? How does Amanda plan for them and make use of them? How do you tell Amanda that it should use one tape in one drive and another tape in the other drive as opposed to finishing one tape

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

Re: two tape libraries with one configuration

On Fri, Jul 14, 2017 at 05:38:49PM -0400, Chris Hoogendyk wrote: > I've just acquired and set up a new Overland T48 with two LTO7 tape drives. > > I already have an Overland T24 with one LTO6 tape drive that I've been using > for a few years. > > I plan on transition

two tape libraries with one configuration

I've just acquired and set up a new Overland T48 with two LTO7 tape drives. I already have an Overland T24 with one LTO6 tape drive that I've been using for a few years. I plan on transitioning our large data to the LTO7 and thought I might keep the basic administrative backups on the LTO6

Re: Backup NAS to LTO7 tape library

memory to buffer the data feed which could vary in rate or be > insufficient to maintain streaming. > > When the data feed is insufficient, the drive waits for the > buffer to fill to some level, starts the tape, when up to > speed writes from the buffer until it drops to some level. &g

Re: Backup NAS to LTO7 tape library

in rate or be insufficient to maintain streaming. When the data feed is insufficient, the drive waits for the buffer to fill to some level, starts the tape, when up to speed writes from the buffer until it drops to some level. The drive stops writing, slows the tape to a stop, reverses the ta

Re: Backup NAS to LTO7 tape library

Makes sense. Thanks, Happy Canada Day, Greg On Fri, Jun 30, 2017 at 7:03 PM, Alan Hodgson wrote: > On Fri, 2017-06-30 at 18:55 -0400, Greg Dickie wrote: > > So I went back and explicitly set compress none. Apparently it > > defaults to "client fast". It seems faster

Re: Backup NAS to LTO7 tape library

On Fri, 2017-06-30 at 18:55 -0400, Greg Dickie wrote: > So I went back and explicitly set compress none. Apparently it > defaults to "client fast". It seems faster now although the size of > the estimate has doubled. What is the deal with compression. > Everything I've seen implies disabling

Re: Backup NAS to LTO7 tape library

t; > > I'm new to amanda so it's likely I just am confused about how it > > should be set up. > > > > What information can I provide that would help narrow it down? > > > > > > I haven't had the pleasure of using hardware that big or fast. > > Log

Re: Backup NAS to LTO7 tape library

Hi Jon, I did. I gave me this: define tapetype IBM-LTO7 { comment "Created by amtapetype; compression disabled" length 5876531200 kbytes filemark 4964 kbytes speed 291436 kps blocksize 2048 kbytes } The drive is SAS connected on a 6G HBA. I'm not sure what units kps is.

Re: Backup NAS to LTO7 tape library

to device > > > which is just writing the 2M blocks I guess. > > I'm new to amanda so it's likely I just am confused about how it > should be set up. > > What information can I provide that would help narrow it down? > > I haven't had the pleasure of using ha

Re: Backup NAS to LTO7 tape library

On Fri, Jun 30, 2017 at 03:30:19PM -0400, Greg Dickie wrote: > Hi Alan, > > Thanks for the response. It looks to me like taper is slow. I'm trying to > not use a holding disk, the NAS is 250TB and doesn't make sense to have > 250TB locally to cache it. It's connected by a 10G ethernet

Re: Backup NAS to LTO7 tape library

roprietary NAS to an LTO7 > > library with one drive but finding it very difficult to get tape > > spanning to work. The changer and drive seem to be configured > > correctly and it was all working fine until we exceeded the size of > > one tape and now whatever I seem to try fr

Re: Backup NAS to LTO7 tape library

On Fri, 2017-06-30 at 11:49 -0400, Greg Dickie wrote: > Hi, > >   I'm just trying to back up a large proprietary NAS to an LTO7 > library with one drive but finding it very difficult to get tape > spanning to work. The changer and drive seem to be configured > correctly and

Backup NAS to LTO7 tape library

Hi, I'm just trying to back up a large proprietary NAS to an LTO7 library with one drive but finding it very difficult to get tape spanning to work. The changer and drive seem to be configured correctly and it was all working fine until we exceeded the size of one tape and now whatever I seem

Re: Segfault from amcheck-device with cleaning tape installed

Sorry to keep replying to myself, but after 300MB of debuginfo, here's a more complete backtrace: Core was generated by `/usr/bin/perl /usr/lib64/amanda/amcheck-device math math'. Program terminated with signal SIGSEGV, Segmentation fault. #0 strlen () at ../sysdeps/x86_64/strlen.S:106 106

Re: Segfault from amcheck-device with cleaning tape installed

To verify everything, I swapped back in a regular tape, no problem. I put the cleaning tape back in and the problem returns. Checking coredumpctl (this is a Fedora system, so systemd is handling the cores) I see that... perl itself is segfaulting. Looking at the backtrace (which

Segfault from amcheck-device with cleaning tape installed

I replaced the last tape in my 48-slot library with a cleaning tape since I'd rather not bother with manually cleaning the drive. But this appears to make amcheck segfault: AMANDA:backup2:amanda/server/math> amcheck -s math Amanda Tape Server Host Check - N

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

t; $storage, $config, $comment) I manually applied this patch to the system Tapelist.pm file, and can confirm a newly-created tapelist file is populated correctly: ==== # rm tapelist # su backup -c "amlabel TestBackup TESTBACKUP-01 slot 1" Reading label... Found an empty tape. Writi

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

> (In the following examples, I delete the 0.TESTBACKUP-01 file out of > the vtape slot1 directory before each test run, so the only difference > is the existence of the "tapelist" file.) > > First test: if tapelist doesn't exist beforehand, amlabel creates it, &g

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

existence of the "tapelist" file.) First test: if tapelist doesn't exist beforehand, amlabel creates it, but the line for the newly-labled tape isn't written to it: = # rm tapelist # cat tapelist cat: tapelist: No such file or directory # su backup -c "amlabel TestBackup TEST

problem with taper not changing tape, 3.4.[12]

I've found what appears to be a bug in the 3.4 release of amanda: under some circumstances, amanda overwrites a tape that was just written. an example from a backup to tape: These dumps were to tape RAIDsSet6-35. The next 2 tapes Amanda expects to use are: RAIDsSet6-36, RAIDsSet6-37. taper

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

017, at 3:17 AM, ts...@portrix-systems.de wrote: > > ARGH, this is awkward, I just figured out what was calling amcheck on Feb 14 > 12:00. One of our cronjobs that is testing whether a new tape for the night > has to be inserted. > > Didn't expect amcheck to use the same interac

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

The patches work great, thanks again. I have noticed another issue regarding "device busy" though: During backup, after the first tape change, I get more "AMANDA VOLUME REQUEST" mails, even though the tape is still beeing written to and far from beeing full. I don't th

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

I committed both patches. Let me know if you have other issues or if it succeed! Jean-Louis On 10/02/17 09:37 AM, ts...@portrix-systems.de wrote: A quick test with amflush on previous holding-disk content didn't show the issue anymore. Tape was ejected, no more locking, flushing was able

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

A quick test with amflush on previous holding-disk content didn't show the issue anymore. Tape was ejected, no more locking, flushing was able 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

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

16:51:41 PST 2016 > > > Tapeinfo: > Vendor ID: 'HP ' > Product ID: 'Ultrium 4-SCSI ' > Revision: 'H63Z' > > > The test backup doesn't fit on one tape. After I get the E-Mail from > the interactivity module, I can see with lsof that the taper still has > a lock on /dev/ns

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

6.8 # uname -rsv Linux 4.1.12-61.1.23.el6uek.x86_64 #2 SMP Tue Dec 20 16:51:41 PST 2016 Tapeinfo: Vendor ID: 'HP ' Product ID: 'Ultrium 4-SCSI ' Revision: 'H63Z' The test backup doesn't fit on one tape. After I get the E-Mail from the interactivity module, I can see with lsof

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

: Vendor ID: 'HP ' Product ID: 'Ultrium 4-SCSI ' Revision: 'H63Z' The test backup doesn't fit on one tape. After I get the E-Mail from the interactivity module, I can see with lsof that the taper still has a lock on /dev/nst1: > # lsof /dev/nst1 COMMAND PID USER FD TYPE DEV

RE: Unable to make tape rotation work in Amanda - Seeking Help

Tape rotation issue is solved by changing taperscan algorithm to oldest. I am validating restores now. -Original Message- From: Stefan G. Weichinger [mailto:s...@amanda.org] Sent: 18 January 2017 20:08 To: Dinesh Vashisht; li...@xunil.at Cc: amanda-users@amanda.org Subject: Re: Unable

Re: Unable to make tape rotation work in Amanda - Seeking Help

Am 2017-01-18 um 12:24 schrieb Dinesh Vashisht: > [amandabackup@pciambkup DailySet19]$ *amcheck DailySet19* > Searching for label 'DailySet19-01':found in slot 1: volume 'DailySet19-01' > all slots have been loaded > > Taper scan algorithm did not find an acceptable volume. > (expecting

RE: Unable to make tape rotation work in Amanda - Seeking Help

After changing the retention-tapes to 11 in amanda.conf, still there is an error Taper error: "No acceptable volumes found" and cannot backup data. Following are details of amcheck & amreport commands: [amandabackup@pciambkup DailySet19]$ amcheck DailySet19 Amanda Tape Ser

Re: Unable to make tape rotation work in Amanda - Seeking Help

I think you should reduce retention-tapes to 11. tapecycle 12 -> retention-tapes 11

RE: Unable to make tape rotation work in Amanda - Seeking Help

[retention-tapes] slot 12: label DailySet19-12 (current) [retention-tapes] [amandabackup@pciambkup root]$ # amadmin DailySet19 tape amandabackup@pciambkup root]$ amadmin DailySet19 tape The next Amanda should go onto 1 new tape. [amandabackup@pciambkup root]$ and show the tapelist file

Re: Unable to make tape rotation work in Amanda - Seeking Help

Am 2017-01-18 um 10:24 schrieb Dinesh Vashisht: *amadmin DailySet1 inventory ?* -- It's not a valid command, instead: that should have been: # amtape DailySet19 inventory and please # amadmin DailySet19 tape and show the tapelist file why did you

RE: Unable to make tape rotation work in Amanda - Seeking Help

I tried this option labelstr "DailySet1-[0-9][0-9]*" creating another DLE. Still getting same error while running 'amcheck DailySet19' and tape rotation is not working: amandabackup@pciambkup DailySet19]$ amcheck DailySet19 Amanda Tape Server Host Check -

RE: Unable to make tape rotation work in Amanda - Seeking Help

What does "amcheck DailySet1" say? -- [amandabackup@pciambkup amanda]$ amcheck DailySet1 Amanda Tape Server Host Check - slot 12: volume 'DailySet1-12' is still active and cannot be overwritten slot 1: volume

Re: Unable to make tape rotation work in Amanda - Seeking Help

I assume the problem is here: labelstr "DailySet1" That should be something like: labelstr "DailySet1-[0-9][0-9]*" " otherwise every tape has the same label.

Re: amtoc doesn't properly generate tape content in amanda 3.4.1

On 17/12/16 12:27 PM, Jean-Francois Malouin wrote: * Jean-Louis Martineau <jmartin...@carbonite.com> [20161216 12:10]: On 16/12/16 10:33 AM, Jean-Francois Malouin wrote: This config has 'taper-parallel-write' set to 2 and during the amdump run both tape drives were in use at the sam

Re: amtoc doesn't properly generate tape content in amanda 3.4.1

* Jean-Louis Martineau <jmartin...@carbonite.com> [20161216 12:10]: > On 16/12/16 10:33 AM, Jean-Francois Malouin wrote: > >This config has 'taper-parallel-write' set to 2 and during the amdump > >run both tape drives were in use at the same time at some point.

Re: amtoc doesn't properly generate tape content in amanda 3.4.1

On 16/12/16 10:33 AM, Jean-Francois Malouin wrote: This config has 'taper-parallel-write' set to 2 and during the amdump run both tape drives were in use at the same time at some point. Could this explain the discrepancy between both outputs? yes, amtoc print the dump in the order

Re: amtoc doesn't properly generate tape content in amanda 3.4.1

at what they show: there is a mismatch between the amtoc output actual physical content of the tape: ~# cat $logdir/NEO-T48-B00022.toc # Server:/partition datelev size[Kb] 0 NEO-T48-B00022: 20161214095300- - 1 tutor172:/raid/ipl_sc

Re: amtoc doesn't properly generate tape content in amanda 3.4.1

Jean-Francois, amtoc was not fixed for the new log file format in 3.4 Try the attached patch. Jean-Louis On 15/12/16 02:46 PM, Jean-Francois Malouin wrote: Hi, Still getting acquainted with amanda-3.4.1 new feature but for the moment I'm having problems correctly generating table-of-content

amtoc doesn't properly generate tape content in amanda 3.4.1

NFO dumper dumper pid 29314 INFO dumper dumper pid 29313 INFO dumper dumper pid 29311 INFO dumper dumper pid 29316 INFO dumper dumper pid 29315 INFO taper taper pid 29308 FINISH planner date 20161214095300 time 1.119 INFO planner pid-done 29306 INFO taper Slot 21 with label NEO-T48-B00021 is usable

Amanda stalls when tape and holding disk both filled

I've run into this situation a couple of times. Amanda doesn't finish running. Top shows it not being active, though many processes exist if I look by user amandabackup. `df -k` shows the holding disks completely full with no free space. The tape drive is unloaded and idle. When I run `amstatus

Re: Disk and Tape Setup Config

Am 2016-09-01 um 20:10 schrieb Debra S Baddorf: On Sep 1, 2016, at 12:32 PM, Ryan Chase <rch...@vt.edu> wrote: Hi, I'm new to Amanda and I'm finding the Documentation difficult to navigate. I have a large nas disk to use for backup as well as a dell tape library. I'd like to backup t

Re: Disk and Tape Setup Config

> On Sep 1, 2016, at 12:32 PM, Ryan Chase <rch...@vt.edu> wrote: > > Hi, > I'm new to Amanda and I'm finding the Documentation difficult to > navigate. I have a large nas disk to use for backup as well as a dell > tape library. I'd like to backup to disk and also to ta

Disk and Tape Setup Config

Hi, I'm new to Amanda and I'm finding the Documentation difficult to navigate. I have a large nas disk to use for backup as well as a dell tape library. I'd like to backup to disk and also to tape for offsite backups. What is the best configuration scenario for this? I've read about a holding

Re: amreport claims tape is full but it is not

On Tue, Apr 26, 2016 at 12:48 PM, Chris Nighswonger < cnighswon...@foundations.edu> wrote: > So the Quantum tech had me run a device health test on the drive using > their xTalk utility. The drive failed with some sort of comm error similar > to what Amanda was seeing. So he then had me clean the

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