introducing vmware validated designs for software …...introducing vmware validated designs for...

Introducing VMware Validated Designsfor Software-Defined Data Center

VMware Validated Design for Software-Defined Data Center 2.0

This document supports the version of each product listed andsupports all subsequent versions until the document isreplaced by a new edition. To check for more recent editionsof this document, see http://www.vmware.com/support/pubs.

EN-002170-00

http://www.vmware.com/support/pubs

Introducing VMware Validated Designs for Software-Defined Data Center

2 VMware, Inc.

You can find the most up-to-date technical documentation on the VMware Web site at:

http://www.vmware.com/support/

The VMware Web site also provides the latest product updates.

If you have comments about this documentation, submit your feedback to:

[email protected]

Copyright © 2016 VMware, Inc. All rights reserved. Copyright and trademark information.

VMware, Inc.3401 Hillview Ave.Palo Alto, CA 94304www.vmware.com

http://www.vmware.com/support/

mailto:[email protected]

http://pubs.vmware.com/copyright-trademark.html

Contents

About Introducing VMware Validated Design for Software-Defined Data Center 5

1 Overview of VMware Validated Designs 7

2 Solution Overview and Design Objectives 9

3 Documentation Structure and Audience 11

4 VMware Software Components in the Validated Design 15

5 Overview of the SDDC Structure 17

Physical Infrastructure Layer 18Virtual Infrastructure Layer 20Cloud Management Layer 24Operations Layer 25

Index 29

VMware, Inc. 3


4 VMware, Inc.

About Introducing VMware Validated Design forSoftware-Defined Data Center

The Introducing VMware Validated Design for Software-Defined Data Center guide provides directions on usingthe content of VMware Validated Design™ for Software-Defined Data Center. The guide also contains ahigh-level overview of the Software-Defined Data Center (SDDC) design supported in this VMwareValidated Design version.

Introducing VMware Validated Design for Software-Defined Data Center focuses on providing guidance aboutusing the VMware Validated Design and includes the following information:

n Design objectives

n Document structure and purpose

n Supported VMware product versions

n SDDC design overview

Intended AudienceIntroducing VMware Validated Design for Software-Defined Data Center is intended for cloud architects,infrastructure administrators, cloud administrators and cloud operators who want to get familiar withVMware Validated Design to deploy and manage an SDDC that meets the requirements for capacity,scalability, business continuity and disaster recovery.

VMware Technical Publications GlossaryVMware Technical Publications provides a glossary of terms that might be unfamiliar to you. For definitionsof terms as they are used in VMware technical documentation, go to http://www.vmware.com/support/pubs.

VMware, Inc. 5

http://www.vmware.com/support/pubs


6 VMware, Inc.

Overview of VMware ValidatedDesigns 1

Use VMware Validated Design to create a Software-Defined Data Center that is based on managementcomponents by VMware, and has a scalable and best-practice configuration.

VMware Validated Design has the following advantages:

One path to SDDC After you satisfy the deployment requirements, follow one consistent path todeploy an SDDC.

SDDC design for use inproduction

VMware Validated Design supports an SDDC that has the followingfeatures:

n High-availability of management components

n Backup-and-restore support

n Monitoring and alerting

n Opportunity to extend the deployment to support disaster recovery

Validated design anddeployment

The prescriptive documentation of VMware Validated Design iscontinuously validated by VMware. Validation provides the followingadvantages to your organization:

n Validated product interoperability

n Validated SDDC features, such as custom workload churn, highavailability of management components, operational continuity, efficientmonitoring, and design with dual-region support in mind

n Reduced risk of deployment and operational problems

n Reduced test effort

Fast SDDC standup By downloading all SDDC products , and following detailed design andstep-by-step instructions, you are able to implement a data center withoutengaging in design work and product research.

Support for latestproduct releases

Every version of VMware Validated Design accommodates new productreleases.

Foundation fordevelopment of SDDCdeployment use cases

