Comprehensive data protection for all workloads
Post Reply
cag
Enthusiast
Posts: 74
Liked: never
Joined: Mar 26, 2011 4:02 am
Full Name: Conrad Gotzmann
Contact:

Veeam Replication to DR Site.

Post by cag » Apr 21, 2011 2:52 am

I need to get an understanding on how veeam deals with this problem.
Step 1 I am creating to new replica of a single VM. Lets say its 200GB in total disk space.
Lets assume I am set to retain 3 restore points.
Step 2 the second time the replication task run lets say 2 GB change based on CBT (Change Block Tracking)
Step 3 the third time the replication task run lets say 10 GB change based on CBT (Change Block Tracking)
Now what happens when the task runs the forth time and another 5GB changed.
As this process runs over the next 30 days how is the original 200GB consolidated so the next CBT size does'nt get bigger and bigger after the original replication.
I ask this becuase your DR site has limited bandwidth and I cannot complete new replica of the 200GB from scratch via wan.

Vitaliy S.
Product Manager
Posts: 23410
Liked: 1665 times
Joined: Mar 30, 2009 9:13 am
Full Name: Vitaliy Safarov
Contact:

Re: Veeam Replication to DR Site.

Post by Vitaliy S. » Apr 21, 2011 9:44 am

Conrad, each and every time you run an incremental replication pass, all the changes are injected to VM's virtual disk files, all the previous changes are saved to a separate rollback file (VRB).

So what happens on the 4th pass? On the 4th incremental run your main VMs files will be updated with the recent changes, and after that your retention policy settings will be applied, meaning that the 1st pass rollback will be deleted.

Should more info be required, please take a look at our F.A.Q topic.

Thanks.

Post Reply

Who is online

Users browsing this forum: Bing [Bot], DerOest, Google [Bot], Majestic-12 [Bot], tgietz and 65 guests