Deduplication Best Practices Question
When looking at the Best Practices for DeDupe in R3 I came across a line that reads:
Perform a duplicate backup job so that you have redundant backups of the data in your deduplication storage folder. This method is preferred over performing full backups using the deduplication writer because this method is easier to control.
Can someone explain what this means?
Currently I am running a full to the dedupe folder every month (takes around 2-3 days to run for 2-3TB) and I run daily incrementals.
If you are going to do that, which is a PITA... I would suggest then, B2D with retention that allows you to get it to tape. I would also duplicate the B2D to the dedupe folder, with the dedupe folder having a retention that is longer than the initial B2D. Thats the beauty of deduplication, store more in less space, thus more full backups on disk for quick recovery.
So Backup to disk, 2-3 day retention
Duplicate to dedupe folder with 30 day retention
duplicate from initial B2D to tape with longer retention as business requirements dictate.
I don't see a reason why you would even bother with incrementals to the dedupe folder, without the fulls. The fulls benefit the most, not the incrementals.