Hi Andy! Thank you very much for your reply! We tried the circumvention which is listed in the APAR, but that doesn't work. We then installed the 5.3.0 client and now the D: drive is seen correctly. However, we can't use this client level: our server is down-leveled for system state backup and we can't upgrade our server (AIX 4.3.3) yet. The APAR mentions the levels affected are 5.2.2 and 5.2.3. I see the same bug in the 5.1.7 client. Can we expect this fix for 5.1.8 too? Thank you very much for your reply in advance! Kindest regards, Eric van Loon KLM Royal Dutch Airlines
-----Original Message----- From: Andrew Raibeck [mailto:[EMAIL PROTECTED] Sent: Monday, January 24, 2005 21:45 To: ADSM-L@VM.MARIST.EDU Subject: Fw: TSM thinks local disk is a cluster disk Eric, I forgot to mention... this is already fixed in 5.3.0. Regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] The only dumb question is the one that goes unasked. The command line is your friend. "Good enough" is the enemy of excellence. ----- Forwarded by Andrew Raibeck/Tucson/IBM on 2005-01-24 13:43 ----- Andrew Raibeck/Tucson/IBM 2005-01-24 08:22 To "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> cc Subject Re: TSM thinks local disk is a cluster disk I suspect IC42268. The APAR description includes a circumvention. Regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] The only dumb question is the one that goes unasked. The command line is your friend. "Good enough" is the enemy of excellence. "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> wrote on 2005-01-24 05:11:45: > Hi *SM-ers! > Our Windows guys discovered that one of their nodes was missing a drive > backup. Drive D: was skipped during backup. > The altered the dsm.opt and added D: to the domain statement. This resulted > in the following error: > > ANS1228E Sending of object '\\kl10116j\d$' failed > ANS1153E Drive : is a cluster disk. > Not valid for backup/archive when CLUSTERNODE option is NO. > > Drive D: however is not a cluster drive, it's a local harddisk! > Does anybody know what's going wrong here? > Kindest regards, > Eric van Loon > KLM Royal Dutch Airlines > > > ********************************************************************** > For information, services and offers, please visit our web site: > http://www.klm.com. This e-mail and any attachment may contain > confidential and privileged material intended for the addressee > only. If you are not the addressee, you are notified that no part of > the e-mail or any attachment may be disclosed, copied or > distributed, and that any other action related to this e-mail or > attachment is strictly prohibited, and may be unlawful. If you have > received this e-mail by error, please notify the sender immediately > by return e-mail, and delete this message. Koninklijke Luchtvaart > Maatschappij NV (KLM), its subsidiaries and/or its employees shall > not be liable for the incorrect or incomplete transmission of this > e-mail or any attachments, nor responsible for any delay in receipt. > ********************************************************************** ********************************************************************** For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. **********************************************************************