VMware Validated Design provides the foundation for use cases that satisfythe requirements of individual organizations or industry segments, such asSDDC for microsegmentation, DevOps and automated IT.

VMware, Inc. 7


8 VMware, Inc.

Solution Overview and DesignObjectives 2

VMware Validated Design has a number of objectives to deliver prescriptive content about an SDDC that isfast to deploy and is suitable for use in production.

Table 2‑1. Objectives of VMware Validated Design

VMware Validated Design Objective Description

Main objective SDDC capable of automated provisioning of workloads

Scope of deployment Greenfield deployment of the SDDC managementcomponents.

Cloud type Private cloud

Number of regions and disaster recovery support n The design documentation provides guidance for anSDDC that is capable of supporting a dual-region casefor failover.

n The deployment documentation provides guidance foran SDDC that supports a single region for bothmanagement and tenant workloads.

By design, the SDDC management components can operatein an environment that supports failover in a dual-regionenvironment with one availability zone. See “PhysicalInfrastructure Layer,” on page 18.

Maximum number of virtual machines n 10,000 running virtual machinesn Churn rate of 150 virtual machines per hourChurn rate is related to provisioning, power cycleoperations, and decommissioning of one tenant virtualmachine by using a blueprint in the cloud managementplatform. A churn rate of 100 means that 100 tenantworkloads are provisioned, pass the power cycleoperations, and are deleted.

Number of hardware pods 3-pod setupThe validated design requires the following pods for SDDCdeployment:n Management pod. Runs the virtual machines of the

management products.n Compute pod. Runs the tenant workloads.n Edge pod. Connects the virtual networks in NSX for

vSphere and the external networks.

Data center virtualization n Compute virtualizationn Software-defined storage in the management and edge

podsn Network virtualization

VMware, Inc. 9

Table 2‑1. Objectives of VMware Validated Design (Continued)

VMware Validated Design Objective Description

Scope of guidance n Storage, compute and networking for the managementpod.

n Number of hosts, amount of storage and configurationn Deployment and initial setup of management

components at the levels of infrastructure, cloudmanagement platform, and operations.

n Basic tenant operations such as creating a tenant,assigning tenant capacity, configuring user access, andadding virtual machines to a service catalog fromsingle-machine blueprints.

n Operations on the management components of theSDDC such as monitoring and alerting, backup andrestore, and post-maintenance validation.

Overall availability 99% availabilityPlanned downtime is expected for upgrades, patching, andon-going maintenance.

Authentication, authorization, and access control n Use of Microsoft Active Directory as a central userrepository.

n Use of service accounts with minimum requiredauthentication and Access Control List configuration.

n Use of basic tenant accounts.

Certificate signing Certificates are signed by an external certificate authority(CA).

Hardening Tenant workload traffic can be separated from themanagement traffic.


10 VMware, Inc.

Documentation Structure andAudience 3

The structure of the VMware Validated Design documentation reflects the best practices in designing anddeploying a data center that is capable of automated provisioning of workloads. The documentationcomponents of the validated design are organized according to audience and deployment stage, and youuse them in a specific order.

Figure 3‑1. VMware Validated Design Documentation Flow

Architecture Overview

Detailed Design

Reference Architecture

Design Phase

Start

Deployment Phase

Planning and Preparation

Deployment Guide for Region A

Operations Phase

Operational Guidance

Architecture OverviewThe first part of VMware Validated Design is Architecture Overview and it introduces the terms andcomponents in the design.

VMware, Inc. 11

Table 3‑1. Architecture Overview Information

Section Attribute Description

Guide VMware Validated Design Reference Architecture Guide

Purpose n Introduce the fundamentals and components in theSDDC design.

n Provide information about the layered structure of theSDDC.

n Describe the building modules and basic behavior ofeach management component.

Audience Cloud architects and cloud administrators

Detailed DesignAfter you learn about the basic modules in the SDDC design, you proceed with detailed design of themanagement components and the required infrastructure.

Table 3‑2. Detailed Design Information


