Whitepaper
April 6, 2021
10 Best Practices for VMware vSphere Backups
Register to Read
Verify your email to continue your product download
We've sent a verification code to:
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Start using Veeam:
Download the product
&
Activate the license key
- Resource Library
- Whitepapers
- 10 Best Practices for VMware vSphere Backup
To maintain service levels, performance and availability, backup and recovery of virtual machines (VMs) on vSphere is fundamental to avoiding and minimizing outages.
The most important general best practice for backups is the 3-2-1 Rule. This means having at least three copies of your data, including a first and second line of backup.
The first and most important thing to do before planning or implementing any solution is to be certain about its requirements. In an ideal world, the business will create the requirements and tell IT which recovery point objective (RPO) and recovery time objective (RTO) is needed.
With this information, it is possible to better size the required hardware. That includes the number of CPU cores and the amount of memory and bandwidth requirements for WAN, LAN and SAN.
Finally, you need a source and backup storage that is fast enough to achieve the required speed. The next step is the backup itself.
Best practices for VMware backup include:
No. 1: Use current versions of Veeam and vSphere
No. 2: Choose your backup mode wisely
No. 3: Plan how to restore
No. 4: Integrate Veeam Continuous Data Protection into your disaster recovery concept
No. 5: Install VMware tools
No. 6: Integrate storage-based snapshots into your backup concept
No. 7: VMware vSAN backup
No. 8: Security
No. 9: Plan your Veeam Backup & Replication deployment with Veeam ONE
No. 10: Application-aware backup via VIX API
Download the full version to learn more about each of these best practices!
The most important general best practice for backups is the 3-2-1 Rule. This means having at least three copies of your data, including a first and second line of backup.
The first and most important thing to do before planning or implementing any solution is to be certain about its requirements. In an ideal world, the business will create the requirements and tell IT which recovery point objective (RPO) and recovery time objective (RTO) is needed.
With this information, it is possible to better size the required hardware. That includes the number of CPU cores and the amount of memory and bandwidth requirements for WAN, LAN and SAN.
Finally, you need a source and backup storage that is fast enough to achieve the required speed. The next step is the backup itself.
Best practices for VMware backup include:
No. 1: Use current versions of Veeam and vSphere
No. 2: Choose your backup mode wisely
No. 3: Plan how to restore
No. 4: Integrate Veeam Continuous Data Protection into your disaster recovery concept
No. 5: Install VMware tools
No. 6: Integrate storage-based snapshots into your backup concept
No. 7: VMware vSAN backup
No. 8: Security
No. 9: Plan your Veeam Backup & Replication deployment with Veeam ONE
No. 10: Application-aware backup via VIX API
Download the full version to learn more about each of these best practices!
About the Author
Hannes Kasparick
Principal Analyst, Product Management, Veeam Software
Principal Analyst, Product Management, Veeam Software
Hannes Kasparick has been working in the IT business since 2004. Today, Hannes is a member of the Veeam Product Management team. In the past he managed Linux and Windows environments, as well as infrastructure services like servers, storage, network and firewalls.