tape header
FILEMARK
first data file
FILEMARK
second data file
...
Dustin
--
Open Source Storage Engineer
http://www.zmanda.com
s to the same
> physical drive? Or Am I missing (once more) something obvious?
Nope, it's a typo - the second should say ..nst1 :)
I'll fix it up. Thanks!
Dustin
--
Open Source Storage Engineer
http://www.zmanda.com
installed them on Solaris, so I don't have any
additional detail for you. It's usually more complicated than just
installing the corresponding packages, because there's a system-global
XML "catalog" that needs to be customized.
Dustin
--
Open Source Storage Engineer
http://www.zmanda.com
ith which part (chunks
are different) was on which tape.
What is the task you're tring to accomplish here?
Dustin
--
Open Source Storage Engineer
http://www.zmanda.com
' for the same dumpfile, and
examining the resulting tarfile.
Dustin
--
Open Source Storage Engineer
http://www.zmanda.com
On Fri, Apr 23, 2010 at 12:43 PM, Chris Hoogendyk
wrote:
> I don't get it. Why is Amanda refusing to use the new tapes (or tape 3)?
See the note in this manpage:
http://wiki.zmanda.com/man/amanda-taperscan.7.html
Dustin
--
Open Source Storage Engineer
http://www.zmanda.com
gt; suitable.
It's not just a bit weird, it's very weird. That's why I wrote up the
manpage :)
Hopefully we'll be adding some new, less insane taperscan algorithms in 3.2.
Dustin
--
Open Source Storage Engineer
http://www.zmanda.com
enums in the catalog)
* Redesigned amreport
o much more natural command-line interface (just run 'amreport $config')
o experimental XML output
* configuration override for dumptype works with inheritance.
Dustin
--
Open Source Storage Engineer
http://www.zmanda.com
On Wed, Apr 28, 2010 at 6:57 AM, Mark Adams wrote:
> I assume this will require space the size of the DLE? (in my case 2T)
Yes, it will.
Dustin
--
Open Source Storage Engineer
http://www.zmanda.com
rom anyone who wants to add a project *and* work that project through
to completion!
Dustin
--
Open Source Storage Engineer
http://www.zmanda.com
ape-2, so I'm not sure where vtape-1
is involved. Perhaps in a previous recovery?
It's amidxtaped which is manipulating the tapes, so you'll want to
look in its debug log to see what's really going on.
Dustin
--
Open Source Storage Engineer
http://www.zmanda.com
(Dumper($plan));
if ($err) {
$self->sendmessage("$err");
return $self->quit();
and re-run, pasting the new amidxtaped debug log. Also, please send
the output of
amadmin test find gustav /raid/hrrt/SCS_SCANS
Thanks!
Dustin
--
Open Source Storage Engineer
http://www.zmanda.com
On Tue, Apr 27, 2010 at 1:59 PM, Dustin J. Mitchell wrote:
> Please download and test it out - with luck, this will be the last
> beta before the final release!
We haven't heard of any showstopper bugs, although we have discovered
and fixed a number of nuisances since the beta2 rele
oes the
same thing. If so, try running it under 'truss' to see what is wrong
with the execve call.
Dustin
--
Open Source Storage Engineer
http://www.zmanda.com
remove the debugging prints I
had you add to amidxtaped.pl.
I'm glad we chased this down! Jean-Louis has already committed the
corresponding patch (r2978).
Dustin
--
Open Source Storage Engineer
http://www.zmanda.com
n - in fact, it's
deprecated in 3.1 and will probably get the axe in 3.2.
Dustin
--
Open Source Storage Engineer
http://www.zmanda.com
On Mon, May 3, 2010 at 4:31 PM, McGraw, Robert P wrote:
> If I manually run the following gtar command I get a segmentation fault
>
> /usr/sfw/bin/gtar --create
Uh-oh .. time to open a Sun^WOracle support case? It looks like a bug
either in ZFS or GNU Tar..
Dustin
--
Open Sourc
ot;gtar on a ZFS
snapshot segfaults", it would be fixed already, so the circumstances
are likely more narrow. Have you checked the Solaris bug tracker? Do
your system logs give any indication of what's going on?
Dustin
--
Open Source Storage Engineer
http://www.zmanda.com
On Tue, May 4, 2010 at 12:27 PM, McGraw, Robert P wrote:
> I setup a lookback for the snapshot and now gtar seem to be working.
It sounds like you have a fairly good understanding of this problem
now. Could you write up either a troubleshooting or How-To article on
the wiki?
Dustin
--
O
On Tue, May 4, 2010 at 1:13 PM, Jean-Francois Malouin
wrote:
> Is it possible with amanda-3.0 and the new changer API to setup a
> mirror/rait using 2 physical tape drives and only one physical
> changer?
Yes! I tested this lightly at one point, and it should work just fine.
Dustin
On Tue, May 4, 2010 at 4:44 PM, Jean-Francois Malouin
wrote:
> One question: should the changerfile parameter for chg-robot point to
> the same file for both child-changers:
Yes, it should - that will allow the changers to avoid stepping on each other.
Dustin
--
Open Source Storage En
rieving the entire DLE will offer some clues (and get you
access to your data).
Dustin
--
Open Source Storage Engineer
http://www.zmanda.com
What is the error? I suspect this:
1273071472.718696: dumper: security_seterror(handle=8074f08,
driver=fef09394 (BSD) error=timeout waiting for REP)
which likely means that you're exceeding the dtimeout for that DLE for
whatever reason. Try increasing that?
Dustin
--
Open Source St
t without *any* data, so I suspect that this is some kind of
ugly interaction between ZFS busily doing copy-on-write to implement
its snapshot while trying to feed data to the syscall-hungry gnutar.
Dustin
--
Open Source Storage Engineer
http://www.zmanda.com
7;s the 'slot ?:' thingie?
The "slot ?:" itself is an artifact of the way the output is printed -
it's a general error not corresponding to any particular slot.
> Wed May 5 14:12:02 2010: amtape: warning: Use of uninitialized value in
> bitwise or (|) at
> /
7;ve uncovered a
bug there all the same, since '1' is treated as '{1,1}'.
Dustin
--
Open Source Storage Engineer
http://www.zmanda.com
On Thu, May 6, 2010 at 1:44 PM, Brian Cuttler wrote:
> Amanda is now failing differently.
>
> tar exited with signal 11.
On Solaris, over a ZFS filesystem. We just saw this error a few days
ago on the list! Check the archives - there was a workaround.
--
Open Source Storage Engineer
http://ww
ending JLM's review (so it will probably be
committed tomorrow). Here are the (3) patches:
http://github.com/djmitche/amanda/commits/raitfixes
Dustin
--
Open Source Storage Engineer
http://www.zmanda.com
.1.
> I'm going to try now using plain gzip instead of pigz, just incase this
> is causing my issues.
It's quite possible..
Dustin
--
Open Source Storage Engineer
http://www.zmanda.com
On Fri, May 7, 2010 at 12:03 PM, Jean-Francois Malouin
wrote:
> Dustin, educate me please!
> How do I proceed with the git patches and
> how do I patch the source on my side?
First, if you click on each of those commits in github, you'll have URLs like
http://github.com/djmitche
ut shell expansion is rewriting that to
# su amanda -c "/opt/amanda-3.1.0beta2/sbin/amtape rait eject 0 1"
and Amanda is trying to eject drive 0, equivalent to {0,0}, so the
second half of your RAIT is complaining. Use single-quotes around the
{..} and you should be fine.
Dust
On Fri, May 7, 2010 at 5:35 PM, Stefan G. Weichinger wrote:
> It's a DRAFT!
Looks good so far, though! Will you be adding this to contrib/ when it's ready?
Dustin
--
Open Source Storage Engineer
http://www.zmanda.com
tapes are HP DAT 160 Data Cartridge C8011A)
I can make my amanda.conf, etc. files available if necessary; this message
seems long enough already without them.
Dustin C. Hatch
Director of Information Systems
Supertechs
13153 State Line Rd.
Kansas City, MO 64145
(816) 559-3620
http://www.gosupertech
On Tue, May 11, 2010 at 4:08 AM, Dustin C. Hatch
wrote:
> [2373787.012572] BUG: Bad page map in process taper pte:48081b
> pmd:261970067
Well, clearly there's a kernel bug here. But that's coming *after*
the taper says it's out of tapes.
Please check the taper deb
> -Original Message-
> From: djmit...@gmail.com [mailto:djmit...@gmail.com] On Behalf Of
> Dustin J. Mitchell
> Sent: Tuesday, May 11, 2010 10:31 AM
> To: Dustin C. Hatch
> Cc: amanda-users@amanda.org
> Subject: Re: taper segfault (BUG: Bad page map in process tape
On Tue, May 11, 2010 at 4:55 PM, Dustin C. Hatch
wrote:
> I update to Kernel version 2.6.32-r7 last night. I was able to do a full
> backup to tape earlier today, using tapes that I know failed before. I
> guess there could have been a driver problem in 2.6.31. I'll try a larger
&
used pbzip2?
Interesting! We're hoping to implement "official" support for this in
the next (3.2) release, so I'm curious to know more about why pigz
failed. In theory, it's a drop-in gzip replacement, right?
Dustin
--
Open Source Storage Engineer
http://www.zmanda.com
On Wed, May 12, 2010 at 11:17 AM, Mark Adams wrote:
> In the mean time I can't get pbzip2 to work at all. It just crashes out
> with the following:
Please attach the whole sendbackup log.
Dustin
--
Open Source Storage Engineer
http://www.zmanda.com
side compression. Since the error is EPIPE, this means either
that pbzip2 exited, or that it closed its standard input prematurely.
The next step would be to figure out why pbzip2 would do that. Does
it automatically compress its stdin and pipe it to stdout?
Dustin
--
Open Source Stora
On Tue, May 18, 2010 at 5:26 AM, Mark Adams wrote:
> You need to specify -c with pbzip2 to have it compress to stdout I
> believe. If you just run it by itself;
Ah! Then, for the moment at least, you'll need to write a wrapper
script that doesn't require any arguments.
Dustin
RROR);
1286 d_self->file = (guint)got_file;
1287 return NULL;
1288 }
So this might be an odd behavior of the tape device.
Dustin
--
Open Source Storage Engineer
http://www.zmanda.com
On Tue, May 18, 2010 at 9:37 AM, Dustin J. Mitchell wrote:
> Hmm.. can you send me the syscall trace (truss or strace) of that?
(truss now in hand..)
Oh, silly me - the code detects that the tape drive needs the
FSF_AFTER_FILEMARK property, by virtue of getting an error from the
device ..
On Wed, May 19, 2010 at 7:27 AM, Gunnarsson, Gunnar
wrote:
> Thanks Dustin the patch is working fine, good work.
Great!
> Compression enabled, does it mean that it is using compression ?
Yep.
Dustin
--
Open Source Storage Engineer
http://www.zmanda.com
less than 1MB.
Did this take a long time, or happen immediately? Can you add some
print's around line 186 of amtapetype to print the blocksize and
number of blocks?
Dustin
--
Open Source Storage Engineer
http://www.zmanda.com
evice->block();
-my $block_size = $device->property_get("block_size");
$stats->{$pattern}->{BYTES} += $blocks_written * $block_size;
$stats->{$pattern}->{FILES} += 1;
$stats->{$pattern}->{TIME} += $duration;
Let me know if that helps? Thanks for your patience!
Dustin
--
Open Source Storage Engineer
http://www.zmanda.com
on tape device: Tried 32768, got 0 at
> /opt/sfw/sbin/amtapetype line 89.
Ah, it's a similar problem as in the previous case, then: the device
goes into an error state, and that state "sticks".
Probably the better solution is to re-create the device as necessary.
Dusti
entire client-side or server-side all
at once, rather than piecemeal. There were some protocol changes
between 2.5.0 and 2.5.1, so you may run into some problems there. See
amanda-compatibility(7) for details.
Dustin
--
Open Source Storage Engineer
http://www.zmanda.com
pe drives.
The fix is here:
http://github.com/djmitche/amanda/commit/amtapetype
and will (I hope) be in the much-delayed 3.1 release.
Dustin
--
Open Source Storage Engineer
http://www.zmanda.com
es, but on Sun it might be via NIS or
something.
Dustin
--
Open Source Storage Engineer
http://www.zmanda.com
On Tue, May 25, 2010 at 12:44 PM, Chris Hoogendyk
wrote:
> I don't mean to question Dustin
I rather enjoy being questioned, so don't worry about that!
This was a guess, and apparently I was correct this time around.
Dustin
--
Open Source Storage Engineer
http://www.zmanda.com
tape drive to
> practice.
It's generally best to upgrade the server first, then migrate clients
one by one.
Dustin
--
Open Source Storage Engineer
http://www.zmanda.com
On Fri, May 28, 2010 at 4:19 AM, Gunnarsson, Gunnar
wrote:
> I got the fatal error see below while testing the new option autolabel, the
> configuration was empty and amcheck -s was ok.
Does the tapelist file exist?
Dustin
--
Open Source Storage Engineer
http://www.zmanda.com
On Fri, May 28, 2010 at 9:12 AM, Dustin J. Mitchell wrote:
> Does the tapelist file exist?
Ah! A while back, we made a missing tapelist a warning in amcheck,
but the taper was not updated to automatically create it in this case.
So you'll need to create your tapelist first - then thi
CHOICE property. But I don't see how to use multiple changers
> with a single Amanda config.
This is currently not supported, but a round-robin changer would be an
interesting addition to the suite of changers we already have. It
would be similar to the current chg-rait, but of course
.
They're usually not particularly helpful, but can be used locally with
a debugger to explore the state of the process just before it died.
Dustin
--
Open Source Storage Engineer
http://www.zmanda.com
ah, Amanda has some (presumably ages-old) functionality to do that
in common-src/file.c. I've always just ignored that code, but I doubt
it's doing anyone any good and I'd be happy to remove it if you think
it's problematic.
Dustin
--
Open Source Storage Engineer
http://www.zmanda.com
On Thu, Jun 3, 2010 at 3:25 PM, McGraw, Robert P wrote:
> Which seem to resolve the problem.
I'm not sure what the question was .. but amgtar in 2.6.1 didn't have
an ACLS property:
http://wiki.zmanda.com/man/2.6.1/amgtar.8.html
Dustin
--
Open Source Storage Engineer
http://www.zmanda.com
EP)
That's 60 seconds.. as I've said *many* times, the BSD auth is from
the stone age. Use something at least slightly newer, like BSDTCP!
Dustin
P.S. Despite a lot of voiced interest, nobody is working on the ssl
auth at the moment. Anyone want to pick that project up?
--
Open Source Storage Engineer
http://www.zmanda.com
oke if there
were an error :)
Dustin
--
Open Source Storage Engineer
http://www.zmanda.com
I *think* this is the same issue being addressed here:
http://forums.zmanda.com/showthread.php?t=2800
Dustin
--
Open Source Storage Engineer
http://www.zmanda.com
meout of 0.
git-svn-id:
https://amanda.svn.sourceforge.net/svnroot/amanda/amanda/tr...@2358
a8d146d6-cc15-0410-8900-af154a0219e0
I don't remember the motivation for the change, though - maybe JLM
does. But the upshot is that it looks like the manpage was not
properly updated.
Dustin
--
Open Source Storage Engineer
http://www.zmanda.com
'dump'}; ($d, $d) } @parts;
use Data::Dumper;
Amanda::Debug::debug("".Dumper([ %dumps ]);
420 my @dumps = values %dumps;
and try again?
Dustin
--
Open Source Storage Engineer
http://www.zmanda.com
u mean "how to clean up old and unnecessary data in holding
disk", right?
You can use amadmin holding delete, as you suggested.
Dustin
--
Open Source Storage Engineer
http://www.zmanda.com
On Wed, Jun 9, 2010 at 9:50 AM, Marc Muehlfeld
wrote:
> Am 09.06.2010 16:43, schrieb Dustin J. Mitchell:
>>
>> The messages will have gone into amidxtaped.*.debug..
>
> But just the following files were created, until the
>>> amrecover - can't talk to tape se
a nonzero scalar so
that's "true".
Attached is a patch - can you try it out? If you need a fresh copy of
Planner.pm, you can get it here:
http://github.com/zmanda/amanda/raw/tags/3_1_0/perl/Amanda/Recovery/Planner.pm
Dustin
--
Open Source Storage Engineer
http://www.zmanda.com
necessary, and complicates packaging. So I'm
trying to strip down the permissions to the bare essentials.
Obviously I got it wrong.
Dustin
--
Open Source Storage Engineer
http://www.zmanda.com
duce
dumps with the "DUMPFILE" header - every header is a "SPLIT_FILE"
header, even if it only has one part. However, Amanda-2.6.* wrote
DUMPFILEs, and when those are read back in it looks like they have
partnum 0, which is not what amidxtaped is expecting.
Let me know if this patch
On Fri, Jun 11, 2010 at 1:41 PM, Dustin J. Mitchell wrote:
> Ah, this is completely different error, but you've given me enough
> info to replicate and fix it. I've attached a source-level patch that
> you can apply, but the better fix is at the C level (and will be in
&
uid bits needed.
I don't know about that - Amanda's been successfully packaged in RPMs
for a while now. If you'd like to start up another thread on that
topic, that'd be fine. Or put the distro maintainers in touch with
Dan Locks.
Dustin
--
Open Source Storage Engineer
http://www.zmanda.com
d it yet.
The patch is in review - there's some lingering discussion of the
proper permissions for amrecover and oldamrecover.
Dustin
--
Open Source Storage Engineer
http://www.zmanda.com
On Sat, Jun 12, 2010 at 1:48 PM, Gene Heskett wrote:
> Is it intentional now that amcheck, amplanner and a couple others are now
> owned by root:root?
No, they should be owned by root:disk (or root:backup, depending on
your system), and setuid.
Dustin
--
Open Source Storage Enginee
On Mon, Jun 14, 2010 at 1:02 AM, Marc Muehlfeld
wrote:
> This second patch fixes the problem. Thanks.
Great - thanks!
Dustin
--
Open Source Storage Engineer
http://www.zmanda.com
On Mon, Jun 14, 2010 at 10:54 AM, McGraw, Robert P wrote:
> If I compile with --with-bsdtcp-security and bsd, can my 2.6.1p2 server use
> bsd security for some clients and bsdtcp for other clients and would I set
> this in the "define dumptype"?
Absolutely.
Dustin
--
On Mon, Jun 7, 2010 at 6:39 AM, Wojciech Giel
wrote:
> Could you provide package for ubuntu server 10.4 LTS amd64 and x86?
You should be able to run packaging/deb/buildpkg on such a system, to
create the packages yourself.
At the moment, we don't have a 10.4 build system set up.
On Mon, Jun 14, 2010 at 3:09 PM, McGraw, Robert P wrote:
> I am not quite sure how amanda uses the --with-tcpportrange=low/high. Does
> this parameter have to be defined in both the client and server software or
> does the server pass the ranges to the client?
It needs to be defined separately
s like an un-fun change of plans for your day, but I'm glad
you made lemonade out of those lemons.
This would be a great story to add to the wiki - maybe we should have
a "Success Stories" section?
Dustin
--
Open Source Storage Engineer
http://www.zmanda.com
t; I need to audit my tape sets to ensure data has been backed up
> correctly, I was anticipating trying to retrieve a single file from each
> tape to confirm this. Does anyone have any suggestions on how best to do
> this or is there any automated way to do this with Amanda?
amcheckdump i
On Tue, Jun 15, 2010 at 10:55 AM, Mark Adams wrote:
> Hi Dustin, Thanks for this pointer. I assume amcheckdump takes just as
> long as the backup takes in the first place?
Within an order of magnitude, yes.
Dustin
--
Open Source Storage Engineer
http://www.zmanda.com
who
wants to take a swing at that, I'll see what I can cook up.
> There seems to be a few typos in the pod for Config.pm btw.
Patches and/or specific pointers would be welcome!
http://wiki.zmanda.com/index.php/Fork_Amanda_on_Github
Dustin
--
Open Source Storage Engineer
http://www.zmanda.com
described in the DATA FORMATS
section, as you've probably already discovered.
Dustin
--
Open Source Storage Engineer
http://www.zmanda.com
typical dump, so that they can use extra tapes on particularly heavy
days.
Dustin
--
Open Source Storage Engineer
http://www.zmanda.com
t as zombies
> until the main amandad process terminates.
2.6.1 isn't really new anymore. Does this still occur in 3.1.0?
Dustin
--
Open Source Storage Engineer
http://www.zmanda.com
s what Amanda is showing. Perhaps you can point more
directly to what seems to be in error?
Dustin
--
Open Source Storage Engineer
http://www.zmanda.com
ge tapes.
That said, the difference between these two numbers suggests something
is being added twice. Can you send the trace log from which this was
generated so that I can take a closer look?
Dustin
--
Open Source Storage Engineer
http://www.zmanda.com
un the
old and new amreports on a bunch of identical real-world logfiles and
check that the results are the same).
So the question is: should the report be updated to make this clearer?
And if so, how? This might be a good place for someone to do a bit
of hacking on the new Amanda::Report::huma
buffer, and thus fall back to the default in-memory
splitsize of 10M, which is fantastically small.
We're working on a fix for this in 3.2 - and probably also moving the
splitting configuration to the tapetype.
Dustin
--
Open Source Storage Engineer
http://www.zmanda.com
zmanda.com/community-builds.php
and give it a run?
Thanks!
Dustin
P.S. For those looking for other ways to help, all of the Amanda
projects I mentioned a while ago are still open.
There's always docs to write, too -- for example,
http://wiki.zmanda.com/index.php/How_To:Backup_to_Amazon_S3 needs
'exclude append'
> directives. It seems there must be a better way.
Surely you could get 90% of the space-saving effects with only 10 extensions..
Dustin
--
Open Source Storage Engineer
http://www.zmanda.com
hanged.. or did I
miss your point?
Dustin
--
Open Source Storage Engineer
http://www.zmanda.com
to get it written :)
Dustin
--
Open Source Storage Engineer
http://www.zmanda.com
On Wed, Jun 30, 2010 at 12:39 PM, Mark Adams wrote:
> How do I enable it?
Assuming you have a new enough version, add
property "NO-QUOTING" "yes"
to your dumptype.
Dustin
--
Open Source Storage Engineer
http://www.zmanda.com
On Wed, Jun 30, 2010 at 12:52 PM, Dustin J. Mitchell wrote:
> property "NO-QUOTING" "yes"
Sorry, that's
property "NO-UNQUOTE" "yes"
Dustin
--
Open Source Storage Engineer
http://www.zmanda.com
On Wed, Jun 30, 2010 at 10:51 AM, Mark Adams wrote:
> Is this possibly my problem Dustin?
>
> NO-UNQUOTE
> If "NO" (the default), gnutar doesn't get the --no-unquote option
> and the diskname can't have some characters, eg. '\'. If "YES"
e all at once!
Dustin
--
Open Source Storage Engineer
http://www.zmanda.com
gnu-tar parameter, and gnutar has
both --unquote and --no-unquote, but --unquote is the default.
Dustin
--
Open Source Storage Engineer
http://www.zmanda.com
few days. Send
another email if you don't hear anything about it soon?
Dustin
--
Open Source Storage Engineer
http://www.zmanda.com
It's something we'd like to address, but will probably not
get to soon -- it's best solved with a completely new approach to
indexing dumps.
Dustin
--
Open Source Storage Engineer
http://www.zmanda.com
Here's some more info:
The reason why ZWC is not excluding the files is because of the way
exclude pattern is specified. Following are my test results:
ZWC 3.1.1 rev 22762
ZMC 3.1.1 rev 22752
1. Correct exclude pattern (Added using ZMC):
**
nfigured the Windows system properly.
Dustin
--
Open Source Storage Engineer
http://www.zmanda.com
fter some protocol negotiation, the
client opens up 3 additional high ports per dump, and the server
connects to those.
Dustin
--
Open Source Storage Engineer
http://www.zmanda.com
901 - 1000 of 1163 matches
Mail list logo
