why don't you take a look from another point of view?
what is the real purpose of your exchange backup?
- restores of single items?
- restore of exchange in case of disaster?
- resore of exchange data in case of disaster?
-other?
when the above question is answered, you can design a backup solution that meets your requirements.
All of these points have been addressed. We did have a disaster a couple of months ago and the backup worked fine. This is not the question I'm having here.
My question is more related to the fact that : The space we are saving in the deduplication storage for the exchange backup ,is it worth more than the long time it take to duplicate the backup to the tape drive. Or vice versa, would it be more efficient to store the exchange backup in a simple disk storage (and taking more space for the backup) to be able to duplicate it faster to a tape drive.
Is it possible to get the efficiency ratio of the compression of the exchange backup only in the deduplication storage? Having this info would help me make a better decision.
Isn't the deduplication ratio provided in the job log of the Exchange backup to deduplication?
The only info I can find in the log is this :
Job Log: BEX_73843.xml Backed up 1 Exchange Server stores Backed up 8374 Exchange Server logs Processed 226122151046 bytes in 1 hour, 12 minutes, and 7 seconds. Throughput rate: 2990 MB/min
I can't find any info regarding the ratio compression per job/server, only per dedup store.
