JeepLimited,
What is the full version of the TSM Server?
What is the os, and versio, that is hosting the TSM Server?
What is the full version of the TSM Client ?
Since there are 2300+ client, what is the lowest and highest TSM Client?
What is the flavor of the Windows os?
Was it a schedule backup or a manual backup?
To exclude the systemstate, the following should work domain all-local -systemstate
Did we stop and restart the schedule service?
Any time when we manually update the dsm.opt file, the schedule service need to be stop and restarted so that the new updates in the dsm.opt file.
Were there any error message in the dsmeror.log and/or the dsmsched.log?
On the TSM Server, in the actlog, around the time frame of the backup were there any error message for the node in question?
As a test in the dsm.opt file update the domain to
domain all-local -systemstate
Atttempt a manual backup of the system state.
ie: dsmc backup systemstate
The manual backup of the system state should not be backed up.
... even threw that in the server clientcoptionset nothing is working.
Forgive me, I do not understand your American idiom, when you say "even threw that in the server..."
Did you issue define cloptset option_set_name and that is it?
Did we only issue define cloptset?
Did we also define a clientopt ?
If we also define the clientopt, did we also associate the node with the clientopt?
Can you post the following.
Q CLO option_set_name
Select two of the 2300+ nodes that is associated with the client option set.
Q Node node_name F=D
Also post the actlog +/- 1hr around the time frame of when we define the client option, the client option set and updated node.
Once we get the test backup to work excluding the systemstate.
I would create a file that list 2300+ nodes.
Create a macro can perform the update node operation, utilizing the file that lists all the node names.
Good Luck,
Sias
