Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Backup sessions remain in MediaW for file class volumes
ADSM/TSM Troubleshooting Tips
Problem(Abstract)
A Tivoli Storage Manager client backs up to a FILE storage pool. The client backup session, and may others, remain in MediaW state for a long period.
Symptom
The QUERY SESSION administrative command shows the session in MediaW. For example :
1 MediaW NODE1 Waiting for mount point(s)
NODE1-FILE_STG1,FILECLASS ,(x Seconds) 2 MediaW NODE1 Waiting for mount point(s)NODE1-FILE_STG1,FILECLASS ,(y Seconds)
Cause
The amount of concurrent sessions and processes require a number of mountpoints greater than the mountlimit value configured with the FILE device class.
Diagnosing the problem
Review the QUERY SESSION output and verify that many sessions are in MediaW state.
Review the QUERY MOUNT output and verify the number of volumes currently mounted for the associated FILE device class. In this example, there were 20 volumes mounted.
Review the QUERY DEVCLASS output and verify the mountlimit value for the associated FILE device class. In this example, the mountlimit value was set to 20.
Resolving the problem
To resolve this issue, either reduce the amount of concurrent sessions and processes such that the number of required mountpoints is less than the FILE device class mountlimit value or increase the FILE device class mountlimit value with the following Tivoli Storage Manager server administrative server command :
UPdate DEVclass <class-name> mountlimit=xx
A Tivoli Storage Manager client backs up to a FILE storage pool. The client backup session, and may others, remain in MediaW state for a long period.
Symptom
The QUERY SESSION administrative command shows the session in MediaW. For example :
1 MediaW NODE1 Waiting for mount point(s)
NODE1-FILE_STG1,FILECLASS ,(x Seconds) 2 MediaW NODE1 Waiting for mount point(s)NODE1-FILE_STG1,FILECLASS ,(y Seconds)Cause
The amount of concurrent sessions and processes require a number of mountpoints greater than the mountlimit value configured with the FILE device class.
Diagnosing the problem
Review the QUERY SESSION output and verify that many sessions are in MediaW state.
Review the QUERY MOUNT output and verify the number of volumes currently mounted for the associated FILE device class. In this example, there were 20 volumes mounted.
Review the QUERY DEVCLASS output and verify the mountlimit value for the associated FILE device class. In this example, the mountlimit value was set to 20.
Resolving the problem
To resolve this issue, either reduce the amount of concurrent sessions and processes such that the number of required mountpoints is less than the FILE device class mountlimit value or increase the FILE device class mountlimit value with the following Tivoli Storage Manager server administrative server command :
UPdate DEVclass <class-name> mountlimit=xx