Appliance MSDP/ Capacity Managed Retention
Yeah, why you want to have 2 copies on the same appliance?
With MSDP as first backuptarget you can benefit from accelerator and client-side-deduplication.
With clients side dedup I had less then 50% of time for a complete restore. (testet with 3 TB redirected restore on a new installed client)
Duplication to tape will be a little faster from adv , but this should not be so important.
There is no capacity managed retention for msdp. I wount work. It will take a couple of hours from expiration of images and have more free space on msdp.
In a Windows environment our dedup rates are beetwen 75 and over 95 %. Depending of kind of data. Compessed SQL backups and outlook pst files are bad for deduplication.
ciao
Martin
No, the deduplication engine will not get backlogged if you send the information directly to it. You just need to manage the amount of streams you are sending to the appliance at once. Start with less streams and work your way up until performance starts to drop, then go back down to the level where you had the most streams and best performance. Keep in mind that if you are duplicating the data from MSDP to tape, you will want to run those when no backup jobs are running, or limit them to 2-4 at a time. They need to rehydrate the data which generally takes a decent amount of resources and affects performance.
And as Martin pointed out, going to MSDP would allow you to use Accelerator and Clientside dedup (depending on the policy type), which work very well together to shorten the amount of time and space used for future operations.
And yes, you can allocate all of the space to MSDP. We have 2 - 5330s that are fully allocated for MSDP, except for a small AdvancedDisk pool for testing.
You are correct though in your assumption that databases generally do not dedup well... But in my opinion, the pros still outweigh the cons for going directly to MSDP first. The only way to know what is best for your environment would be to test both.
Regards,
Tyler
