that as backup, but I
would like a tape system that works well.
This option is worth considering. HD's have many fewer moving parts
than tapes/drives. Even if the critical failure rate is similar,
the annoying failure rate of tape drives is much higher. Which is
to say, they require a lot more
it full of 1TB hard drives and using that as backup, but I
would like a tape system that works well.
This option is worth considering. HD's have many fewer moving parts
than tapes/drives. Even if the critical failure rate is similar,
the annoying failure rate of tape drives is much higher
, five to maybe 15 watts for the FIT-PC and two
external HDs (when they're powered up). Try that with your SCSI tape
drives. :-)
As an extra added benefit, I can do an integrity check on all my
tapes with diff -r --brief. It takes a while, but with screen, who
cares?
Another benefit is that I can
On Wednesday 15 October 2008, Emmanuel Kasper wrote:
Hello
Is it possible to use something a hard drive cartridge like this
http://www.dell.com/content/products/productdetails.aspx/pvaul_rd1000?c=usc
s=04l=ens=bsd as a real tape device in Amanda ? ( Not vtape )
I was wondering
backing up regularly, and soon will increase that to a larger number as
well. I am looking for a good service tape drive that can take care of
the physical offloading of backups, and that plays well with Amanda. I
have an old SCSI HP SureStore that I can never get to really back up to
(Pity
On Wed, Oct 15, 2008 at 7:12 AM, Emmanuel Kasper
[EMAIL PROTECTED] wrote:
Is it possible to use something a hard drive cartridge like this
http://www.dell.com/content/products/productdetails.aspx/pvaul_rd1000?c=uscs=04l=ens=bsd
as a real tape device in Amanda ? ( Not vtape )
I was wondering
On Wed, Oct 15, 2008 at 10:44 AM, Seann Clark
[EMAIL PROTECTED] wrote:
The other alternative I am looking into is getting a large external case and
cramming it full of 1TB hard drives and using that as backup, but I would
like a tape system that works well.
This option is worth considering
Hello
Is it possible to use something a hard drive cartridge like this
http://www.dell.com/content/products/productdetails.aspx/pvaul_rd1000?c=uscs=04l=ens=bsd
as a real tape device in Amanda ? ( Not vtape )
I was wondering if there are physical properties of a hard drive which
prevent it from
3.12TB of data, which I would like
to start backing up regularly, and soon will increase that to a
larger number as well. I am looking for a good service tape drive
that can take care of the physical offloading of backups, and that
plays well with Amanda. I have an old SCSI HP SureStore that I can
Emmanuel Kasper wrote:
Hello
Is it possible to use something a hard drive cartridge like this
http://www.dell.com/content/products/productdetails.aspx/pvaul_rd1000?c=uscs=04l=ens=bsd
as a real tape device in Amanda ? ( Not vtape )
I was wondering if there are physical properties of a hard
would like to
start backing up regularly, and soon will increase that to a larger
number as well. I am looking for a good service tape drive that can
take care of the physical offloading of backups, and that plays well
with Amanda. I have an old SCSI HP SureStore that I can never get to
really back
Of Seann Clark
Sent: Wednesday, October 15, 2008 10:45 AM
To: amanda-users@amanda.org
Subject: Tape drives -- Recommendations?
All,
I am fairly new to the list, not so new to Amanda (I usually troll
IRC when I am looking for help half the time) but I want to poll the
group for suggestions
LTO is the most commonly used tape drive technology among Amanda users. When
we conducted an extensive survey of Amanda usage, almost 40% of
respondents said they use LTO tape drives:
http://wiki.zmanda.com/index.php/Results_of_Amanda_Users_Survey_2006
Considering the price difference between
On Wednesday 15 October 2008, Dustin J. Mitchell wrote:
On Wed, Oct 15, 2008 at 10:44 AM, Seann Clark
[EMAIL PROTECTED] wrote:
The other alternative I am looking into is getting a large external case
and cramming it full of 1TB hard drives and using that as backup, but I
would like a tape
On Sun, Oct 12, 2008 at 6:32 PM, Terry Burton [EMAIL PROTECTED] wrote:
This sounds very interesting and I would certainly like to take a look
at this, though more out of curiosity that anything else, so if it is
not much trouble to make this accessible then please do.
What a great opportunity
On Mon, Oct 6, 2008 at 5:23 PM, Dustin J. Mitchell [EMAIL PROTECTED] wrote:
On Mon, Oct 6, 2008 at 4:54 AM, Terry Burton [EMAIL PROTECTED] wrote:
It would still be great to avoid manually balancing the DLEs between
configs in future if possible, so if any Amanda developers are able to
supply
, or are there other, non-obvious
problems that make this a bad idea.
I have more than one configuration using 1 tape-changer, but not
simultaneously. Makes thing simpler.
chg-zd-mtx does not provide locking.
I took care to share (by symlinks) some of the chg-zd-mtx config files
by the amanda-configurations
each in 24 slots
library to backup +20TB of data. Each server has 2 config concurrently
accessing the robot with chg-zd-mtx. It can be achieved with minimum
difficulties if you have sufficient holding disk space and use tape
spanning. Back in the days, I was even using a 8 drives library split
amanda-users, amanda-hackers,
Is support for simultaneously writing to multiple tape drives on the
Amanda roadmap? If so, when can this be reasonably expected? If not,
what are the major complexities prohibiting this development and is
there anything that is required in order to raise its
* Terry Burton [EMAIL PROTECTED] [20081003 12:47]:
amanda-users, amanda-hackers,
Is support for simultaneously writing to multiple tape drives on the
Amanda roadmap? If so, when can this be reasonably expected? If not,
what are the major complexities prohibiting this development
/FAQ:How_are_backup_levels_defined_and_how_does_Amanda_use_them%3F
Typically, one uses a shorter dumpcycle, fewer runspercycle, and a
longer tapecycle. So, for example, I have 1 week, 7 runs, and 35 tapes.
I understand that you want to conserve tape usage, and are keeping
backups on the holding disk until you have enough to fill a tape. I
Hi,
I've got a backup set for a bunch of Mac OS X users who are backed up on a
daily basis via Samba shares.
Backups are first backed up to holding disk, then dumped to tape once I've got
enough to fill an LTO3 tape.
The other day I was asked to restore a file which had ended up going
On Tue, 23 Sep 2008 at 9:37am, Dan Brown wrote
2. How do I retrieve my file off of tape not using amrecover?
This one's easy -- 'man amrestore'.
--
Joshua Baker-LePain
QB3 Shared Cluster Sysadmin
UCSF
for a bunch of Mac OS X users who are backed up
on a daily basis via Samba shares.
Backups are first backed up to holding disk, then dumped to tape once
I've got enough to fill an LTO3 tape.
The other day I was asked to restore a file which had ended up going
on to tape (just a day or two ago
Dan Brown wrote:
Hi,
I've got a backup set for a bunch of Mac OS X users who are backed up
on a daily basis via Samba shares.
Backups are first backed up to holding disk, then dumped to tape once
I've got enough to fill an LTO3 tape.
The other day I was asked to restore a file which had
Thanks Joshua, Jean-Louis,
amrestore doesn't have the sort of granularity I'd like but the shotgun approach
works as well as a pinpoint approach. I was hoping I wouldn't have to restore
178GB of data for a 10MB file.
Dan Brown
[EMAIL PROTECTED]
on the granularity of your
disklist. When you're using tar as your dumper (and, with smb, you are),
you *have* to read the whole tape file. (Note that this may also be the
case with dump images -- I just haven't used dump in a long while).
That's just how tar works. So if the DLE you need that 10MB
Chris Hoogendyk wrote:
First, it should work. amrecover should get things off the holding disk
or off tape as appropriate. When you say came to realize, I think we
need some more detail on what you mean by that. What errors did you get?
How did you try? Did you use setdate to get
-Louis
Dan Brown wrote:
Chris Hoogendyk wrote:
First, it should work. amrecover should get things off the holding
disk
or off tape as appropriate. When you say came to realize, I
think we
need some more detail on what you mean by that. What errors did
you get?
How did you try? Did you
Hi All,
Many thanks for your reply,
I figured it out, i was relating to an old documentation config from the
internet.
My new holding disk config is a follows.
org BackupServer - Daily Tape
mailto root
dumpuser amanda
inparallel 4
netusage 600
# a filesystem is due for a full backup once
Prashant Ramhit schrieb:
I figured it out, i was relating to an old documentation config from the
internet.
Best and newest documentation of amanda you can find in the wiki:
http://wiki.zmanda.com
--
Marc Muehlfeld (Leitung IT)
Zentrum fuer Humangenetik und Laboratoriumsmedizin Dr. Klein
Hi All,
I am doing a daily backup of my system on an LTO-4 tape with a single
tape drive.
When labelling the tape, I am receiving the errors described below.
Someone please give me a few notes on what is wrong.
Kind regards,
Prashant
### Errors ##
[EMAIL PROTECTED]:/etc/amanda/fullback
Prashant Ramhit wrote:
Hi All,
I am doing a daily backup of my system on an LTO-4 tape with a single
tape drive.
When labelling the tape, I am receiving the errors described below.
Someone please give me a few notes on what is wrong.
Kind regards,
Prashant
### Errors
Prashant Ramhit schrieb:
[EMAIL PROTECTED]:/etc/amanda/fullback# amlabel fullback FULLBACK-01
/etc/amanda/fullback/amanda.conf, line 22: configuration keyword
expected
/etc/amanda/fullback/amanda.conf, line 22: end of line is expected
...
...
diskdir /var/tmp/amanda
Did you upgrade from
Frank Smith schrieb:
What version of amanda are you running? The line 22 of your config that
seems to be causing the error is diskdir /var/tmp/amanda, and diskdir
doesn't seem to be a valid parameter in my version (and probably not yours
either since it is showing an error).
diskdir was the
On Thu, Sep 11, 2008 at 11:53 PM, Olivier Nicole [EMAIL PROTECTED] wrote:
Is there a mechanism in Amanda to ensure that only a single tape
changer process is running at any given time?
No -- and this poses a problem for processes that want to move data
between devices. I'm working
Dustin J. Mitchell wrote at 09:32 -0400 on Sep 12, 2008:
On Thu, Sep 11, 2008 at 11:53 PM, Olivier Nicole [EMAIL PROTECTED] wrote:
Is there a mechanism in Amanda to ensure that only a single tape
changer process is running at any given time?
No -- and this poses a problem
Hello everybody,
I'm trying to configure Amanda, using a tape autoloader. I think I could
use two tape during the backup. Therefore, I'm trying to set amanda so
that it uses *tpchnger chg-multi*. But this device has just 1 driver
(/dev/nst0). My question is that when I configure the file
Adriana Liendo schrieb:
Hello everybody,
I'm trying to configure Amanda, using a tape autoloader. I think I could
use two tape during the backup. Therefore, I'm trying to set amanda so
that it uses *tpchnger chg-multi*.
Why did you choose that one?
Why not use chg-zd-mtx, look inside
On Tue, Aug 19, 2008 at 4:12 PM, Adriana Liendo [EMAIL PROTECTED] wrote:
I'm trying to configure Amanda, using a tape autoloader. I think I could use
two tape during the backup. Therefore, I'm trying to set amanda so that it
uses tpchnger chg-multi. But this device has just 1 driver (/dev/nst0
or so.
RAIT is the current best option. As long as you're mirroring, there's
no problem with deleting a vtape after 7 days. If you need to recover
that data, you'll just retrieve the tape and use it directly. So a
little bit of shell wrapper can get you up and running with this scheme
It looks like the problem is with the robotics in my L9. I've taken out
the cassette holder from the front and the autoloader section is sitting
hald-extended into slot 8 at the back.. 8-) Not sure if I should turn the
unit off and on, or try and manually pull the mechanism out of the tape
Hi all,
I'm going to be setting up a new Amanda config with tapes going offsite.
We're going to be using 30 tapes or so. As the tapes leave straight away
after being written we want to keep copies of the data written to them
on disk for (say) 7 days.
I've looked into using RAIT to do this
or so.
RAIT is the current best option. As long as you're mirroring, there's
no problem with deleting a vtape after 7 days. If you need to recover
that data, you'll just retrieve the tape and use it directly. So a
little bit of shell wrapper can get you up and running with this
scheme in no time
Dustin J. Mitchell schrieb:
On Thu, Aug 7, 2008 at 7:37 PM, Craig Dewick [EMAIL PROTECTED] wrote:
Can any generic DLT-8000 raw drive be used to replace the existing one? I
believe they're all made by Quantum. Other than the tape drive issue, I've
got Amanda working fine backing up all my
On Fri, 8 Aug 2008, Stefan G. Weichinger wrote:
Dustin J. Mitchell schrieb:
On Thu, Aug 7, 2008 at 7:37 PM, Craig Dewick [EMAIL PROTECTED]
wrote:
Can any generic DLT-8000 raw drive be used to replace the existing one? I
believe they're all made by Quantum. Other than the tape drive issue
I've determined my drive can label tapes but can't read old
tapes. I get the Input/Output error whenever trying to read a
previously labeled tape or dd out anything. However, if I re-label
the tape it works again. Does this indicate a failing drive? Any
other ideas?
Thanks,
Steve
Steven Backus wrote at 10:20 -0600 on Aug 7, 2008:
I've determined my drive can label tapes but can't read old
tapes. I get the Input/Output error whenever trying to read a
previously labeled tape or dd out anything. However, if I re-label
the tape it works again. Does this indicate
[EMAIL PROTECTED] writes:
I've seen problematic behavior when the tape unit is set to have a
particular block size (that may not match at read time what was used
to write a tape).
That was the problem. In my rc.local file I have:
/bin/mt defcompression 0
/bin/mt defblksize 0
But with the mt
On Thu, Aug 7, 2008 at 1:06 PM, Steven Backus
[EMAIL PROTECTED] wrote:
Thanks to John Hein and everyone.
I haven't followed this too closely, but are there some takeaway
messages that could be worked into a FAQ here?
http://wiki.zmanda.com/index.php/FAQ
Dustin
--
Storage Software Engineer
On Thu, Aug 7, 2008 at 5:25 PM, Steven Backus
[EMAIL PROTECTED] wrote:
FAQ:Why can I write new labels to my tapes but can't read the old ones?
Check your blocksize. This behavior occurs when the tape unit is
set to have a particular block size (that may not match at read
time what was used
. This behavior occurs when the tape unit is
set to have a particular block size (that may not match at read
time what was used to write a tape).
Steve
--
Steven J. BackusComputer Specialist
University of Utah E-Mail: [EMAIL PROTECTED]
Genetic
Dustin J. Mitchell [EMAIL PROTECTED] writes:
Are there more details to add? The 'mt' invocations in rc.conf may be
helpful to others, for example.
FAQ:Why can I write new labels to my tapes but can't read the old ones?
Check your blocksize. This behavior occurs when the tape unit is
set
at the same
time that a new amanda configuration file is missing a blocksize option.
We should probably just expand the blocksize section of the FAQ and
point people with issues reading tape labels to it as a possible cause.
I know the whole concept of fixed blocksize verse variable can get
This is a little off-topic but relevant since we're all more or less in
the same position in that we're using tape arrays of some sort...
The DLT-8000 drive in my L9 has been running slower and slower over the
past week, and now is not working at all. I suspect all the rollers, etc
On Thu, Aug 7, 2008 at 7:37 PM, Craig Dewick [EMAIL PROTECTED] wrote:
Can any generic DLT-8000 raw drive be used to replace the existing one? I
believe they're all made by Quantum. Other than the tape drive issue, I've
got Amanda working fine backing up all my systems including my
Strongbolt
This all sounds great. Not to sound like an overworked developer, but
could you all please update the FAQ entry accordingly? ;)
http://wiki.zmanda.com/index.php/FAQ:Why_can_I_write_new_labels_to_my_tapes_but_can%27t_read_the_old_ones%3F
Dustin
--
Storage Software Engineer
On Tue, Aug 5, 2008 at 3:04 PM, Vectorz Sigma [EMAIL PROTECTED] wrote:
I have an Ultrium LTO-4, and cannot get it to work with Amanda.
You had pasted some other diagnostic output that I didn't recognize to
#amanda. Can you give some more details? Also, please have a look in
your kernel logs to
My tapedev entry that works is tapedev /dev/nst0 not tapedev tape:/dev/nst0
I have used the follow tape specific entries in my amanda.conf:
tapedev /dev/nst0 # Linux @ tuck, important: norewinding
tapetype LTO4 # what kind of tape it is (see tapetypes below)
labelstr ^FULLBACK-[0-9][0-9
Doyle, thanks for the tip but I got errors when trying it without the
tape: in the string. I forgot to mention that I'm using 2.6.0p1
This is the error:
# amlabel WeeklySet1 Weekly-01
Reading label...
/dev/nst0 uses deprecated device naming convention;
using tape:/dev/nst0 instead.
Can't open
of hand
backing up a filesystem that had over 10million files on it, the db grew
7gb+ additionally for every full backup of this FS I had in the retention
period.
In any event, here is the mt status:
# mt -f /dev/nst0 status
SCSI 2 tape drive:
File number=0, block number=0, partition=0.
Tape block
On Wed, Aug 6, 2008 at 11:00 AM, Vectorz Sigma [EMAIL PROTECTED] wrote:
Doyle, thanks for the tip but I got errors when trying it without the
tape: in the string. I forgot to mention that I'm using 2.6.0p1
The tape: thing is not the issue here -- the code that writes the
deprecation warning
version built by RTist BV - The Netherlands on Oct 11 2007, 23:22:05
Tape Drive identified as LTO4(IBM)
/dev/nst0 - Vendor: IBM
/dev/nst0 - Product ID: ULTRIUM-TD4
/dev/nst0 - Firmware : 74H6
/dev/nst0 - Serialnum : 1310082873
/dev/nst0 - This tape : 5 times loaded into a drive
Done
The mystery deepens.
Can you run 'amlabel' under strace or truss or your local equivalent?
I'd like to know what syscall is returning EBADFD (Bad file
descriptor). Also, please remind me what version of Amanda you're
running.
You can send the strace output to me privately for analysis if you'd
Performance Test Started on Drive (Ultrium 4-SCSI)
(0.0.0[0-/dev/sg0])
- Opening Tape Drive 0.0.0[0-/dev/sg0]
- Successfully opened the Tape Drive /dev/nst0
- 2147 MB written in 28.6348 seconds at 74.9955 MB/s
Matthew Marlowe [EMAIL PROTECTED] wrote:
Are you using RHEL or Fedora? The bug is reported for fedora 8 but
we just noticed a similar issue on a RHEL5.2 box (perhaps this is
one of the feature updates carried over from fedora during the 5.2
upgrade).
I'm on RHEL 4.x, latest updates, that's
by
root:root). I chmod'd to 777 to test and that fixed the problem.
Is it a known deal that we're supposed to change permission on the tape dev
name?
On Wed, Aug 6, 2008 at 2:50 PM, Dustin J. Mitchell [EMAIL PROTECTED]wrote:
The mystery deepens.
Can you run 'amlabel' under strace or truss or your
permissions to the /dev/nst0 device (which was 750 perms and owned by
root:root). I chmod'd to 777 to test and that fixed the problem.
Is it a known deal that we're supposed to change permission on the tape dev
name?
The device should have the group 'disk' (or equivalent), and
amandabackup
Steve,
Ever since my latest update from Red Hat, my VXA-2 tape library
has stopped working. It appears /dev/tape is now a directory
instead of a link to /dev/nst0 and every command I give to the
drive returns /dev/nst0: Input/output error.
See the following Red Hat bug:
https
On 04.08.2008 13:45, Chris Hoogendyk wrote (please find the answer below the
original text):
Steven Backus wrote:
Ever since my latest update from Red Hat, my VXA-2 tape library
has stopped working. It appears /dev/tape is now a directory
instead of a link to /dev/nst0 and every command I
I was doing some amanda testing and labeled a tape. Afterwards I backed up to
the tape using tar not amanda. I used the following syntax tar -c -b 4096 -f
/dev/nst0 /mnt/mail/logancty. I am unable to even list the files on the tape
using tar -t /dev/nst0. We have found that we are able
Matthew Marlowe [EMAIL PROTECTED] writes:
See the following Red Hat bug:
https://bugzilla.redhat.com/show_bug.cgi?id=289381
This bug says:
mt status attempts to use /dev/tape, as a device, when it's a
directory
This could be it, does amanda use this for tape commands?
Are you using
Dustin writes:
Amanda uses what was supplied in the TAPEDEV parameter directly.
Then someone busted more than just the mt status command:
amtape genepi current
returns:
amtape: scanning current slot in tape-changer rack:
slot 2: not an amanda tape (Input/output error)
because
On Tue, Aug 5, 2008 at 11:09 AM, Steven Backus
[EMAIL PROTECTED] wrote:
This could be it, does amanda use this for tape commands?
Amanda uses what was supplied in the TAPEDEV parameter directly.
Dustin
--
Storage Software Engineer
http://www.zmanda.com
I have an Ultrium LTO-4, and cannot get it to work with Amanda.
[EMAIL PROTECTED] ~]$ amlabel WeeklySet1 Weekly-01
Reading label...
Can't open tape device /dev/nst0: Bad file descriptor
amlabel: Could not open device tape:/dev/nst0.
Here is pertinent section of my /etc/amanda/WeeklySet1
Vectorz Sigma schrieb:
[EMAIL PROTECTED] ~]$ amlabel WeeklySet1 Weekly-01
Reading label...
Can't open tape device /dev/nst0: Bad file descriptor
amlabel: Could not open device tape:/dev/nst0.
Allready tried if the drive is accessable by mt directly?
# mt -f /dev/nst0 status
--
Marc
Steven Backus wrote:
Ever since my latest update from Red Hat, my VXA-2 tape library
has stopped working. It appears /dev/tape is now a directory
instead of a link to /dev/nst0 and every command I give to the
drive returns /dev/nst0: Input/output error. I've tried removing
/dev/tape
I have a tape library that had 36 slots. I was using slots 1-28 for my daily
run.
When tapecycle was equal to 28 tapes, I got the following:
zorn-[44] amadmin daily tape
The next Amanda run should go onto tape D6 or a new tape.
tape D7
]
---
Erdös 4
Original Message
Subject:Re: amadmin daily tape question
Date: Mon, 04 Aug 2008 14:39:34 -0400
From: Chris Hoogendyk [EMAIL PROTECTED]
To: McGraw, Robert P [EMAIL PROTECTED]
References: [EMAIL PROTECTED]
McGraw, Robert P wrote
Ever since my latest update from Red Hat, my VXA-2 tape library
has stopped working. It appears /dev/tape is now a directory
instead of a link to /dev/nst0 and every command I give to the
drive returns /dev/nst0: Input/output error. I've tried removing
/dev/tape and linking it to /dev/nst0
Mtrento,
There are a few different issues here:
1. Setting tape_splitsize affects the way dumps are broken up when writing to
tape, but does not affect they way they are stored on the holding disk. So
dumps will still be done directly if they are larger than the holding disk,
even if you have
The old tapeio layer supported UWARE, XENIX, and AIX tape interfaces
in addition to modern POSIX tape. The Device API also supports these
tape devices, but we don't have any capacity to test the
implementation at this point. Based on some googling, recent versions
of AIX and HP/UX have POSIX
On Friday 13 June 2008 15:13:13 Chris Hoogendyk wrote:
I will still need to know whether
there is a clean and recommended way to tell Amanda to terminate
operations immediately (accepting that ufsdumps will probably just hang).
In recent (~last year?) versions of amanda, amcleanup will also
running when the power dropped. I have no way of
knowing if the tape was writing when the power dropped or was just
sitting in the drive. Anyway, amcleanup did it's job. The serious
problem is with the library. It was improperly powered off, and it now
doesn't seem to sense the tape
for the battery backups to carry everything.
Amanda backups were running when the power dropped. I have no way of
knowing if the tape was writing when the power dropped or was just
sitting in the drive. Anyway, amcleanup did it's job. The serious
problem is with the library
year),
I adjusted my config a bit and set reserve to 15%. In the frenzy of
running around helping people get their equipment up after our power
outage, and dealing with my confused tape library, I forgot that I had
made that adjustment.
Lewis Donofrio wrote:
Sounds like a job for the admin
On Mon, Jun 09, 2008 at 10:39:16PM -0400, Robert Kuropkat wrote:
Did something bad, but not sure what. I had a tape with a bar code
label but apparently no Amanda label. So I labeled it and hoped the
next backup would write to it. It did not. It was tape #28 and I had
already passed
Jean-Louis took a look at my config, and it turns out I had a foolish error. I
had used the following lines from the default config:
# flush-threshold-dumped, flush-threshold-scheduled, taperflush, and autoflush
# are used to control tape utilization. See the amanda.conf #40;5#41; manpage
Jon LaBadie wrote:
On Mon, Jun 09, 2008 at 10:39:16PM -0400, Robert Kuropkat wrote:
Did something bad, but not sure what. I had a tape with a bar code
label but apparently no Amanda label. So I labeled it and hoped the
next backup would write to it. It did not. It was tape #28 and I
;
nbsp; 172.16.1.126 /test pri 14041 lev 0 nsize 2065870 csize 1032935
DELAYING DUMPS IF NEEDED, total_size 1033031, tape length 209715200 mark 0
nbsp; delay#58; Total size now 1033031.
PROMOTING DUMPS IF NEEDED, total_lev0 1032935, balanced_size 258233...
planner#58; time 1.061#58; analysis took 0.000
, total_size 1033031, tape length 209715200 mark 0
nbsp; delay#58; Total size now 1033031.
PROMOTING DUMPS IF NEEDED, total_lev0 1032935, balanced_size 258233...
planner#58; time 1.061#58; analysis took 0.000 secs
GENERATING SCHEDULE#58;
DUMP 172.16.1.126 9ffe00 /test
Did something bad, but not sure what. I had a tape with a bar code
label but apparently no Amanda label. So I labeled it and hoped the
next backup would write to it. It did not. It was tape #28 and I had
already passed that number in the sequence (Tape #30). So I figured I
did something
A couple of people have asked me if I have solved this, and I have not.
The error seems to be a problem with the taper not being able to write to my
tape drive. It sends a REQUEST_NEW_TAPE to the driver, who replies NO_NEW_TAPE.
I am unable to figure out what the problem is. What problem
On Fri, Jun 6, 2008 at 8:36 PM, nbarss [EMAIL PROTECTED] wrote:
taper: Total dump size should be 130801kb, part size is 21474836480kb
..
It could just be an extra 'kb' tacked on the end, or a serious calculation
error.
It is just a typo, but should definitely be fixed. Amanda has a bad
habit
On Wed, May 7, 2008 at 2:21 PM, Nathan Barss [EMAIL PROTECTED] wrote:
Please forgive my n00bness. This is probably a simple configuration error on
my part, but I am having a problem getting Amanda to flush to tape.
Everything else seems to work fine. The report when I run amflush looks
Hi,
with regards to Amanda version 2.5.x, does Amanda kind of automatically
do tape spanning, or does this need to be configured somewhere?
I'm testing a newer version, and was just wondering...haven't really
touched Amanda for more than a year because it never breaks...
:)
Hi Johan,
Tape spanning has been in Amanda since 2.5.0 release.
You can find details how to configure tape spanning here:
http://wiki.zmanda.com/index.php/Splitting_dumps_across_tapes
Regards
Dmitri Joukovski
From: [EMAIL PROTECTED] [mailto:[EMAIL
On Fri, May 9, 2008 at 5:35 AM, Johan Booysen [EMAIL PROTECTED] wrote:
with regards to Amanda version 2.5.x, does Amanda kind of automatically do
tape spanning, or does this need to be configured somewhere?
By default, no, it won't do spanning. See
http://wiki.zmanda.com/index.php
Hi all,
Thanks very much for your replies.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Dustin J. Mitchell
Sent: 09 May 2008 15:09
To: Johan Booysen
Cc: amanda-users@amanda.org
Subject: Re: tape spanning
On Fri, May 9, 2008 at 5:35 AM, Johan Booysen
Please forgive my n00bness. This is probably a simple configuration error on
my part, but I am having a problem getting Amanda to flush to tape. Everything
else seems to work fine. The report when I run amflush looks like this (and is
similar to the report from amdump):
Hostname
801 - 900 of 4500 matches
Mail list logo
