VMware技术销售专家(VTSP)3
- 格式:docx
- 大小:23.86 KB
- 文档页数:6
Ready NodesVMWare Virtual SANVMware's Virtual SAN (vSAN) brings performance, low cost and scalability to virtual cloud deployments running on HPE hardware. An issue the cloud deployment model raises is the problem of adequate storage performance to virtual instances. Spinning disks and limited bandwidth networks lower IO rates over local drives. VMware’s solution to this is vSAN, which adds a temporary local storage “instance” in the form of a solid-state drive to each server. vSAN extends the concept of local instance storage to a shareable storage unit in each HPE server, where additionally, the data can be accessed by other servers over a LAN. The benefits of VSAN include:• Increased performance due to local server access to Flash storage• Lower infrastructure cost by removing the need for networked storage appliances • Highly scalable --simply add more servers to increase storage • Eliminate boot storms since data is stored locally• Unified management --no storage silo versus server silo separation problemsMellanox 10/25G Ethernet interconnect solutions enable unmatched competitive advantages in VMware environments by increase efficiency of overall server utilization and eliminating I/O bottleneck to enable more virtual machines per server, faster migrations and speed access to storage. Explore this reference guide to learn more about how Mellanox key technologies can help improve efficiencies in your vSAN environment. Higher Efficiency RoCE CertifiedWithout Offloads With Mellanox Offloads Efficient Hardware OffloadsA variety of new workloads and technologies areincreasing the load on CPU utilization. Overlay networks protocols, OVS processing, access to storage and others are placing a strain on VMware environments. High performance workloads require intensiveprocessing which can waste CPU cycles, and choke networks. The end result is that application efficiency is limited and virtual environments as a whole become inefficient. Because of these challenges, data center administrators now look to alleviate CPU loads by implementing intelligent network components that can ease CPU strain, increase network bandwidth and enable scale and efficiency in virtual environments.Mellanox interconnects can reduce the burden byoffloading many networking tasks, thereby freeing CPU resources to serve more VMs and process more data. Side-by-side comparison shows over a 70% reduction in CPU resources and a 40% improvement in bandwidth.Reduce CPU OverheadvSphere 6.5, introduced Remote Direct Memory Access over Converged Ethernet (RoCE). RoCE allows direct memory access from one computer to another without involving the operating system or CPU. The transfer of data is offloaded to a RoCE-capable adapter, freeing the CPU from the data transfer process and reducing latencies. For virtual machines a PVRDMA (para-virtualized RDMA) network adapter is used tocommunicate with other virtual machines. Mellanox adapters are certified for both in vSphere.Without Offloads With OffloadsRoCE dramatically accelerates communication between two network endpoints but also requires a switch that is configured for lossless traffic. RoCE v1 operates overlossless layer 2 and RoCE v2 supports layer 2 and layer 3. To ensure a lossless environment, you must be able to control the traffic flows. Mellanox Spectrum switchessupport Priority Flow Control (PFC) and Explicit Congestion Notification (ECN) which enables a global pause across the network to support RDMA. Once RoCE is setup onvSphere close-to-local, predictable latency can be gained from networked storage along with line-rate throughput and linear scalability. This helps to accommodate dynamic, agile data movement between nodes.HPE StoreFabric M-series and Mellanox ConnectX adapter solutions for VMWareProven PerformanceRDMA for vSAN and Ne x t-Gen StorageRDMA (Remote Direct Memory Access) allows two system to connect sub-OS directly to memory without requiring CPU cycles. This enables high bandwidth, increased IOPS, and low latencyconnectivity, which accelerates workloads running on parallel systems better than traditional TCP/IP connectivity.RDMA benefits to vSAN clusters include:•Improved app performance•Improved resync/rebuild/rebalance time •NVMe-oF technology enablement •Better VM consolidation•Improves cloning and vMotion operations times •Faster metadata updates across vSAN hostsMellanox End-to-End vSAN SolutionHyperconvergedReduce CapExHypeconverged deployments, like HPE SimpliVity and HPESynergy, are a demandingenvironment for networkinginterconnects. These consist ofthree software components: compute virtualization, storage virtualization and management, in which all three require an agile and responsive network.Deploying on 25G networks, like offered with Mellanox ConnectX adapters, assists with offload capabilities to optimizeperformance and availability of synchronization and replication ofvirtualized workloads .CapEx Analysis: 10G vs 25G Mellanox adapters and switchesaccelerate VM resources to improveperformance, enhance efficiency and provide high-availability and are a must-have feature for any VMware and hyperconverged environment. Deployment ConfigsEthernet AdaptersNetwork ManagementHPE vSAN Ready node AF-86x HPE 640FLR-SFP2810/25 2p ConnectX-4Lx(included in ReadyNode bundle)Just Add HPE StoreFabric M-series ToR 2x HPE StoreFabric SN2010M18 x 10/25G SFP + 4 x 40/100G QSFP up ½ width ToR switch means Full HA in 1UvSAN vSphere VMVMVMVMVMVM VM3x HPE DL380 Gen10 with SAS Exp.36x 32GB DDR415x HPE 1.6TB SAS WI SFF SSD 75x HPE 3.2TB SAS MU SFF SSD3x HPE Smart Array P816-a Gen10 12G 3c Dual 8GB microSD USB kitSKU: DL380Gen10_Expander_SAS_AF8-1HPE vSAN ReadyNode RAUp to 80TB in 7U including ToR▪Enable near-native performance for VMs thru stateless offloads▪Extend hardware resources w/ ROCE (RDMA over converged Ethernet)▪Accelerate virtualized networks with VXLAN, GENEVE & NVGRE▪Align network services with compute services for multitenant network supportHPE 640SFP282p 10/25G Ethernet HPE 842QSFP281p 100G EthernetHPE Smart Fabric Orchestrator ▪Visibility –topology view + in-band activity monitoring▪Automation –template based deployment and self healing▪Compliance –Interop validation with HPE SPOCK▪Reports –Fabric Reports + Ad-hoc reportingMonitoring▪Performance monitoring ▪Health monitoring ▪Detailed telemetry ▪Alerts and notificationsThere are over 20 HPE vSAN ReadyNodes with Mellanox Adapters, including:RDMARDMAVMWare vSAN works BEST on Mellanox RDMA enabled adapters and switches•DL380Gen10_All_NVMe_AF4 –1•DL380Gen10_All_NVMe_AF4 –2•DL360Gen10_SAS_AF4 –1•DL380Gen10_SAS_AF4 –1•DL380Gen10_All_NVMe_AF6 –1•DL380Gen10_All_NVMe_AF6 -2•DL360Gen10_SAS_AF6 -1•DL380Gen10_SAS_AF6 –1•DL360Gen10_SAS_AF8 –1•DL380Gen10_All_NVMe_AF8 –1•DL380Gen10_All_NVMe_AF8 –2•DL380Gen10_Expander_SAS_AF8 -1•DL360Gen10_SAS_HY2-1•DL380Gen10_SAS_HY2 -1。
VtspV5.5 vstp销售培训课程 6 vSphere 解决方案的体系结构设计试题及答案(红色标记为正确答案)VMware 承诺构建一个充满活力的在线学习社区,为您提供成为VMware 技术销售专家所需参加的新课程和学习机会的最新相关信息。
以下哪些选项属于这项承诺中的内容?请选择三项。
@VMwareVTSP on TwitterLinkedIn 上的VMware 技术销售专家(VTSP) 小组VMware Partner LinkVTSP Community on Facebook在对客户的环境进行分析后,您获得了详细的性能和容量数据,现在您将利用这些数据为解决方案中所需的vSphere ESXi 主机制定详细的规格。
您可以采用的服务器配置有两种,它们均符合技术要求。
•配置 A 支持解决方案所需的所有功能特性。
您可以使用四台这样的服务器作为ESXi 主机,精确满足所有性能和容量要求,而不提供备用容量。
•配置B 可为每台ESXi 主机提供多一倍的CPU 和内存容量,但成本将增加60%。
在与客户商讨如何进一步优化解决方案规范的后续会面中,他们确认了自己的要求:一旦任一主机发生故障,所有服务都能自动重新启动;并且希望能调整解决方案的规模,使其容量和性能比目前所需的指标高出20%。
此项要求旨在为今后两年的预期增长提供支持,这样他们就无需在此时段内购买更多服务器硬件。
在不考虑许可的情况下,以下哪一项服务器配置和数量对此客户而言最经济高效?请选择一个原因。
6 台采用配置A 的ESXi 主机5 台采用配置A 的ESXi 主机4 台采用配置B 的ESXi 主机3 台采用配置B 的ESXi 主机客户已大致接受了您为大型vSphere 环境设计的方案。
除其他事项外,您已指定该解决方案将使用Storage I/O Control、Storage DRS、Storage Profiles,并且您的设计要求存储解决方案必须能够将某些功能(如数据块复制和清零)分流到存储阵列。
vmwarevtsp认证网络课程课程install安装VMware vSphere 4.1——ESX4.1/ESXi4.1安装vSphere Client4.1安装vCenter Server4.1安装vSphere许可创建 VMware vSphere 环境所需的重要组件包括:VMware ESX:这是一个虚拟化平台,用于将物理服务器划分为多个虚拟机分区。
每个虚拟机均代表一个完整的系统,都配备有处理器、内存、网络连接、存储和 BIOS。
ESX 具有两个版本。
VMware ESX 也称为传统ESX,包含一个内置的服务控制台。
它作为可刻录到 DVD 介质上的可引导 ISO 映像提供。
VMware ESXi 不包含服务控制台,可通过两种形式提供:VMware ESXi Embedded 和 VMware ESXi Installable。
ESXi Embedded 是内置在服务器物理硬件中的固件。
ESXi Installable 作为可安装的CD-ROM 引导映像提供。
可将ESXi Installable 软件安装到服务器的硬盘驱动器上。
vSphere Client:它是用于访问 ESX 主机或 vCenter Server 的图形管理用户界面。
vSphere Client 安装在Windows 计算机上,它是与虚拟基础架构进行交互的主要方法。
可以从ESX 主机或vCenter Server 下载 vSphere Client 软件。
VMware vCenter Server 和插件:VMware vCenter Server 可为数据中心提供便捷的单一控制点。
vCenter Server 是一项Windows 服务,安装后可自动运行。
作为 Windows 服务,即使未与vSphere Client 相连,同时也没有任何用户登录到其所驻留的计算机,vCenter Server 还是会在后台持续运行,执行监控和管理 ESX 主机和虚拟机。
在对新vSphere 5.5 迁移项目进行现场调查期间,您发现客户的一些应用服务器当前配置了32 个单独的物理磁盘。
客户指出,他们希望在迁移期间保留这一底层结构,不想将这些磁盘整合到较少数量的磁盘中。
如何配置这些虚拟机的虚拟机存储才能满足客户要求?请选择一个原因。
任意类型的三个虚拟SCSI 控制器三个虚拟Paravirtualized SCSI 控制器三个虚拟LSI Logic SAS SCSI 控制器三个虚拟BusLogic SCSI 控制器v vSphere 5.5 虚拟机可以配置为使用SCSI 连接磁盘。
这些虚拟磁盘可通过以下哪两种方式调配?请选择两个原因。
作为VMFS 或NFS 数据存储上的VMDK 格式文件作为使用原始设备映射(RDM) 的块存储作为VMDK 格式化的本地磁盘或与SAN 连接的SCSI 磁盘作为本地磁盘、与SAN 连接的磁盘或NAS VMFS 磁盘@vSphere VMFS 数据存储可以用精简配置的SAN 卷来配置。
如果虚拟机存储在精简配置的SAN 卷上,而此卷在虚拟机尝试写入新数据时备用容量不足,则虚拟机可能会崩溃。
通过以下哪几项SAN 硬件功能特性,vSphere 5.5 能够以更可控的方式解决此问题?请选择两个原因。
VAAI - 虚拟机Stun 基元VASA - 虚拟机Stun 基元VAAI - 虚拟机关闭基元VASA - 虚拟机关闭基元v为确保在一组虚拟机之间均衡分配存储I/O 资源,客户启用了Storage I/O Control。
不过他们遇到了问题,使用SIOC 后,有一个虚拟机比其他虚拟机占用的资源要多,并且此虚拟机的表现不符合他们的预期。
以下哪几项可能是导致此问题的原因?请选择两个原因。
虚拟机位于光纤通道存储上虚拟机具有原始设备映射数据存储由多个盘区组成未在服务器上启用Storage I/O Control@v您的客户表示,他们希望在其新vSphere 5.5 环境中使用vCenter Appliance 和VSA。
d a t a s he e t / 1What Is Virtual SAN?VMware Virtual SAN is a new software-defined storage tier for VMware vSphere, bringing the benefits of the software-defined data center to storage. By clustering server hard disk and solid state drives (HDDs and SSDs), Virtual SAN creates a flash-optimized, highly resilient shared datastore designed for virtual environments.Based on a hypervisor-converged distributed architecture embedded in the vSphere kernel, Virtual SAN can make optimal data placement and I/O optimizations. Because it sits directly in the I/O data path, the product is able to deliver the highest levels of performance, scalability, and resilience without taxing the CPU with additional overhead.Virtual SAN also differs from other storage products in its policy-based approach to storage management. This management architecture enables administrators to specify storage attributes—such as capacity, performance, and availability—in the form of simple policies on a per-VM basis. These policies, governed by service-level agreements (SLAs), dynamically self-tune and load-balance the system so that each virtual machine has the right level of resources. The system can adapt to ongoing changes in workload conditions to ensure that each virtual machine has the storage resources it needs.Virtual SAN distributed architecture leverages enterprise-grade SSDs for high-performance read/write caching and HDDs for cost-effective data persistence. Using server-side storage, Virtual SAN delivers unmatched price/performance compared to other Virtual Storage Appliances (VSA) or midrange hybrid arrays in themarket today. The Virtual SAN datastore granularly scales up by adding more disks or scales out by adding more hosts, allowing users to configure the system to meet their needs flexibly.Virtual SAN is simple and automates time-consuming manual storage tasks. Not only is Virtual SAN managed through the VMware vSphere® Web Client, but it also integrates with other VMware products such as VMware® vCenter™ Site Recovery Manager™ and VMware vCloud® Automation Center™. This integration makes provisioning and management of storage in virtual environments easy and seamless.Key Features and CapabilitiesHypervisor-converged storage software – Virtual SAN is embedded in the vSphere kernel. This unique characteristic of Virtual SAN makes integration with vSphere seamless and enables best performance and scalability.VMware® Virtual SAN™ is a new software-defined storage tier for VMware vSphere® environments. Virtual SAN clusters server disks and flash to create radically simple, high performance, resilient shared storage designed for virtual machines.• Radically simple storage designed for virtual machines• Hypervisor-converged storage software that creates a high-performance, persistent storage tier • Significantly reduced TCO by up to 50 percent • Integrated with VMware stack• Flash-optimized architecture for compelling price/performance• Low upfront investment; grow as you go with granular linear scaling of performance, capacity, and cost• Rapid storage provisioning and automated, self-tuning ongoing management• Single pane of glass management with vSphere •Backed by VMware support and all major server OEMsVMware, Inc. 3401 Hillview Avenue Palo Alto CA 94304 USA Tel 877-486-9273 Fax 650-427-5001 Copyright © 2014 VMware, Inc. All rights reserved. This product is protected by U.S. and international copyright and intellectual property laws. VMware products are covered by one or more patents listed at /go/patents. VMware is a registered trademark or trademark of VMware, Inc. in the United States and/or other jurisdictions. All other marks and names mentioned herein may be trademarks of their respective companies. Item No: VMW5139-DS-VIRTUAL-SAN-USLET-111 03/14Lower TCO – Virtual SAN lowers TCO by up to 50 percent. Because it uses enterprise-grade HDDs and SSDs to create a converged and resilient SAN-like storage tier within the hypervisor, the price/performance value of Virtual SAN is unmatched by any other VSA or midrange hybrid array.System RequirementsHardware Host• 1GB NIC; 10GB NIC recommended • SATA/SAS HBA or RAID controller• At least one SSD and one HDD for each capacity-contributing node Cluster• Minimum cluster size: three hostsHardware Compatibility List/resources/compatibility/search.php?deviceCategory=vsanSoftware• One of the following: vSphere 5.5 U1 (VMware vSphere® any edition or above), VMware vSphere® with OperationsManagement™ 5.5 U1 (any edition), or VMware vCloud® Suite 5.5 U1 (any edition)• VMware® vCenter Server™ 5.5 U1Learn MoreFor more information or to purchase VMware products, call 877- 4 -VMWARE (outside North America, +1-650 -427-5000), visit /products , or search online for an authorized reseller. For detailed product specifications and system requirements, refer to the vSphere documentation.VM-centric policy-based management – Storage requirements are associated with individual virtual machines or virtual disks in the form of policy statements. Virtual SAN automatically translates these policy statements into system configurations to instantly provision storage with the right SLAs.Server-side read/write caching – Virtual SAN minimizes storage latency by accelerating read/write disk I/O traffic with built-in caching on enterprise-grade server-side flash technology.Built-in failure tolerance – Virtual SAN leverages distributed RAID and cache mirroring to ensure that data is never lost if a disk, host, or network fails.Single pane of glass management with vSphere – Virtual SAN removes the need for training on specialized storage interfaces or the overhead of operating them. Provisioning is now as easy as two clicks.Granular nondisruptive scale-up or scale-out – You can easily and nondisruptively expand the capacity of the Virtual SAN datastore by adding hosts to a cluster or disks to a host.Hardware independence – Virtual SAN can be deployed on hardware from any server manufacturer. This gives you the flexibility to build out customized storage systems in heterogeneous hardware environments.Interoperability with VMware stack – Virtual SAN leverages vSphere snapshots, vSphere clones, VMware vSphere® Data Protection™, and vSphere Replication for data protection, backup, rapid cloning, and disaster-recovery (DR) purposes. Virtual SAN interoperates with vCloud Automation Center and vCenter™ Operations Management Suite™ and can be deployed in conjunction with VMware® Horizon View™ in VDI environments and vCenter Site Recovery Manager in DR environments.BenefitsSimple – Virtual SAN is the first policy-driven storage product that simplifies how storage is provisioned and managed. It gives you a new way to manage storage by automating many of today’s manual tasks. The new model doesn’t involve LUNs or RAID configurations and removes the need for manual adjustments. High performance – By using server-side flash technology, Virtual SAN enables true server-side read/write caching. The solution optimizes the I/O data path to maximize throughput and minimize latency, and because it is embedded in the VMware® ESXi™ kernel, it is a truly unique solution that delivers better performance than a virtual appliance or an external device.。
本幻灯片显示了构成“v Spher e 虚拟机管理”系列课程的各单元,以及学完每个单元所需的时间。
?“创建虚拟机”单元是“vSp here虚拟机管理”系列课程的第一个单元,它介绍了创建虚拟机的各种方法。
完成本单元的学习后,您将能够:描述虚拟机的体系结构。
使用下列方式创建虚拟机:使用“Creat e New Virt ual M achin e”(创建新虚拟机)向导;使用模板部署;克隆现有虚拟机;使用 vCe nterGuide d Con solid ation将物理机转换为虚拟机。
首先,我们来查看一下虚拟机的一些主要体系结构功能特性。
虚拟机是一台软件计算机,它像一台物理计算机一样运行着操作系统和应用程序。
虚拟机可提供基于x86 的硬件平台。
虚拟机就像物理计算机一样工作,并且包含它自己的虚拟CPU、内存、硬盘和网卡。
?虚拟机由一组文件构成,并由主机的物理资源提供支持。
每台虚拟机都具有虚拟设备,这些设备可提供与支持它的物理硬件相同的功能。
E SX 或ESXi主机的V Mkern el 可将虚拟机的设备映射到主机上的物理设备。
例如,虚拟S CSI 磁盘驱动器可映射到与ESX 主机相连的SAN L UN 上的虚拟磁盘文件。
此外,虚拟以太网网卡也可通过虚拟交换机端口连接至特定主机的网卡。
您可以从一系列虚拟硬件中进行选择,其中包括此处显示的设备。
例如,您可以选择要为虚拟机配置的 RA M 的容量。
虚拟机可以看到的处理器即物理主机中的处理器。
?应该记住的是,ES X 或E SXi 主机提供的虚拟机平台独立于主机系统及其物理硬件。
?无论在何种系统上运行,每个VMwar e 平台产品都将提供同一套虚拟硬件。
VSP与VTSP注册、培训和考试全流程1、打开VMware的Partners官方网站/partners/partners.html 输入用户名和密码进行登录:2、选择“Partner University”3、选择“汉语”4、接下来需要在网上进行2名VSP和2名VTSP的免费培训和考试,下面以VSP为例,点击VSP的“Plan Details”5、点击“Add this Plan”6、接下来可以看到VSP的9门课程,如果是VSP3升级到VSP4则只需要完成下面的3门课程。
我们以“VSP合作伙伴计划和激励”这们课程为例,点击进入。
7、选择中文版本,点击Register。
8、点击“Continue”9、partner university会来一封邮件提醒你这门课程注册成功。
点击“Start this Course”进行在线培训。
10、培训界面见下图:11、培训结束后,回到partner university界面,在myEducantion的下拉菜单中选择myEnrollmentes12、点击“Continue”进入下一步13、如果课程没有学习完、或者在考试前还想重温一遍,可以点击“Continue this Course”再次进行培训。
如果确定要进行考试了,点击进入。
14、了解考试信息后,点击“Continue”开始进行考试15、考试通过后可以重新开始下一门课程的注册、培训和考试,选择“myEducation”里的“myTasks”16、选择VSP4的Manage Plan:17、重新开始从第六步进行其他课程的注册、培训和考试。
18、当所有课程都考试通过后,3个工作日内在“myEducation”里的“myTranscrips”可以看到VSP和VTSP的证书。
19、可以在这里看到VSP和VTSP证书。
20、示例:。
VMware Virtual SAN 6.1Server disks as central storage for VMware environmentsVirtual SAN (VSAN) is hypervisor-converged storage and clusters server disks and flash to create radically simple, high performance, resilient shared storage designed for virtual machines.At a GlanceVMware® Virtual SAN™ is VMware’s software defined storage solution for Hyper-Converged Infrastructure (HCI).Seamlessly embedded in the hypervisor, Virtual SAN delivers enterprise-ready, high-performance shared storage for VMware vSphere® Virtual Machines. It leverages commodity x86 components that easily scale to drastically lower TCO by up to 50%. Seamless integration with vSphere and the entire VMware stack makes it the simplest storage platform for virtual machines — whether running business-critical applications, virtual desktops or remote server room apps.Key Benefits■ Radically Simple – Deploy with 2-clicks through the standard vSphere Web Client and automate management using storage policies.■ High Performance – Flash accelerated for high IOthroughput and low latency. Deliver up to 7M IOPS with predictable sub-millisecond response time from a single, all-flash cluster.■ Elastic Scalability – Elastically grow storage performance and capacity by adding new nodes or drives withoutdisruption. Linearly scale capacity and performance from 2 to 64 hosts per cluster.■ Lower TCO – Lower storage TCO by up to 50% by deploying standard x86 hardware components for low upfront investment and by reducing operational overhead. ■ Enterprise High Availability – Enable maximum levels of data protection and availability with asynchronous long distance replication and stretched clusters. ■ Advanced Management – Single pane of glass management from vSphere with advanced storage performance monitoring, troubleshooting and capacityTopicsWhat is VMware Virtual SAN?VMware Virtual SAN is VMware’s software-defined storage solution for hyper-converged infrastructures, a software-driven architecture that delivers tightly integrated compute, networking and shared storage from a single, virtualized PRIMERGY server. Virtual SAN delivers high performance, highly resilient shared storage by clusteringserver-attached flash devices and/or hard disks (HDDs). Virtual SAN delivers enterprise-class storage services for virtualized production environments along with predictable scalability and all-flash performance — all at a fraction of the price of traditional, purpose-built storage arrays. Just like vSphere, Virtual SAN provides users the flexibility and control to choose from a wide range of hardware options and easily deploy and manage it for a variety of IT workloads and use cases. Virtual SAN can be configured as all-flash or hybrid storage. Architecture and Performance: Uniquely embedded within the hypervisor kernel, Virtual SAN sits directly in the I/O data path. As a result, Virtual SAN is able to deliver the highest levels of performance without taxing the CPU with overhead or consuming high amounts of memory resources, as compared to other storage virtual appliances that run separately on top of the hypervisor. Virtual SAN can deliver up to 7M IOPS with an all-flash storage architecture or 2.5M IOPS with a hybrid storage architecture.Scalability: Virtual SAN has a distributed architecture that allows for elastic, non-disruptive scaling from 2 to 64 hosts per cluster. Both capacity and performance can be scaled at the same time by adding a new host to the cluster (scale-out); or capacity and performance can be scaled independently by merely adding new drives to existing hosts (scale-up). This “Grow-as-you-Go” model provides linear and granular scaling with affordable investments spread out over time. Management and Integration: Virtual SAN does not require any additional software to be installed—it can be enabled in a few, simple clicks. It is managed from the vSphere Web Client and integrates with the VMware stack including features like vMotion®, HA, Distributed Resource Scheduler™ (DRS) and Fault Tolerance (FT) as well as other VMware products such as VMware Site Recovery Manager™, VMware vRealize™ Automation™ and vRealize Operations™.Automation: VM storage provisioning and storage service levels (e.g. capacity, performance, availability) are automated and controlled through VM-centric policies that can be set or modified on-the-fly. Virtual SAN dynamically self-tunes, adjusting to ongoing changes in Key Features and CapabilitiesKernel embedded– Virtual SAN is built into the vSphere kernel, optimizing the data I/O path to provide the highest levels of performance with minimal impact on CPU and memory resources.All-Flash or hybrid architecture– Virtual SAN can be used in all-flash architecture for extremely high and consistent levels of performance or in a hybrid configuration to balance performance and cost.Expanded enterprise-readiness– support for vSphere Fault Tolerance, asynchronously replicating VMs across sites based on configurable schedules of up to 5 minutes, continuous availability with stretched clusters and major clustering technologies including Oracle RAC and Microsoft MSCS.Granular non-disruptive scale-up or scale-out– Non-disruptively expand the capacity of the Virtual SAN data-store by adding hosts to a cluster (scale-out) to expand capacity and performance or disks to a host (scale-up) to add capacity or performance.Single pane of glass management with vSphere– Virtual SAN removes the need for training on specialized storage interfaces or the overhead of operating them. Provisioning is now as easy as two clicks.VM-centric policy-based management– Virtual SAN uses storage policies, applied on a per-VM basis, to automate provisioning and balancing of storage resources to ensure that each virtual machine gets the specified storage resources and services.Virtual SAN Stretched Cluster– Create a stretched cluster between two geographically separate sites, synchronously replicating data between sites and enabling enterprise-level availability where an entire site failure can be tolerated, with no data loss and near zero downtime. Advanced management– Virtual SAN Management Pack for vRealize Operations delivers a comprehensive set of features to help manage Virtual SAN, including global visibility across multiple clusters, health monitoring with proactive notifications, performance monitoring and capacity monitoring and planning. The Health Check Plug-in complements the management pack for additional monitoring including HCL compatibility check and real-time diagnostics.Server-side read/write caching– Virtual SAN minimizes storage latency by accelerating read/write disk I/O traffic with built-in caching on server-side flash devices.Built-in failure tolerance– Virtual SAN leverages distributed RAID and cache mirroring to ensure that data is never lost if a disk, host, network or rack fails.Deployment OptionsCertified Hardware: Control your hardware infrastructure by choosing from certified components on the hardware compatibility list, see /resources/compatibility/search.php?deviceCat egory=vsanPRIMEFLEX for VMware VSAN: Select a pre-configured hardware solution that is certified to run Virtual SAN. More information under:/global/products/computing/integrated-systems/ vmware-vsan.htmlVMware System RequirementsVirtual SAN certified:■1GB NIC; 10GB NIC recommended■SATA/SAS HBA or RAID controller■At least one flash caching device and one persistent storage disk (flash or HDD) for each capacity-contributing nodeClusterMinimum cluster size: two hostsSoftware■One of the following: VMware vSphere 6.0 U1 (any edition), VMware vSphere with Operations Management™ 6.1 (any edition), or VMware vCloud Suite® 6.0 (any edition updated with vSphere 6.0U1)■VMware vCenter Server™ 6.0 U1Additional hintWhen the Fujitsu 2GB UFM Flash Device is used as a boot device for VMware ESXi (vSphere) an additional local HDD is mandatory to store trace files and core dumps generated by VSAN. Such small HDD has to be connected to the onboard SAS/SATA controller and is not part of the VSAN storage.PRIMERGYFollowing PRIMERGY Servers are released for VMware software: VMware Systems Compatibility HCL:/go/hclFujitsu Manageability with ServerView SuiteServerView is able to manage PRIMERGY servers by means of the CIM provider that Fujitsu has integrated for VMware vSphere▪Management of the physical machine under the host operating system ESXi▪ServerView RAID for configuration and management of the RAID controllers in the physical machine▪Management of the virtual machines under the guest operating systems Windows and Linux▪Remote access via onboard Integrated Remote Management▪SupportMandatory Support and Subscription (SNS)SNS (Support and Subscription) is mandatory for at least 1 year for all VMware software products. Fujitsu offers its own support for VMware OEM software products. This support is available for different retention periods and different support levels. The Fujitsu support levels are: Platinum Support (7x24h) or Gold Support (5x9h). Both service levels can be ordered either for 1, 3 or 5 year support terms. Please choose the appropriate Support for your project.Your support agreement is with Fujitsu and VMware exclusively through Fujitsu (not with VMware directly). SNS is only for Fujitsu servers like PRIMERGY and PRIMEQUEST. Of course, SNS for VMware (OEM) software products can be renewed at Fujitsu prior to the end of the SNS term. SNS for VMware (OEM) software products cannot be renewed at VMware directly.Support Terms and ConditionsFujitsu Terms and Conditions can be found under:FUJITSU ServiceContract SoftwareFUJITSU Support Pack SoftwareTechnical Appendix VMware SoftwareFujitsu Professional ServiceInstallation, configuration or optimization services for VMware software are optional service offerings. Additionally operations services from Fujitsu are available. Any additional and optional service can be requested from Fujitsu Professional Services.Product Activation Code RegistrationPlease register your activation code at/code/fsc.Registration will generate the license key. Help can be found at: /support/licensing.html.If you have any problems, you can send an email to*********************.WarrantyClass: CConditionsThis software product is supplied to the customer under the VMware conditions as set forth in the EULA of the VMware software at/download/eula/.More informationIn addition to VMware software, Fujitsu provides a range of platform solutions. They combine reliable Fujitsu products with the best in services, know-how and worldwide partnerships. Fujitsu PortfolioBuilt on industry standards, Fujitsu offers a full portfolio of IT hardware and software products, services, solutions and cloud offering, ranging from clients to datacenter solutions and includes the broad stack of Business Solutions, as well as the full stack of Cloud offerings. This allows customers to select from alternative sourcing and delivery models to increase their business agility and to improve their IT operation’s reliability. Computing Products/global/products/computing /Software/software/To learn more about VMware vSphere please contact your Fujitsu sales representative, Fujitsu business partner, or visit our website. /ftsFujitsu Green Policy Innovation is ourworldwide project for reducing burdens on the environment.Using our global know-how, we aim to contribute to the creation of a sustainable environment for future generations through IT.Please find further information at/global/about/environ mentAll rights reserved, including intellectual property rights. Changes to technical data reserved. Delivery subject to availability. Any liability that the data and illustrations are complete, actual or correct is excluded. Designations may be trademarks and/or copyrights of the respective manufacturer, the use of which by third parties for their own purposes may infringe the rights of such owner.For further information see/fts/resources/navigati on/terms-of-use.html©2015 Fujitsu Technology Solutions GmbHTechnical data is subject to modification and delivery subject to availability. Any liability that the data and illustrations are complete, actual or correct is excluded. Designations may be trademarks and/or copyrights of the respective manufacturer, the use of which by third parties for their own purposes may infringe the rights of such owner.Phone: +49 5251/525-2182 Fax : +49 5251/525-322182E-mail:*************************.com Website: /fts 2015-11-30 EN。
SOLUTION BRIEF ©2014 Mellanox Technologies. All rights reserved.This document discusses an implementation ofVMware Virtual SAN TM (VSAN) that supports thestorage requirements of a VMware Horizon™View™ Virtual Desktop (VDI) environment. Al-though VDI was used to benchmark the perfor-mance of this Virtual SAN implementation, anyapplication supported by ESXi 5.5 can be used.VSAN is VMware’s hypervisor-converged storagesoftware that creates a shared datastore acrossSSDs and HDDs using multiple x86 server hosts.T o measure VDI performance, the Login VSI work-load generator software tool was used to test theperformance when using Horizon View. VDI per-formance is measured as the number of virtualdesktops that can be hosted while delivering auser experience equal to or better than a physicaldesktop including consistent, fast response timesand a short boot time. Supporting more desktopsper server reduces CAPEX and OPEX requirements.Benefits of Virtual SANData storage in VMware ESXenvironments has historicallybeen supported using NAS-or SAN-connected sharedstorage from vendors such asEMC, Netapp, and HDS. Theseproducts often have consider-able CAPEX requirements andbecause they need specially-trained personnel to supportthem, OPEX increases as well.VSAN eliminates the needfor NAS- or SAN-connectedshared storage by using SSDsand HDDs attached locally tothe servers in the cluster. Aminimum of three servers arerequired in order to survive a server failure. Infor-mation is protected from storage device failure byreplicating data on multiple servers. A dedicatednetwork connection between the servers provideslow latency storage transactions.SSDs Boost Virtual SAN PerformanceApplication performance is often constrainedby storage. Flash-based SSDs reduce delays(latency) when reading or writing data to harddrives, thereby boosting performance.READ Caching: By caching commonly accesseddata in SSDs READ latency is significantlyreduced because it is faster to retrieve datadirectly from the cache than from slow, spin-ning HDDs. Because DRS1 may cause VMs tomove occasionally from one server to another,VSAN does not attempt to store a VM’s dataon a SSD connected to the server that hoststhe VM. This means many READ transactionsmay need to traverse the network, so highbandwidth and low latency is critical.Implementing VMware’s Virtual SAN™ with Micron SSDs and the Mellanox Interconnect SolutionFigure 1. Virtual SAN1 VMware’s Dynamic Resource Scheduling performs application load balancing every 5 minutes.WRITE Buffering: VSAN temporarily buffers all WRITEsin SSDs to significantly reduce latency. T o protectagainst SSD or server failure, this data is also stored on a SSD located on different server. At regular intervals, the WRITE data in the SSDs are de-staged to HDDs. Because Flash is non-volatile, data that has not been de-staged is retained during a power loss. In the event of a server failure, the copy of the buffered or de-staged data on the other server ensures that no data loss will occur.Dedicated Network Enables Low Latency for VSANMost READ and all WRITE transactions must traverse over a network. VSAN does not try to cache data that is local to the application because it results in poor balancing of SSD utilization across the cluster. Because caching is distributed across multiple servers, a dedicated network is required to lower contention for LAN resources. For data redundancy and to enable high availability, data is written to HDDs located on separate servers. Since two traverses across the network are typically required for a READ and one for a WRITE, the latency of the LAN must be sub-millisecond. VMware recommends at least a 10GbE connection.VSAN-Approved SSD ProductsVMware has a compatibility guide specifically listing I/O controllers, SSDs, and HDDs approved for implementing VSAN. Micron’s P320h and P420m PCIe HHHL SSD cards are listed 2 in the compatibility list.Tested ConfigurationThree servers, each with dual Intel Xeon E5-2680 v2 pro-cessors and 384GB of memory, were used for this test. Each server included one disk group consisting of one SSD and six HDDs. Western Digital 1.2TB 10K rpm SAS hard drives were connected using an LSI 9207-8i host bus adapter set to a queue depth of 600. A 1.4TB Micron P420m PCIe card was used for the SSD. A dedicatedstorage network supporting VSAN used Mellanox’s end-to-end 10GbE interconnect solution, including their SX1012 twelve-port 10GbE switch, ConnectX ®-3 10GbE NICs and copper interconnect cables.On the software side, ESXi 5.5.0 Build 1623387 and Ho-rizon View 5.3.2 Build 1887719 were used. Within the desktop sessions, Windows 7 64-bit was used. Each per-sistent desktop used 2GB of memory and one vCPU. VDI performance was measured as the number of virtual desk-tops that could be hosted while delivering a user experi-ence equal to or better than a physical desktop.ResultsVersion 4.1.0.757 of the Login VSI load simulator was used for testing. This benchmark creates the workload representative of an office worker using Microsoft Office applications. The number of desktop sessions is steadily in-creased until a maximum is reached, in this case 450 ses-sions. Increasing the number of sessions raises the load on the servers and the VSAN-connected storage, which causes response times to lengthen. Based on minimum, average, and maximum response times, the benchmark software will calculate VSImax, which is their recommen-dation for the maximum number of desktops that can be supported. The following figure shows that using the three-server configuration, up to 356 desktops can be supported.Figure 2. VSAN Test Configuration2The Virtual SAN compatibility guide is located at https:///resources/compatibility/search.php?deviceCategory=vsan350 Oakmead Parkway, Suite 100, Sunnyvale, CA 94085Tel: 408-970-3400 • Fax: © Copyright 2014. Mellanox Technologies. All rights reserved.Mellanox, Mellanox logo, ConnectX, and SwitchX are registered trademarks of Mellanox Technologies, Ltd. All other trademarks are property of their respective owners.15-4175SB Rev1.0Other critical factors in VDI environments are the times required to boot, deploy, and recompose desktops. Boot is when an office worker arrives at work and wants to access their desktop. Deploy is the creation of a desktop session, and recompose is the update of an existing session. An update may be required after a patch release has been dis-tributed. For this test, 450 desktops were simultaneously booted, deployed, and recomposed.• Boot: 0.7 seconds/desktop • Deployment: 7.5 seconds/desktop • Recompose: 9.2 seconds/desktopConclusionSoftware-defined storage appears to be a viable alternative to SAN or NAS storage from our experience using VSAN. Using directly-attached SSDs and HDDs can provide supe-rior performance by bypassing the need for shared storage. The VSAN implementation provides the fault tolerance and high availability necessary for enterprise environments that has historically has been the limitation of DAS.Read caching and write buffering using the Micron P420mPCIe SSD sufficiently masks the latency limitations of HDDs, allowing VMs to run at high performances. Since VMs frequently move between servers for load balancing, there is no guarantee that SSDs that are local to the VM will have cached data. The Mellanox interconnect provides low latencies whenever accessing data between servers is necessary.T o evaluate the Micron and Mellanox hardware supporting VSAN, VMware’s Horizon View virtual desktop application was implemented. Using the Login VSI workload simu-lator, 356 desktops were hosted across three servers. This number is comparable to what a SAN- or NAS-connected shared storage implementation can support, but at a frac-tion of the cost.About Login VSILogin Virtual Session Indexer (Login VSI) is a software tool that simulates realistic user workloads for Horizon View and other major desktop implementations. It is an industry stan-dard for measuring the VDI performance that a softwareand hardware implementation can support.Figure 3. VSAN Results。
VMware vSphere 网络概述VMware vSphere 网络:概述”要想详细地了解虚拟网络组件,必须要了解 vSphere 数据中心的体系结构。
典型的 vSphere 数据中心包含多种基本物理构建块,例如 x86 计算服务器、存储网络和阵列、IP 网络、管理服务器和桌面客户端。
计算服务器是指在裸机上运行 VMware ESXi ™的业界标准 x86 服务器。
虚拟机驻留在 ESXi 服务器上。
虚拟机所需的所有资源均由ESXi 服务器提供。
每台计算服务器在虚拟环境中均称为独立主机。
可将具有相似配置的多个 x86 服务器组合在一起并连接到同一网络和存储子系统,从而在虚拟环境中形成一个资源池。
在光纤通道存储区域网络(SAN 阵列)、Internet 小型计算机系统接口(iSCSI SAN 阵列),以及网络连接阵列(NAS 阵列)等应用广泛的存储技术的支持下,vSphere 可满足不同数据中心的存储需求。
通过存储区域网络在各组服务器之间共享存储阵列,这使 IT 部门可以将存储资源汇聚成资源池,从而更灵活地为虚拟机调配存储资源。
每台计算服务器可以拥有多个千兆位以太网网卡,为整个数据中心提供高带宽且可靠的网络连接。
借助 VMware vCenter™可以方便地对数据中心进行单点控制。
它在 Windows 2003 和2008 Server 64 位版操作系统上运行,可提供许多基本的数据中心服务,例如访问控制、性能监视和配置。
vCenter Server 可将各个计算服务器的资源整合起来,以供整个数据中心内的所有虚拟机共享。
它通过以下方式做到这一点:根据系统管理员设定的策略,管理分配给计算服务器的虚拟机,以及分配给特定计算服务器内虚拟机的资源。
即使无法访问 vCenter Server(例如,网络断开),计算服务器也能继续工作。
计算服务器可分别单独管理,这些计算服务器将基于上一次设置的资源分配策略,继续运行分配给它们的虚拟机。
ssss为新的vSphere 5.5 构建设计规格时,您必须定义要配置的组件,以确保IT 基础架构管理团队能够看到环境中的关键状态变化(如硬件故障、CPU 或网络过量使用),而且他们有自动化的程序来促进合规性和标准化。
您需要专注于哪两个vCenter 基础架构管理功能,以确保您的设计满足客户的这些具体需求?请选择两个原因。
警报Orchestrator资源映射vCenter 插件???????????????/您的客户有一个大型vSphere 环境,支持50 台vSphere 主机和近1000 个虚拟机。
他们可以支持Microsoft SQL 或Oracle 数据库,并且想安装具有特定配置的vCenter,以保证在发生硬件故障时不会停机。
他们必须选择哪种vCenter 配置?请选择一个原因。
含vSphere Fault Tolerance 的vCenter Appliance含vCenter Heartbeat 的vCenter Appliance含vSphere Fault Tolerance 的vCenter Installable含vCenter Heartbeat 的vCenter Installablessss您的客户表示,存储分配决策给他们的虚拟基础架构管理员造成了严重的管理负担,他们需要一种解决方案来简化或消除此任务。
借助哪一项vSphere 技术,他们能够依据容量指定用于虚拟机的存储,而不需要为每个虚拟机选择特定的数据存储位置?请选择一个原因。
虚拟机存储配置文件Storage DRSStorage I/O ControlVAAI?????????客户有一个环境将用于托管约10 个虚拟机。
客户表示,他们必须能够支持您已确认所有vCenter 版本都支持的几项功能特性,但您必须根据其需求明确应推荐哪些vCenter 版本。
您必须询问以下哪些问题?环境中的工作负载是否会增长到20 个以上?客户是否可能需要 3 台以上的ESXi 服务器?客户是否需要支持vMotion?客户是否打算使用分布式虚拟交换机?ssss您的客户要求您实施一个解决方案来自动管理存储,希望能够通过迁移虚拟机文件来避免数据存储中出现I/O 和空间利用率瓶颈。
#1 HyperConverged Appliance for SMB and ROBOStarWind Virtual SAN®Compute and Storage Separated Multi-Node Cluster Scale-Out Existing Deploymentsfor VMware vSphereMAY 2015TECHNICAL PAPERTrademarks“StarWind”, “StarWind Software” and the StarWind and the StarWind Software logos are registered trademarks of StarWind Software. “StarWind LSFS” is a trademark of StarWind Software which may be registered in some jurisdictions. All other trademarks are owned by their respective owners. ChangesThe material in this document is for information only and is subject to change without notice. While reasonable efforts have been made in the preparation of this document to assure its accuracy, StarWind Software assumes no liability resulting from errors or omissions in this document, or from the use of the information contained herein. StarWind Software reserves the right to make changes in the product design without reservation and without notification to its users.Technical Support and ServicesIf you have questions about installing or using this software, check this and other documents first - you will find answers to most of your questions on the Technical Papers webpage or in StarWind Forum. If you need further assistance, please contact us.Copyright ©2009-2016 StarWind Software Inc.No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical, photocopying, recording or otherwise, without the prior written consent of StarWind Software.In 2016, Gartner named StarWind “Cool Vendor for Compute Platforms”.Gartner does not endorse any vendor, product or service depicted in its research publications, and does not advise technology users to select only those vendors with the highest ratings or other designation. Gartner research publications consist of the opinions of Gartner's research organization and should not be construed as statements of fact. Gartner disclaims all warranties, expressed or implied, with respect to this research, including any warranties of merchantability or fitness for a particular purpose.About StarWindStarWind is a pioneer in virtualization and a company that participated in the development of this technology from its earliest days. Now the company is among the leading vendors of software and hardware hyper-converged solutions. The company’s core product is the years-proven StarWind Virtual SAN, which allows SMB and ROBO to benefit from cost-efficient hyperconverged IT infrastructure. Having earned a reputation of reliability, StarWind created a hardware product line and is actively tapping into hyperconverged and storage appliances market. In 2016, Gartner named StarWind “Cool Vendor for Compute Platforms” following the success and popularity of StarWind HyperConverged Appliance. StarWind partners with world-known companies: Microsoft, VMware, Veeam, Intel, Dell, Mellanox, Citrix, Western Digital, etc.ContentsIntroduction (4)Solution Diagram (5)Replacing Partner for (DS2) (6)Creating Virtual Disk (DS3) (11)Configuring ESXI Cluster (18)Configuring the iSCSI Initiator (18)Contacts (25)IntroductionTraditionally VMware requires having some sort of the shared storage to guarantee the data safety, allow the virtual machines migration, enables continuous application availability and eliminates any single point of failure within IT environment. VMware users have to choose between two options when choosing the shared storage:•Hyper-Converged solutions, that allows sharing the same hardware resources for the application (i.e. hypervisor, database) and the shares storage, thus decreasing the TcO and achieving the outstanding performance results•compute and Storage separated solutions that keeps the compute and storage layers separately from each other, thus making the maintenance easier, increasing the hardware usage efficiency and allows building the system accurately for solving the taskThis guide is intended for experienced StarWind users, VMware and Windows system administrators and IT professionals who would like to add the Scale-Out node to the StarWind Virtual SAN® cluster. It provides a step-by-step guidance on scaling out the hyper-converged 2-node StarWind Virtual SAN that converts the storage resources of the separated general purpose servers into a fault tolerant shared storage resource for ESXi.A full set of up-to-date technical documentation can always be found here, or by pressing the Help button in the StarWind Management Console.For any technical inquiries please visit our online community, Frequently Asked Questions page, or use the support form to contact our technical support department.Compute and Storage Separated Multi-Node Cluster Scale-Out ExistingDeployments for VMware vSphereSolution DiagramThe diagram bellow illustrates the network and storage configuration of the resulting solution described in the guide.Physical storage sizing in Scale-Out modelPhysical Storage on StarWind node1Physical Storage on StarWind node2Physical Storage on StarWind node3ds1ds3ds3ds2Replacing Partner for (DS2)1.Add third StarWind node (SW3)2.Open replication manager for DS2 on the second StarWind node3.Click Remove Replica4.Click Add replica5.Select Synchronous “Two-Way” Replication and click next6.Enter name or IP address of the third StarWind node7.Select Create new Partner device8.Click Change Network Settings9.Select HeartBeat and synchronization channelsClick OK. You will return to Network Option for Synchronization Replication. Click Next.10.Click Create Replica11.After creation click Finish to close Replication WizardCreating Virtual Disk (DS3)1.Open Add Device Wizard through one of the following ways:•Right-click a StarWind server and select Add Device (advanced) from the shortcut menu.•Select a StarWind server and click the Add Device (advanced) button on the toolbar.2.As Add Device Wizard appears, follow the instructions to complete the creation of a newdisk.3.Select Hard disk device as the type of a device to be created. click Next to continue.4.Select Virtual disk. Click Next to continue.5.Specify a virtual disk location and size.Click Next.6.Specify virtual disk options.Click Next to continue.7.Define the caching policy and specify the cache size (in MB). You can also set maximumavailable cache size by selecting the appropriate checkbox.Click Next to continue.8.Optionally, define the L2 caching policy and the cache size. Click Next to continue.9.Specify target parameters. Select the Target Name checkbox to enter a custom name of atarget.Otherwise, the name is generated automatically in accordance with the specified target alias.Click Next to continue.10.Click Create to add a new device and attach it to the target.11.Click Finish to close the wizard.12.Right-click the recently created device and select Replication Manager from the shortcutmenu. Then, click Add replica.13.Select Synchronous two-way replication as a replication mode. Click Next to proceed.14.Specify a partner hostname, IP address and port number.Click Next.15.Choose create new Partner Device and click Next.16.Click Change network settings....17.Specify interfaces for synchronization and Heartbeat channels. Click OK. Then click Next.18.Click Create Replica.Click Finish to close the wizard.19.The successfully added devices appear in the StarWind Console.Configuring ESXI ClusterConfiguring the iSCSI Initiator1.Select a host.2.Click the Manage tab and select the Storage inset and Storage Adapters item.3.The list of the available storage adapters appears. Select iSCSI Software Adapter. OpenTargets.click the Add… button.4.Enter IP address of new StarWind node. Click OK.5.Do same for each iScSI_Data networks by clicking Add and specifying the server IPaddress.Click Rescan.6.In the Rescan dialog click OK.7.Repeat the same procedure for another cluster host.Setting up a Datastore1.Right click on host and select New datastore.2.New Datastore wizard appears.3.Select VMFS.Click next.4.Enter name of datastore (DS3) and device for datastore.Click next5.Select VMFS 5Click next.6.Enter datastore size.Click next7.Verify the settings. Click Finish.8.Check another host for a new datastore. If a new datastore is not listed among theexisting datastores, click Rescan All.Compute and Storage SeparatedMulti-Node Cluster Scale-Out ExistingDeployments for VMware vSphere ContactsUS Headquarters EMEA and APAC1-617-449-7717 1-617-507-5845 +44 20 3769 1857 (UK)+49 302 1788 849 (Germany) +33 097 7197 857 (France) +7 495 975 94 39 (Russian Federation and CIS) 1-866-790-2646Customer Support Portal:Support Forum:Sales: General Information: https:///support https:///forums ***********************************StarWind Software, Inc. 35 Village Rd., Suite 100, Middleton, MA 01949©2016, StarWind Software Inc. All rights reserved.。
vzzz客户正在他们的环境中使用快照,他们想要将虚拟机和虚拟磁盘恢复为制作快照时的状态。
但是,在恢复到前一个快照时,虚拟机被关闭。
这可能是什么原因造成的?请选择一个原因。
客户未选择生成虚拟机内存快照这一选项客户未选择使客户机内存处于静默状态这一选项虚拟机一向在都是在关闭状态下从快照还原的客户未在客户操作系统中安装VMware Toolsv您正处于大规模部署具有各种硬件配置的虚拟机之前的规划阶段。
以下哪几项是有效规划环境所必须执行的重要步骤?请选择两个原因。
为虚拟机创建虚拟交换机端口组查阅配置上限文档确保具备足够的许可配置VMware vSphere 主机配置文件vzzz客户想通过一个vSphere 集群来支持他们的生产环境,要求您就此提交一份设计。
在检查此设计时,他们注意到您指定的物理RAM 总量小于他们为此集群需要支持的虚拟机所确定的RAM 总量。
他们担心此解决方案无法以所需的配置支持虚拟机。
您应该与客户讨论vSphere 的以下哪些功能特性,以便说明vSphere 如何能够支持此设计中已经集成的内存超额分配功能?请选择三项。
透明页共享页面压缩内存压缩内存抖动内存释放zzz客户的vSphere 5.5 环境中的所有主机都正确配置了vSphere Standard 版。
他们有一个虚拟机是从其中一个主机的本地存储运行的,他们想使用Enhanced vMotion 将其实时迁移到共享存储。
在vSphere Client 中选择迁移选项时,他们发现没有选项可用来进行虚拟机的vMotion,但可以使用Storage vMotion。
为什么他们无法使用Enhanced vMotion 来同时迁移虚拟机及其存储?Enhanced vMotion 迁移需要Enterprise 版许可证Enhanced vMotion 迁移需要Enterprise Plus 版许可证Enhanced vMotion 选项仅在使用vSphere Web Client 时才提供他们未配置Enhanced vMotion Compatibility 集群@@@@客户需要一种解决方案,以便让他们使用vMotion 在所有主机之间快速移动正在运行的虚拟机。
他们的当前设置包含8 台完全相同的主机,运行的是免费版的vSphere Hypervisor。
他们至少需要执行以下哪几项操作,才能实现此功能?请选择两个原因。
从免费版vSphere 许可证升级为vSphere Standard 版许可证从免费版vSphere 许可证升级为vSphere Enterprise 版许可证部署共享存储以用于虚拟机存储将每个虚拟机都复制到NFS 共享@zzz在迁移阶段,哪种迁移方法可以将虚拟磁盘从厚配置格式转换为精简配置格式?请选择一个原因。
vMotionEnhanced vMotionStorage vMotion冷复制vzzz客户正在调查其vSphere 生产环境的灾难恢复解决方案,他们在此生产环境中广泛使用了DRS、HA 和vMotion 技术。
他们发现,如果要使存储解决方案能够支持从其现有站点进行硬件复制,则成本估算值过于高昂。
您正考虑建议他们采用vSphere Replication 解决方案,但必须先确保他们的环境能够对此提供支持。
您必须检查以下哪些事项,才能确信vSphere Replication 是适当的解决方案?请选择两个原因。
现场确认ESXi Server 的版本确认他们仅使用iSCSI 存储确认他们具有Enterprise Plus 版许可证确认15 分钟的RPO 可以满足他们的需要@zzz您向客户建议了一种解决方案,用于扩展负责支持HA 和DRS 的现有vSphere 集群,集群中的所有虚拟机都运行Windows Server 2008 R2。
此现有集群采用Intel Xeon X5650 CPU,您在建议中为新主机指定了同样的CPU。
客户对您的设计提出了质疑,他们认为使用配备AMD CPU 的主机成本效益会更高。
选择基于AMD 的主机会产生什么重大影响?请选择两个原因。
( 本题只可以先一个)将无法在所有主机之间运行vMotion 和全自动DRS无法使用HA,因为在新主机上重新启动虚拟机时,虚拟机可能会崩溃仅当将DRS 重新配置为使用冷迁移时,才能继续使用DRS客户将不得不创建一个EVC DRS 集群来同时支持两种主机类型vzzz您正处于vSphere Data Protection Advanced (VDPA) 的部署阶段。
但是,您发现您的同事未签字同意所有安装前提条件。
为成功部署和管理VDPA 设备,需要以下哪几项?请选择三项。
vCenter ServervSphere Desktop Client“vSphere Web Client”vCenter Operations ManagerSingle Sign-Onvzzz某位客户一直在对vSphere 5.5 解决方案进行应用开发测试,这需要虚拟机配备的虚拟CPU 最多达64 个。
他们已经成功测试了小规模的虚拟机,但无法启动某个创建时配备了64 个虚拟CPU 的虚拟机。
此虚拟机已在vCenter Server 中正确注册。
这一问题最有可能是由什么原因造成的?请选择一个原因。
客户使用的是免费版VMware vSphere Hypervisor主机未获得正确数量的物理内核和内存许可客户未在其ESXi 主机上禁用透明页面共享主机未获得正确数量的物理内核许可vzzz在客户环境中实施单根I/O 虚拟化(SR-IOV) 之前,必须满足哪些要求?请选择三项。
确保物理主机已安装vSphere 5.5确保主机配备了Intel 处理器查阅vSphere 文档,确保主机配置受支持确保主机配备了AMD 处理器vzzz在解决方案设计阶段,客户要求位于某一应用集群中的两个虚拟机必须配置虚拟网卡,以便为二者之间的网络通信提供最佳性能。
客户指出,这些虚拟机可在同一vSphere ESXi 主机上运行,但由于网络体系结构的原因,它们不能连接到同一虚拟交换机。
您会建议客户使用哪种适配器?请选择一个原因。
灵活VMXNET3E1000使用何种适配器无关紧要,因为虚拟机将位于同一主机上vzzz在设计vMotion 时,您应该注意以下哪几个事项?请选择三项。
所有主机都必须使用同一供应商同一系列的CPU所有主机都必须配置了千兆位以太网网络连接解决方案应该包括用于虚拟机的共享存储必须指定虚拟机运行兼容的客户操作系统必须指定vSphere 主机需获得Enterprise 版许可证的许可vzzz您正在为客户设计一种远程桌面解决方案,对方要求每个虚拟机必须具有 4 个虚拟CPU、128 GB 的RAM 且能够支持图形密集型工作负载。
解决方案中必须具备以下哪些功能特性才能满足客户的设计目标?请选择两个原因。
基于硬件的虚拟GPU 支持VMware vSphere 5.1VMware Horizon View每台vSphere 主机都配备128 GB 的RAM@zzz以下哪项是vSphere CPU 调度程序的主要设计目标?请选择一个原因。
合理性Efficiency(能效)吞吐量隔离v客户指出其虚拟机中的某个应用性能不佳,性能计数器显示此应用的CPU 资源利用率为95%。
客户想要在不关闭虚拟机的情况下为其热添加额外的CPU,但无法做到。
以下哪几项可能是导致此问题的原因?请选择两个原因。
客户操作系统必须支持热添加CPU必须关闭虚拟机才能添加CPU虚拟机中未安装VMware Tools需要Enterprise Plus 许可证才能热添加CPUvzzz您正在与客户讨论通过使用虚拟机模板来进行部署。
客户不清楚模板与克隆之间的区别,也完全不了解为什么应该创建模板。
您会使用以下哪些示例来演示它们之间的区别?请选择两个原因。
模板无法编辑或开启,因此非常适合用来统一部署大量配置完全相同的虚拟机克隆是克隆时虚拟机的精确副本,因此最适合用来快速创建虚拟机的测试和开发副本克隆包含虚拟机上的所有活动快照,因此,如果要复制虚拟机快照,则必须使用克隆模板具有极高的移动性,可用来在vSphere 环境之外导出和传输配置完整的虚拟机v vzzz为确保可以成功在一个环境与另一个环境之间进行复制,您在开始复制之前必须先验证客户的虚拟基础架构是否遵守特定限制。
以下哪几项是适用项?请选择两个原因。
必须将一个“主”vSphere Replication 设备与vCenter Server 配对必须能够为每个虚拟设备分配 4 GB 的RAM 和 4 个虚拟CPU应该确保与所有使用中的vSphere 功能兼容禁止部署多个vSphere Replication 虚拟设备vzzz您的客户正在考虑为其环境实施虚拟机备份解决方案。
他们需要一个能够让他们动态扩展备份数据容量并备份150 个虚拟机的解决方案。
哪种解决方案最适合您的客户?请选择一个原因。
vSphere Data ProtectionvSphere Data Protection Advancedv您试图向正在运行的虚拟机热添加一个IDE 磁盘;但此选项呈灰色显示。
这可能是什么原因造成的?请选择一个原因。
无法向正在运行的虚拟机热添加IDE 磁盘@zzz客户指出,几个虚拟机的运行速度低于预期。
在调查此问题时,您发现每个虚拟机都有多个活动快照。
您还发现虚拟机所在数据存储中的可用存储空间过少。
您会向客户提出哪些与使用快照有关的建议?请选择两个原因。
不应在生产系统中长时间使用快照快照只能与完整的虚拟机备份一起使用使用Storage vMotion 将虚拟机磁盘文件转换为精简配置磁盘检查是否将vSphere 数据存储警报设置为高于30% 的值且该功能是否正常客户有一款运行 4 个虚拟机的应用解决方案。
他们需要在一定时间内不断地将此解决方案复制到一些单独的生产实例中。
您会建议客户使用哪种最适合其需要的部署方法?请选择一个原因。
关闭虚拟机,将其转换为 4 个模板。
然后在需要时使用这 4 个模板来部署 4 个新虚拟机。
当需要新的解决方案实例时,应该基于原始的应用解决方案虚拟机克隆 4 个新虚拟机。
将这 4 个虚拟机转换为一个模板。
当需要新的解决方案实例时,使用此模板来部署虚拟机基于正在运行的虚拟机制作多个克隆,并在需要这些克隆之前将其存放到辅助存储中。
当需要时,将这些克隆迁移到生产环境。
zzz客户的现有备份解决方案可以备份虚拟机,但只能执行完全备份。
他们有意使用vSphere Data Protection 设备来替换现有的虚拟机备份解决方案,但想要进一步了解其优势。
以下哪几项是使用VDP 的优势?请选择两个原因。