Configuring vSAN storage policies and their practical application
•Als PPTX, PDF herunterladen•
0 gefällt mir•158 views
Storage Policy Based Management (SPBM) allows data services like replication, encryption, and performance policies to be applied on a per-VM or per-VMDK level through configurable storage policies. The presenter discusses how SPBM is central to VMware's software-defined storage vision and allows administrators to take an application-centric approach to assigning storage services and service level agreements. Administrators can define storage policies, apply them dynamically to VMs, and change policies without disrupting services.
Empfohlen
Empfohlen
Weitere ähnliche Inhalte
Was ist angesagt?
Was ist angesagt? (20)
Ähnlich wie Configuring vSAN storage policies and their practical application
Ähnlich wie Configuring vSAN storage policies and their practical application (20)
Mehr von VMUG IT
Mehr von VMUG IT (20)
Kürzlich hochgeladen
Kürzlich hochgeladen (20)
Configuring vSAN storage policies and their practical application
- 1. vSAN "a la carte” viaggio tra i menù di configurazione delle storage policy e loro applicazione pratica Gianni Resti System Engineer VMware, Software Defined Storage Specialist
- 2. 2© 2017 VMware Inc. All rights reserved. About The Presenter Name Gianni Resti Title Sr. Software Defined Storage System Engineer Storage & Availability Business Unit Background More than 12 years of experience in IT Infrastructure - 9 years in a Storage Vendor as Infrastructure Consultant & PM - 3 years in VMware as Technical Account Manager (TAM) - Currently in VMware as Sr. Software Defined Storage System Engineer Skills and Certification ITIL v2, v3 VMware VTSP 4, VTSP 5, VCP6 Project Management Professional (PMP) BS 25999 (Business Continuity Lead Auditor)
- 3. 3© 2017 VMware Inc. All rights reserved. What’s the central element in our life, today?
- 4. 4© 2017 VMware Inc. All rights reserved.
- 5. 5© 2017 VMware Inc. All rights reserved. How do we manage all of that data? How do we keep it safe? How can we grant an App-Centric SLA on data instead to an Hardware-Centric SLA ? Storage Policy Based Management
- 6. 6 Introduction to Storage Policy Based Management
- 7. 7© 2017 VMware Inc. All rights reserved. The SPBM Paradigm SPBM is the foundation of VMware's Software Defined Storage vision Common framework to allow storage and host related capabilities to be consumed via policies. Applies data services (e.g. replication, encryption, performance) on a per VM, or even per VMDK level, through policies
- 8. 8© 2017 VMware Inc. All rights reserved. Policies are App-Centric Policy is related to the VMs and not to the Datastore It can be changed on the fly with no service disruption It can be assigned with the granularity of a single VM disk
- 9. 9© 2017 VMware Inc. All rights reserved. Storage Policy Rules available with vSAN 6.6.1 • Level of Failure to Tolerate (FTT) – Primary Level of Failure to Tolerate (Across Site) – Secondary Level of Failure to Torerate (Local to Site) • Failure Tolerance Method – Mirroring (RAID1) – Erasure Coding (RAID5/6) • IOPS Limit • Object Checksum • Force Provisioning • Stripe number for Object • Flash cache Read reservation (%) • Object Space Reservation (%) • Affinity site • TECH PREVIEW@VMWORLD: Data Protection & Disaster Recovery
- 10. 10© 2017 VMware Inc. All rights reserved. vSAN Failure to Tolerate (FTT) Overview 10 vSphere vSAN Object Based Storage No preconfigured disk protection or service level Managed through disk storage policies Prevents component failure Applied at VMDK level .vmdk Copy 1 Copy 2Witness FTT=1 (RAID 1) vSAN Datastore SSD SSD SSD SSD SSD SSD SSD SSD SSD SSD SSD SSD SSD SSD SSD SSD SSD SSD
- 11. 11© 2017 VMware Inc. All rights reserved. vSAN Failure to Tolerate (FTT) Overview 11 vSphere vSAN vSAN Datastore SSD SSD SSD SSD SSD SSD SSD SSD SSD Object Based Storage No preconfigured disk protection or service level Managed through disk storage policies Prevents component failure Applied at VMDK level .vmdk SSD SSD SSD SSD SSD SSD SSD SSD SSD FTT=1 ERASURE CODE (RAID 5)
- 12. 12© 2017 VMware Inc. All rights reserved. vSAN Failure to Tolerate (FTT) Overview 12 vSphere vSAN vSAN Datastore SSD SSD SSD SSD SSD SSD SSD SSD SSD .vmdk SSD SSD SSD SSD SSD SSD SSD SSD SSD FTT=2 ERASURE CODE (RAID 6) Object Based Storage No preconfigured disk protection or service level Managed through disk storage policies Prevents component failure Applied at VMDK level
- 13. 13© 2017 VMware Inc. All rights reserved. vSAN Failure to Tolerate (FTT) Overview 13 vSphere vSAN vSAN Datastore SSD SSD SSD SSD SSD SSD SSD SSD SSD SSD SSD SSD SSD SSD SSD SSD SSD SSD Object Based Storage No preconfigured disk protection or service level Managed through disk storage policies Prevents component failure Applied at VMDK level Redo LogDatabase
- 14. 14© 2017 VMware Inc. All rights reserved. vSAN Primary FTT vSphere vSAN ClusterCluster 5ms RTT, 10GbE Redundancy locally and across sites With site failure, vSAN maintains availability with local redundancy in surviving site No change in stretched cluster configuration steps Optimized site locality logic to minimize I/O traffic across sites RAID-6 3rd site for witness RAID-6 RAID-1
- 15. 15© 2017 VMware Inc. All rights reserved. vSAN Secondary FTT vSphere vSAN ClusterCluster User can specify single site location of VM’s components if site level protection is unnecessary Policy driven using SPBM Reduces network and storage requirements Ideal for solutions that already use application redundancy (Exchange DAGs, SQL Availability groups, etc.) 3rd site for witness RAID-6 5ms RTT, 10GbE
- 16. 16© 2017 VMware Inc. All rights reserved. Storage Policy Management
- 17. 1 7 Define a Storage Policy
- 18. 18© 2017 VMware Inc. All rights reserved.
- 19. 1 9 Apply a Storage Policy
- 20. 20© 2017 VMware Inc. All rights reserved.
- 21. 2 1 Change a Storage Policy
- 22. 22© 2017 VMware Inc. All rights reserved.
- 24. Apply an IOPS Limit
- 25. 25© 2017 VMware Inc. All rights reserved.
- 26. 26© 2017 VMware Inc. All rights reserved. Summary • The amount of data in the world is exploding! • Data is critical to your organization, and in many cases, how you innovate with this data keeps you ahead of your competitors. • Managing that data, keeping it safe and providing the appropriate data services at the granularity of an application can be complex • Storage Policy Based Management, a fundamental building block to VMware’s Software Defined Storage achieves this. • With SPBM, data services (e.g. replication, RAID level, IOPS Limits) can be assigned to your data on a per VM or per VMDK basis. 26
Hinweis der Redaktion
- Name Title Background Skills/Certifications Interests
- Minimum of 3 hosts in a cluster configuration All 3 host MUST!!! contribute storage Maximum of 32 hosts Locally attached disks Magnetic disks (HDD) Flash-based devices (SSD) Network connectivity 1GB Ethernet 10GB Ethernet (preferred)
- Minimum of 3 hosts in a cluster configuration All 3 host MUST!!! contribute storage Maximum of 32 hosts Locally attached disks Magnetic disks (HDD) Flash-based devices (SSD) Network connectivity 1GB Ethernet 10GB Ethernet (preferred)
- Minimum of 3 hosts in a cluster configuration All 3 host MUST!!! contribute storage Maximum of 32 hosts Locally attached disks Magnetic disks (HDD) Flash-based devices (SSD) Network connectivity 1GB Ethernet 10GB Ethernet (preferred)
- Minimum of 3 hosts in a cluster configuration All 3 host MUST!!! contribute storage Maximum of 32 hosts Locally attached disks Magnetic disks (HDD) Flash-based devices (SSD) Network connectivity 1GB Ethernet 10GB Ethernet (preferred)
- Key Message/Talk track: vSAN’s ability to provide a fully active-active, stretched cluster has already proven it’s value in data centers. vSAN 6.6 takes this a step further, allowing for storage redundancy within a site AND across sites at the same time. This helps deliver effective, affordable protection against entire site outages, as well as host outages within a site. This level of protection is extraordinary, and what many of our customers have asked for. Lower TCO is the result of no need to purchase additional hardware or software, while addressing protection requirements with software you already know. ---------------------------------- Overview: Ensures redundancy within a site (host failures), as well as across sites (site failures) when using stretch clusters. With site failure, vSAN maintains availability with local redundancy in surviving site No change in stretched cluster configuration steps Optimized site locality logic to minimize I/O traffic across sites ---------------------------------- Details: Synchronous I/O occurs within a site, as well as across sites. This means: If host or fault domain fails in a site, failover will occur in the same site without any loss of data. If a site fails, failover to the other site occurs without any loss of data. Site availability is maintained by witness VM that resided in central location, accessible by both sides. Internal availability is maintained by internal witness components. Supported “Failure Tolerance Method” (FTM) configurations: RAID1 across sites, with RAID1 in each site: Hybrid, and All-Flash RAID1 across sites, with RAID5/6 in each site: All-Flash “Secondary Failures to Tolerate” (SFTT) represents the FTT policy within a site (0-3) “Primary Failures to Tolerate” (PFTT) represents the FTT policy across sites (0-1) “Affinity” is an SPBM rule that specifies the site that the vSAN object is placed in Options: None, Preferred Fault Domain, Secondary Fault Domain Data Path optimizations for Stretch Clusters Local Read Local Resync Single cross-site write for multiple replicas Partial repairs supported vSAN datastore must upgraded to the vSAN on-disk format version 5.0, as a part of vSAN 6.6 *The term “PFTT” represents FTT policy across sites ONLY when using stretched clusters. In non stretched clusters, “SFTT” is NOT used, and “PFTT” represents the policy within a site ---------------------------------- Internal:
- Key Message/Talk track: vSAN™ 6.6 not only added more protection for stretched cluster topologies, but it now provides easy to configure options that allow you to protect VMs across a site, or just within a single site. This allows for more effective use of network and storage resources across the infrastructure, and simplifies design and operation of an environment. With this level of flexibility and ease, an organization’s protection requirements can easily be met. ---------------------------------- Overview: User can specify site location of VM’s components if site level protection is unnecessary Policy driven setting allows user to specify site (preferred or secondary) where VM data should be placed. Reduces network and storage requirements Ideal for solutions that already use application redundancy (Exchange DAGs, SQL Availability groups) ---------------------------------- Details: Site affinity setting tied to objects using PFTT=0. (representing FTT policy across site of 0) “Affinity” is an SPBM rule that specifies the site that the vSAN™ object is placed in Options: None, Preferred Fault Domain, Secondary Fault Domain New policy setting will be honored by all vSAN™ operations, including repairing, rebalancing, decommissioning Should be used in conjunction with DRS affinity rule so that site location for computing is controlled. (vSAN™ SPBM will control location of storage components, and vSphere® DRS affinity rule will control location of compute.) *The term “PFTT” represents FTT policy across sites ONLY when using stretched clusters. In non stretched clusters, “SFTT” is NOT used, and “PFTT” represents the policy within a site ---------------------------------- Internal: https