RecoveryOne
ADSM.ORG Senior Member
- Joined
- Mar 15, 2017
- Messages
- 347
- Reaction score
- 81
- Points
- 0
So been giving this one some thought and for the life of me, can't see a way around this.
Situation:
50Tb of data presented as multiple volumes from san to physical Win2k8 server. Volumes will be removed from the 2k8 and presented as rdm to 2016 server inside of VMWare. Not concerned about using TDP to back this up, plan on excluding the disks if they are vrdm, or setting the flag to ignore prdm volumes.
What I'm concerned about is, even if we did the same drive letter and mappings, with the same dsm.opt file copied over and node name from the retired box, this will be in effect a full fresh backup won't it?
Normally I'd not be worried as data reduction would level things out. In this case, no data reduction is being performed. Hits a non deduplicated file pool and migrates off to tape for primary storage. So, I will end up burning a lot of tapes for a new fresh ingest. So much so that I may not have enough scratch. I have a workaround to address that, but would like to avoid if possible.
Thought I'd ask here and see if anyone has any tricks up their sleeves to prevent this from becoming a new 'full'.
Thanks and stay safe out there.
Situation:
50Tb of data presented as multiple volumes from san to physical Win2k8 server. Volumes will be removed from the 2k8 and presented as rdm to 2016 server inside of VMWare. Not concerned about using TDP to back this up, plan on excluding the disks if they are vrdm, or setting the flag to ignore prdm volumes.
What I'm concerned about is, even if we did the same drive letter and mappings, with the same dsm.opt file copied over and node name from the retired box, this will be in effect a full fresh backup won't it?
Normally I'd not be worried as data reduction would level things out. In this case, no data reduction is being performed. Hits a non deduplicated file pool and migrates off to tape for primary storage. So, I will end up burning a lot of tapes for a new fresh ingest. So much so that I may not have enough scratch. I have a workaround to address that, but would like to avoid if possible.
Thought I'd ask here and see if anyone has any tricks up their sleeves to prevent this from becoming a new 'full'.
Thanks and stay safe out there.