1 / 18

veeam/blog Twitter : @ RickVanover @BckpAcademy @ Veeam

How to do a backup wrong: Top mistakes. Rick Vanover. MCITP vExpert VCP Veeam Software. http://www.veeam.com/blog Twitter : @ RickVanover @BckpAcademy @ Veeam. About the Speaker. Contributor to industry publications. Agenda. Supportability and platforms

paniz
Télécharger la présentation

veeam/blog Twitter : @ RickVanover @BckpAcademy @ Veeam

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. How to do a backup wrong:Top mistakes Rick Vanover • MCITP vExpert VCP • Veeam Software http://www.veeam.com/blog • Twitter: @RickVanover @BckpAcademy @Veeam

  2. About the Speaker Contributor to industry publications

  3. Agenda • Supportability and platforms • Files, application data and restore expectations • Consistency levels • Missing VMs • Error and warning notification • Capacity calculations • Backup frequency • Wrong type of backup

  4. Supportability • Products usually are matched to a platform • VMware vSphere and Hyper-V have big impact

  5. Platforms and design 57 VMs and growing *MUST* include domain of failure in design of backup for VMs Backup Separate VMEmail Server VMSQL Server VMFileServer VMApplication Server Backup infrastructure vSphere or Hyper-V hosts Storage

  6. Files, application data and expectations • Files may not be enough to satisfy restore requirements • Ensure proper recovery options • Special applications may require special attention • Email systems • Database systems • Web services • Authentication services Backup system Production VMs VMSQL VMAD/DNS VMApp Backups vSphere or Hyper-V

  7. Consistency levels • Different products on different platforms may offer different consistency levels in backups Recommended viewing Elias Khnaser’s session on consistency: “Backing up enterprise applications: Transaction consistency is key” Writers Volume Shadow Copy Service Requestor Provider Disk volume

  8. Missing VMs Age-old problem: New system added, but what about getting it backed up. Does virtualization help this situation?No. It makes it worse Cross-Checkwhat is missing over time with growth

  9. Interactive Demo Datastores, folders, vApps, resource pools in vSphere

  10. Error and alert notification • Nothing worse than going in to do a restore to find that a backup has failed • Ensure alerting and notifications indicate relevant information • What failed (or incurred a warning) • Ensure the right person gets the alert • Alerting versus resolutions • Email, SNMP, pager, logs, reports • This is important if not addressed, retention can be exhausted

  11. “Un-Fixing” problems Sometimes IT pros have to “Make it work” That may mean turning off components that can’t easily be fixed • Don’t throw problems under the rug • Take the time to determine root cause of issues • Learn something from issues to avoid repeat occurrences • Note what you fix and make that available internally for future issues that may come up VMs fail over to healthy host VM VM VM VM VM VM VM VM VM VM VM VM Failed Server Healthy Server Shared Storage for VMs

  12. Capacity calculations Designing a backup solution takes into account a number of metrics: • Storage capacity: tape, disk, cloud, etc. • Retention requirements • Data profile change rate This is a challenge as VMs grow Deduplication can help avoid doing backups wrong Windows Server 2012 can help avoid shortages • Backup performance • Bandwidth

  13. Backup frequency • All VMs are not created equal • Nor are all protection requirements • If multiple frequencies are in use, how do you know which one is best for the situation? • Does the frequency match the needs of the business and applications?

  14. Avoid taking the wrong type of backup There are many types of backups: • Image • File-based backup • Application backup Also avoid the wrong type of snapshot Is a snapshot a backup? No • But, it can be used as part of a backup • Why is this important? Is data backed up – but useless without the application? Example: exclusions, user data and files

  15. Multiple copies of backup • It is always a good idea to have multiple copies of backups: on disk, tape, copy of contents on disk • Layered approach

  16. Over-complicating things Things to over-complicate: • Raw Device Mapping (RDM) • Pass-through storage • iSCSI in-guest • Lack of enlightenment kit • Obsolescence • If virtualization doesn’t need to be complex, don’t make it complex: • Will help backups • Will help troubleshooting • Aid in future changes

  17. What We Covered • Supportability and platforms • Files, application data and restore expectations • Consistency levels • Missing VMs • Error and warning notification • Capacity calculations • Backup frequency • Wrong type of backup

  18. Enjoy and share this material • Feel free to promote this material • Recommend your peers to pass certification • Blog, Tweet and share this material and your experience on Facebook • You’re an Expert? We will be happy to have you as Backup Academy contributor. Apply here. Web: http://www.backupacademy.com E-mail: feedback@backupacademy.com Twitter: BckpAcademy Facebook: backup.academy

More Related