obiwan2
ADSM.ORG Member
- Joined
- Dec 8, 2005
- Messages
- 184
- Reaction score
- 0
- Points
- 0
- Location
- Cologne / Germany
- Website
- Visit site
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 !!!!!
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 !!!!!