Serengeti
Newcomer
Here's the situation:
TSM server version: 5.1.6
Client OS version: Win 2003
Client TSM version: 5.2.0.1
Naturally, all our backups fail on system objects because the 5.2 client on Win2003 attempts to use VSS and the 5.1.6 server has no idea how to handle it. Searching the mailing list I found a number of messages leading me to believe that the only way to work around this is to upgrade our server to 5.2.x or downgrade our clients to 5.1.x.
That's fine if that's the way it's gotta be, but isn't there a really simple option I can add to my cloptset that would force the 5.2 client to use legacy methods to backup system objects?
TSM server version: 5.1.6
Client OS version: Win 2003
Client TSM version: 5.2.0.1
Naturally, all our backups fail on system objects because the 5.2 client on Win2003 attempts to use VSS and the 5.1.6 server has no idea how to handle it. Searching the mailing list I found a number of messages leading me to believe that the only way to work around this is to upgrade our server to 5.2.x or downgrade our clients to 5.1.x.
That's fine if that's the way it's gotta be, but isn't there a really simple option I can add to my cloptset that would force the 5.2 client to use legacy methods to backup system objects?
