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.

Moving TSM-Backup and all its data from one Cluster to an other Cluster

Discussion in 'TSM Client' started by obiwan2, Jul 23, 2012.

  1. obiwan2

    obiwan2 New Member

    Joined:
    Dec 8, 2005
    Messages:
    125
    Likes Received:
    0
    Location:
    Cologne / Germany
    Hi Guys,

    I have a very "nice" problem and I really need your help ....

    The situation:
    - we had an "old" Windows-Clustersystem (Windows Server 2000)
    - the data was held on an Enterprise Virtual Array (EVA)
    - TSM-Nodename: CLUSTERA
    - Domain: G:
    - the filespace was \\clustera\g$

    Now comes the NEW Cluster:
    - the new Windows-Clustersystem is a Windows Server 2008 R2 Enterprise System
    - the data is now held on a NEW EVA-System, but was copied with a tool called FastCopy (equ. to RoboCopy)
    - TSM-Nodename: CLUSTERB
    - Domain: F:

    To keep the old backupdata (with all the versions of backupfiles) I did the following:
    1. renamed CLUSTERA to CLUSTERA-OLD
    2. renamed CLUSTERB to CLUSTERA
    3. renamed \\clustera-old\g$ to \\clustera\f$
    4. changed the old "domain G:" to "domain F:" in the dsm.opt for the clusternode
    5. changed all paths to logfiles etc. in the dsm.opt for the clusternode

    After starting the dsmcad and the scheduler by switching to "online" in the cluster-admin all things seemed to be ok !!!
    BUT.........one day later I could see the following results (for example):
    3511.snd 27,65 MB Backed Up 06/06/2007 (therefore an inactive version)
    3511.snd 27,65 MB Backed Up 07/23/2012 (as it is on the EVA-system...the active version)

    3512.snd 7,14 MB Backed Up 06/06/2007
    3512.snd 7,14 MB Backed Up 07/23/2012

    and so on.......and so on.
    Nearly every file (!) is now backed up again ... although it already exists in the backup !!!

    Were the steps that I've done ok or is there a mistake ???

    Thanks for any hint !!!!!
     
  2.  
  3. inestler

    inestler Member

    Joined:
    Mar 12, 2007
    Messages:
    151
    Likes Received:
    7
    Location:
    switzerland
    which file flags did you copy with FastCopy?
     
  4. obiwan2

    obiwan2 New Member

    Joined:
    Dec 8, 2005
    Messages:
    125
    Likes Received:
    0
    Location:
    Cologne / Germany
    All of them....
    -------------------------------------------------------
    Just an idea: Is the reason -MAYBE- the new domain F: ?

    If the old HL_NAME was G:\35xx and --due to using the new domain-statement-- the new HL_NAME is now F:\35xx, then the reason is -in my opinion- absolutely clear ! Then it's a new drive that TSM was never known....
     
  5. inestler

    inestler Member

    Joined:
    Mar 12, 2007
    Messages:
    151
    Likes Received:
    7
    Location:
    switzerland
    you are absolutely right
     
  6. obiwan2

    obiwan2 New Member

    Joined:
    Dec 8, 2005
    Messages:
    125
    Likes Received:
    0
    Location:
    Cologne / Germany
    Thank you !!

    I thought as much ! But I wasn't absolutely sure ... now I am !
     
  7. szwkrz

    szwkrz New Member

    Joined:
    Sep 25, 2008
    Messages:
    1
    Likes Received:
    0
    Hi

    We have a similar situation where we are moving our data from one array to another array and will be presented to the same host with the same mount point, will this force TSM to trigger a full backup or will it just continue running incremental backups ??
     

Share This Page