-Zoltan Forray 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
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
