Vmware Validated Design 20 Introduction Guide

Introducing VMware Validated Designs
for Software-Defined Data Center

VMware Validated Design for Software-Defined Data Center 2.0
This document supports the version of each product listed and

supports all subsequent versions until the document is
replaced by a new edition. To check for more recent editions
of this document, see http://www.vmware.com/support/pubs.
EN-002170-00
Introducing VMware Validated Designs for Software-Defined Data Center
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:
docfeedback@vmware.com
Copyright © 2016 VMware, Inc. All rights reserved. Copyright and trademark information.
VMware, Inc.
3401 Hillview Ave.
Palo Alto, CA 94304
www.vmware.com
2 VMware, Inc.
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 18
Virtual Infrastructure Layer 20
Cloud Management Layer 24
Operations Layer 25
Index 29
VMware, Inc. 3
4 VMware, Inc.
About Introducing VMware Validated Design for
Software-Defined Data Center
The Introducing VMware Validated Design for Software-Defined Data Center guide provides directions on using
the content of VMware Validated Design™ for Software-Defined Data Center. The guide also contains a
high-level overview of the Software-Defined Data Center (SDDC) design supported in this VMware
Validated Design version.
Introducing VMware Validated Design for Software-Defined Data Center focuses on providing guidance about
using 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 Audience
Introducing 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 with
VMware Validated Design to deploy and manage an SDDC that meets the requirements for capacity,
scalability, business continuity and disaster recovery.
VMware Technical Publications Glossary

VMware Technical Publications provides a glossary of terms that might be unfamiliar to you. For definitions
of terms as they are used in VMware technical documentation, go to
http://www.vmware.com/support/pubs.
VMware, Inc. 5
6 VMware, Inc.
Overview of VMware Validated
Designs 1
Use VMware Validated Design to create a Software-Defined Data Center that is based on management
components 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 to
deploy an SDDC.
SDDC design for use in VMware Validated Design supports an SDDC that has the following
production features:
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 and The prescriptive documentation of VMware Validated Design is

deployment continuously validated by VMware. Validation provides the following
advantages to your organization:
n Validated product interoperability
n Validated SDDC features, such as custom workload churn, high

availability of management components, operational continuity, efficient
monitoring, 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 and
step-by-step instructions, you are able to implement a data center without
engaging in design work and product research.
Support for latest Every version of VMware Validated Design accommodates new product
product releases releases.
Foundation for VMware Validated Design provides the foundation for use cases that satisfy
development of SDDC the requirements of individual organizations or industry segments, such as
deployment use cases SDDC for microsegmentation, DevOps and automated IT.
VMware, Inc. 7
8 VMware, Inc.
Solution Overview and Design
Objectives 2
VMware Validated Design has a number of objectives to deliver prescriptive content about an SDDC that is
fast 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 management

components.
Cloud type Private cloud
Number of regions and disaster recovery support n The design documentation provides guidance for an
SDDC that is capable of supporting a dual-region case
for failover.
n The deployment documentation provides guidance for
an SDDC that supports a single region for both
management and tenant workloads.
By design, the SDDC management components can operate
in an environment that supports failover in a dual-region
environment with one availability zone. See “Physical
Infrastructure Layer,” on page 18.
Maximum number of virtual machines n 10,000 running virtual machines

n Churn rate of 150 virtual machines per hour
Churn rate is related to provisioning, power cycle
operations, and decommissioning of one tenant virtual
machine by using a blueprint in the cloud management
platform. A churn rate of 100 means that 100 tenant
workloads are provisioned, pass the power cycle
operations, and are deleted.
Number of hardware pods 3-pod setup

The validated design requires the following pods for SDDC
deployment:
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 virtualization

n Software-defined storage in the management and edge
pods
n 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 management

