On Saturday 19 December 2020 15:26:07 Nathan Stratton Treadway wrote:
> On Sat, Dec 19, 2020 at 14:43:56 -0500, Gene Heskett wrote:
> > On Saturday 19 December 2020 12:12:07 Nathan Stratton Treadway wrote:
> > > On Sat, Dec 19, 2020 at 10:43:42 -0500, Gene Heskett wrote:
> > > > new error file,
On Saturday 19 December 2020 15:26:07 Nathan Stratton Treadway wrote:
> On Sat, Dec 19, 2020 at 14:43:56 -0500, Gene Heskett wrote:
> > On Saturday 19 December 2020 12:12:07 Nathan Stratton Treadway wrote:
> > > On Sat, Dec 19, 2020 at 10:43:42 -0500, Gene Heskett wrote:
> > > > new error file,
On Sat, Dec 19, 2020 at 14:43:56 -0500, Gene Heskett wrote:
> On Saturday 19 December 2020 12:12:07 Nathan Stratton Treadway wrote:
>
> > On Sat, Dec 19, 2020 at 10:43:42 -0500, Gene Heskett wrote:
> > > new error file, from /home on GO704:(word wrap off)
> > >
> > > dd
On Saturday 19 December 2020 12:12:07 Nathan Stratton Treadway wrote:
> On Sat, Dec 19, 2020 at 10:43:42 -0500, Gene Heskett wrote:
> > new error file, from /home on GO704:(word wrap off)
> >
> > dd if=/sdb/dumps/20201219085654/GO704._home.0 bs=32k count=1
>
> Okay, that output looks good good.
>
On Sat, Dec 19, 2020 at 10:43:42 -0500, Gene Heskett wrote:
> new error file, from /home on GO704:(word wrap off)
>
> dd if=/sdb/dumps/20201219085654/GO704._home.0 bs=32k count=1
Okay, that output looks good good.
for completeness, can you post the section from this Amanda Report
covering this
On Saturday 19 December 2020 09:42:55 Nathan Stratton Treadway wrote:
> On Sat, Dec 19, 2020 at 03:32:07 -0500, Gene Heskett wrote:
> > But the problem is not fixed:
>
> Well, at least this time it's a one-part dump file, so that may make
> investigation at little easier
>
> > FAILURE DUMP
On Saturday 19 December 2020 09:42:55 Nathan Stratton Treadway wrote:
> On Sat, Dec 19, 2020 at 03:32:07 -0500, Gene Heskett wrote:
> > But the problem is not fixed:
>
> Well, at least this time it's a one-part dump file, so that may make
> investigation at little easier
>
> > FAILURE DUMP
On Sat, Dec 19, 2020 at 03:32:07 -0500, Gene Heskett wrote:
> But the problem is not fixed:
Well, at least this time it's a one-part dump file, so that may make
investigation at little easier
>
> FAILURE DUMP SUMMARY:
> rpi4 /usr/lib lev 0 partial taper: source server crc
On Mon, Nov 30, 2020 at 18:41:40 -0500, Gene Heskett wrote:
> > On Mon, Nov 30, 2020 at 12:46:46 -0500, Nathan Stratton Treadway wrote:
> > > I assume that the first few lines of the
> > > coyote._home_gene_Pictures.0 file is an Amana header (including an
> > > XML chunk); can you post that here?
On Mon, Nov 30, 2020 at 12:46:46 -0500, Nathan Stratton Treadway wrote:
> I assume that the first few lines of the coyote._home_gene_Pictures.0
> file is an Amana header (including an XML chunk); can you post that
> here?
Hmmm, it might also be useful to see the header from the
On Mon, Nov 30, 2020 at 03:12:41 -0500, Gene Heskett wrote:
> Doing a level 0 on /home/gene/Pictures, it logged this in the email:
>
> coyote /home/gene/Pictures lev 0 partial taper: source server crc
> (44cff778:11146117120) and input server crc (dfd0e83a:11146117120)
> differ)
> coyote
My wrapper script failed to write its stuff to this mornings backup.
Doing a level 0 on /home/gene/Pictures, it logged this in the email:
coyote /home/gene/Pictures lev 0 partial taper: source server crc
(44cff778:11146117120) and input server crc (dfd0e83a:11146117120)
differ)
coyote
Greetings all;
Whats the exact syntax for specing the style of estimates done?
>From the man page for amanda.conf, the estimate done seems to be part of
a dumptype most logicly specified as
estimate client # but could be
estimate calcsize # or
estimate server # and I just found it was
From: owner-amanda-us...@amanda.org <owner-amanda-us...@amanda.org> on behalf
of Charles Stroom <char...@stremen.xs4all.nl>
Sent: February 13, 2018 4:28:02 PM
To: amanda-users@amanda.org
Subject: Re: again level 1 backup problems.
To sum up the problems I have had:
To sum up the problems I have had:
I have now a properly working amanda working with my pictures
directory divided over 5 disks defined in the disklist, that all resides
on a Windows formatted separate disk.
I have done a number of tests with all kind of variations on my vfat
disk, but I
18:43:30 +0100
From: Charles Stroom <char...@stremen.xs4all.nl>
To: Jean-Louis Martineau <jmartin...@carbonite.com>
Subject: Re: again level 1 backup problems.
Hi Jean-Louis,
before your email arrived, I was testing something different.
I copied the whole ~/pictures tree back
fat, and I will add that feature to amgtar.
Jean-Louis
From: owner-amanda-us...@amanda.org <owner-amanda-us...@amanda.org> on behalf
of Charles Stroom <char...@stremen.xs4all.nl>
Sent: February 6, 2018 5:58:23 PM
To: amanda-users@amanda.org
Subject: a
I have had level 1 problems about 4 years ago. In that case, the level
1 behaved as a level 0, so level 1 in fact did a real full backup.
I have similar problems now again, similar, but not the same.
I have amanda 3.5.5 running which on a daily base makes cycled backup
on DDS-4 tapes of my Linux
Hello,
i have DLEs which are bigger than a single tape now. And i thought the solution
would be to change the following in my amanda.conf
runtapes 2
holdingdisk hd1 {
comment first holding disk
directory /mnt/amanda-holding # where the holding disk is
chunksize 50Gb # size
On 06/07/2012 05:47 AM, Karsten Fuhrmann wrote:
Hello,
i have DLEs which are bigger than a single tape now. And i thought the solution
would be to change the following in my amanda.conf
runtapes 2
holdingdisk hd1 {
comment first holding disk
directory /mnt/amanda-holding # where
Thanks,
but how do i tell amanda that i changed the tape when the backup is run through
a cronjob each night?
On 07.06.2012, at 14:11, Jean-Louis Martineau wrote:
On 06/07/2012 05:47 AM, Karsten Fuhrmann wrote:
Hello,
i have DLEs which are bigger than a single tape now. And i thought the
On 06/07/2012 08:53 AM, Karsten Fuhrmann wrote:
Thanks,
but how do i tell amanda that i changed the tape when the backup is run through
a cronjob each night?
configuring chg-manual is the old way to do it, it is better to
configure and interactivity module:
# amanda.conf
# define an
It turns out I have been running on 4.0.0alpha-4692 for a while, all the
newer ones have a broken build:
libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../config -I../gnulib
-fno-strict-aliasing -D_GNU_SOURCE -
pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -Wall -Wextra
Greetings from the canary;
I just built and installed the 4-alpha-4359 tarball, and I noted that the
configure, or the build, paused for about 30 seconds, long enough to get my
attention make move the solitaire I was playing to see what the hangup
was, and it took off again just as I cleared
On 04/19/2011 11:46 AM, Jean-Louis Martineau wrote:
The fix is already committed.
If you have a similar problem, then make a new bug report with all
relevant information including the amgtar debug file.
Jean-Louis
Pardon me for not readily knowing, where would be the proper place to
file a
Please reference:
http://old.nabble.com/Re%3A-amgtar-getting-Permission-denied-td28223185.html
With Amanda 3.2.2 I am getting the symptom described in the web page
above. I also notice that estimate, backup and restore code paths all
are missing the appropriate seteuid(0)/setuid(0) code.
Would
The fix is already committed.
If you have a similar problem, then make a new bug report with all
relevant information including the amgtar debug file.
Jean-Louis
Trever L. Adams wrote:
Please reference:
http://old.nabble.com/Re%3A-amgtar-getting-Permission-denied-td28223185.html
With
On Thursday, September 30, 2010 12:04:37 pm ad...@geronimoalloys.com did
opine:
Will you please take my email off the distibution list.
ad...@geronimoalloys.com
bran...@geronimoalloys.com
*...@geronimoalloys.com
*...@tejasalloys.com
Thanks
I do not readily know how to do that,
, no amflush. Just amtape (which worked for your main
config) and amcheck (which didn't), checking the data link in between.
Find the underlying pattern, so we can map that pattern to a
solution.
Dustin
There appears to be tracking, I did 'amtape test slot next' all the way
around to slot-1 again
On Wednesday, September 29, 2010 08:23:54 am Dustin J. Mitchell did opine:
On Tue, Sep 28, 2010 at 10:19 PM, Gene Heskett gene.hesk...@gmail.com
wrote:
Like run a catchup loop of at least 2 runs? Or just plain amdump
test by hand and see what falls out for two runs?
No, no amdump, no
On Wed, Sep 29, 2010 at 7:39 AM, Gene Heskett gene.hesk...@gmail.com wrote:
For SG, I removed the data link from the test setup. Running amcheck test
does restore it.
Removing it from the running setup and running amcheck Daily does not. But
it doesn't seem to effect amdump or amcheck in
On Wednesday, September 29, 2010 11:24:04 am Dustin J. Mitchell did opine:
On Wed, Sep 29, 2010 at 7:39 AM, Gene Heskett gene.hesk...@gmail.com
wrote:
For SG, I removed the data link from the test setup. Running amcheck
test does restore it.
Removing it from the running setup and
On Wed, Sep 29, 2010 at 11:33 AM, Gene Heskett gene.hesk...@gmail.com wrote:
Note the --with-config=Daily \, but the subdir when running am* Daily is
/amandatapes/Dailys, note the plural. Is this line even required?
No, --with-config is largely ignored, and the name of the vtape
directory
On Wednesday, September 29, 2010 01:35:19 pm Dustin J. Mitchell did opine:
On Wed, Sep 29, 2010 at 11:33 AM, Gene Heskett gene.hesk...@gmail.com
wrote:
Note the --with-config=Daily \, but the subdir when running am* Daily
is /amandatapes/Dailys, note the plural. Is this line even
amcheck dead in water:
[ama...@coyote amanda-3.2.0alpha.svn.3460]$ amcheck Daily
Amanda Tape Server Host Check
-
Holding disk /usr/dumps: 620929024 kB disk space available, using 620417024
kB
amcheck-device: syntax error at
On Wed, Sep 29, 2010 at 13:40:27 -0400, Gene Heskett wrote:
On Wednesday, September 29, 2010 01:35:19 pm Dustin J. Mitchell did opine:
Can you add some debug prints to Amanda/Changer/disk.pm?
494 # TODO: locking
Amanda::Debug::debug(set_current: symlinking $curlink to slot$slot)
On Wed, Sep 29, 2010 at 12:53 PM, Chris Nighswonger
cnighswon...@foundations.edu wrote:
Line 473 should have a double colon rather than a single... ie.
Amanda::Debug::debug rather than Amanda::Debug::debug
Sorry about that, Gene. You can just edit the file under /usr, rather
than re-making
On Wednesday, September 29, 2010 02:32:52 pm Chris Nighswonger did opine:
amcheck dead in water:
[ama...@coyote amanda-3.2.0alpha.svn.3460]$ amcheck Daily
Amanda Tape Server Host Check
-
Holding disk /usr/dumps: 620929024 kB disk space available, using
On Wednesday, September 29, 2010 02:51:47 pm Dustin J. Mitchell did opine:
On Wed, Sep 29, 2010 at 12:53 PM, Chris Nighswonger
cnighswon...@foundations.edu wrote:
Line 473 should have a double colon rather than a single... ie.
Amanda::Debug::debug rather than Amanda::Debug::debug
Sorry
On Wed, Sep 29, 2010 at 1:51 PM, Gene Heskett gene.hesk...@gmail.com wrote:
Wed Sep 29 14:41:23 2010: amcheck-device: set_current: symlinking
/amandatapes/test/data to slot1
And is this link in place on the filesystem now? What's the
difference between the 14:31 and 14:41 runs of amcheck?
On Sun, Sep 26, 2010 at 6:03 PM, Dustin J. Mitchell dus...@zmanda.com wrote:
That said, the new chg-disk *is* supposed to duplicate the data
symlink quirk, so I'll take a look at why it's not doing that.
And I just verified that this works for me -- it's also tested for by
the installchecks.
On Tuesday, September 28, 2010 07:14:47 pm Dustin J. Mitchell did opine:
On Sun, Sep 26, 2010 at 6:03 PM, Dustin J. Mitchell dus...@zmanda.com
wrote:
That said, the new chg-disk *is* supposed to duplicate the data
symlink quirk, so I'll take a look at why it's not doing that.
And I just
On Tue, Sep 28, 2010 at 6:26 PM, Gene Heskett gene.hesk...@gmail.com wrote:
I now see a 'data' link to slot 5, I nuked that 2 days ago because nothing
was paying an attention to it, and neither amcheck nor amdump was updating
it, and the loss causes no errors, none, nada, zip. My helper script
On Tuesday, September 28, 2010 09:42:43 pm Dustin J. Mitchell did opine:
On Tue, Sep 28, 2010 at 6:26 PM, Gene Heskett gene.hesk...@gmail.com
wrote:
I now see a 'data' link to slot 5, I nuked that 2 days ago because
nothing was paying an attention to it, and neither amcheck nor amdump
was
On Tue, Sep 28, 2010 at 9:06 PM, Gene Heskett gene.hesk...@gmail.com wrote:
Anyway, its setup, and awaiting orders Cap'n. Next?
Can you replicate any of the failure-to-update-data errors with this
test config?
Dustin
--
Open Source Storage Engineer
http://www.zmanda.com
On Tuesday, September 28, 2010 11:16:55 pm Dustin J. Mitchell did opine:
On Tue, Sep 28, 2010 at 9:06 PM, Gene Heskett gene.hesk...@gmail.com
wrote:
Anyway, its setup, and awaiting orders Cap'n. Next?
Can you replicate any of the failure-to-update-data errors with this
test config?
to get
my database all in step again.
Is anyone else actually using GenesAmandaHelper-0.6? I can send you the
two scripts that are changed privately, just yelp.
--
Cheers, Gene
There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order.
-Ed
-disk around the beginning of August.
I have now patched my script for new means of assuring my data files go into
the correct subdir of a vtape setup, but it will take a month or so to get
my database all in step again.
Is anyone else actually using GenesAmandaHelper-0.6? I can send you
of it in the ChangeLog, I read it again early this morning
from about the middle of July.
I have now patched my script for new means of assuring my data files
go into the correct subdir of a vtape setup, but it will take a month
or so to get my database all in step again.
Is anyone else actually using
On Sun, Sep 26, 2010 at 4:34 PM, Gene Heskett gene.hesk...@gmail.com wrote:
Yes I did, but that didn't give me a clue that the 'data' link to whatever
had been deprecated and that for cleanliness, I should go around an nuke
it. No mention of it in the ChangeLog, I read it again early
an nuke it. No mention of it in the ChangeLog, I read it
again early this morning from about the middle of July.
The new changer was added sometime before that. YOU changed your
configuration to use it in August. In retrospect, we should have
named it something different -- perhaps chg-vfs
On Friday 11 June 2010, Dustin J. Mitchell wrote:
On Fri, Jun 11, 2010 at 2:25 PM, Gene Heskett gene.hesk...@gmail.com
wrote:
Ok, but todays 3156 just fell over, same perms problem.
Right, I haven't fixed it yet.
And 3161 is still confused. ;-) In the final mix, how is this supposed to
On Sat, Jun 12, 2010 at 12:05 PM, Gene Heskett gene.hesk...@gmail.com wrote:
And 3161 is still confused. ;-) In the final mix, how is this supposed to
work?, and I'll change my 2 scripts accordingly.
I think you're just pulling my chain now, but I'll go again:
Right, I haven't fixed it yet
, but I'll go again:
I didn't think I was.
Right, I haven't fixed it yet.
The patch is in review - there's some lingering discussion of the
proper permissions for amrecover and oldamrecover.
Is it intentional now that amcheck, amplanner and a couple others are now
owned by root:root
On Sat, Jun 12, 2010 at 1:48 PM, Gene Heskett gene.hesk...@gmail.com 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
On Saturday 12 June 2010, Dustin J. Mitchell wrote:
On Sat, Jun 12, 2010 at 1:48 PM, Gene Heskett gene.hesk...@gmail.com
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
On Fri, Jun 11, 2010 at 12:10 AM, Gene Heskett gene.hesk...@gmail.com wrote:
At the end of the install, it falls over with:
make[1]: Leaving directory `/home/amanda/amanda-3.2.0alpha.svn.3147'
bash: /usr/local/sbin/amcheck: Permission denied
And sure enough, when I go check, amcheck is owned
On Friday 11 June 2010, Dustin J. Mitchell wrote:
On Fri, Jun 11, 2010 at 12:10 AM, Gene Heskett gene.hesk...@gmail.com
wrote:
At the end of the install, it falls over with:
make[1]: Leaving directory `/home/amanda/amanda-3.2.0alpha.svn.3147'
bash: /usr/local/sbin/amcheck: Permission denied
On Fri, Jun 11, 2010 at 2:25 PM, Gene Heskett gene.hesk...@gmail.com wrote:
Ok, but todays 3156 just fell over, same perms problem.
Right, I haven't fixed it yet.
Are you sure you want to change how that works?
Yes - chowning everything to amanda is actually *less* secure (since
it means that
On Friday 11 June 2010, Dustin J. Mitchell wrote:
On Fri, Jun 11, 2010 at 2:25 PM, Gene Heskett gene.hesk...@gmail.com
wrote:
Ok, but todays 3156 just fell over, same perms problem.
Right, I haven't fixed it yet.
Are you sure you want to change how that works?
Yes - chowning everything to
Greetings folks;
I just used my usual scripts to install 3.2alpha-3147, and its dead.
Something in the install script isn't properly setting ownerships and perms.
At the end of the install, it falls over with:
make[1]: Leaving directory `/home/amanda/amanda-3.2.0alpha.svn.3147'
bash:
On Thu, Sep 17, 2009 at 4:08 AM, Dominik Schips domi...@s235.de wrote:
The error message in the amanda status report is:
dump to tape failed: driver: [writing file: No space left on device]
Can you attach the trace log so we can see what happened after that?
And also the taper's debug log.
Hello,
I did an upgrade from Amanda 2.4.4p3-3 (Debian sarge) to Amanda
2.5.2p1-4 (Debian lenny).
After this upgrade Amanda didn't take a new tape if a DLE failed because
of emty space on the current tape.
With Amanda 2.4.4 it took the next tape if it reaches the end of one
tape.
I changed some
Additional information about this problem.
An additional external USB hard drive has been added to this host about
one month ago. The filesystem on this hard drive is not backed up with
Amanda. But the observation is that the Broken Pipe problem seems to
disappear when the filesystem on this
sure that it doesn't occur again.
Thanks,
Yogesh
amdump.1
Description: Binary data
Dustin,
I was playing with dividing a large DLE, 270Gig (which is yet another
thread for this same server) and started a run yesterday morning, so
the PM run with maxdumps reduced from 4 to 3 did not run last night.
The client is in a 'good' state, so we should be set for tonight,
but a known
Server is Solaris 10 x86 (on an X4500), Amanda 2.6.1p1
Lyra client is the same version on also running Solaris 10, but
Sparc, on a T1000.
Both Lyra:/ and Curie:/ are standard comp-root, ufs file systems.
(Other DLEs on both systems use zfs-snapshots).
(amnda client) Lyra has defunct jobs again
On Wed, Jul 8, 2009 at 8:54 AM, Brian Cuttlerbr...@wadsworth.org wrote:
(amnda client) Lyra has defunct jobs again. I removed all of
the cruft a couple of days ago and amanda ran successfully, but
the issue has recurred.
The defunct jobs are a known deficiency, but as you said earlier, they
go
that type of cross interaction).
On Wed, Jul 08, 2009 at 10:06:39AM -0400, Dustin J. Mitchell wrote:
On Wed, Jul 8, 2009 at 8:54 AM, Brian Cuttlerbr...@wadsworth.org wrote:
(amnda client) Lyra has defunct jobs again. I removed all of
the cruft a couple of days ago and amanda ran successfully
On Wed, Jul 8, 2009 at 10:18 AM, Brian Cuttlerbr...@wadsworth.org wrote:
The job on the server completes, the amandad on the client
does not terminate, causing the 'dump' failures following
days on the particular client.
OK. Sorry if I missed that in the earlier emails. What
authentication
All,
Amanda has won Linux Journal's Linux Choice Award for 2009:
http://www.linuxjournal.com/article/10451
Jean-Louis
On Fri, Nov 7, 2008 at 7:49 PM, Gene Heskett [EMAIL PROTECTED] wrote:
Which means it should be in the CONFIGURATION-OVERRIDE section of a 'man
amanda'. But it isn't mentioned that I can see. This is the latest 2.6.0p2
from your home page at zmanda.
I'm not sure why you'd look in
On Saturday 08 November 2008, Dustin J. Mitchell wrote:
On Fri, Nov 7, 2008 at 7:49 PM, Gene Heskett [EMAIL PROTECTED]
wrote:
Which means it should be in the CONFIGURATION-OVERRIDE section of a 'man
amanda'. But it isn't mentioned that I can see. This is the latest
2.6.0p2 from your home
On Thu, Nov 6, 2008 at 7:28 PM, Gene Heskett [EMAIL PROTECTED] wrote:
Older? 1.17 is the default for an F8 install. Are you saying that this has
finally been addressed, and that amanda can now tell tar to ignore that?
Yep -- check the amanda-users and bug-tar archives.
Dustin
--
Storage
On Friday 07 November 2008, Dustin J. Mitchell wrote:
On Thu, Nov 6, 2008 at 7:28 PM, Gene Heskett [EMAIL PROTECTED]
wrote:
Older? 1.17 is the default for an F8 install. Are you saying that this
has finally been addressed, and that amanda can now tell tar to ignore
that?
Yep -- check the
On Sat, Nov 1, 2008 at 5:59 AM, Gene Heskett [EMAIL PROTECTED] wrote:
I just went back through my emails from amanda for the last several days, and
its appears that the device mapper has struck again by using volatile
numbers. With 2.6.28-rc2, all the disks are now at a major device number
On Thursday 06 November 2008, Dustin J. Mitchell wrote:
On Sat, Nov 1, 2008 at 5:59 AM, Gene Heskett [EMAIL PROTECTED]
wrote:
I just went back through my emails from amanda for the last several days,
and its appears that the device mapper has struck again by using volatile
numbers
Greetings all;
I just went back through my emails from amanda for the last several days, and
its appears that the device mapper has struck again by using volatile
numbers. With 2.6.28-rc2, all the disks are now at a major device number of
8, where they used to be 254.
/usr/movies, which
Jennifer Luisi schrieb:
/export/amanda/vtapes/tape1/slots:
total 44
lrwxrwxrwx 1 amanda disk 39 Nov 26 13:53 data -
/export/amanda/vtapes/tape1/slots/slot4
-rw--- 1 amanda disk 11 Nov 26 13:53 info
drwxr-xr-x 2 amanda disk 4096 Nov 26 12:38 slot1
[...]
You seem to have mixed
:
SUCCESS taper [hostname] /export/backup 20071126 0 [sec 188.985 kb 0 kps
0.0 {wr: writers 0 rdwait 188.984 wrwait 0.000 filemark 0.000}]
INFO driver [hostname] /export/backup 0 [dump to tape failed, will try
again]
I've googled and read docs and how-to's to get where I am now
shows:
SUCCESS taper [hostname] /export/backup 20071126 0 [sec 188.985 kb 0
kps 0.0 {wr: writers 0 rdwait 188.984 wrwait 0.000 filemark 0.000}]
INFO driver [hostname] /export/backup 0 [dump to tape failed, will try
again]
What's the dumper result for the disk?
Jean-Louis
PROPERLY!
again, this is probably because I killed them. How long should amanda
be running before it completes? I've got my disklist down to one host
and one very small directory and I'm still not able to get any data
written to my tape/disk.
Thanks,
Jen
failed: Connection
timed out
driver: result time 189.086 from dumper0: TRY-AGAIN 01-2 could not
connect to data port: Connection timed out
On the client-side, I found the following in my sendbackup.*.debug file:
sendbackup: debug 1 pid 30171 ruid 33 euid 33: start at Tue Nov 27
11:49:37
Jennifer Luisi schrieb:
I think I'm getting closer to the problem. There seems to be a
connection issue between my server and client. If anyone has any input,
I'd appreciate it. I've got iptables on my client set up to accept port
10080 connections from my server, and it's obviously talking
driver: result time 189.086 from dumper0: TRY-AGAIN 01-2 could not
connect to data port: Connection timed out
On the client-side, I found the following in my sendbackup.*.debug file:
sendbackup: debug 1 pid 30171 ruid 33 euid 33: start at Tue Nov 27
11:49:37 2007/usr/lib/amanda/sendbackup
Jennifer Luisi schrieb:
Okay, I figured out what my silly little problem was. Apparently, you
need to turn on amanda on your server before anything will work.
An interesting observation:
software has to be started to work
;)
It's
interesting that there isn't a useful error to point out
1051091 158.7 2:36 6737.3
5:39 3097.9
server /projekte 0 8876700 11223553 126.4 43:33 4295.4
60:48 3076.9
Once again the data seems to grow while it's written to the tape.
But I think I figured out the problem. During the calculation of the
estimates everything seems to be ok and all
2971.2
server /literatur 0 662255 1051091 158.7 2:36 6737.3
5:39 3097.9
server /projekte 0 8876700 11223553 126.4 43:33 4295.4
60:48 3076.9
Once again the data seems to grow while it's written to the tape.
But I think I figured out the problem. During the calculation
0 1221325 1796309 147.1 4:44 6321.5
9:46 3065.4
server /intorg 0 188995 199786 105.7 1:22 2427.2
1:07 2971.2
server /literatur 0 662255 1051091 158.7 2:36 6737.3
5:39 3097.9
server /projekte 0 8876700 11223553 126.4 43:33 4295.4
60:48 3076.9
Once again
2427.2 1:07 2971.2
server /literatur 0 662255 1051091 158.7 2:36 6737.3 5:39 3097.9
server /projekte 0 8876700 11223553 126.4 43:33 4295.4 60:48 3076.9
Once again the data seems to grow while it's written to the tape. But
I think I figured out the problem. During
1051091 158.7 2:36 6737.3 5:39 3097.9
server /projekte 0 8876700 11223553 126.4 43:33 4295.4 60:48 3076.9
Once again the data seems to grow while it's written to the tape.
But I think I figured out the problem. During the calculation of
the estimates everything seems to be ok and all
Hello again,
I still try find the cause of my problems with amanda. When the
backup finishes, I get the following dump summary:
DUMPER STATSTAPER STATS
HOSTNAME DISKL ORIG-kB OUT-kB COMP% MMM:SS KB/s MMM:SS KB/s
Post the amdump.1 log file.
Jean-Louis
Sebastian Henrich wrote:
Hello again,
I still try find the cause of my problems with amanda. When the backup
finishes, I get the following dump summary:
DUMPER STATSTAPER STATS
HOSTNAME DISK
Hi!
Amanda can't find the IP for the hostname 'pc-cedric'.
Check your name server configuration, /etc/hosts, ...
Jean-Louis
Cédric Lucantis wrote:
hi!
I'm actually trying to upgrade amanda to the latest svn version (from the
cvs 2.51b2 version which was working fine) and by the same
hi!
I'm actually trying to upgrade amanda to the latest svn version (from the cvs
2.51b2 version which was working fine) and by the same time installing it in
another directory. I could build and install it but i now have this message
after an amcheck which I don't understand:
WARNING:
Cédric,
Amanda can't find the IP for the hostname 'pc-cedric'.
Check your name server configuration, /etc/hosts, ...
Jean-Louis
Cédric Lucantis wrote:
hi!
I'm actually trying to upgrade amanda to the latest svn version (from the cvs
2.51b2 version which was working fine) and by the same
Amanda can't find the IP for the hostname 'pc-cedric'.
Check your name server configuration, /etc/hosts, ...
well, I have the following in my /etc/hosts:
127.0.0.1 localhost.localdomain localhost pc-cedric
and this in .amandahosts:
localhost.localdomain amanda
Greetings;
amanda, version 2.5.1b2-20060829, just did it again.
The whole firewall box failed, and there are still 16 copies of gtar
running on that box, each consuming 5 to 8% of the cpu.
This is with those timeout numbers doubled from the thread of 2 weeks or so
ago doubled.
I suspect
Regarding my recent post regarding strategy incronly and skip-full,
I just found out more about the problems I've had in the past with this
simply by checking the amanda.conf manual page it says:
skip-full /boolean/
Default: no. If true and planner has scheduled a full backup,
Hello All:
After a very long time, maybe after 2 years or so, I started seeing amflush
problems again. No configuration was changed and nothing was touched too.
Amflush refuses to backup stuff left in the holding space to the tape. My
tape drive blinks with activity as soon as I start amflush
1 - 100 of 277 matches
Mail list logo
