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?


Zoltan Forray
TSM Software & Hardware Administrator
Virginia Commonwealth University
UCC/Office of Technology Services
zforray AT vcu DOT edu - 804-828-4807
Don't be a phishing victim - VCU and other reputable organizations will
never use email to request that you reply with your password, social
security number or confidential personal information. For more details
visit http://infosecurity.vcu.edu/phishing.html