pod.
n Number of hosts, amount of storage and configuration
n Deployment and initial setup of management
components at the levels of infrastructure, cloud
management platform, and operations.
n Basic tenant operations such as creating a tenant,
assigning tenant capacity, configuring user access, and
adding virtual machines to a service catalog from
single-machine blueprints.
n Operations on the management components of the
SDDC such as monitoring and alerting, backup and
restore, and post-maintenance validation.
Overall availability 99% availability

Planned downtime is expected for upgrades, patching, and
on-going maintenance.
Authentication, authorization, and access control n Use of Microsoft Active Directory as a central user
repository.
n Use of service accounts with minimum required
authentication 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 the

management traffic.
10 VMware, Inc.
Documentation Structure and
Audience 3
The structure of the VMware Validated Design documentation reflects the best practices in designing and
deploying a data center that is capable of automated provisioning of workloads. The documentation
components of the validated design are organized according to audience and deployment stage, and you
use them in a specific order.
Figure 3‑1. VMware Validated Design Documentation Flow

Start
Design Phase
Architecture Overview
Detailed Design
Reference Architecture
Deployment Phase
Planning and Preparation
Deployment Guide for Region A
Operations Phase
Operational Guidance
Architecture Overview
The first part of VMware Validated Design is Architecture Overview and it introduces the terms and
components 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 the

SDDC design.
n Provide information about the layered structure of the
SDDC.
n Describe the building modules and basic behavior of
each management component.
Audience Cloud architects and cloud administrators
Detailed Design
After you learn about the basic modules in the SDDC design, you proceed with detailed design of the
management 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 of

each layer and of the components that are a part of the
layer.
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 Preparation

After you understand the details of the design, you plan your environment according to the requirements of
the design so that you can deploy the designed SDDC directly without additional testing and
troubleshooting efforts.
Table 3‑3. Planning and Preparation Information

Guide VMware Validated Design Planning and Preparation Guide
Purpose Collect all requirements that your environment must meet

so that you can follow VMware Validated Design to create
an SDDC. The Planning and Preparation section provides
prerequisites for the following areas:
n Required software including VMware products, scripts
and third-party software
n Networking configuration including VLANs, example
IP addresses and DNS names
n Active Directory user configuration
n Specifications of the virtual machines that you must
provide in advance
Audience Cloud architects, infrastructure administrators, cloud

administrators and cloud operators
12 VMware, Inc.
Chapter 3 Documentation Structure and Audience
Deployment Guide for Region A

After you make sure that your environment has the required structure and configuration, follow the
Deployment 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 management

component of the SDDC according to the selected
design 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 tenant
workloads.
n Provide procedures for integration of the products to
form one functional system.

Operational Guidance
After you deploy the SDDC, follow the Operational Guidance documentation to operate the environment and
the management workloads .
Table 3‑5. Operational Guidance Information

Guide VMware Validated Design Operational Guidance that is

delivered as a set of add-on packages.
Purpose For each management component, provide the following

information:
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, and
lists of notifications that are most symptomatic.
n Step-by-step instructions about validating the
operation of the SDDC after software maintenance
such as restore, upgrade or failover .

VMware, Inc. 13
14 VMware, Inc.
VMware Software Components in the
Validated Design 4
VMware Validated Design is based on a set of individual VMware products with different versions that are
available 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 or Virtual SAN 6.2

higher
VMware NSX for vSphere Enterprise NSX for vSphere 6.2.2
VMware vRealize Automation vRealize Automation 7.0.1

Advanced or higher
vRealize Orchestrator 7.0.1
vRealize Orchestrator Plug-in for 1.0.3

NSX
v Realize Orchestrator Plug-in for 7.0.1

vRealize Automation 7.0.1
VMware vRealize Business for Cloud VMware vRealize Business for Cloud 7.0.1 and 7.0.1 express patch
Standard
VMware vRealize Operations Manager vRealize Operations Manager 6.2.1

Advanced or higher
vRealize Operations Management 3.0.2
Pack for NSX for vSphere

