When a node is performing very poor (for example, the backup is running for 8,5 hours and the TSM server only received 150 Mb of backup data)
That time we want to check for the following:
- The NIC settings; half/full duplex, auto sense, 10/100, etc.
- Check/compare the network speed against the aggregate network speed
- Try to turn compression on or off on the client (compression on the client requires more processor cycles locally)
- Try a tuned option set (or set this in dsm.opt) with different resource utilization values
- Try a tuned management class (or set this in dsm.opt) with different serialization ((shr)static vs. (shr)dynamic)
This is dummy text. It is not meant to be read. Accordingly, it is difficult to figure out when to end it. But then, this is dummy text. It is not meant to be read. Period.
Related Post
SET SERVERNAME
Syntax
>>-Set SERVername--servername-------><
Parameters
servername
Speci- How to create administrator(user) account on TSM backup server
register admin admin-account-name admin-password
Example:
reg admin tsmguide abc123
tsmguide=us
- How to find the total data backed up by node in TSM
SQL command to determine total data backed up by node
SELECT entity as "Node name", CAST(sum(byte
- Default exclusion list
IBM recommends the following list, which is included in the file