Slow Restores from Deduplicated Vault

Thread needs solution
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Contributions: 2
Commentaires: 0

I'm running ABR11 and had this problem on ABR10 as well. My average restore times for a large server (300GB) in a vault without deduplication is about 4 hours. To restore the same server from a vault with deduplication, it takes 4 days.

I have disabled deduplication on all of my vaults for now because I can't wait 4 days to restore any server. I have worked with Acronis support for several hours but no luck so far. Has anyone had similar experiences with deduplication restores?

mer 18/04/2012 - 16:08
0 Users found this helpful
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Forum Member
Contributions: 11
Commentaires: 88

What does your storage node look like? how much RAM? How fast is the disk where the dedup data is?
How big is your dedup-database? Is it bigger than your available RAM?
Is the cache hot when you start the restore (i.e. is the StorageServer.exe process really large (7-8G or really small (250M)?

From observation (and numerous debugging session of previous buggybuilds) I know this:
When the Storage Node process starts or has a cold cache (after being idle for a while) it is ridiculously slow. But as it gradually (and slowly) reads in the dedup database into memory, it gets significantly faster. I have backup sets that take 60-90 minutes in the morning (with cold cache) the go down to 8 minutes or less in the afternoon (with a similar set and similar amounts of data).

Did your restore actually take 4 days or did you abort after the estimate told it would take 4 days?
How long does a Validation of the backup in question take?

jeu 19/04/2012 - 18:28