Guide VMware Validated Design Reference Architecture Guide

Purpose n Provide complete details about the configuration ofeach layer and of the components that are a part of thelayer.

n Describe available design alternatives.n Provide design decisions to reflect the main design

issues and the rationale behind a chosen solution path.

Audience Cloud architects and cloud administrators

Planning and PreparationAfter you understand the details of the design, you plan your environment according to the requirements ofthe design so that you can deploy the designed SDDC directly without additional testing andtroubleshooting efforts.

Table 3‑3. Planning and Preparation Information


Guide VMware Validated Design Planning and Preparation Guide

Purpose Collect all requirements that your environment must meetso that you can follow VMware Validated Design to createan SDDC. The Planning and Preparation section providesprerequisites for the following areas:n Required software including VMware products, scripts

and third-party softwaren Networking configuration including VLANs, example

IP addresses and DNS namesn Active Directory user configurationn Specifications of the virtual machines that you must

provide in advance

Audience Cloud architects, infrastructure administrators, cloudadministrators and cloud operators


12 VMware, Inc.

Deployment Guide for Region AAfter you make sure that your environment has the required structure and configuration, follow theDeployment Guide for Region A to start the SDDC implementation.

Table 3‑4. Deployment Guide Information


Guide VMware Validated Design Deployment Guide for Region A

Purpose n Provide step-by-step instructions for each managementcomponent of the SDDC according to the selecteddesign path in Detailed Design.

n Cover the single-region setup of the SDDC.n Provide details about setting up the virtual

infrastructure for both management and tenantworkloads.

n Provide procedures for integration of the products toform one functional system.


Operational GuidanceAfter you deploy the SDDC, follow the Operational Guidance documentation to operate the environment andthe management workloads .

Table 3‑5. Operational Guidance Information


Guide VMware Validated Design Operational Guidance that isdelivered as a set of add-on packages.

Purpose For each management component, provide the followinginformation:n Step-by-step instructions about backing and restoring

the components of each management product.n Step-by-step instructions about setting up dashboards

and activating alerts for monitoring the SDDC, andlists of notifications that are most symptomatic.

n Step-by-step instructions about validating theoperation of the SDDC after software maintenancesuch as restore, upgrade or failover .


Chapter 3 Documentation Structure and Audience

VMware, Inc. 13


14 VMware, Inc.

VMware Software Components in theValidated Design 4

VMware Validated Design is based on a set of individual VMware products with different versions that areavailable in a common downloadable package.

Table 4‑1. VMware Software in the VMware Validated Design

Product Group and Edition Product Name Product Version

VMware vSphere Enterprise Plus ESXi 6.0 Update 2

vCenter Server Appliance (ISO) 6.0 Update 2

VMware Virtual SAN Standard orhigher

Virtual SAN 6.2

VMware NSX for vSphere Enterprise NSX for vSphere 6.2.2

VMware vRealize AutomationAdvanced or higher

vRealize Automation 7.0.1

vRealize Orchestrator 7.0.1

vRealize Orchestrator Plug-in forNSX

1.0.3

v Realize Orchestrator Plug-in forvRealize Automation 7.0.1

7.0.1

VMware vRealize Business for CloudStandard

VMware vRealize Business for Cloud 7.0.1 and 7.0.1 express patch

VMware vRealize Operations ManagerAdvanced or higher

vRealize Operations Manager 6.2.1

vRealize Operations ManagementPack for NSX for vSphere

3.0.2

vRealize Operations ManagementPack for vRealize Log Insight

1.0.1

vRealize Operations ManagementPack for vRealize Automation

2.0

vRealize Operations ManagementPack for Storage Devices

6.0.4

VMware vRealize Log Insight vRealize Log Insight 3.3.1

vRealize Log Insight Content Packfor NSX for vSphere

3.3

vRealize Log Insight Content Packfor Virtual SAN

2.0

vRealize Log Insight Content Packfor vRealize Automation 7.0

