I've gotten caught in a bill-back hassle with one of our clients.
Quick background:
1. Node1 has backed up their data for years.
2. Node2 was created to back up a new server.
3. Some, but not all, data has been COPIED from the Node1 server to the
Node2 server. Not moved, just copied. They can't access the data, but refuse
to let server admins delete it.
4. This has resulted in "double-billing" because TSM server now has both
Node1 and Node2 with the data that was copied.
5. Node1 has to stay in production to backup data that will never be
relocated.
Will this approach work to clean up TSM DB occupancy for Node1 data?
1. Rename folder E:\DATA to E:\OLDDATA.
2. Place an EXCLUDE.DIR E$\OLDDATA in dsm.opt
3. Stop/start the scheduler.
Will TSM resolve E:\DATA (which no longer exists) and all the files in it and
its sub-folders as a "deleted files" and expiration processing would remove
those files from the TSM DB for Node1?
There are sub-folders to OLDDATA, so the syntax for the EXCLUDE.DIR will need
to respect that structure.
The expire would delete E:\DATA when the "keep the last file version" term has
passed.
Other folders in E$ will continue to backup from Node1.
Thanks for helping out.
------------------------------------------------------------
Harold Vandeventer
Systems Programmer
State of Kansas - Office of Information Technology Services
STE 751-S
910 SW Jackson
(785) 296-0631
[Confidentiality notice:]
***********************************************************************
This e-mail message, including attachments, if any, is intended for the
person or entity to which it is addressed and may contain confidential
or privileged information. Any unauthorized review, use, or disclosure
is prohibited. If you are not the intended recipient, please contact
the sender and destroy the original message, including all copies,
Thank you.
***********************************************************************
|
