I have a weird problem and I am out of ideas.
Windows 2008 R2 SP1, Xeon E5645 @2.40GHz (2 Processors), 96GB of RAM, 64 bits
TSM server 6.3.0 64 bits
TSM client 6.2.4.0
When I do a selective backup of 5.58MB_568Files_129Folders I have a slow behavior which points me to a database problem.
Total number of objects inspected: 699
Total number of objects backed up: 699
Total number of objects updated: 0
Total number of objects rebound: 0
Total number of objects deleted: 0
Total number of objects expired: 0
Total number of objects failed: 0
Total number of subfile objects: 0
Total number of bytes inspected: 4.25 MB
Total number of bytes transferred: 4.25 MB
Data transfer time: 0.37 sec
Network data transfer rate: 11,615.57 KB/sec
Aggregate data transfer rate: 1.67 KB/sec
Objects compressed by: 0%
Total data reduction ratio: 0.00%
Subfile objects reduced by: 0%
Elapsed processing time: 00:43:27
The database seems to have a fair amount of disk activity, then all of a sudden it stops. Almost as if a threshold has been reached.
I did some client and server traces with IBM support, but unless I put this a sev1 there is little change of them looking at this "minor" performance problem. TSM support points me to the Performance Tuning Guide, but I will escalate if I can't find any way out.
Here is some info that came back from TSM support:
Most of the time for this transaction was spent in Tm Lock Wait.
The final statistics for the whole backup show
DB2 Reg Exec 9859 11785.606 1.195 17.066
Tm Lock Wait 78 17054.885 218.652 3240.208
These are the 2 factors that impact the performance .
The meaning of the parameters is:
Tm Lock Wait Acquiring transaction manager lock
DB2 Reg Exec Execute the registered SQL statement
This indicates that the problem is with the db2 database.
And this was with a test of 14.4MB_952Files_188Folders selective backup.
I think there might be an OS issue but I am not sure where to begin.
A call will probably be opened with MS on Monday.
Seems also that the problem is present when I move the database to new disks ... (but that may be just slow DB2 restore process). ... I am trying to eliminate any disk related issues by moving the database and logs to different disks ... now in the process to move DB and log to C: ...
Any ideas are welcome. Please.
Windows 2008 R2 SP1, Xeon E5645 @2.40GHz (2 Processors), 96GB of RAM, 64 bits
TSM server 6.3.0 64 bits
TSM client 6.2.4.0
When I do a selective backup of 5.58MB_568Files_129Folders I have a slow behavior which points me to a database problem.
Total number of objects inspected: 699
Total number of objects backed up: 699
Total number of objects updated: 0
Total number of objects rebound: 0
Total number of objects deleted: 0
Total number of objects expired: 0
Total number of objects failed: 0
Total number of subfile objects: 0
Total number of bytes inspected: 4.25 MB
Total number of bytes transferred: 4.25 MB
Data transfer time: 0.37 sec
Network data transfer rate: 11,615.57 KB/sec
Aggregate data transfer rate: 1.67 KB/sec
Objects compressed by: 0%
Total data reduction ratio: 0.00%
Subfile objects reduced by: 0%
Elapsed processing time: 00:43:27
The database seems to have a fair amount of disk activity, then all of a sudden it stops. Almost as if a threshold has been reached.
I did some client and server traces with IBM support, but unless I put this a sev1 there is little change of them looking at this "minor" performance problem. TSM support points me to the Performance Tuning Guide, but I will escalate if I can't find any way out.
Here is some info that came back from TSM support:
Most of the time for this transaction was spent in Tm Lock Wait.
The final statistics for the whole backup show
DB2 Reg Exec 9859 11785.606 1.195 17.066
Tm Lock Wait 78 17054.885 218.652 3240.208
These are the 2 factors that impact the performance .
The meaning of the parameters is:
Tm Lock Wait Acquiring transaction manager lock
DB2 Reg Exec Execute the registered SQL statement
This indicates that the problem is with the db2 database.
And this was with a test of 14.4MB_952Files_188Folders selective backup.
I think there might be an OS issue but I am not sure where to begin.
A call will probably be opened with MS on Monday.
Seems also that the problem is present when I move the database to new disks ... (but that may be just slow DB2 restore process). ... I am trying to eliminate any disk related issues by moving the database and logs to different disks ... now in the process to move DB and log to C: ...
Any ideas are welcome. Please.
Last edited: