On Mon, Mar 27, 2017 at 09:53:21 -0400, Jean-Louis Martineau wrote: > Nothing can be done. > > The backup are done with the 'localhost' hostname > You must use it when restoring.
In particular, the dumps written to tape include the hostname as part of the header block in the dump-file itself, so even if you were to somehow manage to change all the online indexing information to use the new name, you would never be able to use Amanda's normal restore process with the existing dumps-on-tape. > On 23/03/17 09:50 AM, [email protected] wrote: > > For the past couple of years, I've been using amanda to back up the > > server amanda was running on, and I stupidly used the name localhost > > for those backups. > > > > Now I want to move amanda to a different server. I will use the actual > > name of the new server. But when I set up backups of the old server, I > > would like amanda to realize that this "new" machine already has a bunch > > of pre-existing backups that it can both recover from and build upon. > > > > Is there a way I can do that? Re-assign all of these backups from > > localhost to the (old) server's actual name? Note that even without wanting to change the hostname used for one of the DLEs, it'll take "some work" to migrate the existing dump database from the old backup server to the new one. Depending on your environment, it may be easier just to start the new server "from scratch", keeping the old server around for recovery purposes until the new server has been running long enough that the old server's backups are obsolete.... (Obviously you'd use the correct hostname for the old "localhost" DLE when you configured that DLE on the new server.) Nathan ---------------------------------------------------------------------------- Nathan Stratton Treadway - [email protected] - Mid-Atlantic region Ray Ontko & Co. - Software consulting services - http://www.ontko.com/ GPG Key: http://www.ontko.com/~nathanst/gpg_key.txt ID: 1023D/ECFB6239 Key fingerprint = 6AD8 485E 20B9 5C71 231C 0C32 15F3 ADCD ECFB 6239
