Ram TK Krishnamurthy wrote:
Gene
Do you still see the Note: regarding .../curinfo/.. and ../index/..
on the amcheck output?
I have run into situation, where dumps fail until I create that by hand.
Its actually not created in the next run. A bug is filed.
I just tried this on 2.5.0b2 and it
I've had backups working for over 2 months now.A system reboot started daily failures on the remote machine:Report says: ==FAILURE AND STRANGE DUMP SUMMARY: planner: ERROR host1NAK : amandad busy host01 /export RESULTS MISSING etc...amandad.debug says:
On Thu, 26 Jan 2006, Gene Heskett wrote:
I've attemped to add a couple of disklist entries to my backup schedule,
but I've run into a problem that doesn't seem to make a lot of sense to
me.
I've copied the .amandahosts file over to that box in /home/amanda, and
added the fqdn and alias
On Friday 27 January 2006 02:48, Ram TK Krishnamurthy wrote:
Gene
Do you still see the Note: regarding .../curinfo/.. and ../index/..
on the amcheck output?
No, that apparently worked ok. FWIW I run the latest 2.4.5 snapshot on
the server, this box. And according to the emails, it all worked as
On Friday 27 January 2006 06:05, shoaib r wrote:
I've had backups working for over 2 months now.
A system reboot started daily failures on the remote machine:
Report says:
==
FAILURE AND STRANGE DUMP SUMMARY:
planner: ERROR host1NAK : amandad busy
host01 /export RESULTS
Paul Bijnens wrote:
Ram TK Krishnamurthy wrote:
Gene
Do you still see the Note: regarding .../curinfo/.. and ../index/..
on the amcheck output?
I have run into situation, where dumps fail until I create that by hand.
Its actually not created in the next run. A bug is filed.
I just tried
Ram TK Krishnamurthy wrote:
I just tried this on 2.5.0b2 and it gives no problem at all.
Interesting. Thats where it failed for me.
How did you verify that amdump completed successfully? In my
case amdump return without any errors, but the log files showed me
that the dump had failed.
Which
Definitely seems Ok. I will have to take another look at my config. The
error I saw was
more amtrmidx.20060125143614.debug
amtrmidx: debug 1 pid 30613 ruid 33 euid 33: start at Wed Jan 25
14:36:14 2006
/usr/lib/amanda/amtrmidx: version 2.5.0b2
natasha /boot
could not open index directory
Hello again,
I don't have a problem this time, but I'm curious:
The dump user on the clients is not required to have the permissions to
read what he's backing up - read access to the devices is sufficient.
Still, we can exclude file-wise and have a TOC on the server afterwards.
How does this
Jens Theisen schreef:
I don't have a problem this time, but I'm curious:
The dump user on the clients is not required to have the permissions to
read what he's backing up - read access to the devices is sufficient.
Still, we can exclude file-wise and have a TOC on the server afterwards.
2006/1/27, shoaib r [EMAIL PROTECTED]:
I've had backups working for over 2 months now.
A system reboot started daily failures on the remote machine:
The tape server is backing its filesystems up sucessfully. However the one
and only remote server is not.
Does anyone have any ideas?
Thank
It seems that even though I'm using gcc, and configure
find gcc as 'gcc', it still adds to the Makefiles the
xlc options -q32 and -qlonglong.
Has anyone found a way around this ? Or anyone found a
way to get amanda to build in AIX ?
AIX 5.2 ML7
Gcc either PDSLIB 4.02 or IBM Freeware 3.3.2
Amanda
12 matches
Mail list logo
