18 Things NOT to do with your vSphere VMs

18 Things NOT to do with your vSphere VMs
Paul.parkin@veeam.com
@Veeam_UKI
IMG_2080.jpg
3-2-1 Rule!!!!
IMG_2081.jpg
When data is office site, how long will it take to come back?
IMG_2082.jpg
Get rid of RDMs (Few use cases for them now)
IMG_2084.jpg
Try to backup less data $$$
IMG_2085.jpg
Beware the HBA when changing versions
IMG_2086.jpg
Upgrade using replication to move from 5.5 to 6
IMG_2087.jpg
What oppertunies are available in v6 and are they available with the current architecture
IMG_2090.jpg
IMG_2089.jpg
Beware the VMware HCL & RTFM!
IMG_2090-(1).jpg
Storage Profiles are highly recommended.
IMG_2091.jpg
* Veeam backs up vCentre VM but enables granular restore of objects, including storage policies
IMG_2091-(1).jpg
Consider what happens to the metadata of a restored vApp.
IMG_2091-(2).jpg
vSphere tags are under utilised in the real world.
IMG_2093.jpg
Restores can make a problem worse.
IMG_2094.jpg IMG_2092.jpg
Don’t backup to much!
IMG_2095.jpg
Backup media and storage bottle necks control restore speed.
IMG_2096.jpg
No offsite copy leads to tears
IMG_2097.jpg
Protect the logs and review what is in them. Part of compliance
IMG_2098.jpg
Consider the ‘cost’ of backups. Normal issue is storage path or total IOPs available
Create a play book of restore options for services.
Veeam 8 has 47 different options for recovering.
Look at VSS 3, storage spaces and Win 2016 for dedupe tech.
FastFSP

2 Responses to “18 Things NOT to do with your vSphere VMs”

Leave a Reply

  • (will not be published)

XHTML: You can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>