My dumps have been failing right when it seems the dump should complete.
Below is a snippet of information in the amreport that I get every
night. The client and server have no problems communicating so I'm not
sure why I would get this type of message. Does anyone have any ideas?
Thanks
Jeff
I suspect that you've got an ld.so path issue.
The best way to deal with that is to have the linking invocations of gcc
specify -R /where/ever/your/libs/are, with LD_LIBRARY_PATH unset.
Hi all:
I'm trying to run make for Amanda 2.4.2p2 on a Solaris 2.8 SPARC server
with the following configure options:
./configure --with-user=amanda --with-group=amanda
During the make process, the following error occurs. Here's the tail end
of the error message:
rm -f genversion.h genversion
If, for example, you setup your internal machines to have domains like
'host.private.daily.umn.edu', you would want your resolv.conf to look like
this:
domain private.daily.umn.edu
search private.daily.umn.edu daily.umn.edu
nameserver x
It all depends how you've setup your internal DNS, sinc
Yes. We can run nslookup from the amanda server on the hostnames of any
of the machines with NAT addresses we want it to backup and they resolve
to the proper NAT addresses.
The file /etc/resolv.conf has a domain and a nameserver entry, no search
entry, unless thats a synonymous term with nameser
Ok, if you run this:
nslookup `hostname`
on the amanda server, does that resolve? In the resolv.conf file, are
there 'domain' and 'search' entries? You can ping all the internal
machines, correct? What about some other service like ssh?
As a last resort, you could run tcpdump while running am
Our NAT addresses are class C (192.168.0.xxx). The Amanda server resides
at 192.168.0.18. It is unable to back itself up. We have a DNS server
set up for the NAT addresses at 192.168.0.10 that is referred to in
/etc/resolv.conf as the only DNS server for the Amanda server. However
the Amanda s
On Tue, 19 Mar 2002, Lee Parsons wrote:
> We tried it both ways. The backup server actually refers to another
> machine on the NAT range for its DNS, so when it pings the names of the
> machines with NAT addresses, it will get responses from their NAT IPs.
> We also added them manually to the /e
If the server can't back up itself, I'd start there. I just checked on my
system and IP's seem to work, at least with amcheck, so perhaps that will
solve your problem. If you used the FBSD port (/usr/ports) system on your
server to build Amanda, I think it automatically required FQDN for the
hos
We tried it both ways. The backup server actually refers to another
machine on the NAT range for its DNS, so when it pings the names of the
machines with NAT addresses, it will get responses from their NAT IPs.
We also added them manually to the /etc/hosts file on the backup server to
point to th
"christopher cuse" <[EMAIL PROTECTED]> writes:
> Hi All,
>
> I noticed that attempting to specify a share name containing spaces in
> disklist bombs during amcheck. Has anyone worked around this? I am trying to
> backup a number of directories on each client machine from the
> administrative sha
I seem to remember someone saying a while ago on this list that it
is possible to specify in the disklist what interface on the server an
amanda client should use.
This is because my backups are taking an age or rather the
estimates are taking an age. I thought if I could tell each client to
remove the white spaces in the share name. Make 'Documents and Settings'
'docs' or whatever. just remove all spaces... your life will become much
more simple.
works for me
On Tue, 2002-03-19 at 08:38, christopher cuse wrote:
> Hi All,
>
> I noticed that attempting to specify a share name contai
Hi All,
I noticed that attempting to specify a share name containing spaces in
disklist bombs during amcheck. Has anyone worked around this? I am trying to
backup a number of directories on each client machine from the
administrative share created through the windows profile on the samba server
i
On March 19 2002, "Robert SHEN" wrote:
> I got the following message in the report sent by amanda, does anyone figure
> out the meaning:
> > gtar: ./dumps/20020319/host.domain._dev_sda5.0.tmp: file changed as we
> read it
Just as the message says, that file changed
]
sendbackup: info BACKUP=/bin/tar
sendbackup: info RECOVER_CMD=/bin/gzip -dc |/bin/tar -f... -
sendbackup: info COMPRESS_SUFFIX=.gz
sendbackup: info end
> gtar: ./dumps/20020319/host.domain._dev_sda5.0.tmp: file changed as we
read it
| Total bytes written: 3427215360 (3.2GB, 3.5MB/s)
sendbackup: s
16 matches
Mail list logo
