Key data protection best practices for your virtual environment
•Download as PPTX, PDF•
1 like•499 views
This document discusses best practices for using Veeam backup software with Tintri storage systems. It provides an overview of Tintri's VM-level storage capabilities and how they integrate with Veeam. Specific topics covered include using the "Direct NFS Access Mode" for backups, sizing backup proxies, configuring repositories, and Hyper-V support.
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (20)
Similar to Key data protection best practices for your virtual environment
Similar to Key data protection best practices for your virtual environment (20)
More from actualtechmedia
More from actualtechmedia (7)
Key data protection best practices for your virtual environment
- 1. Key Data Protection Best Practices for your Virtual Environment
- 2. About the Speakers David M. Davis vExpert, CCIE, & Partner ActualTech Media Bill Roth Sr Technical Marketing Engineer Tintri Jason Leiva Solutions Architect Veeam
- 3. The Modern Enterprise Enhanced with Veeam & Tintri Bill Roth, Tintri Jason Leiva, Veeam
- 4. @Tintri VM-Level Quality of Service VM-Level Analytics VM Data Management VM-Level Automation with PowerShell and REST Multi-Hypervisor (vSphere, Hyper-V, RHEV, OpenStack, XenServer) Simple, automatic with no tuning required Tintri is VM-aware Storage © 2016 Tintri, Inc. All Rights Reserved. 4 VM-level storage management
- 5. Watch the Full Webinar here:
- 6. @Tintri VM-Level Analytics 6 Maintain Visibility? Guarantee Performance? Real Time Analytics Performance Isolation and QoS © 2016 Tintri, Inc. All Rights Reserved. VM-Level Quality of Service
- 7. @Tintri VISIBILITY across the IT Stack End-to-end visibility Root cause | Data-driven decisions © 2016 Tintri, Inc. All Rights Reserved.
- 8. @Tintri Guarantee the PERFORMANCE of every app Automatic Performance Isolation for every app Policy-based VM Quality of Service (QoS) Auto-tuning | No noisy neighbors © 2016 Tintri, Inc. All Rights Reserved.
- 9. @Tintri Tintri Global Center Advanced Up to 10 PB 160,000 VMs 6.4M IOPS 32 VMstores © 2016 Tintri, Inc. All Rights Reserved. TGC Standard offers: • Real-time analytics and management for up to 32 VMstores and over 160K VMs • Manage policies for groups of VMs and maintain those policies as VMs are moved • Automate management with REST API or PowerShell TGC Advanced adds: • Create pools of VMstores (mixed capacity, performance, all-flash and hybrid) • Optimize VM distribution across pool with VM-level software intelligence
- 10. @Tintri Modern Scale-out Architecture 10 Federated pool of storage Use of high density SSDs Balance capacity and performance Scale compute and storage independently Accommodate existing and future systems © 2016 Tintri, Inc. All Rights Reserved.
- 11. @Tintri Tintri VM Scale-out HEALTH: PERFORMANCE: CAPACITY: Automatically or manual triggered redistribution Retain snapshots, policies and stats during migration Pool expansion by adding storage nodes © 2016 Tintri, Inc. All Rights Reserved.
- 12. @Tintri Direct NFS Access Mode © 2016 Tintri, Inc. All Rights Reserved. VM Veeam Backup Server ESXi Host Veeam Backup Repository VMware VM VM VM P Veeam Backup Proxy with NFS client Additional transport mode for NFS VM data blocks are read from production storage VM data blocks are processed by a backup proxy The backup proxy sends the data to the target repository
- 13. @Tintri Direct NFS Access Mode © 2016 Tintri, Inc. All Rights Reserved. 13 • Performance Expectations: Using backup proxy VMware Backup Proxy for disk Hard disk 1 [nfs] Using backup proxy VMware Backup Proxy for disk Hard disk 2 [nfs] Hard disk 2 (256.0 GB) 46.5 read at 157 MB/s [CBT] Hard disk 1 (128.0 GB) 40.5 GB read at 156 MB/s [CBT] NAME TYPE OBJECTS STATUS D-NFS-10 VMware Backup 1 Stopped D-NFS-11 VMware Backup 1 0% completed at 332 MB/s D-NFS-12 VMware Backup 1 2% completed at 310 MB/s
- 14. @Tintri Direct NFS Access Mode © 2016 Tintri, Inc. All Rights Reserved. 14 Backup Proxy: Physical or virtual? CPU & RAM sizing? 10 GbE NICs? Minimum number of proxies? • Virtual proxy placement? NFS datastore NFS client Backup proxy Backup repository 8 Hardware Summary Memory CPUs 16384 MB ???
- 15. @Tintri Direct NFS Access Mode © 2016 Tintri, Inc. All Rights Reserved. 15 Proxy server settings: Transport mode Connected datastores Maximum concurrent tasks
- 16. @Tintri Direct NFS Access Mode © 2016 Tintri, Inc. All Rights Reserved. 16 Transport mode: Automatic selection Direct storage access Failover to network mode.
- 17. @Tintri Direct NFS Access Mode © 2016 Tintri, Inc. All Rights Reserved. 17 Connected datastores: Automatic detection Manual selection
- 18. @Tintri Direct NFS Access Mode © 2016 Tintri, Inc. All Rights Reserved. 18 Configuration details: • Settings > Data IPs Proxy requires NFS access to the Tintri VMstore • Settings > NFS access Proxy requires Tintri VMstore “Data IP” access
- 19. @Tintri Direct NFS Access Mode © 2016 Tintri, Inc. All Rights Reserved. 19 Max concurrent tasks: Default value is based on CPU cores Each disk of every VM to be processed is a separate task Tintri recommends a maximum of 4 concurrent tasks for Direct NFS access mode
- 20. @Tintri Direct NFS Access Mode © 2016 Tintri, Inc. All Rights Reserved. 20 Why 4 max concurrent tasks? High throughput per backup or restore stream – tasks complete faster New transport mode for NFS – direct pipeline may compete with hypervisor traffic Recommendation may be updated as we gain a better understanding of customer deployments NAME STATUS ACTION VeeamClient10 Pending Queued for precessing at 6/2/2016 10:57:35AM Resource not ready: VMware backup proxy
- 21. @Tintri Throttling Performance © 2016 Tintri, Inc. All Rights Reserved. 21 • Global setting • Minimum value is 5 ms I/O Control: Enable Storage latency control
- 22. @Tintri Throttling Performance © 2016 Tintri, Inc. All Rights Reserved. 22 Network Traffic Rules: • Proxy & repository Throttle network traffic between backup infrastructure components
- 23. @Tintri Direct NFS Access Mode © 2016 Tintri, Inc. All Rights Reserved. 23 How to adhere to the recommended 4 task maximum: Configure 1 proxy to use Direct storage access Limit maximum concurrent tasks to 4 Configure additional proxy or proxies to use Virtual appliance or Network 1 4
- 24. @Tintri Direct NFS Access Mode © 2016 Tintri, Inc. All Rights Reserved. 24 Based on scheduling requirements, create one or more backup jobs that use the proxy configured for Direct storage access Create one or more jobs that use the proxy configured for Virtual appliance or Network How to adhere to the recommended 4 task maximum:
- 25. @Tintri “Restore entier VM” uses Direct NFS access mode Direct NFS Access Mode © 2016 Tintri, Inc. All Rights Reserved. 25 Recovery: • Multiple VMDKs are restored sequentially “Restore VM hard disks” uses Direct NFS access mode
- 26. @Tintri Direct NFS Access Mode © 2016 Tintri, Inc. All Rights Reserved. 26 Advanced Settings > vSphere: VMware Tools quiescence cannot be enabled Changed block tracking can be enabled
- 27. @Tintri Direct NFS Access Mode © 2016 Tintri, Inc. All Rights Reserved. 27 VMware KB 2010953 / Veeam KB 1681 • Challenge exists with Virtual appliance (hot-add) and NFS v3 • VM may become unresponsive for approximately 30 seconds Direct NFS access may mitigate this challenge Snapshot removal
- 28. @Tintri Backup Repositories… © 2016 Tintri, Inc. All Rights Reserved. 28 P Backup Proxy “A” Backup Repository Backup Repository P Backup Proxy P Backup Proxy “B” Backup Repository Backup Repository Backup Repository Flexible backup infrastructure: Standalone proxies, standalone repository Combined proxy & repository Scale-out repository (logical entity)
- 29. @Tintri Backup Repositories… © 2016 Tintri, Inc. All Rights Reserved. 29 Backup Repository Backup Repository Backup Repository Scale-out repository: Standalone repositories are added Advanced settings Policy selection
- 30. @Tintri Backup Repositories… © 2016 Tintri, Inc. All Rights Reserved. 30 Backup Repository Backup Repository Backup Repository Scale-out repository: Advanced settings for “Performance” policy Backup placement settings Allowed backup files per extent
- 31. @Tintri Backup Repositories… © 2016 Tintri, Inc. All Rights Reserved. 31 Job settings: Advanced settings for backup job “Storage” Inline data deduplication Compression VMware Tools
- 32. @Tintri Hyper-V Support © 2016 Tintri, Inc. All Rights Reserved. 32 Veeam Backup & Replication VSS Requestor VM Hyper-V Host Hyper-V VM VM VM Hyper-V VSS Framework File Share Shadow Copy Provider SMB 3.0 File Server File Share Shadow Copy Agent VSS Framework on SMB 3.0 server SMB 3.0 share
- 33. Thank you
- 34. Prize Winner! And the Winners of the iPad Pro is…
- 35. What are your Questions?
Editor's Notes
- ** slides full screen ** make us all organizers ** click SHOW MY SCREEN ** Start broadcast ** RECORD —— [TITLE SLIDE] Hello and Welcome to….. Key Data Protection Best Practices for your Virtual Environment My name is David Davis and I'll be the moderator, and initial speaker, on today's event, sponsored by Sureline Systems If you have questions during the webinar, please use the gotomeeting question box to enter your question. The speakers will be answering questions LIVE as they come in and we’ll have a Q&A session at the end of the webinar. One luck attendee today will 1 iPAD PRO so stay tuned for that drawing! We’ve got a lot to cover so Let’s get started!!
- So that you have a little background on who is presenting today, let me first tell you about myself. My name is David Davis and I’m a VMware vExpert, VCP, CCIE, and a video training author, on the topic of virtualization, for pluralsight.com. I started my career in IT as a server and network admin, working in the datacenter. Later I was an IT manager at medium enterprise where we had a very successful server consolidation project, consolidating roughly 80% of our servers. It was then that I learned about the great power and efficiency that virtualization could provide. Since then, I’ve been writing, speaking, and creating video training around virtualization. I’ve spoke at VMware user groups and Vmworld in the US, Canada, and Europe. I’m the co-owner of actualtechmedia.com where we create technical marketing content and demand generation for companies in virtualization, storage, and cloud computing. My blog is virtualizaitonsoftware.com and you can find me on Twitter as @DavidMDavis. Our panelists are… Now that you know who we are, let’s start this webinar off by talking about some of the ongoing challenges we are facing in IT.
- The foundation of Tintri’s solution is VM-aware storage. With traditional storage, the user manages LUNs or volumes. In a virtualized environment there are 10s or hundreds of VMs in a LUN or volume. What you want is storage that supports the abstraction of virtual machine. Management should be done at the VM not the LUN volume. So this is VM-aware storage. It provides VM level QoS, VM level analytics, VM data management for replication, cloning. Everything can be done via an API. Vm-aware storage is hypervisor neutral. It can support vSphere, Hyper-V and OpenStack VMs on the same storage system.
- So how do you operate at scale and guaranteed performance for each application as well as providing visibility. With VM-aware storage, End to end visibility is provided by always-on real time analytics. You can guarantee the performance of every application in a pool of systems using performance isolation and can set QoS policies on individual VMs. It’s the capabilities of VM-aware storage that simplifies the management of a large environment.
- What if you had complete VISIBILITY across the IT stack: Host, Network, and Storage? What if you could see everything at the level you care about: VM level? You could pinpoint the root cause of issues at a glance Make decisions based on real data Manage policies for hundreds of thousands of VMs at the VM level
- What if you could isolate each VM automatically, without manual tuning? And what if you could set quality of service policies for individual VMs and groups of VMs: unique policies for VDI and databases, or production and test/dev workloads? You would gain the ability to share your storage with mixed workloads, VDI and databases for example, without worrying about them fighting for resources, all without tuning. And if you want to guarantee a little more performance to certain workloads, and less for others, you can do that too through set-it-and-forget-it policies. No noisy neighbors.
- Tintri Global Center is our single pane of glass for customers with multiple VMstores. You can manage up to 32 VMstores across geographies from a single location. That’s the equivalent of managing just 32 datastores with 3.2PB of capacity for 112,000 VMs and 4.5M IOPS from one place.
- Our new scale out architecture is designed for virtualized environments. It takes a very similar approach to the way that Vmware scales compute using DRS. It provides federated pools of storage. You can create multiple pools. You can mix and match different kinds of storage nodes in a pool. A pool can include our current Vmstores, older Vmstores and future storage nodes. There is no custom interconnect between the nodes. Each storage node has a lot of performance and capacity – up to 300 TB and 5000 VMs. It’s balanced in capacity and performance. When you add a storage node, you are adding performance as well as capacity. Compare this to large scale-up all-flash systems that have a lot of capacity but are limited by performance. The architecture is also built on the independent scaling of compute and storage. Today you can go from 1 to 32 storage nodes. But there are no intrinsic limits on storage scaling. For compute, you can start with a small number of servers and scale to hundreds or even thousands of compute nodes. It’s modern scale out all flash storage for virtualized environments and the cloud.
- Now let’s look at the Scale out software works. The VM scale out algorithm redistribute VMs to optimize the system. It uses data about every VM that is running in the system to make decisions. The algorithm considers the capacity, performance of each VM and any policies associated with each VM. It also has data about each individual storage node. In order to optimize the system it may recommend that some VMs should be migrated to new storage nodes. When a migration occurs all snapshots, policies and stats are retained. I am now going to hand it over to Sunil who will give a demo of VM-scale out.
- The data path for the backup (or restore) bypasses the ESXi host.
- Reported to us from customer in Europe - multiple VMs with an aggregate data transfer rate of more than 500 MB/s. And from the lab at Tintri – two VMs being backed up with an aggregate data transfer rate of more than 600 MB/s. We believe that Direct NFS can be 300% faster than NBD.
- We receive many questions about backup proxy servers. For instance, what are the advantages / disadvantages of deploying physical or virtual backup proxies? When deploying virtual backup proxy proxy servers, should the be statically assigned to specific ESXi hosts or should be DRS be allowed to migrate them? Do we have guidelines on backup proxy sizing? How many backup proxies should a user plan on deploying?
- Important backup proxy server settings are shown here; transport mode, connected datastores, and max concurrent tasks. We’ll look at these settings in greater detail on subsequent slides.
- Automatic selection is typically preferred and will use Direct storage access whenever possible. The caveat is that Automatic selection may select Virtual appliance if for some reason Direct storage access is unavailable. With either choice, the optional ability to failover to network mode can be enabled.
- In some environments it may be necessary to use manual datastore selection. When using manual datastore selection, specific datastores can be added.
- The backup infrastructure components are flexible in that they can be configured in different ways to achieve different objectives. In the first example, the infrastructure is scaled to have multiple proxies connect to an independent repository. This facilitates scaling the ability to deliver backup and replication traffic while also eliminating a single-proxy-point-of-failure. The second example depicts a proxy and repository hosted on the same machine. This simple combined backup infrastructure may be best suited to smaller environments. The scale-out repository is a logical entity, where multiple repositories are configured to create a pool of devices and systems, summarizing their capacity.
- Tintri and Veeam Software Solution Brief tintri_backup_and_recovery_best_practices_with_veeam