1.0

VMware, Inc. 15

Table 4‑1. VMware Software in the VMware Validated Design (Continued)

Product Group and Edition Product Name Product Version

vRealize Log Insight Content Packfor vRealize Orchestrator 7.0

1.1

vRealize Log Insight Content Packfor vRealize Operations Manager 6.x

1.6

VMware vSphere Data Protection VMware vSphere Data Protection 6.1.2

Product ConsiderationsUse the list of software components for VMware Validated Design under the certain considerations.

n VMware makes available patches and releases to address critical security issues for several products.Verify that you are using the latest security patches and releases for a given component whendeploying VMware Validated Design.

n Because this validated design version provides instructions for a single-region SDDC implementation,the list does not include the VMware products for disaster recovery, such as VMware Site RecoveryManager and vSphere Replication.


16 VMware, Inc.

Overview of the SDDC Structure 5The SDDC architecture in VMware Validated Design consists of layers. The layered structure enables you tocreate the SDDC in modules and to handle each set of components separately.

For information about the design and deployment of each layer, see VMware Validated Design ReferenceArchitecture Guide and VMware Validated Design Deployment Guide for Region A .

Figure 5‑1. Components of a Software-Defined Data Center

ServiceManagement

Portfolio Management

OperationsManagement

CloudManagement

Layer

Service Catalog

Self-Service Portal

Orchestration

BusinessContinuity

Fault Tolerance and Disaster

Recovery

Backup & Restore

Hypervisor

Pools of Resources

Virtualization Control

VirtualInfrastructure

Layer

Compute

Storage

Network

PhysicalLayer

Security

Replication Compliance

Risk

Governance

n Physical Infrastructure Layer on page 18The physical layer contains the compute, storage and network resources in your data center. Theseresources are organized in pods.

n Virtual Infrastructure Layer on page 20The virtual infrastructure layer contains the components that provide compute, networking andstorage resources to the management and tenant workloads.

n Cloud Management Layer on page 24The cloud management layer enables you to deliver tenants with automated workload provisioningby using a self-service portal.

n Operations Layer on page 25The operations layer of the SDDC provides capabilities for performance and capacity monitoring, andfor backup and restore of the cloud management components.

VMware, Inc. 17

Physical Infrastructure LayerThe physical layer contains the compute, storage and network resources in your data center. Theseresources are organized in pods.

Figure 5‑2. Physical Configuration of the SDDCSpineSwitch SpineSwitch SpineSwitch

ToR Switch ToR Switch ToR Switch ToR Switch

Compute pods

Management pod(4 ESXi hosts)

Edge pod(4 ESXi hosts)

External connection

ToR Switch ToR Switch

L2

L3

PodsA pod is a logical grouping of hardware that supports a certain function and is easy to replicate. Pods canhave different configurations of server, storage, and network equipment. Usually each pod spans one rack,but in smaller environments you can aggregate multiple pods into a single rack.

VMware Validated Design uses the following pods:

Management Pod Runs the virtual machines of the components that manage the SDDC, such asvCenter Server, NSX Manager, NSX Controller nodes, vRealize OperationsManagement, vRealize Log Insight, vRealize Automation, vRealizeOrchestrator and vRealize Business.

VMware Validated Design uses one management pods that occupies half arack.

Compute Pod Hosts the SDDC tenant workloads.

VMware Validated Design uses up to 6 compute pods, each pod occupyingone rack.

Edge Pod Compute pods are usually not set up with external network connectivity. Inthis case, external connectivity is pooled into edge pods. Edge pods connectthe virtual networks in NSX for vSphere and the external networks.

VMware Validated Design uses one edge pod that occupies half a rack.


18 VMware, Inc.

Regions and Availability ZonesAvailability zones and regions have different purposes.

Availability zone Represent the fault domain of the SDDC. Multiple availability zones canprovide continuous availability of an SDDC.

VMware Validated Design supports one availability zone per region.

