I;m upgrading one of my Amanda servers. I noticed that on one of
my Oracle machines (HP-UX 10.20) that the report was returning
file changed errors on some of the .dbf files. ell, yes, but they
are in the gtar exclude file. Odd I thought.
I have not upgraded the clients yet, so I thought I would
stan wrote:
Here's the line that causes the error:
char *aparent = vstralloc(parent_dir, /, include, NULL);
Any sugestiosn as to wheer to begin on resoloving this?
see if this patch help:
--- calcsize.c 9 Mar 2006 16:51:41 - 1.36
+++ calcsize.c 29 Mar 2006 15:45:08 -
On Sun, Apr 16, 2006 at 08:14:55AM -0700, Kevin Till wrote:
stan wrote:
Here's the line that causes the error:
char *aparent = vstralloc(parent_dir, /, include, NULL);
Any sugestiosn as to wheer to begin on resoloving this?
see if this patch help:
--- calcsize.c 9 Mar 2006
I recently set up an amanda (2.4.3-4)server servicing two amanda clients, allrunning RHES 3.0 Linux. For both clients, I chose to use GNU Tar (1.13.25) to backup partitions vice dump. Everything works quite well, but I'm used to seeing a dump summary in the emailed report from other amanda
On Sun, Apr 16, 2006 at 03:44:32PM -0400, George wrote:
I recently set up an amanda (2.4.3-4) server servicing two amanda clients,
all running RHES 3.0 Linux. For both clients, I chose to use GNU Tar (
1.13.25) to backup partitions vice dump. Everything works quite well, but
I'm used to seeing
On 4/16/06, stan [EMAIL PROTECTED] wrote:
On Sun, Apr 16, 2006 at 03:44:32PM -0400, George wrote: I recently set up an amanda (2.4.3-4) server servicing two amanda clients,
all running RHES 3.0 Linux. For both clients, I chose to use GNU Tar ( 1.13.25) to backup partitions vice dump. Everything
George schreef:
I recently set up an amanda (2.4.3-4) server servicing two amanda
clients, all running RHES 3.0 Linux. For both clients, I chose to use
GNU Tar (1.13.25) to backup partitions vice dump. Everything works quite
well, but I'm used to seeing a dump summary in the emailed report
Hello!
I am backing up to disk. I thought I put away enough holding space, but
apparently not. I get the following warning.
WARNING: holding disk /data: only 91831964 KB free (104857600 KB
requested)
How important is this? Am I taking a big performance hit because of
this? Or can I ignore
David Leangen wrote:
Hello!
I am backing up to disk. I thought I put away enough holding space, but
apparently not. I get the following warning.
WARNING: holding disk /data: only 91831964 KB free (104857600 KB
requested)
How important is this? Am I taking a big performance hit
Thank you!
I'm still having trouble with my backup on a particular client, but it
may be due to another issue... So, I'll start another thread.
On Sun, 2006-04-16 at 22:16 -0500, Frank Smith wrote:
David Leangen wrote:
Hello!
I am backing up to disk. I thought I put away enough holding
I'm still not able to backup one of my local networked hosts. The only
problem I can find in the logs is this:
could not open index directory /usr/adm/amanda/daily/index/host/_home/
Could this be a cause of my problems?
I am running the process from my backup server like so:
$root: sudo -u
On Mon, Apr 17, 2006 at 12:46:15PM +0900, David Leangen wrote:
I'm still not able to backup one of my local networked hosts. The only
problem I can find in the logs is this:
could not open index directory /usr/adm/amanda/daily/index/host/_home/
Could this be a cause of my problems?
The index would not be created unless a backup had succeeded.
Have you ever succeeded in backing up this DLE? If not,
the problem is likely elsewhere.
No, since I have updated to 2.5.0, I have not.
But this is the only error or warning message that I could find.
Any ideas where I could
I just had to move to a new install of Amanda due to a crash of my
backup server. The new server is using the Amanda 2.4.5p1 packages
under Fedora Core 5, the old server was redhat 9 and Amanda 2.4.4p2. I
copied the config from the old server to the new exact, and all worked
fine (minus
I finally noticed some log files that I never before noticed existed.
Apparently, my backup is larger than my tape space. But, shouldn't it
span multiple tapes? If I'm not mistaken, this is what happened in
earlier versions.
I suppose that this explains why my backup suddenly fails now for
15 matches
Mail list logo
