Download
slide1 n.
Skip this Video
Loading SlideShow in 5 Seconds..
Instructor - Allan Ackerman VCA-DCV & VCP5-DCV PowerPoint Presentation
Download Presentation
Instructor - Allan Ackerman VCA-DCV & VCP5-DCV

Instructor - Allan Ackerman VCA-DCV & VCP5-DCV

335 Views Download Presentation
Download Presentation

Instructor - Allan Ackerman VCA-DCV & VCP5-DCV

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. CIT 198 Week#10Module 8 from the eBook - VDPSybexChapter#8Creating and configuring VMware Clusters Instructor - Allan Ackerman VCA-DCV & VCP5-DCV Click the graphic for assessment

  2. This week our objectives will be • Complete labs 13 & 14 from the NDG/Cisco • Complete labs 21, 22, 23 on the in-class virtual lab. • In chapter 8 of the Sybex book we will be covering creating and configuring VMware clusters • In chapter 8 of the eBook we will be covering VMware Data Protection - VDP. • There are no NDG nor in-class labs on the VDP appliance as you need a fair amount of disk storage. If you have an extra TB drive at home I recommend you set it up there and give it a try. Our lecture experience will be - just to talk about VDP and not do it. So today’s lecture will be short. • Next week’s quiz will be 80% from the Sybex book chapter 8 plus tonight’s labs and 20% from the eBook on VDP. Week#10 vSphere 5.1 & 5.5

  3. Important classroom info for the week of April 1 • Our quiz scores are better this weekand we are getting better each week. • The midterm exam average was 79% • 7 people in the class have already taken and passed their VCP-DCV exam - congratulations. • We have a huge amount of lab work for our week#10 session. So our lecture will be short tonight - so we can get the labs done. • First do NDG labs 13 &14. • In-class lab 21 will be a reinstall of vSphere 5.5 as our free 60 day eval is about to expire. This time around, however, the vSphere c# client will not be used. Only the web client will be used for the whole configuration. Week#10 vSphere 5.1 & 5.5

  4. Overview of this week’s labsin-class lab#21 • We will probably see this error tonight when we log in – if not you will be very close to this point. • So we are going to do a reinstall of vSphere 5.5 and this time the c# client will be outlawed – only the web client will be used. Week#10 vSphere 5.1 & 5.5

  5. In-class lab#21 • Good news – the installation will not take 3 weeks like before but only a couple of hours to get a total reinstall of our virtual datacenter. • To begin - uninstall the following programs – all of the fifteen programs listed below -- Week#10 vSphere 5.1 & 5.5

  6. Our in-class lab#21 • Next power down your esxi1 and esxi2 host. • Edit the settings to boot to the hypervisor installation ISO. • Power on the ESXi hosts and reinstall a new image on top of the old virtual machine. • This install will be almost like lab 5, but we will select the option - Install ESXi, overwrite the VMFS datastore. • Reconfigure your ESXi hosts just like in lab 5 • You will constantly have to go back to labs 4-10 to get our in-class configuration settings as we do lab 21. Week#10 vSphere 5.1 & 5.5

  7. Our in-class lab#21 After ESXi1 and ESXi2 are installed, setup their configuration settings to be: • 192.168.246.21/24 and 192.168.246.22/24. • Set your domain name to be vita.local • Set your default gateway to be 192.168.246.2 • Set your DNS server to be 192.168.246.19 • Make sure you test your network settings – when they test out OK go to the next step. If they do not test out OK call over your instructor. Week#10 vSphere 5.1 & 5.5

  8. Our in-class lab#21 • Go back to vc.vita.local. • Launch the vSphere 5.5 installation ISO. • Install vSphere 5.5 just like we did in previous labs. The only difference will be when it says keep my existing database – we will not select that option but select Replace my existing database with an empty one. This will happen when we are installing the Inventory Service. • Next fire up the web client and do all the configuration settings that we did in our previous labs, but this time just use the web client. The differences are outlined fairly well in the lab 21 write-up. Week#10 vSphere 5.1 & 5.5

  9. Our in-class lab#21 • Remember nested virtualization works, but it is an unsupported configuration in VMware. • I did lab 21 on my AMD 8350 CPU with the web client on March 30, 2014 and the web client locked up three times when I was configuring the iSCSI Starwind drives. • I just had to reboot and continue on with my configuration. I was able to complete the whole configuration with the web client. • Stay away from any link that says advanced when configuring your iSCSI or NFS datastores with the web client. Week#10 vSphere 5.1 & 5.5

  10. Our in-class lab#21 • Remember the only time I had trouble with the Web client was with configuring the iSCSI Starwind drives. • Hopefully our in-class virtual lab with a Intel I7 processors will not have any trouble configuring the Starwind iSCSI drives – tonight’s lab will be the test. • Remember I used an AMD processor – hoping that was the cause of my three lockups. • The good news – you will not loose your templates or virtual machines. Everything will just come right back after you reinstall the iSCSI drives and the NFS datastore. • Even the iSCSI2 VMFS datastore with its extents will come back perfectly. Week#10 vSphere 5.1 & 5.5

  11. Our in-class lab#22 & 23 • Lab 22 will cover snapshots and how to use them. This lab will be similar to our NDG lab. Snapshots are not exactly intuitive, so having some extra practice is not a bad idea. • Lab 23 we will setup a two host ESXi cluster. • We will configure HA and look at its various configuration settings • We will configure DRS and look at its various configuration settings. • Make sure you know both of these labs for next week’s quiz. Week#10 vSphere 5.1 & 5.5

  12. Our NDG lab#13 Our goals in this lab will be to: • Unregister a virtual machine in the vCenter Server inventory. • Register a virtual machine in the vCenter Server inventory. • Unregister and delete virtual machines from disk. • Take snapshots of a virtual machine. • Revert to a snapshot. • Delete an individual snapshot. • Use the Delete All function in Snapshot Manager. Week#10 vSphere 5.1 & 5.5

  13. Our NDG lab#14 Our goals in the lab will be to • Create a vApp • Power on a vApp • Remove a vApp Week#10 vSphere 5.1 & 5.5

  14. Data Protection Module 8 Week#10 vSphere 5.1 & 5.5

  15. You Are Here Table of Contents Week#10 vSphere 5.1 & 5.5

  16. Importance • Over time, your VMware vSphere® environment might undergo changes to its hardware or software configuration. In addition, application data goes through constant change. • From a manageability perspective, making regular backups of your vSphere environment is important. • Backing up virtual machines requires strategies that leverage virtualization architecture to perform highly efficient backups. Week#10 vSphere 5.1 & 5.5

  17. Learner Objectives After this module, you should be able to do the following: • Describe the problems when using traditional backup in virtual infrastructure. • Describe solutions for backing up and restoring virtual machines that use virtual infrastructure. • Discuss technologies that make virtual machine backup and restore operations faster and easier. • Describe how to back up and restore a virtual machine. • Describe how to back up and restore VMware® vCenter Server™. • Discuss a strategy for backing up and restoring a VMware vSphere® ESXi™ host’s configuration data.

  18. Traditional Backup Method physical server physical server (uses nearly 100 percent ofserver resources during backup) backup agent backup server operating system operating system x86 architecture x86 architecture network connection backup to tape or disk data to back up Week#10 vSphere 5.1 & 5.5

  19. Backup Challenges in Virtualized Environments traditional backup method backupserver VMware vSphere • Excessive physical resource use generated by each virtual machine. • Backup agents installed in virtual machines monopolize host CPU resources during backups, which results in less CPU resource for other virtual machines running on that ESXi host. • I/O resources like network and storage are also saturated with read and write operations during backup. Week#10 vSphere 5.1 & 5.5

  20. Virtual Architecture Advantages • No backup agent installation is required. • Use of virtual machine snapshot functions is enabled. • Backup processing is offloaded from ESXi hosts to a backup server. • Virtual machines see the same virtual hardware. • Virtual disks can be thin-provisioned. • Faster backup and recovery times are enabled through the use of changed block tracking and data deduplication. • A single backup image can be created. • Both image-level and file-level restoration can be performed. Week#10 vSphere 5.1 & 5.5

  21. vSphere Storage APIs – Data Protection VMware vSphere® Storage APIs − Data Protection (VADP): • Enables backup and recovery of entire virtual machine images across SAN storage or local area networks • Is an API that is directly integrated with backup tools from third-party vendors • Enables you to remove load from the host and consolidate backup load onto a central backup server • Protects virtual machines that use any type of storage supported by ESXi (Fibre Channel, iSCSI, NAS, or local storage)

  22. Offloaded Backup Processing backupserver VMware vSphere • Configure the storage environment so that the backup server can access the storage volumes that are managed by the ESXi hosts. • Backup processing is offloaded from the ESXi host to the backup server, which prevents local ESXi resources from becoming overloaded. mount virtual disks to backup server tape disk Week#10 vSphere 5.1 & 5.5

  23. Changed Block Tracking virtual machine H/W version 9ctkEnabled=truescsi0:0.ctkEnabled=truescsi1:0.ctkEnabled=true virtual machine H/W version 7ctkEnabled=truescsi0:0.ctkEnabled=true • Copy only file blocks that have changed since the last backup. • Changed block tracking enables faster incremental backups and near-continuous data protection. -ctk.vmdk -ctk.vmdk -ctk.vmdk Week#10 vSphere 5.1 & 5.5

  24. Data Deduplication storage array backup 1 • Data deduplicationhas the following characteristics: • Does not store twice those blocks with the same information as a previous backup • Reduces 12 file blocks to 4 unique file blocks • Saves storage capacity • Provides faster backup performance backup 2 backup 3 unique file blocks Week#10 vSphere 5.1 & 5.5

  25. VMware vSphere Data Protection Easy, disk-based backup and recovery solution for virtual machines: • Pre-configured virtual machine appliance • Agent-less, web-based backup and recovery management • Patented de-duplication technology • Entire virtual machine and file-level restores • Included with all versions of VMware vSphere (except Essentials)

  26. vSphere Data Protection Details • Scalability (maximums): • 100 virtual machines per VDP appliance • 10 appliances per vCenter Server • 2 TB of deduplicated storage • Appliances deployed with .5 TB, 1 TB, or 2 TB • Efficient backup mechanism: • vSphere API for Data Protection (VADP) • Changed Block Tracking (CBT) • Variable-length segment size • Deduplication across all virtual machines performed in VDP appliance • SCSI hot add, which avoids copying entire .vmdk across network Week#10 vSphere 5.1 & 5.5

  27. vSphere Data Protection Key Components vSphere vSphere • Virtual Machine Appliance: • Linux virtual machine .ova package • Easy, fast deployment • vSphere Infrastructure: • Changed Block Tracking • VSS in VMware Tools • Appliance Storage Sizes: • .5 TB • 1 TB • 2TB • vCenter Integration: • Manage through Web client vCenter Server VMware vSphere® Web Client Week#10 vSphere 5.1 & 5.5

  28. VDP Architecture vCenter Server vSphere Data Protection VDP Appliance • 4 vCPUs, 4 GB RAM • 850GB, 1.6 TB or 3.1 TB • SLES 11 64-bit vCenter Server 5.1 vSphere 4.0 or higher vSphere vSphere Web Client Deduplication Store (.vmdk files)

  29. VDP Deployment and Configuration • After installation, VDP-configure is in“maintenance mode”: • Status - Services and logs • Configuration - Network, vCenter, and system settings • Rollback - Roll back repository of backups (more on this later) • Upgrade - Upgrade VDP appliance Week#10 vSphere 5.1 & 5.5

  30. Virtual Machine Backup vSphere Backup Select objects - containers (data center, folder, clusters, and so on) and individual virtual machines Week#10 vSphere 5.1 & 5.5

  31. Restoring a Virtual Machine Restore Week#10 vSphere 5.1 & 5.5

  32. File Level Restore (FLR) Restore individual files from backup: • VMware vSphere® Data Protection™ Restore Client: • http://<VDP ip address>:8580/flr • VMware® Tools™ must be installed. • Windows NTFS and Linux LVM, Ext 2, Ext 3 are supported (basic disks). View all restore points or filter by date

  33. VDP Reporting - User Interface VDP appliance capacity Success and failures at a glance List of virtual machines, Backup Jobs, and so on, with the ability to filter Details for object Week#10 vSphere 5.1 & 5.5

  34. Backing Up vCenter Server • Choose a complementary backup solution that matches your vCenter Server deployment. • Perform a full backup of your vCenter Server system. • Before starting backups, stop these services: • VMware vCenter Server • VMware VCMSDS (the Active Directory Application Mode database) • Database service (SQL, Oracle, DB2) • Back up the vCenter Server database, using recommended practices provided by the database vendor. • Back up the SSL certificates. • Back up the vpxd.cfg file. Week#10 vSphere 5.1 & 5.5

  35. Backing Up ESXi Host Configuration Data • Always back up your host configuration after installation, after changing the configuration, and after upgrading the host. • ESXi configuration: • Use the vicfg-cfgbackup command. • This command backs up and restores the host’s configuration. • Run the command from VMware vSphere® Command-Line Interface. Week#10 vSphere 5.1 & 5.5

  36. Review of Learner Objectives • You should be able to do the following: • Describe the problems when using traditional backup in virtual infrastructure. • Describe solutions for backing up and restoring virtual machines that use virtual infrastructure. • Discuss technologies that make virtual machine backup and restore operations faster and easier. • Describe how to back up and restore a virtual machine. • Describe how to back up and restore vCenter Server. • Discuss a strategy for backing up and restoring an ESXi host’s configuration data. Week#10 vSphere 5.1 & 5.5

  37. Key Points • When you plan your backup strategy for virtual machines, be aware of the various techniques that complement virtual infrastructures. • Data Recovery is an agentless, 64-bit, Linux-based virtual appliance used for backing up and recovering virtual machines. • Data Recovery uses deduplication store technology to make efficient use of the backup storage. • Data can be restored per virtual machine, per virtual disk, or per file. • Questions? Week#10 vSphere 5.1 & 5.5

  38. Assessment week#10

  39. You can have 50 virtual machines per VDP appliance • True or False Week#10 vSphere 5.1 & 5.5

  40. Answer • False - it is 100 VM per VDP appliance. Week#10 vSphere 5.1 & 5.5

  41. You can have up to 10 appliances per vCenterServer True or False Week#10 vSphere 5.1 & 5.5

  42. Answer • True Week#10 vSphere 5.1 & 5.5

  43. VDP in vSphere 5.1 is replacing VDR in vSphere 5.0. True or False Week#10 vSphere 5.1 & 5.5

  44. Answer • True Week#10 vSphere 5.1 & 5.5

  45. Licensing for VDP is included with vSphere Essentials Plus or greater. True or False Week#10 vSphere 5.1 & 5.5

  46. Answer • True Week#10 vSphere 5.1 & 5.5

  47. VDP is an appliance that is delivered as an OVA template. True or False Week#10 vSphere 5.1 & 5.5

  48. Answer • True Week#10 vSphere 5.1 & 5.5

  49. What are the three sizes that the VDP comes in for the deduplication data store? • 0.5TB • 1TB • 2TB • 4TB Week#10 vSphere 5.1 & 5.5

  50. Answer • A, B, & C Week#10 vSphere 5.1 & 5.5