Comprehensive data protection for all workloads
Post Reply
rizks_2000
Enthusiast
Posts: 77
Liked: never
Joined: Feb 17, 2010 1:12 am
Full Name: Anthony Rizk
Contact:

Actual vs. Estimated - 60GB to 72GB

Post by rizks_2000 »

When setting up a replica job, the actual size is 60GB and then Veeam Backup is adding 20% to that for their estimated space usage. It actually does this on all jobs? Why? Seems like a high amount of storage overhead. I can see a small tad more, but why 20%?
Gostev
Chief Product Officer
Posts: 31457
Liked: 6647 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland
Contact:

Re: Actual vs. Estimated - 60GB to 72GB

Post by Gostev »

Anthony, we assume daily replicas and and amount of changes equal to 10% of VMDK size. This is the estimation formula current product version is using.
rizks_2000
Enthusiast
Posts: 77
Liked: never
Joined: Feb 17, 2010 1:12 am
Full Name: Anthony Rizk
Contact:

Re: Actual vs. Estimated - 60GB to 72GB

Post by rizks_2000 »

so it is actually estimating and provisioning for future differential replica jobs then?
Gostev
Chief Product Officer
Posts: 31457
Liked: 6647 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland
Contact:

Re: Actual vs. Estimated - 60GB to 72GB

Post by Gostev »

Yes, this additional space to host those VRB files (reversed incrementals) to enable failover to earlier point in time in cases of software corruption or virus.
Gostev
Chief Product Officer
Posts: 31457
Liked: 6647 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland
Contact:

Re: Actual vs. Estimated - 60GB to 72GB

Post by Gostev »

I am actually thinking on changing 10% to 5% in the next release. Per feedback real average is about 2% daily across most VMs, so 5% might be better for most cases (except Exchange and SQL which can produce up to 30% daily disk changed due to transaction logs, but 10% is not good for this either, anyway)
Post Reply

Who is online

Users browsing this forum: Achraf, Semrush [Bot] and 155 guests