Region Each region is a separate SDDC instance. You use multiple regions fordisaster recovery across individual SDDC instances.

In VMware Validated Design, regions have similar physical and virtualinfrastructure design but different naming.

Table 5‑1. Regions in VMware Validated Design

Region Disaster Recovery RoleRegion-SpecificDomain Name

Region A Protected sfo01.rainpole.local

Region B Recovery lax01.rainpole.local

NetworkVMware Validated Design uses a Layer 3 leaf-and-spine network architecture.

StorageVMware Validated Design provides guidance for the storage of the management components. The designuses two storage technologies:

n Virtual SAN. Virtual SAN storage is the default storage type for the SDDC management components.

The storage devices on Virtual SAN ready servers provide the storage infrastructure. Because VMwareValidated Design uses Virtual SAN in hybrid mode, each rack server must have one SSD and two HDDdevices that form a disk group with capacity .

n NFS. NFS storage is the secondary storage for the SDDC management components. It provides spacefor workload backup, archiving log data and application templates.

NFS storage required an NFS-capable external storage arrays.

Chapter 5 Overview of the SDDC Structure

VMware, Inc. 19

Virtual Infrastructure LayerThe virtual infrastructure layer contains the components that provide compute, networking and storageresources to the management and tenant workloads.

vCenter Server DesignTable 5‑2. vCenter Server Design Details

Design Area Description

vCenter Server instances You deploy two vCenter Server instances in the followingway:n One vCenter Server supporting the SDDC

management components.n One vCenter Server supporting the compute

components and workloads.Using this model provides the following benefits:n Isolation of management and compute operationsn Simplified capacity planningn Separated upgraden Separated roles

Clusters You distribute hosts and workloads in the followingclusters:n Management cluster that contains all management

hosts and handles resources for the managementworkloads.

n Edge cluster that contains the NSX Controller instancesand the NSX Edge services gateway devices for thecompute pod.

n Compute cluster that contains a set of hosts for tenantworkloads. The compute cluster configuration is forreference purposes.

Deployment model VMware Validated Design uses two Platform ServicesController instances and two vCenter Server instances. Forredundancy, the design joins the two Platform ServicesController instances to the same vCenter Single Sign-Ondomain, and points each vCenter Server instance to onePlatform Services Controller instance.


20 VMware, Inc.

Figure 5‑3. vCenter Server Cluster Layout

APPOS

APPOS

APPOS

APPOS

APPOS

APPOS

APPOS

APPOS

APPOS

APPOS

APPOS

APPOS

APPOS

APPOS

APPOS

APPOS

APPOS

APPOS

MgmtVC

Region AManagement Cluster

ESXi ESXi ESXi ESXi ESXi ESXi ESXi

Region ACompute / Edge Cluster

Region BManagement Cluster

Region BCompute / Edge Cluster

PSC

ComputeVC

PSC

MgmtVC

ESXi ESXi ESXi ESXi ESXi ESXi ESXi

PSC

ComputeVC

PSC

Dynamic Routing and Application Virtual NetworksVMware Validated Design supports dynamic routing for both management and compute workloads, andalso introduces a model of isolated application networks for the management components.

Dynamic routing support includes the following nodes:

n Pair of NSX Edge service gateways (ESGs) with ECMP enabled for north/south routing across allregions.

n Universal distributed logical router (UDLR) for east/west routing across all regions.

Application virtual networks provide support for limited access to the nodes of the applications throughpublished access points. Three application virtual networks exist:

n Common application virtual network that connects the components that are designed to fail over to arecovery region.

n Application virtual network in Region A for components that are not designed to fail over.

n Application virtual network in Region B for components that are not design to fail over.


VMware, Inc. 21

Figure 5‑4. Virtual Application Network Components and Design

VC

OSPSC

OSSRM

OSVDP

OS

ECMPESG's

ToR Switches

Internet/EnterpriseNetwork

Mgmt-Management

Compute-Management

Legend:

EdgePODs

ComputePODs

