wirb
ADSM.ORG Member
- Joined
- May 7, 2004
- Messages
- 67
- Reaction score
- 0
- Points
- 0
- Location
- Western Washingtion, USA
- Website
- Visit site
Hi all,
Running TSM 5.2.4.5 on Win2k, all clients are 5.2.4
got a couple of issues that have me stumped.
I have a node that had the client re-installed after the node name changed. It still thinks it's the old node. It's backing up the data (in addition to the new node with the old name). But I can't get it to use the new node name. The client's managed by the CAD. DSMSCHED.LOG shows the CAD polling for the correct schedule time but using the wrong node name. The node is defined in TSM with the new name, and associated with the schedule using the new name (it's the 2nd node associated with this schedule). Here's what I've done:
- updated the nodename and password on client via dsmcutil
- done the same again, updating password on the server
- There was no administrator defined for that node; all our other nodes have administrators (their node names, listed in the "administrators" section of TSM management GUI). So I defined an administrator for it, using the other node administrators as a guide.
- the node definition has the correct TCP/IP name and address.
- I even forced the node name setting in DSM.OPT
I'm wondering whether deleting and re-registering the node will help (I did not do the original node registration). In the meantime, I could use some ideas about this.
Also, at the beginning of this week, one of our nodes that normally takes about 4 hours to back up suddenly started taking 2 days. No changes have been made; the amount of data has not changed much, it's clean of virii etc, the virus scanner is not curently scanning, previous backups have been running flawlessly. Looking at CPU usage dsmsvc is taking 96 MB of memory, which is normal, but the CPU's pegged at 100%. Any ideas other than killing the backup and bouncing the CAD??
thanks everyone!
Running TSM 5.2.4.5 on Win2k, all clients are 5.2.4
got a couple of issues that have me stumped.
I have a node that had the client re-installed after the node name changed. It still thinks it's the old node. It's backing up the data (in addition to the new node with the old name). But I can't get it to use the new node name. The client's managed by the CAD. DSMSCHED.LOG shows the CAD polling for the correct schedule time but using the wrong node name. The node is defined in TSM with the new name, and associated with the schedule using the new name (it's the 2nd node associated with this schedule). Here's what I've done:
- updated the nodename and password on client via dsmcutil
- done the same again, updating password on the server
- There was no administrator defined for that node; all our other nodes have administrators (their node names, listed in the "administrators" section of TSM management GUI). So I defined an administrator for it, using the other node administrators as a guide.
- the node definition has the correct TCP/IP name and address.
- I even forced the node name setting in DSM.OPT
I'm wondering whether deleting and re-registering the node will help (I did not do the original node registration). In the meantime, I could use some ideas about this.
Also, at the beginning of this week, one of our nodes that normally takes about 4 hours to back up suddenly started taking 2 days. No changes have been made; the amount of data has not changed much, it's clean of virii etc, the virus scanner is not curently scanning, previous backups have been running flawlessly. Looking at CPU usage dsmsvc is taking 96 MB of memory, which is normal, but the CPU's pegged at 100%. Any ideas other than killing the backup and bouncing the CAD??
thanks everyone!