Pack for vRealize Log Insight
vRealize Operations Management 2.0

Pack for vRealize Automation

Pack for Storage Devices
VMware vRealize Log Insight vRealize Log Insight 3.3.1
vRealize Log Insight Content Pack 3.3

for NSX for vSphere

for Virtual SAN

for vRealize Automation 7.0
VMware, Inc. 15
Table 4‑1. VMware Software in the VMware Validated Design (Continued)

Product Group and Edition Product Name Product Version

for vRealize Orchestrator 7.0

for vRealize Operations Manager 6.x
VMware vSphere Data Protection VMware vSphere Data Protection 6.1.2
Product Considerations
Use 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 when
deploying 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 Recovery
Manager and vSphere Replication.
16 VMware, Inc.
Overview of the SDDC Structure 5
The SDDC architecture in VMware Validated Design consists of layers. The layered structure enables you to
create 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 Reference
Architecture Guide and VMware Validated Design Deployment Guide for Region A .
Figure 5‑1. Components of a Software-Defined Data Center
Service Cloud Service Catalog Business Security

Management Management Continuity
Layer
Self-Service Portal
Orchestration
Virtual Hypervisor Fault Tolerance

Infrastructure
and Disaster Governance
Layer Pools of Resources Recovery
Virtualization Control
Portfolio Backup &
Risk
Management Restore
Physical Compute
Layer
Storage
Operations
Replication Compliance
Management Network
n Physical Infrastructure Layer on page 18

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

The virtual infrastructure layer contains the components that provide compute, networking and
storage resources to the management and tenant workloads.
n Cloud Management Layer on page 24

The cloud management layer enables you to deliver tenants with automated workload provisioning
by using a self-service portal.
n Operations Layer on page 25

The operations layer of the SDDC provides capabilities for performance and capacity monitoring, and
for backup and restore of the cloud management components.
VMware, Inc. 17
Physical Infrastructure Layer

The physical layer contains the compute, storage and network resources in your data center. These
resources are organized in pods.
Figure 5‑2. Physical Configuration of the SDDC

SpineSwitch SpineSwitch SpineSwitch
External connection
ToR Switch ToR Switch ToR Switch ToR Switch ToR Switch ToR Switch
L3
L2
Management pod(4 ESXi hosts)
Edge pod(4 ESXi hosts)
Compute pods
Pods
A pod is a logical grouping of hardware that supports a certain function and is easy to replicate. Pods can
have 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 as
vCenter Server, NSX Manager, NSX Controller nodes, vRealize Operations
Management, vRealize Log Insight, vRealize Automation, vRealize
Orchestrator and vRealize Business.
VMware Validated Design uses one management pods that occupies half a
rack.
Compute Pod Hosts the SDDC tenant workloads.
VMware Validated Design uses up to 6 compute pods, each pod occupying

one rack.
Edge Pod Compute pods are usually not set up with external network connectivity. In
this case, external connectivity is pooled into edge pods. Edge pods connect
the 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.
Chapter 5 Overview of the SDDC Structure
Regions and Availability Zones

Availability zones and regions have different purposes.
Availability zone Represent the fault domain of the SDDC. Multiple availability zones can
provide 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 for
disaster recovery across individual SDDC instances.
In VMware Validated Design, regions have similar physical and virtual

infrastructure design but different naming.
Table 5‑1. Regions in VMware Validated Design

Region-Specific
Region Disaster Recovery Role Domain Name
Region A Protected sfo01.rainpole.local
Region B Recovery lax01.rainpole.local
Network
VMware Validated Design uses a Layer 3 leaf-and-spine network architecture.
Storage
VMware Validated Design provides guidance for the storage of the management components. The design
uses 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 VMware
Validated Design uses Virtual SAN in hybrid mode, each rack server must have one SSD and two HDD
devices that form a disk group with capacity .
n NFS. NFS storage is the secondary storage for the SDDC management components. It provides space
for workload backup, archiving log data and application templates.
NFS storage required an NFS-capable external storage arrays.
VMware, Inc. 19
Virtual Infrastructure Layer