192.168.11/24

Edge-Management

Transit Networks

Management Application

vRLIvROps CollectorvRA Proxy

vRA/vRO/vRBvROps

Universal Distributed Logical Router

ESGLoadBalancer

Mgmt-xRegion01-VXLAN

192.168.31/24

Mgmt-xRegionА01-VXLAN

Software-Defined Storage Design for Management ProductsWorkloads on the management and edge clusters store their data on cluster-specific Virtual SAN datastores.Each Virtual SAN datastore spans all 4 ESXi hosts of each cluster, and each host adds one disk group to thedatastore.

Applications store their data according to the default storage policy for Virtual SAN.


22 VMware, Inc.

Figure 5‑5. Virtual SAN Conceptual Design

APP

OSAPP

OS

APP

OSAPP

OS

APP

OSAPP

OS

APP

OSAPP

OSAPP

OSAPP

OS

APP

OSAPP

OSAPP

OSAPP

OS

ESXi

APP

OSAPP

OS

ESXi ESXi

Virtual InfrastructureManagement

ESXi ESXi ESXi

NSXController

(Mgmt)

OtherManagementApplications

NSXEdge

(Mgmt)

NSXManager(Mgmt)

NSXManager

(Compute)

NSXEdge

(Compute)

NSXController(Compute)

ESXi ESXi ESXi ESXi ESXi ESXi

SDDC Payload

Virtual Infrastructure Compute Edge

Edge ClusterCompute Cluster Management Cluster

Managed by: Compute vCenter Server Managed by: Management vCenter Server

Network: External(Internet/MPLS)

Network: Internal SDDCFabric (Spine/Leaf)

Compute Pod Management/Edge Pod

vCenterServer(Mgmt)

vCenterServer

(Compute)

No Virtual SAN Used Here Virtual SAN Datastore (Edge) Virtual SAN Datastore (Management)

vSphere Data Protection, vRealize Log Insight and vRealize Automation Content Library use NFS exports.You create two datastores: one in the management cluster for vSphere Data Protection and one in thecompute cluster for vRealize Automation.

Figure 5‑6. NFS Storage Exports

Region A

NFS Storage Array

Volume 1 Volume 2

Export(vRealize

Automation)

Export(vRealize

Log Insight)

Export(vSphere

Data Protection)

NFS Storage Array

Volume 1 Volume 2

Export(vRealize

Automation)

Export(vRealize

Log Insight)

Export(vSphere

Data Protection)

Region B


VMware, Inc. 23

Cloud Management LayerThe cloud management layer enables you to deliver tenants with automated workload provisioning byusing a self-service portal.

Table 5‑3. Cloud Management Design Details

Design Attribute Description

Software components n vRealize Automationn vRealize Orchestratorn vRealize Business

Deployment model of vRealize Automation Distributed deployment with support for vSphereendpoints by using vSphere Proxy Agent virtual machines.You install the vRealize Automation components onmultiple machines.

High availability and load balancing Supported for all nodes except the Microsoft SQL databaseserver and vRealize Business.

Endpoints n vCenter Server for the management clustern vCenter Server for the compute and edge clusters

Blueprint configuration Single-machine blueprints

Tenants A single tenant company called Rainpole.

Fabric groups One fabric group in a region with all resources in thecompute and edge cluster assigned.

Business groups Two business groups, one for production and one fordevelopment.


24 VMware, Inc.

Figure 5‑7. vRealize Automation Tenant Design

Production Business Group

Rainpole Tenanthttps://vra.mycompany.com/vcac/org/rainpole

Business Group Manager

Development Business Group

TenantAdminBusiness Group

Manager

Fabric Admin

IaaSAdmin

ProdReservation

DevReservation

EdgeReservation

Region A Fabric Group

ProdReservation

DevReservation

EdgeReservation

Region B Fabric Group

Region A Data Center Infrastructure Fabric

Region B Data Center Infrastructure Fabric

https://vra.mycompany.com/vcac

