-----Zoltan Forray <[email protected]> wrote: ----- >We had an incident this morning that ended up being caused by a >Windows server that was renamed (internally) and connected to a >domain (previously standalone), thus initiating a full backup of >an 8TB volume/space, since TSM now sees it as new filespaces. > >How do I handle this to avoid a full backup? Will simply renaming >the >filespaces take care of this or is there a more elegant >solution?
We have occasionally renamed Windows TSM clients. Renaming file spaces for drive letters works fine in terms of avoiding full backups. I would not recommend renaming system state file spaces that incorporate the node name.
