Haven't looked at 5.1 yet, I know there is a new command something like "move nodedata". However as you are upgrading OS and rearranging disks, I would take your last option - Rename nodes (rename NODE NODE_OLD), then register new node names and do full backup of new machines.
After comfortable period, you can delete "old" nodes data. (Remember to check schedules, associations follow rename node. Need to delete assoc and associate with new node). David Longo >>> [EMAIL PROTECTED] 05/30/02 01:56PM >>> Hello again, here's the deal- we have approximately 50 frame relay nodes that backup to TSM servers. These NT boxes' drives are almost full (max is 16G on these) and partitions were created to hold data (D:\) and app shares (E:\). We are getting replacements (80G and expandable), and will be xcopying data from the old to the new, but the OS will be 2000. The plan right now is to just create a big D:\ drive and xcopy the files from the old D: and E: drives to this new D: drive. Host names may remain the same, but maybe not-- since we won't be a full 2000 enterprise, and 2000 can't "emulate" an old NT BDC, the old boxes may remain in the remote locations to serve as the BDCs-- without changing their hostnames. How can I tell/trick TSM to not backup up these "new" files on a different drive again and to know about previous versions of files with the old drive letter? Or is this issue moot due to the OS change? I can rename the node data and resolve the issue with a full backup due to the change in hostname, but I don't see any way to rename the filespace names to keep from having to do a full backup. I am not up to speed on 5.1, maybe the ability is there with the new code? tia lisa "MMS <health-first.org>" made the following annotations on 05/30/02 17:29:16 ------------------------------------------------------------------------------ This message is for the named person's use only. It may contain confidential, proprietary, or legally privileged information. No confidentiality or privilege is waived or lost by any mistransmission. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it, and notify the sender. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. Health First reserves the right to monitor all e-mail communications through its networks. Any views or opinions expressed in this message are solely those of the individual sender, except (1) where the message states such views or opinions are on behalf of a particular entity; and (2) the sender is authorized by the entity to give such views or opinions. ==============================================================================