Folks, We are apparently in the minority due to the fact that we don't want to backup the SYSTEM_OBJECT on Windows 2000 on our clients. I have contacted Tivoli support and know that my only option currently is to use the DOMAIN statement in the dsm.opt file to control this. Therefore I come to the community and ask what (if any) requests have you made of the developers for design changes concerning this topic.
I know some developers frequent this list, and if any of them care to comment on this, I would love to have your input. I plan on talking with Tivoli Marketing soon, asking for a design change to incorporate a feature that will allow me to exclude the SYSTEM_OBJECT; so maybe something like an option called EXCLUDE.SYSTEMOBJECT. It is my opinion that this should be an option that could be set from a server client option set, so that each client dsm.opt file doesn't need to be modified. This is a problem in my environment, as I have over 10,000 clients total, and it's difficult to make changes that require user action. When I spoke with Tivoli support about my problem, he mentioned that when designing the capability to backup the system files, they were required to take an 'all or nothing' approach. While this seems to be true, they make it quite difficult for the user to choose the 'nothing' route, much different from the philosophy TSM normally espouses. OK, thanks for listening. I look forward to your comments. -Matt
