Not only is it not right that it gave a "Completed" message, it's also not right that dsmcad.nlm will even load without the TSA's being loaded first. I've done that a couple times also, although I'm just used to checking for the TSA's right away now.
Troy Frank Network Services University of Wisconsin Medical Foundation 608.829.5384 >>> [EMAIL PROTECTED] 8/25/2004 4:16:10 PM >>> It's actually Netware 6.0 and turns out that the problem is that the TSA600.NLM wasn't loaded. There were errors all over the DSMERROR.LOG and DSMSCHED.LOG files, nothing was backed up, but the client still notified the TSM server that the event completed successfully. That just plain isn't right! I am still waiting to hear back on my PMR with Tivoli support. Bill -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Richard van Denzel Sent: Wednesday, August 25, 2004 10:25 AM To: [EMAIL PROTECTED] Subject: Re: Problems with Netware 5.6 backups Yeah, but like Mark said, don't always believe the client. What does de NW server itself report about the OS version? Richard. Bill Boyer < [EMAIL PROTECTED] > Sent by: "ADSM: Dist Stor Manager" < [EMAIL PROTECTED] > 25-08-2004 16:14 Please respond to "ADSM: Dist Stor Manager" To: [EMAIL PROTECTED] cc: Subject: Re: Problems with Netware 5.6 backups Nope: tsm: CCPTSM>q no academic1 f=d Node Name: ACADEMIC1 Platform: NetWare Client OS Level: 5.60 Client Version: Version 5, Release 1, Level 6.6 Policy Domain Name: STANDARD Last Access Date/Time: 08/25/2004 10:15:46 Days Since Last Access: <1 Password Set Date/Time: 08/13/2003 09:54:07 Days Since Password Set: 378 Invalid Sign-on Count: 0 Locked?: No Contact: Compression: Client Archive Delete Allowed?: Yes Backup Delete Allowed?: No Registration Date/Time: 08/13/2003 09:54:07 Registering Administrator: WBOYER Last Communication Method Used: Tcp/Ip Bytes Received Last Session: 6,909.33 M Bytes Sent Last Session: 66.00 M Duration of Last Session: 2,531.00 Pct. Idle Wait Last Session: 14.42 Pct. Comm. Wait Last Session: 42.51 Pct. Media Wait Last Session: 0.00 Optionset: NETWARE URL: http:\\10.1.48.45:1581 Node Type: Client Password Expiration Period: Keep Mount Point?: No Maximum Mount Points Allowed: 1 Auto Filespace Rename : No Validate Protocol: No TCP/IP Name: ACADEMIC1 TCP/IP Address: 10.1.48.45 Globally Unique ID: -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Richard van Denzel Sent: Wednesday, August 25, 2004 9:55 AM To: [EMAIL PROTECTED] Subject: Re: Problems with Netware 5.6 backups Bill, You'll probably mean Netware 6.5? Richard. Bill Boyer < [EMAIL PROTECTED] > Sent by: "ADSM: Dist Stor Manager" < [EMAIL PROTECTED] > 25-08-2004 15:59 Please respond to "ADSM: Dist Stor Manager" To: [EMAIL PROTECTED] cc: Subject: Problems with Netware 5.6 backups TSM Server 5.1.7.1 on Windows2000 TSM 5.1.6.6 on Netware 5.6 servers I have found several Netware 5.6 servers that are completing the backup events successfully, but no data is backed up. The event is marked complete, but there are no end of backup statistics in the activity log. In one case a Netware 5.6 server is issueing lots of ANR0484W Protocol Violation errors, the schedule is marked complete, no ending statistics and all the filespaces for that node do not show a current backup completiong date. Now that I start looking, I see several of the Netware servers having this problem. We're using the TSM Operational Reporter for notifications and when it doesn't flag events as missed or failed, we assume good backups. That's doesn't appear to be the case. Anyone out there doing Netware 5.6 server backups running into problems like this? I've opened a PMR, and am waiting to hear back. Bill Boyer "An Optimist is just a pessimist with no job experience." - Scott Adams Confidentiality Notice follows: The information in this message (and the documents attached to it, if any) is confidential and may be legally privileged. It is intended solely for the addressee. Access to this message by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken, or omitted to be taken in reliance on it is prohibited and may be unlawful. If you have received this message in error, please delete all electronic copies of this message (and the documents attached to it, if any), destroy any hard copies you may have created and notify me immediately by replying to this email. Thank you.
