Enabling Windows 2012R2 deduplication on a file server will impact the size of the incremental replication jobs. A 2.5Tb file server has replicated happily for a week or so taking anywhere from 20-60 min on average and then today veeam believes everything has changed thus kicking off a large incremental replication. At this rate, it will take about 36 hours to replicate. What are our options in this scenario? Obviously, we want to take advantage of deduplication of our file servers, however, we also want to replicate. Recommendations?
Thanks
-
- Enthusiast
- Posts: 25
- Liked: 3 times
- Joined: Mar 12, 2012 3:10 am
- Full Name: Jay
- Location: Cincinnati, OH
- Contact:
-
- Product Manager
- Posts: 20406
- Liked: 2299 times
- Joined: Oct 26, 2012 3:28 pm
- Full Name: Vladimir Eremin
- Contact:
Re: Replicating a deduplicated file server
Mostly likely, garbage collection or other regular deduplication activity happened, which resulted in high amount of changed blocks.A 2.5Tb file server has replicated happily for a week or so taking anywhere from 20-60 min on average and then today veeam believes everything has changed thus kicking off a large incremental replication
That's expected behaviour. Working on image level, VB&R concerns only with changed blocks and usage of in-guest deduplication leads to high amount of changed blocks.Enabling Windows 2012R2 deduplication on a file server will impact the size of the incremental replication jobs.
Thanks.
Who is online
Users browsing this forum: billy.tsang, Majestic-12 [Bot] and 265 guests