or “how not to” backup your virtual infrastructure · upgrade to latest hyper-v version if...
TRANSCRIPT
The worst practices or “how not to” backup your virtual infrastructure
Mikhail Vasiliev
Veeam Systems Engineer
AGENDA
No Planning/Sizing
No Planning/Sizing
Veeam ONE
•
•
•
Retention Doesn’t Work!
More backup files than specified restore points
Make sure you provision repository space accordingly
Forward incremental retention
RETENTION
Retention Issues
SureBackup® sessions that are left running for long periods to perform
some testing on VMs
Instant VM Recovery™ sessions that are not migrated to production
Restore points may be locked by a running session preventing them from being removed
Not Finalizing Instant VM Recovery
VM is running from your backup storage – don’t expect real production performance
Migrate to production as soon as possible. More about ways to do that in the UserGuide
Job Chaining
Longer backup windows in the majority of cases
Administrative error prone
Major protection disruption due to a single problematic job
Doesn’t scale well
Are you sure
you need it?
Job chaining
Unless there is a specific use case, let Veeam do resource
scheduling for you.
Better way to manage resources
One Job to Rule Them All
Reduces scheduling flexibility (especially for active full backups)
Restores from tape will take a long time and require a lot of space on staging repo
Harder to add/relocate repositories
Problems with synthetic/transform jobs on slower NAS boxes
Adding all VMs into a single job
Opposite strategy is not that good either
Hyper-V Issues
Upgrade to latest Hyper-V version if
possible
Install critical Hyper-V hotfixes (we have a KB
for 2008R2 and 2012(R2) hotfixes: vee.am/kb1838)
Use hardware VSS provider and off-host
backup whenever possible
If you have issues with Guest VSS processing in Veeam jobs, check vee.am/kb1855 for a
list of possible reasons
Check with Host OS/Guest OS version compatibility matrix. Microsoft has it all
published on Technet.
What to keep in mind
Not Verifying Your Backups
OS booting issues
Applications and services problems
Multiple interdependent VM configuration scenarios
Things you can’t catch without SureBackup
Slow SureBackup
What Makes SureBackup Go Slowly?
Slow or deduplicating backup storage
Long forward incremental chains
Host starving of resources
Thank you!Open Q&A
Visit go.veeam.com/v9 for more
Mikhail Vasiliev
Systems Engineer
@mmvasilyev