Thank you for your comment. However, you bring up another question by mentioning that a "node does not equal a system nor a license."
I was wondering if my MS Cluster servers take a "license" for every separate resource I am backing up with a separate schedule/dsm.opt, and therefore a separate node ID? -----Original Message----- From: Seay, Paul [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 24, 2002 3:57 PM To: [EMAIL PROTECTED] Subject: Re: TSM Client Licensing You should be able to register more nodes than you have licenses. The reason is a node does not equal a system nor a license. You can define 10 nodes in your dsm.sys stanzas on one system and that is only one license. To most the license thing is a pain; however, it does help you as a customer stay in compliance. Only you can determine how many places you have the client installed. Paul D. Seay, Jr. Technical Specialist Naptheon Inc. 757-688-8180 -----Original Message----- From: Jon Adams [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 24, 2002 6:40 PM To: [EMAIL PROTECTED] Subject: TSM Client Licensing Hello everyone, Can anyone confirm that if your TSM server is not quite current on client licensing (the request just went up to Purchasing), nodes can still be created, associated and backed up or restored, though the server license compliance status states "failed"? Are there ANY issues other than a status message, that we should be aware of? In advance, thank you for your comments. ____________________________________________ Jon R. Adams IT IPS BST Infrastructure Premera Blue Cross Mountlake Terrace, WA 425-670-5770 [EMAIL PROTECTED]
