Re: Changed host name. amrecover tries to contact old host.
2005-11-25 21:14:14
On 11/22/05, Joe Konecny <jkonecny AT rmtohio DOT com> wrote:
Paddy Sreenivasan wrote: > <snip> > >
I have a FreeBSD 5.2.1 server running 2.4.4p2. I had to > change the > >
host name on it. I set the new host name with "hostname > <hostname>", > >
edited /etc/rc.conf for the new host name, edited /etc/hosts, > disklist > >
and .amandahosts to reflect the new name. Ran amcheck and
then > >
amdump with no errors. Testing amrecover <config> and
it still > >
tries to contact the old host. amrecover <config> -s > new.hostname > >
works but it reports there are no indexes. The index file > (.gz) is in > >
in the new hostname index directory. So... why no
indexes and > > why does amrecover still want the old host? > > Just tried it. Still tries to contact old hostname. Does amandaidx > need killed and restarted? > >
> > Try amrecover -s <hostname> -t <hostname> > > Paddy
Still tells me no index records for host...
I'm a bit confused as to why amrecover <hostname> uses the old hostname. It doesn't get compiled in does it?
index and curinfo files store hostnames. In an earlier email, you mentioned you have moved index (*.gz) file
to new hostname. I'm not sure what this index file is.
Take a look at /etc/amanda/<config name>/index and /etc/amanda/<config name>/curinfo directories.
I think you can move the files to new hostnames and amrecover should work.
For example:
mv /etc/amanda/<config name>/index/<old hostname> /etc/amanda/<config name>/index/<new hostname>
mv /etc/amanda<config name>curinfo/<old hostnam> /etc/amanda/<config name>/curinfo<new hostname>
Paddy --
Amanda documentation: wiki.zmanda.com Amanda forums: forums.zmanda.com
|
|
|