dlemieux33
ADSM.ORG Member
We've had to temporarily stop the expiration of our exchange backups. We Will be resuming a 28day expiration cycle on the new backups, while we still retain the old under a "forever" policy.
We run TDP for exchange ver 5.4. TSM server is at 5.5.1.
The exchange server is 5.02 and is clustered.
I have considered renaming the node which would keep that data intact. This would allow for continued access by the client node, with only changes at the TSM server. But I'm not comfortable about the restore process if they need to access this old data. Has anyone performed a restore of exchange data using this method?
What's my best option?
Is renaming the filespaces within the existing node an option? I must not lose this data.
I thought about getting a backupset but read where tsm 5.5.1 does not support that for TDP for EXCHANGE.
We run TDP for exchange ver 5.4. TSM server is at 5.5.1.
The exchange server is 5.02 and is clustered.
I have considered renaming the node which would keep that data intact. This would allow for continued access by the client node, with only changes at the TSM server. But I'm not comfortable about the restore process if they need to access this old data. Has anyone performed a restore of exchange data using this method?
What's my best option?
Is renaming the filespaces within the existing node an option? I must not lose this data.
I thought about getting a backupset but read where tsm 5.5.1 does not support that for TDP for EXCHANGE.
