From The Field Series – Veeam v6 Replication
This is the start of a “from the field” (FTF) series of blog posts based on the common considerations and scenarios I’ve run into while helping customers and partners designing, implementing, and evaluating host based replication for disaster recovery and business continuity. Veeam v6 is an awesome and cost effective solution that many companies have implemented, but there are several outside factors in a virtual datacenter that will directly impact the speed, efficiency, reliability and success of replication jobs. So, over the next couple of weeks I will be adding posts exploring the various factors that, in my experience, greatly impact a host based replication solution.
This series will not contain technical answers, official best practices, or “how to” steps on designing a Veeam Replication solution. The series will attempt to make virtualization admins think about their virtual infrastructure architecture, the virtual machines, and suggest what might need to be modified to maximize host-based replication. I will try to cover the topics from both the vSphere and Hyper-V perspective.
If you need more technical details, information about Veeam features, or help with the “how to” on any of the topics covered please contact your regional Veeam Engineer or your Veeam Partner / Valued Added Reseller.
Here is my outline of posts to come in the FTF Veeam Replication series:
Phased Implementation Methodology (link)
- Phase 1 (2 weeks) – Install, configure, and get jobs running
- Phase 2 (2 weeks) – The 80-20 VM(s) Adjustment
- Phase 3 (1 week) – Final Tweaks
- Ongoing monitoring (forever!)
Optimizing Snapshots (link)
If you are planning on replicating VMware VMs then you have to be able to create and commit healthy VMware snapshots before you ever introduce Veeam in your environment.
Veeam Architecture (link)
- Proxies – where and why
- DNS and Permissions
- Where to install the Veeam Server?
- Concurrent Jobs (or Tasks)
Applications in the VMs (link)
- Agentless options is Windows VMs
- Agentless options in Linux VMs
- VM cluster nodes
- Should you truncate logs for replication jobs?
CBT and VM data rate of change
Once Veeam establishes a full replica of your VM on the target datastore it will only replicate changed blocks. How many changed blocks each job run depends on each VM’s personality.
Replication and Network Physics
Veeam can help a little by throttling itself, but the replica data has to be sent across your WAN!
- ESX Versions
- Upgrades and the API
- Backup Repository for Replication
- Building jobs
- Datastore space at the target site
The information provided in this series is not necessarily supported or endorsed by Veeam software. This series is based solely on my experience and ideas. FWIW I have been acredited as a VMSP and VMTSP, and certified as a Backup Expert by the Backup Academy.
I’ll expand on the topics in each post! Once a post is published I will add links to it here. This post then becomes a table of contents for the series.
Let me know in the comments if there is something else you would like to see covered.
[ad] Empty ad slot (#1)!