The virtual infrastructure layer contains the components that provide compute, networking and storage
resources to the management and tenant workloads.
vCenter Server Design

Table 5‑2. vCenter Server Design Details
Design Area Description
vCenter Server instances You deploy two vCenter Server instances in the following
way:
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 operations
n Simplified capacity planning
n Separated upgrade
n Separated roles
Clusters You distribute hosts and workloads in the following

clusters:
n Management cluster that contains all management
hosts and handles resources for the management
workloads.
n Edge cluster that contains the NSX Controller instances
and the NSX Edge services gateway devices for the
compute pod.
n Compute cluster that contains a set of hosts for tenant
workloads. The compute cluster configuration is for
reference purposes.
Deployment model VMware Validated Design uses two Platform Services

Controller instances and two vCenter Server instances. For
redundancy, the design joins the two Platform Services
Controller instances to the same vCenter Single Sign-On
domain, and points each vCenter Server instance to one
Platform Services Controller instance.
20 VMware, Inc.
Figure 5‑3. vCenter Server Cluster Layout

Region A Region A Region B Region B
Management Cluster Compute / Edge Cluster Management Cluster Compute / Edge Cluster
APP APP APP APP APP APP

PSC PSC PSC PSC
OS OS OS OS OS OS

Mgmt Compute Mgmt Compute
OS OS OS OS OS OS
VC VC VC VC

OS OS OS OS OS OS
ESXi ESXi ESXi ESXi ESXi ESXi ESXi ESXi ESXi ESXi ESXi ESXi ESXi ESXi
Dynamic Routing and Application Virtual Networks

VMware Validated Design supports dynamic routing for both management and compute workloads, and
also 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 all
regions.
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 through
published access points. Three application virtual networks exist:
n Common application virtual network that connects the components that are designed to fail over to a
recovery 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

Legend:
Transit Networks
Compute-Management
Edge-Management
Management Application
Mgmt-Management
Internet/
Enterprise Compute Edge
Network PODs PODs
VC PSC SRM VDP

OS OS OS OS
ToR
Switches
ECMP
ESG's
Universal Distributed Logical Router
ESG
Load
Balancer
192.168.11/24 192.168.31/24
Mgmt-xRegion01-VXLAN Mgmt-xRegionА01-VXLAN
vROps vRLI
vRA/vRO/vRB vROps Collector
vRA Proxy
Software-Defined Storage Design for Management Products

Workloads 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 the
datastore.
Applications store their data according to the default storage policy for Virtual SAN.
22 VMware, Inc.
Figure 5‑5. Virtual SAN Conceptual Design
Virtual Infrastructure Other

Management Management
Applications
APP APP
OS OS
NSX NSX
Controller Edge
(Mgmt) (Mgmt)
APP APP APP APP
OS OS OS OS
NSX NSX
Virtual Infrastructure Manager Manager
Compute Edge (Compute) (Mgmt)
APP APP APP APP

SDDC Payload APP APP
OS OS
OS OS
OS OS
APP APP APP APP NSX NSX vCenter vCenter

OS OS OS OS
Controller Edge Server Server
(Compute) (Compute) (Compute) (Mgmt)
No Virtual SAN Used Here Virtual SAN Datastore (Edge) Virtual SAN Datastore (Management)
Managed by: Compute vCenter Server Managed by: Management

vCenter Server
Compute Cluster Edge Cluster Management Cluster
ESXi ESXi ESXi ESXi ESXi ESXi ESXi ESXi ESXi ESXi ESXi ESXi
Network: Internal SDDC

Fabric (Spine/Leaf)
Network: External
(Internet/MPLS)
Compute Pod Management/Edge Pod
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 the
compute cluster for vRealize Automation.
Figure 5‑6. NFS Storage Exports
Region A Region B
NFS Storage Array NFS Storage Array
Volume 1 Volume 2 Volume 1 Volume 2

