- Posts: 3
- Liked: never
- Joined: Nov 05, 2009 3:11 am
- Full Name: David Moylan
I have in other deployments used Veeam Replication which works fine, but in this instance I have no ESX server at the other end. I wish to just use the backup side of things this time. I plan to do the first backup with the storage locally and then use the change block tracking for continued backups.
What I wanted to validate was
(a) will this work as I expect it should?
(b) am I able to take advantage of de-dup, or will this not be possible due to large amounts of comparitive traffic going across the wan link? (ie: does veeam keep information about the remote storage blocks in its local database? or does it query the backup image when performing the de-dup during the next server backup?)
many thanks in advance
- Product Manager
- Posts: 24920
- Liked: 2104 times
- Joined: Mar 30, 2009 9:13 am
- Full Name: Vitaliy Safarov
Basically, you can leverage all the benefits of changed block tracking feature over WAN link if your virtual infrastructure meets the following requirements: Setting Up Changed Block Tracking. If you want to perform a backup job over a WAN link, you surely can store the backups locally (as it will be your first run, you'll have only a VBK file presented), then move them to remote storage and change the destination target on existing jobs.
As for the de-duplication, as you already know it works within the job. See the Best Setup For De-Dup, and all the information on de-duplicated blocks is stored in VBK (storage format), for ex. we will require only 3 mb of traffic to be transmitted over WAN for 200 GB deduped blocks (approx.), so definitely it is worth using. Also don't forget about compression options
Also please have a look at Design Recommendations Hope it helps.