• Tenant Creation• System Branding• System Notification Providers• Event LogsSystem Admin

Default Tenant

Fabric Admin

Operations LayerThe operations layer of the SDDC provides capabilities for performance and capacity monitoring, and forbackup and restore of the cloud management components.

vRealize Operations ManagerYou use vRealize Operations Manager to monitor the management components of the SDDC includingvSphere, NSX for vSphere and vRealize Automation.

vRealize Operations Manager is also sized to accommodate the number of tenant workloads per the designobjectives.


VMware, Inc. 25

Figure 5‑8. vRealize Operations Manager Logical Design

RemoteCollector

RemoteCollector

Management/Compute

vCenter Server

vRealizeAutomation

Remote Collector Cluster

RemoteCollector

NSX

Analytics Cluster

Management/Compute

vCenter Server

NSX

Region A Region B

RemoteCollector

Shared Storage

Remote Collector Cluster

Master MasterReplica Data Data

Shared Storage

Table 5‑4. vRealize Operations Manager Design Details


Deployment model n Analytics cluster of four nodes: master, master replicaand two data nodes

n Remote collector cluster that consists of two remotecollectors that communicate with two vCenter Serverinstances in the region

Monitored components n vCenter Server and Platform Services Controllern Management, Edge and Compute ESXi hostsn All components of NSX for vSphere for the

management and compute clustersn vRealize Automation and vRealize Orchestratorn vRealize Log Insightn vRealize Operations Manager (Self Health Monitoring)

vRealize Log InsightYou use vRealize Log Insight to access the logs of the SDDC management components from a central placeand view this information in visual dashboards.


26 VMware, Inc.

Figure 5‑9. vRealize Log Insight Logical Design

Management/Compute

vCenter Server

vRealizeAutomation

vRealize Log Insight Cluster

Master Worker Worker

NSX

vRealize Operations

Manager

event forwarding

VMDK Storage(Virtual

SAN or NAS)

Archiving Storage(NAS)

Management/Compute

vCenter Server

vRealize Log Insight Cluster

Master Worker Worker

NSX

VMDK Storage(Virtual

SAN or NAS)

Archiving Storage(NAS)

Region A Region B

Table 5‑5. vRealize Log Insight Design Details


Deployment model Cluster of master node and two worker nodes.

Monitored components n vCenter Server and Platform Services Controllern Management, Edge and Compute ESXi hostsn All components of NSX for vSphere for the

management and compute clustersn vRealize Automation and vRealize Orchestratorn Analytics cluster nodes of vRealize Operations

Manager

Archiving Archiving location on an NFS export

vSphere Data ProtectionYou deploy vSphere Data Protection to backup the virtual machines of the SDDC management components.vSphere Data Protection stores its data and the backup copies of virtual machines on the NFS datastore inthe management cluster.


VMware, Inc. 27

Figure 5‑10. vSphere Data Protection Design

VM VM

Authentication

Platform Services Controller

vCenter Server

vSphere Data ProtectionRegion A

vSphere Data ProtectionVM Snapshot/Backup Agent

Backup Datastore

Authentication

Platform Services Controller

vCenter Server

vSphere Data ProtectionRegion B

vSphere Data ProtectionVM Snapshot/Backup Agent

Backup Datastore


28 VMware, Inc.

Index

Bbill of material 15

Ddesign objectives 9documentation

guides 11flow 11structure 11

documentation overview 5

Gglossary 5

Iintended audience 5

Mmain features 7

SSDDC

application virtual network 20architecture 17backup and restore 25capabilities 9cloud management 24dynamic routing 20layers 17logging 25monitoring and alerting 25NFS 20operations 25physical infrastructure 18pods 18regions 18service catalog 24software components 15software-defined networking 20software-defined storage 20tenant configuration 24virtual infrastructure 20Virtual SAN 20

VMware, Inc. 29


30 VMware, Inc.

introducing vmware validated designs for software …...introducing vmware validated designs for...

Documents