Export Export Export Export Export Export
(vRealize (vRealize (vSphere (vRealize (vRealize (vSphere
Automation) Log Insight) Data Protection) Automation) Log Insight) Data Protection)
VMware, Inc. 23
Cloud Management Layer

The cloud management layer enables you to deliver tenants with automated workload provisioning by
using a self-service portal.
Table 5‑3. Cloud Management Design Details

Design Attribute Description
Software components n vRealize Automation

n vRealize Orchestrator
n vRealize Business
Deployment model of vRealize Automation Distributed deployment with support for vSphere
endpoints by using vSphere Proxy Agent virtual machines.
You install the vRealize Automation components on
multiple machines.
High availability and load balancing Supported for all nodes except the Microsoft SQL database
server and vRealize Business.
Endpoints n vCenter Server for the management cluster

n 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 the
compute and edge cluster assigned.
Business groups Two business groups, one for production and one for
development.
24 VMware, Inc.
Figure 5‑7. vRealize Automation Tenant Design
Rainpole Tenant
https://vra.mycompany.com/vcac/org/rainpole
Production Business Group Development Business Group

Tenant
Business Group Business Group Admin
Manager Manager
Prod Dev Edge Prod Dev Edge

Reservation Reservation Reservation Reservation Reservation Reservation
IaaS
Admin
Region A Fabric Group Region B Fabric Group
Fabric Admin Fabric Admin
Region A Region B
Data Center Infrastructure Fabric Data Center Infrastructure Fabric
Default Tenant
• Tenant Creation
• System Branding
• System Notification
Providers
System Admin • Event Logs
https://vra.mycompany.com/vcac
Operations Layer
The operations layer of the SDDC provides capabilities for performance and capacity monitoring, and for
backup and restore of the cloud management components.
vRealize Operations Manager

You use vRealize Operations Manager to monitor the management components of the SDDC including
vSphere, NSX for vSphere and vRealize Automation.
vRealize Operations Manager is also sized to accommodate the number of tenant workloads per the design
objectives.
VMware, Inc. 25
Figure 5‑8. vRealize Operations Manager Logical Design
Region A Region B
Management/ vRealize Management/
Compute Automation Compute
vCenter Server vCenter Server
NSX Remote Collector Cluster Remote Collector Cluster NSX
Remote Remote Remote Remote

Collector Collector Collector Collector
Shared Shared
Storage Storage
Analytics Cluster
Master
Master Data Data
Replica
Table 5‑4. vRealize Operations Manager Design Details

Deployment model n Analytics cluster of four nodes: master, master replica

and two data nodes
n Remote collector cluster that consists of two remote
collectors that communicate with two vCenter Server
instances in the region
Monitored components n vCenter Server and Platform Services Controller

n Management, Edge and Compute ESXi hosts
n All components of NSX for vSphere for the
management and compute clusters
n vRealize Automation and vRealize Orchestrator
n vRealize Log Insight
n vRealize Operations Manager (Self Health Monitoring)
vRealize Log Insight

You use vRealize Log Insight to access the logs of the SDDC management components from a central place
and view this information in visual dashboards.
26 VMware, Inc.
Figure 5‑9. vRealize Log Insight Logical Design
Region A Region B
Management/ vRealize Management/
Compute Automation Compute
NSX vRealize Log Insight Cluster vRealize Log Insight Cluster NSX
event
forwarding
Master Worker Worker Master Worker Worker

vRealize
Operations
Manager
VMDK Storage Archiving VMDK Storage Archiving

(Virtual Storage (Virtual Storage
SAN or NAS) (NAS) SAN or NAS) (NAS)
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 Controller

