I ran into a problem where the client gave errors on the drives that were
in the cluster, but not present on the particular node the backup was
running on.

In that case it was on a polyserve cluster, and polyserve wasn't (still
isn't?)  formally supported by TSM.

A solution was to write a script on the client that only checked for
success on the truly local drives, and call this script as a command
schedule.

[RC]



From:   Rick Adamson <RickAdamson AT WINN-DIXIE DOT COM>
To:     ADSM-L AT VM.MARIST DOT EDU
Date:   04/26/2011 08:08 AM
Subject:        [ADSM-L] ANS1071E Invalid domain name entered: (Drive Not
Available)
Sent by:        "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>



We have a Windows 2003 R2 client using TSM BA 5.5.3.3. (TSM server
5.5.5.2.)



When the scheduled backup runs an error is posted; ANS1071E Invalid
domain name entered: '(Drive Not Available). As per disk management the
client has a C,D, and G drive, which all seem to be backing up
correctly. Checking in the Disk Management utility it only lists the C,
D, G, (and CD drive). Checking the windows registry under
HKLM\SYSTEM\MountedDevices there are numerous drive GUIDS and letters
listed that do not exist but I assume are user mappings.



However, if I open the GUI and attempt a manual backup and expand
"Local" the C, D, G drives are listed as well as 4 entries that state
"Drive not Available"



Since there are no Domain statements defined for the client "all local"
is applied by default.



Has anyone run into this before, and where exactly does the BA client
get the "All Local" drive information to determine what it needs to
backup?

Is there a way to reset and/or remove the erroneous drive listing?



Appreciate any insight you can share....

TIA



   Rick Adamson

  Jacksonville, FL


U.S. BANCORP made the following annotations
---------------------------------------------------------------------
Electronic Privacy Notice. This e-mail, and any attachments, contains 
information that is, or may be, covered by electronic communications privacy 
laws, and is also confidential and proprietary in nature. If you are not the 
intended recipient, please be advised that you are legally prohibited from 
retaining, using, copying, distributing, or otherwise disclosing this 
information in any manner. Instead, please reply to the sender that you have 
received this communication in error, and then immediately delete it. Thank you 
in advance for your cooperation.



---------------------------------------------------------------------