Networker

[Networker] NW 7.6.1/Win2K8 host - errors after renaming client

2012-05-02 00:09:50
Subject: [Networker] NW 7.6.1/Win2K8 host - errors after renaming client
From: bingo <networker-forum AT BACKUPCENTRAL DOT COM>
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Date: Tue, 1 May 2012 21:07:58 -0700
There are certain things that NW has to rely on. One of them is the unique 
hostname resolution. This is obvious. NW also assigns the internal identifier 
'clientid' when a client is configured the first time. It is invisibly assigned 
and stored inside NW's media index. You can not change it.

But you do not need to cheat NW. The procedure to 'move' data is pretty simple:
  - Define both client in NW (you only need a hostname resolution to do that)
  - Run the backup on the old server
  - Restore the data to the new server (so-called 'directed recovery')
  - Decommission the old machine as it is not needed any more 

Your message maybe due to 2 problems:
  - The new client has not been configured yet. This is easy to solve. See 
above.
  - If you just rename the client, then the clientid may remain the same. 
Changing it is impossible as it remains invisible.
  - You better start all over with new backups.
  - And do not forget to prepare your NW client:
      - stop the NW client daemon/service
      - delete the ..../nsr/res/nsrladb directory
      - restart the NW client listener

One of my collegues just had a similar problem when we needed to rename some 
clients because our standard hostname was misinterpreted by SAP. Fortunately 
these were new servers. Unfortunately i was on vacation and i did not verify 
the clientid before and after the renaming.

#######

BTW, running a full backup over a WAN is weird. It will of course work .. as 
longs as there are no interrupts.

However, may i strongly suggest that you install a local (disk) backup device 
and temporarily promote the client to a Storage Node. In this case, a local 
backup will take place and only the metadata needs to be transferred. Bare in 
mind that the WAN speed is still a limiting factor when you backup a lot of 
tiny files (too much metadata)!

Then bring the backup media (device) to the NW server's site and migrate/stage 
it to your desired backup media. If you need additional licenses your sales rep 
is able to provide temporary ones.

+----------------------------------------------------------------------
|This was sent by carsten_reinfeld AT avus-cr DOT de via Backup Central.
|Forward SPAM to abuse AT backupcentral DOT com.
+----------------------------------------------------------------------

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

<Prev in Thread] Current Thread [Next in Thread>