n Management, Edge and Compute ESXi hosts
n All components of NSX for vSphere for the
management and compute clusters
n vRealize Automation and vRealize Orchestrator
n Analytics cluster nodes of vRealize Operations
Manager
Archiving Archiving location on an NFS export
vSphere Data Protection

You 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 in
the management cluster.
VMware, Inc. 27
Figure 5‑10. vSphere Data Protection Design
Authentication Authentication
Platform Services Controller Platform Services Controller
vSphere Data Protection vSphere Data Protection

Region A Region B
vSphere Data Protection vSphere Data Protection

VM VM Snapshot/ VM VM Snapshot/
Backup Agent Backup Agent
Backup Datastore Backup Datastore
28 VMware, Inc.
Index
B
bill of material 15
D
design objectives 9
documentation
guides 11
flow 11
structure 11
documentation overview 5
G
glossary 5
I
intended audience 5
M
main features 7
S
SDDC
application virtual network 20
architecture 17
backup and restore 25
capabilities 9
cloud management 24
dynamic routing 20
layers 17
logging 25
monitoring and alerting 25
NFS 20
operations 25
physical infrastructure 18
pods 18
regions 18
service catalog 24
software components 15
software-defined networking 20
software-defined storage 20
tenant configuration 24
virtual infrastructure 20
Virtual SAN 20
VMware, Inc. 29
30 VMware, Inc.

Vmware Validated Design 20 Introduction Guide

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Vmware Validated Design 20 Introduction Guide

Uploaded by

Copyright:

Available Formats

Introducing VMware Validated Designs

for Software-Defined Data Center

This document supports the version of each product listed and

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

n Document structure and purpose

n Supported VMware product versions

n SDDC design overview

VMware Technical Publications Glossary

VMware Validated Design has the following advantages:

n High-availability of management components

n Monitoring and alerting

n Opportunity to extend the deployment to support disaster recovery

Validated design and The prescriptive documentation of VMware Validated Design is

n Validated product interoperability

n Validated SDDC features, such as custom workload churn, high

n Reduced risk of deployment and operational problems

n Reduced test effort

Table 2‑1. Objectives of VMware Validated Design

Main objective SDDC capable of automated provisioning of workloads

Scope of deployment Greenfield deployment of the SDDC management

Cloud type Private cloud

Maximum number of virtual machines n 10,000 running virtual machines

Number of hardware pods 3-pod setup

Data center virtualization n Compute virtualization

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

Scope of guidance n Storage, compute and networking for the management

Overall availability 99% availability

Certificate signing Certificates are signed by an external certificate authority

Hardening Tenant workload traffic can be separated from the

Figure 3‑1. VMware Validated Design Documentation Flow

Planning and Preparation

Deployment Guide for Region A

Table 3‑1. Architecture Overview Information

Guide VMware Validated Design Reference Architecture Guide

Purpose n Introduce the fundamentals and components in the

Audience Cloud architects and cloud administrators

Table 3‑2. Detailed Design Information

Guide VMware Validated Design Reference Architecture Guide

Purpose n Provide complete details about the configuration of

Audience Cloud architects and cloud administrators

Planning and Preparation

Table 3‑3. Planning and Preparation Information

Guide VMware Validated Design Planning and Preparation Guide

Purpose Collect all requirements that your environment must meet

Audience Cloud architects, infrastructure administrators, cloud

Deployment Guide for Region A

Table 3‑4. Deployment Guide Information

Guide VMware Validated Design Deployment Guide for Region A

Purpose n Provide step-by-step instructions for each management

Audience Cloud architects, infrastructure administrators, cloud

Table 3‑5. Operational Guidance Information

Guide VMware Validated Design Operational Guidance that is

Purpose For each management component, provide the following

Audience Cloud architects, infrastructure administrators, cloud

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

VMware vSphere Enterprise Plus ESXi 6.0 Update 2

vCenter Server Appliance (ISO) 6.0 Update 2

VMware Virtual SAN Standard or Virtual SAN 6.2