also doesn't cater to no-reuse tapes :)
Tested on Red Hat, running on an EL4 server, but should be compatible
with python 1.5.2.
--
Jamie Wilkinson
Senior Systems Administrator
Anchor Systems Hosting, Colocation, and Managed Servers
#!/usr/bin/python
looks at the amanda database, and the currently
Thankyou for both copies of your courteous email!
This one time, at band camp, Joe Rhett wrote:
On Thu, Sep 01, 2005 at 09:46:43AM +1000, Jamie Wilkinson wrote:
There's a patch from John Stange that I don't believe has been committed to
CVS, but it takes care of splitting dumps and spanning
This one time, at band camp, Joe Rhett wrote:
1. Why aren't we backing up chunks to different tapes yet? Amanda is the
only backup software which doesn't handle this.
-and more importantly-
2. Why is it trying to back up 53gb to a 33gb tape definition?
#2 is clearly a bug. #1 is a feature
This one time, at band camp, Scott R. Burns wrote:
Can the version of GNU tar you are using handle single archives of this size
? There were some older versions that used signed long internals that
overflowed on me in the past and caused problems.
It's 1.13.25 from RHEL 3. I havne't seen
This one time, at band camp, Jon LaBadie wrote:
As I noted, I was uncertain of the details, someone understanding more
about the networking aspects can comment more. But just for clarification
of the way I worded that:
- I did not say anything about the backup data stream over udp
- Your logs
This one time, at band camp, Jon LaBadie wrote:
On Thu, Aug 18, 2005 at 10:16:48AM +1000, Jamie Wilkinson wrote:
Another data point though; this backup today started at 1:30am (it's now
10:15am) and is only 35% through -- about 20GiB. This is pretty abnormal
(well, compared back to when
I have a very large DLE, approaching 100GB, on my fileserver. The backup
server is running 2.4.5, and the fileserver is running 2.4.5b1.
The dump on this DLE is returning the following error:
bulkhead.b /data/home lev 0 FAILED [data read: Connection reset by peer]
in the summary, which looks
This one time, at band camp, Jon LaBadie wrote:
Search back over the list archives for details that I don't remember.
Thanks :)
I think some have had this symptom when there was some sort of network
timeout setting that affected the index stream. Not certain, but I
think it was a UDP setting
This one time, at band camp, Jon LaBadie wrote:
On Wed, Jul 13, 2005 at 11:07:25PM +0200, Stefan G. Weichinger wrote:
Let's think something like
/etc/amanda/amanda.conf
/etc/amanda/tapetype.conf
I don't think any 3rd party/optional/... packages should install
into the root filesystem. Not
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:
I got sick of having to cross-check amtape show against amadmin tape and the
list of tapes that we needed to take offsite, so I wrote the attached
program to do all the hard work for me. It's probably not 100% perfect but
I tried to make it not rely on our own specific configuration as much as
This one time, at band camp, Gene Heskett wrote:
If you have plenty of holdingdisk space, I would think they would go
there. Even with the default reserve of 100%, you should still get
the incremental. You might have to look in the debug files to see
why they were completely skipped.
If the
This one time, at band camp, Frank Smith wrote:
After further thought I believe Alex was correct about the
scheduler limiting itself to what will fit, so increasing
runtapes to 2 should let you get incrementals of everthing
on the day the full of your big DLE occurs.
I'm not seeing a post by Alex
This one time, at band camp, Gene Heskett wrote:
In general, we only need one LTO1 a day, this particular DLE is a
freak statistic well outside the standard deviations of the other
DLE sizes, so doing a flush once every cycle is more appealing
than allocating two tapes per run.
Can you, by
This one time, at band camp, Gene Heskett wrote:
On Tuesday 15 February 2005 19:49, Jamie Wilkinson wrote:
This one time, at band camp, Gene Heskett wrote:
If you have plenty of holdingdisk space, I would think they would
go there. Even with the default reserve of 100%, you should still
get
This one time, at band camp, Frank Smith wrote:
--On Wednesday, February 16, 2005 11:51:11 +1100 Jamie Wilkinson [EMAIL
PROTECTED] wrote:
This one time, at band camp, Frank Smith wrote:
After further thought I believe Alex was correct about the
scheduler limiting itself to what will fit, so
We've got one problem machine that has about 90GB in one DLE, and our tapes
are 100GB LTO1s.
Of course, once a cycle, the server decides it can only write maybe 5 DLES
out of 150+ to the tape, because one of them is 80GB+, and so all the other
dumps end up being reported as
FAILED [dumps way
This one time, at band camp, Gaby vanhegan wrote:
Hi,
I just found a load of old dumps in my holding directory that, for
whatever reason, weren't written to tape. I've now flushed all of
these to tape but they're still in the holding folder. Is it safe to
rm -rf them all now?
I've seen one
This one time, at band camp, Frank Smith wrote:
--On Tuesday, February 15, 2005 17:44:32 +1100 Jamie Wilkinson [EMAIL
PROTECTED] wrote:
We've got one problem machine that has about 90GB in one DLE, and our tapes
are 100GB LTO1s.
Of course, once a cycle, the server decides it can only write
This one time, at band camp, Paul Bijnens wrote:
Eric Dantan Rzewnicki wrote:
what are some good options for long term archival storage?
Someone stole my crystal ball...
Or did he mean amanda.conf options ?
This one time, at band camp, Germán C. Basisty wrote:
Hi!
I have Amanda server running on a Linux box. In another machine, I have
Solaris 9 running Amanda client and PostgreSQL. I would like to know if
someone has experience backupping PostgreSQL with Amanda.
I have thought the following
This one time, at band camp, Gene Heskett wrote:
On Wednesday 12 January 2005 20:57, Jamie Wilkinson wrote:
This one time, at band camp, Germán C. Basisty wrote:
Hi!
I have Amanda server running on a Linux box. In another machine, I
have Solaris 9 running Amanda client and PostgreSQL. I would
This one time, at band camp, Skylar Thompson wrote:
On Thu, Jan 13, 2005 at 03:09:42PM +1100, Jamie Wilkinson wrote:
Because the database being dumped is not on the machine that runs amdump,
and adding another RPC that duplicates the one already in amanda is
unjustifiable.
It would be a bit
This one time, at band camp, Zadikem, Travis-taz wrote:
Has anyone successfully setup and has running Amanda on Redhat 9.x with an
HP Autoloader (24x6 or 40x6). If so, can you please send me the configs. I
can't
seem to get mine working properly and we would like to use it for backing up
our
Mad props to all the people responsible for chg-zd-mtx, my new robot worked
perfectly overnight to flush the weekends dumps onto 3 tapes, and this
mornings backup too.
Moving to the robot from a single tape drive was trivially easy, the
documentation was sweet.
Thanks!
We're looking at increasing our backup capacity, and I'm wondering if anyone
has any recommendations for a rackable tape changer, with about a 9 tape
capacity (I'm thinking LTO tapes) and a SCSI interface.
Anything at all would help; I'm especially interested in such devices that
you are using in
This one time, at band camp, Jamie Wilkinson wrote:
We're looking at increasing our backup capacity, and I'm wondering if anyone
has any recommendations for a rackable tape changer, with about a 9 tape
capacity (I'm thinking LTO tapes) and a SCSI interface.
Thanks everyone who replied
The tapelist file says my tape ANCHOR3 is reusable. Grepping through the
output of amadmin export for ANCHOR3 returns nothing. However, amcheck
tells me that it can't overwrite active tape ANCHOR3.
There are 16 tapes in the tapecycle, runtapes is 1, dumpcycle is 5 days,
runspercycle is 5.
This one time, at band camp, Jamie Wilkinson wrote:
The tapelist file says my tape ANCHOR3 is reusable. Grepping through the
output of amadmin export for ANCHOR3 returns nothing. However, amcheck
tells me that it can't overwrite active tape ANCHOR3.
There are 16 tapes in the tapecycle, runtapes
This one time, at band camp, Jamie Wilkinson wrote:
This one time, at band camp, Jamie Wilkinson wrote:
The tapelist file says my tape ANCHOR3 is reusable. Grepping through the
output of amadmin export for ANCHOR3 returns nothing. However, amcheck
tells me that it can't overwrite active tape
This one time, at band camp, Brian Cuttler wrote:
Did you have some flushes during the last period ?
Yeah, many.
I believe its not just the eldest reusable tape, I believe amanda
will not want to re-use it with tapecycle dates of it having been
last written.
Ok, thanks, that may be it.
--
This one time, at band camp, Ernest Byaruhanga wrote:
amdtape command has now gone for 30 hours!! is this normal? can someone
please send me their configuration in case they are using a similar tape?
I've got an HP Ultrium 1, and use this tapetype:
define tapetype HP-Ultrium {
comment HP
This one time, at band camp, Andrew Hall wrote:
http://security.uchicago.edu/tools/gpg-amanda/
One of the nice things about plain tar is that it can cope with stream
errors; if one block on the tape is busted then you can still recover the
rest of the backup.
A while ago (probably 4 months past)
This one time, at band camp, DK Smith wrote:
Are we sure that this answers the question that was asked? i.e. is it
the
correct answer in limited number of cases but not all cases? Is your
test case a coincidence?
Well, I'm not 100% sure. I only noticed a correlation between the output of
This one time, at band camp, Jamie Wilkinson wrote:
So I'm wondering if there's a amadmin command or somesuch that we can use
that'll tell us which tapes are in the set of tapes required to do a full
restore from, i.e. for all DLEs (I think that's the correct term) the tapes
that hold that image
This one time, at band camp, Paul Bijnens wrote:
Is the server doing an mt fsf or is it just reading the tape up to the
matching backup image?
It's not spawning a mt fsf when I do a ps, as far as I can tell.
If I strace the amrestore process I see it doing the following ioctls
between file
This one time, at band camp, Paul Bijnens wrote:
Jamie Wilkinson wrote:
So, short of recompiling to increase READ_TIMEOUT like amrecover
suggests, is there any simple way to get the restore process to work
faster? Is there a neat way of keeping a precomputed index of the tape
somewhere so
This one time, at band camp, Paul Bijnens wrote:
Jamie Wilkinson wrote:
So, short of recompiling to increase READ_TIMEOUT like amrecover
suggests, is there any simple way to get the restore process to work
faster? Is there a neat way of keeping a precomputed index of the tape
somewhere so
I'm restoring some files using amrestore on the client machine, but due
to the size of the tape being restored from (100GB) I usually hit a
timeout on the client side while waiting for amrestore on the server to
find the correct image.
So, short of recompiling to increase READ_TIMEOUT like
This one time, at band camp, Jamie Wilkinson wrote:
I'm restoring some files using amrestore on the client machine, but due
I mean, amrecover on the client machine.
--
[EMAIL PROTECTED] http://spacepants.org/jaq.gpg
This one time, at band camp, Kris Vassallo wrote:
One day last week after AMANDA had been running fine for months it
just broke and I now am seeing this in my email log daily:
What's your etimeout set to, and how big is the filesystem on
host.domain:/backup/repo and /home ?
I've just had the
This one time, at band camp, Paul Bijnens wrote:
Gene Heskett wrote:
On Monday 22 March 2004 05:20, Paul Bijnens wrote:
You can always compile a recent amanda version yourself.
It's actually quiet easy.
Quiet? Methinks you meant 'quite' since the installation of amanda
from the latest tarball
I'd like to see how big a file was, to make sure I'm restoring a version
of the right size (as it got corrupted); I notice that the commands in
amrecover are limited in that ls will only give a date and a filename.
Is it possible to get a file size from an index somewhere, or is this
data not
43 matches
Mail list logo
