Re: HP Ultrium LTO C7972A Tapetype parameters
This one time, at band camp, Tim Edwards wrote: >Since it took almost 50 hours(!) for amtapetype to produce this I >thought I'd share it with the list in case it helps someone else: You might wanna add that to the faq-o-matic, next to my almost identical entry: http://amanda.sourceforge.net/cgi-bin/fom?_recurse=1&file=1#file_459
HP Ultrium LTO C7972A Tapetype parameters
Since it took almost 50 hours(!) for amtapetype to produce this I
thought I'd share it with the list in case it helps someone else:
define tapetype HPLTOC7972A {
comment "just produced by tapetype prog (hardware compression off)"
length 213576 mbytes
filemark 974 kbytes
speed 2116 kps
}
--
Tim Edwards
Re: got empty schedule from planner???
khalid maqsudi wrote: what steps can I take to preserve my config files and current setup. I'm "make install" does not install or modify any existing config files. running it on solaris 8. Also, I don't mind compiling amanda 2.4.4p4 and is that the better option or should I stick to 2.4.5 with gcc 3? 2.4.4p4 is stable. If you don't need the new features in 2.4.5, it's probably easier to go back to 2.4.4p4, then to install gcc 3 on Solaris. -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, * * quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ...* * ... "Are you sure?" ... YES ... Phew ... I'm out * ***
Re: got empty schedule from planner???
what steps can I take to preserve my config files and current setup. I'm running it on solaris 8. Also, I don't mind compiling amanda 2.4.4p4 and is that the better option or should I stick to 2.4.5 with gcc 3? -Thanks - Original Message - From: "Paul Bijnens" <[EMAIL PROTECTED]> To: "khalid maqsudi" <[EMAIL PROTECTED]> Cc: "amanda" Sent: Tuesday, June 14, 2005 4:21 PM Subject: Re: got empty schedule from planner??? > khalid maqsudi wrote: > > Hi, > > can anyone point out why My backup is not running. > [...] > > (brought to you by Amanda version 2.4.5) > > > > > > WARNING driver WARNING: got empty schedule from planner > > > I've not yet had the time to find out exactly why, but when compiling > amanda with gcc 2.95.X results in a broken planner, segfaulting. > > Compile again using gcc 3, or fall back to amanda 2.4.4p4. > > > > -- > Paul Bijnens, XplanationTel +32 16 397.511 > Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 > http://www.xplanation.com/ email: [EMAIL PROTECTED] > *** > * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, * > * quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * > * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * > * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * > * kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ...* > * ... "Are you sure?" ... YES ... Phew ... I'm out * > *** >
Re: got empty schedule from planner???
khalid maqsudi wrote: Hi, can anyone point out why My backup is not running. [...] (brought to you by Amanda version 2.4.5) WARNING driver WARNING: got empty schedule from planner I've not yet had the time to find out exactly why, but when compiling amanda with gcc 2.95.X results in a broken planner, segfaulting. Compile again using gcc 3, or fall back to amanda 2.4.4p4. -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, * * quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ...* * ... "Are you sure?" ... YES ... Phew ... I'm out * ***
got empty schedule from planner???
Hi, can anyone point out why My backup is not running. These dumps were to tape daily04. The next tape Amanda expects to use is: a new tape. The next new tape already labelled is: daily02. FAILURE AND STRANGE DUMP SUMMARY: m5413 /cust/home/khalid lev 0 FAILED [disk /cust/home/khalid, all estimate failed] STATISTICS: Total Full Incr. Estimate Time (hrs:min) 0:00 Run Time (hrs:min) 0:02 Dump Time (hrs:min) 0:00 0:00 0:00 Output Size (meg) 0.0 0.0 0.0 Original Size (meg) 0.0 0.0 0.0 Avg Compressed Size (%) -- -- -- Filesystems Dumped 0 0 0 Avg Dump Rate (k/s) -- -- -- Tape Time (hrs:min) 0:00 0:00 0:00 Tape Size (meg) 0.0 0.0 0.0 Tape Used (%) 0.0 0.0 0.0 Filesystems Taped 0 0 0 Avg Tp Write Rate (k/s) -- -- -- USAGE BY TAPE: Label Time Size % Nb daily04 0:00 0K 0.0 0 NOTES: planner: Adding new disk m5413:/cust/home/khalid. driver: WARNING: got empty schedule from planner taper: tape daily04 kb 0 fm 0 [OK] DUMP SUMMARY: DUMPER STATS TAPER STATS HOSTNAME DISK L ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s -- - m5413 -ome/khalid 0 FAILED --- (brought to you by Amanda version 2.4.5) WARNING driver WARNING: got empty schedule from planner
Re: I am correctly concluding I need only a tapecycle of 10 tapes - Using 10 tapes for fortnightly backup scheme.
Hi Again Thus continue and labelling DailySet101 - 110 as So far, to Dailyset 122 Thus end of each month pull that tape and carry on as usual. Thus as I started the backup with tape DailySet102 for tuesday as I want DailySet101 for first week monday. Have I got to edit the tapelist accordingly. Do I just On Tue, 2005-06-14 at 10:24 -0400, Jon LaBadie wrote: > On Tue, Jun 14, 2005 at 02:03:19PM +0100, Chuck Amadi Systems Administrator > wrote: > > Hi Great > > > > Yes I am going to use 10 tapes in total and reuse the first tape after > > 10 week days worth of backups. > > > > Thus is it fine to pull the last Friday tape at the end of the Month for > > archiving and then re-label the tape I pulled. > > > > > > On Tue, 2005-06-14 at 08:21 -0400, Jon LaBadie wrote: > > > On Tue, Jun 14, 2005 at 12:45:07PM +0100, Chuck Amadi Systems > > > Administrator wrote: > > > > Hi I have 10 dat tapes that I will run per my cycle 5 per 5 day week. > > > > Thus every fortnight. > > > > I am correctly concluding I need only a tapecycle of 10 tapes > > > > I hope to pull out the last Friday tape in that Month to archive and > > > > thus label another tape to replace it. > > > > > > > > Here's my config file. > > > > > > > > dumpcycle 0 weeks # the number of days in the normal dump cycle > > > > runspercycle 1 # the number of amdump runs in dumpcycle days > > > > # (4 weeks * 5 amdump runs per week -- just > > > > weekdays) > > > > tapecycle 10 tapes # the number of tapes in rotation > > > > # 4 weeks (dumpcycle) times 5 tapes per week > > > > (just > > > > # the weekdays) plus a few to handle errors that > > > > > > > > > > Think of tapecycle as how many "different" tapes amanda must use > > > before it will reuse the first one. In your setup, it looks like > > > full backups every run, tapecycle is as critical as a setup doing > > > mixed full and incrementals. Set it to whatever you want, or are > > > comfortable, having amanda not overwrite before being allowed to > > > reuse. If you want the last 10 full dumps to be sure to be around, > > > then set it to 10. If the last 5 is comfortable, you can set it > > > to 5, but still use 10 tapes. Amanda will only check that at least > > > 5 are still the most recent. > > > I just want to make certain I'm not confusing > your intent because of terminology. > > You want to "pull" the monthly tape and > "relabel the tape you pulled". > > That second part (relabelling) is a different tape, > right? If so, it is not "relabelling" but just > an initial label for that tape. > > Now, if you mean to use the same label as the one > pulled, think twice. Amanda keeps indexes of what > is on a tape. If you use the same label as the > pulled tape, then you will soon lose the index > for the pulled tape (when the new tape is used). > > Instead, when you pull a tape, mark it a "no-reuse". > The index will be retained. But the new tape will > need to have a different label. > > In fact, you could label up 22 tapes, 10 for cycling, > 12 in anticipation of pulling monthly for a year. > Your tapecycle could be set to 10, and you could > cycle through your first 10, or all 22. Amanda will > still ensure that the most recently used 10 are not > overwritten. Monthly, just pull whichever of the > 22 was used. You will have a "hole" in your tape > cycle, but amanda won't care. > > But maybe the human (you) will :)) If so, set your > label scheme up to be something like DS-xx.y where > xx is your ordering sequence and y is which replac- > ment. Maybe you label up DS-01.0 to DS-10.0. At > the end of the month, say you have to "pull" DS-05.0 > Mark it as no-reuse and label up a new DS-05.1. This > preserves your ordering and tells you it is a tape > not in the initial cycle. Might be important for > some tapes (eg. DAT) which have a fairly short life. > > Just some ideas. > > jl -- Unix/ Linux Systems Administrator Chuck Amadi The Surgical Material Testing Laboratory (SMTL), Princess of Wales Hospital Coity Road Bridgend, United Kingdom, CF31 1RQ. Email chuck.smtl.co.uk Tel: +44 1656 752820 Fax: +44 1656 752830
Re: I am correctly concluding I need only a tapecycle of 10 tapes - Using 10 tapes for fortnightly backup scheme.
On Tue, Jun 14, 2005 at 02:03:19PM +0100, Chuck Amadi Systems Administrator wrote: > Hi Great > > Yes I am going to use 10 tapes in total and reuse the first tape after > 10 week days worth of backups. > > Thus is it fine to pull the last Friday tape at the end of the Month for > archiving and then re-label the tape I pulled. > > > On Tue, 2005-06-14 at 08:21 -0400, Jon LaBadie wrote: > > On Tue, Jun 14, 2005 at 12:45:07PM +0100, Chuck Amadi Systems Administrator > > wrote: > > > Hi I have 10 dat tapes that I will run per my cycle 5 per 5 day week. > > > Thus every fortnight. > > > I am correctly concluding I need only a tapecycle of 10 tapes > > > I hope to pull out the last Friday tape in that Month to archive and > > > thus label another tape to replace it. > > > > > > Here's my config file. > > > > > > dumpcycle 0 weeks # the number of days in the normal dump cycle > > > runspercycle 1 # the number of amdump runs in dumpcycle days > > > # (4 weeks * 5 amdump runs per week -- just > > > weekdays) > > > tapecycle 10 tapes # the number of tapes in rotation > > > # 4 weeks (dumpcycle) times 5 tapes per week > > > (just > > > # the weekdays) plus a few to handle errors that > > > > > > > Think of tapecycle as how many "different" tapes amanda must use > > before it will reuse the first one. In your setup, it looks like > > full backups every run, tapecycle is as critical as a setup doing > > mixed full and incrementals. Set it to whatever you want, or are > > comfortable, having amanda not overwrite before being allowed to > > reuse. If you want the last 10 full dumps to be sure to be around, > > then set it to 10. If the last 5 is comfortable, you can set it > > to 5, but still use 10 tapes. Amanda will only check that at least > > 5 are still the most recent. I just want to make certain I'm not confusing your intent because of terminology. You want to "pull" the monthly tape and "relabel the tape you pulled". That second part (relabelling) is a different tape, right? If so, it is not "relabelling" but just an initial label for that tape. Now, if you mean to use the same label as the one pulled, think twice. Amanda keeps indexes of what is on a tape. If you use the same label as the pulled tape, then you will soon lose the index for the pulled tape (when the new tape is used). Instead, when you pull a tape, mark it a "no-reuse". The index will be retained. But the new tape will need to have a different label. In fact, you could label up 22 tapes, 10 for cycling, 12 in anticipation of pulling monthly for a year. Your tapecycle could be set to 10, and you could cycle through your first 10, or all 22. Amanda will still ensure that the most recently used 10 are not overwritten. Monthly, just pull whichever of the 22 was used. You will have a "hole" in your tape cycle, but amanda won't care. But maybe the human (you) will :)) If so, set your label scheme up to be something like DS-xx.y where xx is your ordering sequence and y is which replac- ment. Maybe you label up DS-01.0 to DS-10.0. At the end of the month, say you have to "pull" DS-05.0 Mark it as no-reuse and label up a new DS-05.1. This preserves your ordering and tells you it is a tape not in the initial cycle. Might be important for some tapes (eg. DAT) which have a fairly short life. Just some ideas. jl -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: I am correctly concluding I need only a tapecycle of 10 tapes - Using 10 tapes for fortnightly backup scheme.
Hi Great Yes I am going to use 10 tapes in total and reuse the first tape after 10 week days worth of backups. Thus is it fine to pull the last Friday tape at the end of the Month for archiving and then re-label the tape I pulled. Thanks I am nearly there . Cheers On Tue, 2005-06-14 at 08:21 -0400, Jon LaBadie wrote: > On Tue, Jun 14, 2005 at 12:45:07PM +0100, Chuck Amadi Systems Administrator > wrote: > > Hi I have 10 dat tapes that I will run per my cycle 5 per 5 day week. > > Thus every fortnight. > > I am correctly concluding I need only a tapecycle of 10 tapes > > I hope to pull out the last Friday tape in that Month to archive and > > thus label another tape to replace it. > > > > Here's my config file. > > > > dumpcycle 0 weeks # the number of days in the normal dump cycle > > runspercycle 1 # the number of amdump runs in dumpcycle days > > # (4 weeks * 5 amdump runs per week -- just > > weekdays) > > tapecycle 10 tapes # the number of tapes in rotation > > # 4 weeks (dumpcycle) times 5 tapes per week > > (just > > # the weekdays) plus a few to handle errors that > > > > Think of tapecycle as how many "different" tapes amanda must use > before it will reuse the first one. In your setup, it looks like > full backups every run, tapecycle is as critical as a setup doing > mixed full and incrementals. Set it to whatever you want, or are > comfortable, having amanda not overwrite before being allowed to > reuse. If you want the last 10 full dumps to be sure to be around, > then set it to 10. If the last 5 is comfortable, you can set it > to 5, but still use 10 tapes. Amanda will only check that at least > 5 are still the most recent. > -- Unix/ Linux Systems Administrator Chuck Amadi The Surgical Material Testing Laboratory (SMTL), Princess of Wales Hospital Coity Road Bridgend, United Kingdom, CF31 1RQ. Email chuck.smtl.co.uk Tel: +44 1656 752820 Fax: +44 1656 752830
Re: I am correctly concluding I need only a tapecycle of 10 tapes - Using 10 tapes for fortnightly backup scheme.
On Tue, Jun 14, 2005 at 12:45:07PM +0100, Chuck Amadi Systems Administrator wrote: > Hi I have 10 dat tapes that I will run per my cycle 5 per 5 day week. > Thus every fortnight. > I am correctly concluding I need only a tapecycle of 10 tapes > I hope to pull out the last Friday tape in that Month to archive and > thus label another tape to replace it. > > Here's my config file. > > dumpcycle 0 weeks # the number of days in the normal dump cycle > runspercycle 1 # the number of amdump runs in dumpcycle days > # (4 weeks * 5 amdump runs per week -- just > weekdays) > tapecycle 10 tapes # the number of tapes in rotation > # 4 weeks (dumpcycle) times 5 tapes per week > (just > # the weekdays) plus a few to handle errors that > Think of tapecycle as how many "different" tapes amanda must use before it will reuse the first one. In your setup, it looks like full backups every run, tapecycle is as critical as a setup doing mixed full and incrementals. Set it to whatever you want, or are comfortable, having amanda not overwrite before being allowed to reuse. If you want the last 10 full dumps to be sure to be around, then set it to 10. If the last 5 is comfortable, you can set it to 5, but still use 10 tapes. Amanda will only check that at least 5 are still the most recent. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Howto commence using a previously used test tape into production cycle of tapes to backup root directory.
On Tue, Jun 14, 2005 at 12:04:03PM +0100, Chuck Amadi Systems Administrator wrote: > Hi Great > > I did see that note > > Q: Why does `amcheck' say `cannot overwrite active tape'? > > A: Because, if you configure Amanda to use N tapes, by setting > tapecycle to N in `amanda.conf', before Amanda overwrites a tape, it > must write to at least other N-1 tapes. Of course, Amanda will always > refuse to overwrite a tape marked for `noreuse' with `amadmin'. > Furthermore, such tapes are not counted when Amanda computes `N-1' > tapes. > >If, for some reason, you want to tell Amanda to overwrite a > particular tape, regardless of its position in the cycle, use > `amrmtape'. This command will remove this tape from the `tapelist' > file, that is used to manage the tape cycle, and will delete > information about backups stored in that tape from the Amanda > database. > > Cheers > > On Tue, 2005-06-14 at 12:58 +0200, Filip Rembia³kowski wrote: > > At 06/14/05 12:19, Chuck Amadi Systems Administrator wrote: > > > Hi all > > > > > > I have finished testing phase and I would like to use the initial tape > > > again this tape had dumped /etc which obviously didn't dump much data. > > > I am now going to change the disklist from "/etc" to "/" what is the > > > best way to go about it. > > > > > > Cheers > > > > > > > > just amrmtape and amlabel again :) > > > > Man amlabel, the -f option. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
I am correctly concluding I need only a tapecycle of 10 tapes - Using 10 tapes for fortnightly backup scheme.
Hi I have 10 dat tapes that I will run per my cycle 5 per 5 day week. Thus every fortnight. I am correctly concluding I need only a tapecycle of 10 tapes I hope to pull out the last Friday tape in that Month to archive and thus label another tape to replace it. Here's my config file. dumpcycle 0 weeks # the number of days in the normal dump cycle runspercycle 1 # the number of amdump runs in dumpcycle days # (4 weeks * 5 amdump runs per week -- just weekdays) tapecycle 10 tapes # the number of tapes in rotation # 4 weeks (dumpcycle) times 5 tapes per week (just # the weekdays) plus a few to handle errors that Cheers Chuck -- Unix/ Linux Systems Administrator Chuck Amadi The Surgical Material Testing Laboratory (SMTL), Princess of Wales Hospital Coity Road Bridgend, United Kingdom, CF31 1RQ. Email chuck.smtl.co.uk Tel: +44 1656 752820 Fax: +44 1656 752830
Re: Howto commence using a previously used test tape into production cycle of tapes to backup root directory.
Hi Great I did see that note Q: Why does `amcheck' say `cannot overwrite active tape'? A: Because, if you configure Amanda to use N tapes, by setting tapecycle to N in `amanda.conf', before Amanda overwrites a tape, it must write to at least other N-1 tapes. Of course, Amanda will always refuse to overwrite a tape marked for `noreuse' with `amadmin'. Furthermore, such tapes are not counted when Amanda computes `N-1' tapes. If, for some reason, you want to tell Amanda to overwrite a particular tape, regardless of its position in the cycle, use `amrmtape'. This command will remove this tape from the `tapelist' file, that is used to manage the tape cycle, and will delete information about backups stored in that tape from the Amanda database. Cheers On Tue, 2005-06-14 at 12:58 +0200, Filip Rembiałkowski wrote: > At 06/14/05 12:19, Chuck Amadi Systems Administrator wrote: > > Hi all > > > > I have finished testing phase and I would like to use the initial tape > > again this tape had dumped /etc which obviously didn't dump much data. > > I am now going to change the disklist from "/etc" to "/" what is the > > best way to go about it. > > > > Cheers > > > > > just amrmtape and amlabel again :) > > -- Unix/ Linux Systems Administrator Chuck Amadi The Surgical Material Testing Laboratory (SMTL), Princess of Wales Hospital Coity Road Bridgend, United Kingdom, CF31 1RQ. Email chuck.smtl.co.uk Tel: +44 1656 752820 Fax: +44 1656 752830
Backup through firewall: --with-portrange=xxx,yyy - reconfigure client/server/both?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I am trying to backup a client which resides behind a firewall. As per the notes at http://amanda.sourceforge.net/fom-serve/cache/139.html I see that AMANDA needs to be rebuilt with options for - --with-portrange=xxx,yyy and --with-udpportrange=xxx,yyy My question is, does AMANDA need to be rebuilt with those options (a) on the server; (b) on the client; (c) on both the client and the server? Dave. - -- Dave Ewart [EMAIL PROTECTED] Computing Manager, Cancer Epidemiology Unit Cancer Research UK / Oxford University PGP: CC70 1883 BD92 E665 B840 118B 6E94 2CFD 694D E370 N 51.7518, W 1.2016 -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFCrrlGbpQs/WlN43ARAtcjAJ9Kl2OcreXzuCwkziEyvdvp4pOWEACZAd/1 oGQ4Zx5FyG9gyMb/jlx2z3Q= =x16Q -END PGP SIGNATURE-
Re: Howto commence using a previously used test tape into production cycle of tapes to backup root directory.
At 06/14/05 12:19, Chuck Amadi Systems Administrator wrote: Hi all I have finished testing phase and I would like to use the initial tape again this tape had dumped /etc which obviously didn't dump much data. I am now going to change the disklist from "/etc" to "/" what is the best way to go about it. Cheers just amrmtape and amlabel again :) -- Filip Rembiałkowski Administrator sieci Kolmet Sp. z o.o. tel:+48-22-5332007 tel:+48-604065651 http://www.kolmet.com.pl mailto:[EMAIL PROTECTED]
Howto commence using a previously used test tape into production cycle of tapes to backup root directory.
Hi all I have finished testing phase and I would like to use the initial tape again this tape had dumped /etc which obviously didn't dump much data. I am now going to change the disklist from "/etc" to "/" what is the best way to go about it. Cheers -- Unix/ Linux Systems Administrator Chuck Amadi The Surgical Material Testing Laboratory (SMTL), Princess of Wales Hospital Coity Road Bridgend, United Kingdom, CF31 1RQ. Email chuck.smtl.co.uk Tel: +44 1656 752820 Fax: +44 1656 752830
Re: out-of-tape on dump errors
Hi Mike! Does anyone now why Amanda might generate an out of tape error in a situation where it blatantly isn't anywhere even close to the end of the tape? As I understand it, Amanda interpretes any non-ok result from the tape device as "out of tape" - as most backup and tape handling software does. Bye, Peter WOTLmade
out-of-tape on dump errors
Hi,
Does anyone now why Amanda might generate an out of tape error in a
situation where it blatantly isn't anywhere even close to the end of the
tape?
I'm dumping four servers to an external Ultrium 100/200Gb unit, with
hardware compression turned off, and the largest filesystem failed last
night. Selected excerpts from the log:-
==
*** A TAPE ERROR OCCURRED: [[writing filemark: Input/output error]].
Some dumps may have been left in the holding disk.
Run amflush to flush them to tape.
The next tape Amanda expects to use is: ACU-STD-15.
FAILURE AND STRANGE DUMP SUMMARY:
castor sda12 lev 1 STRANGE
castor sda8 lev 0 STRANGE
castor sda10 lev 0 FAILED [out of tape]
==
the filesystem in question:-
==
DUMPER STATS TAPER STATS
HOSTNAME DISK L ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s
- --- -
castor sda10 0 36167772 20726828 57.3 188:08 1836.2 FAILED --
==
and the notes:-
==
NOTES:
planner: Incremental of pollux:sda8 bumped to level 2.
planner: Incremental of castor:sda8 bumped to level 2.
planner: Incremental of yildun:hda6 bumped to level 2.
taper: tape ACU-STD-14 kb 9456384 fm 29 writing filemark: Input/output
error
driver: going into degraded mode because of tape error.
==
The tapetype entry was generated for this drive by running amtapetype,
and is:-
define tapetype HP-ULTRIUM-230 {
comment "HP Ultrium 230e"
length 101376 mbytes
filemark 0 kbytes
speed 13855 kps
}
I've had successful runs with more data than this one would have had -
is this just a glitch, or is there something I can/should be doing about it?
Mike.
