obiwan2
ADSM.ORG Member
- Joined
- Dec 8, 2005
- Messages
- 184
- Reaction score
- 0
- Points
- 0
- Location
- Cologne / Germany
- Website
- Visit site
Hi,
until today we had a Windows Server 2008 R2 Cluster with shared storage. The data of these shares were backed-up by the TSM-client on a daily basis.
Today we switched to a Windows Server 2012 R2 Cluster with new (!) shared storage and all data from the old storage was copied to the new storage using RoboCopy.
I have then done the following:
- I renamed the filespaces in TSM from \\oldclustername\drive$ to \\newclustername\drive$
- I made sure that the TSM Nodenames were equal
In order to prevent a new full backup, the volume ID's of the old shares were transferred to the new system.
Nevertheless, a test with "preview backup {driveletter}" showed that a full backup will be performed!
What must be done to prevent a new full backup ? Is there any chance ?
Thanks
obiwan
until today we had a Windows Server 2008 R2 Cluster with shared storage. The data of these shares were backed-up by the TSM-client on a daily basis.
Today we switched to a Windows Server 2012 R2 Cluster with new (!) shared storage and all data from the old storage was copied to the new storage using RoboCopy.
I have then done the following:
- I renamed the filespaces in TSM from \\oldclustername\drive$ to \\newclustername\drive$
- I made sure that the TSM Nodenames were equal
In order to prevent a new full backup, the volume ID's of the old shares were transferred to the new system.
Nevertheless, a test with "preview backup {driveletter}" showed that a full backup will be performed!
What must be done to prevent a new full backup ? Is there any chance ?
Thanks
obiwan