Hi Shannon! When asking for help with technical problems, it helps all involved to know the technical details. "TSM won't back up anymore" is very vague; there could be any number of reasons why this would be the case. If the info below doesn't help, then you should provide more detail, such as what exactly changed on the machine (old name, new name), options file, error messages received (output from "dsmc query session" would suffice), any messages received on the server (see the TSM server activity log), and any other symptoms that you are seeing.
In general, when renaming a Windows TSM client machine, here are some important factors to consider (I may be forgetting some, but this is what occurs to me off-hand): - If you use the client machine name as the node name, then you'll want to rename the node on the TSM server. - If you use the NODENAME parameter in the client options file, you'll need to update the client options file with the new node name. - Since most of the Windows file spaces include the machine name, they should be renamed (unless you want new backups created from scratch, but that is unlikely the case). That is, if my machine name is \\storman, then my file space names would look like \\storman\c$. If I rename my machine to "araibeck", then the new machine is \\araibeck. Thus the file space \\storman\c$ should be renamed to \\araibeck\c$. - When using PASSWORDACCESS GENERATE, the password will need to be re-encrypted after the machine is renamed. You can perform a simple "dsmc query session", which should result in being prompted to enter the password. If you don't know the password, the TSM administrator can update the node with a new password, which you can then enter when the client prompts you. - See the client manual for information about configuring TSM in a cluster environment (if you are moving to a cluster environment). Also see the TSM Problem Determination Guide available from http://publib.boulder.ibm.com/tividd/td/IBMStorageManagerMessages5.2.2.html which has some hints about password problems. Regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] The only dumb question is the one that goes unasked. The command line is your friend. "Good enough" is the enemy of excellence. "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> wrote on 06/17/2004 12:39:43: > > Okay, I was really wrong! I think I'm going to have to reinstall a new > client? It turns out this is a Win2K, not NW like I was > told the first time. Which means that the registry will have to be updated, > so I think that means I'm going to have to reinstall a client. Do you think > that would work? Then I can still give it the same node name and they will > still be able to restore from the old backups? Or is that wishful > thinking.... Any other ideas? > > Shannon > > > > > Madison Gas & Electric Co. > Operations Analyst - Data Center Services > Office 608-252-7260 > Fax 608-252-7098 > e-mail [EMAIL PROTECTED] > > > Ted Byrne <[EMAIL PROTECTED]> > Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> > 06/17/2004 12:54 PM > Please respond to "ADSM: Dist Stor Manager" > > > To: [EMAIL PROTECTED] > cc: > Subject: Re: Rename of Client server > > > > > Be aware also that you are probably going to wind up with different > filespace names, since the name of the server is part of the filespace's > name on Netware (and Windows). For example, server LAXF45 has the SYS > volume recorded as LAXF45\SYS:. So you're going to get a full backup of > the server's volumes when the backup does run > > Ted > > > At 01:49 PM 6/17/2004, you wrote: > > >Never mind, the answer hit me two seconds after I clicked the send > >button. TSM won't care what the server name as long as the TSM client has > >the same nodename in the dsm.opt. I probably just need to rest the > >password to reconnect them. If I'm wrong let me know otherwise thanks > >again and sorry for taking up your time. > >Shannon > > > > > >Shannon C Bach > > > >06/17/2004 12:38 PM > > > > To: [EMAIL PROTECTED] > > cc: > > Subject: Rename of Client server > > > >Soon most of our NW's will be migrated to a cluster. In getting ready for > >this process one of the server administrator's renamed one of his Novell > >servers that I have been backing up. Now he's called to tell me and can't > >understand why TSM won't back it up anymore. I found lots of stuff on > >renaming nodes but nothing on what to do if a client server is > >renamed. Any suggestions??? > > > >Thanks! Shannon > > >
