Good afternoon all...
This is my first post, so go easy on me, OK?
We've recently been told, after more than 10 years of being a TSM-oriented shop, that "thou shalt use EMC Networker". While our migrations have been relatively painless (stand up a new backup server, attach a new library, etc), we have recently run into some problems when changing client names after lifecycling servers. As we're lifecycling certain hardware, we're also converting our backups over to networker.
For instance, let's say we have a client named "production-server1.localdomain" (not a real server name) that we're replacing with a new hardware device named staging-server1.localdomain (also not a real server name).
Here's our current process:
1. Copy all of the data from "production..." to "staging..."
2. Do a full backup of "staging..." to networker
3. Rename "production-server1.localdomain" to "lifecycle-server1.localdomain"
4. Rename "staging..." to "production..."
5. Update IP address on "production..."
4. Power down old "production..." server and send to auction.
During this process, we introduce errors because Networker is expecting the client name to be staging-server1.localdomain. We've tried deleting the client in the GUI and re-creating using the same clientid to no avail. We've tried nsrck -r -y staging-server1.localdomain. We've tried deleting the index folder for staging-server1.localdomain.
As it stands, no scheduled backups are running for this box spitting out the following error:
39077:save: error, `staging-server1.localdomain' is not a registered client
The production-server1.localdomain (the desired end-state name) is registered as a client in the Networker Admin GUI and both DNS and WINS are correct. We've even tried using an alias in the client properties in the gui to no avail.
The weird thing is that we can do directed backups from the Networker client GUI on the new production-server1.localdomain box so there seems to be something in our backup server's index that is hanging things up.
Can ayone shed any light on how to delete all references to the old server name?
At this point we're willing to endure another full backup over a 256k link, but scheduling backups is a must.
Please keep in mind that we have one backup in progress over a terribly slow link (128k at best) that won't complete for a few days so a reboot of the backup server or restart of the networker services is out of the question (unless, of course you have a tip to work around this).