1. Forum Rules (PLEASE CLICK HERE TO READ BEFORE POSTING) Click the link to access ADSM.ORG Acceptable Use Policy and forum rules which should be observed when using this website. Violators may be banned from this website. This message will disappear after you have made at least 12 posts. Thank you for your cooperation.

Local Disks now Showing up as Cluster Disks

Discussion in 'Backup / Archive Discussion' started by rtiebout, Jun 29, 2009.

  1. rtiebout

    rtiebout New Member

    Joined:
    Jul 9, 2008
    Messages:
    21
    Likes Received:
    0
    The physical nodes of our cluster just started reporting that they couldn't backup the local disks anymore. After looking into it the dsmerror logs show that the disks are now seen as \\clustername\c$ and are cluster disks and can't back them up with the clusternode option set to yes. those same disks used to be \\hostname\c$ and were backing up just fine for a long time.
    What has changed? i've upgraded the client versions and am now running 5.5.1.16
    I can get the backups to run if i set the physical nodes dsm.opt option for being a clusternode but then all of the filespaces will be named incorrectly. Any help would be greatly appreciated.

    Thanks.
     
  2.  
  3. Eldoraan

    Eldoraan Senior Member

    Joined:
    Feb 19, 2003
    Messages:
    288
    Likes Received:
    10
    Occupation:
    Data Protection
    Location:
    Charlotte, NC
    I would assume someone shared the C: out via SMB and now the client sees it as a shared resource on cluster. Do you use domain statements in your dsm.opt files? It's best to lock down Windows cluster configs so that a "E:\TSM\dsm.opt" file on a cluster resource with E: as member only backs up the E: drive. So "Domain E:" in that dsm.opt file will tell TSM to only backup the E: drive and nothing else.
     
  4. JohanW

    JohanW Moderator

    Joined:
    Nov 12, 2006
    Messages:
    986
    Likes Received:
    14
    Occupation:
    sysadmin
    Location:
    Netherlands
    What was your previous client version? If it was old enough, the configuration may have to be done again, including the cluster service configuration (you do have the CAD, scheduler &c. configured as cluster resources, don't you?), because the location for certain things in the registry has changed.

    Check the appropriate version of the manual for cluster configuration, esp. the Registry Replication, and check everything.
     
  5. JohanW

    JohanW Moderator

    Joined:
    Nov 12, 2006
    Messages:
    986
    Likes Received:
    14
    Occupation:
    sysadmin
    Location:
    Netherlands
    That's normal in a cluster, and I can only hope everyone already has it configured that way. :up:
    And this is absolutely NOT normal, and I should hope nobody does this. :eek:

    OP, if so, please let us know. I'm not about to test for this effect myself .. :D
     
  6. rtiebout

    rtiebout New Member

    Joined:
    Jul 9, 2008
    Messages:
    21
    Likes Received:
    0
    We do use the DOMAIN statement to make sure that the cluster resources only back up their own drives.
    I'll check on the sharing of the local drives but other than the default admin shares there shouldn't have been any other cluster shares created for those drives.
    My previous client version was 5.3.0.5 What is the best way to upgrade the tsm clients? cluster or otherwise. Should i uninstall the client then install the new one? Which registry locations have changed?
     
  7. JohanW

    JohanW Moderator

    Joined:
    Nov 12, 2006
    Messages:
    986
    Likes Received:
    14
    Occupation:
    sysadmin
    Location:
    Netherlands
    No need to uninstall, as far as I've found. Changes for all versions are documented here.
    This may or may not affect cluster resources, so give it a gander.
     
  8. rtiebout

    rtiebout New Member

    Joined:
    Jul 9, 2008
    Messages:
    21
    Likes Received:
    0
    After speaking with TSM support and searching the web we came up with a Microsoft HotFix that seemed to fit this issue. And after applying the hotfix the local disks are now seen by TSM as beeing local to the system and no longer cluster disks.
    Here is the microsoft hotfix page: http://support.microsoft.com/kb/928385
    Thanks for all the help.
     

Share This Page