Smiley face

Google
در فروشگاه اينترنتي داتيس   در كل اينترنت

تقويم و مناسبتها

رهگيري مرسولات پستي

كاربرگرامي شما مي توانيد پس از دريافت باركد پســتي از طريق دكمه رهگيري سفارشـات ، بوسيله دكمه رهگيري مرسوله پستي ، مرسـوله خود را از طريق وب سايت اداره پســت رديابي نماييد.

Datissoftware

Datissoftware

نماد ها

logo-samandehi

عناوين علمي و آموزشي

نرم افزارهاي مورد نياز

IDM دانلود Internet Download Manager
Chrome دانلود Google Chrome
Firefox دانلود Mozilla Firefox
Winrar دانلود Winrar
FlashPlayer دانلود Flash Player
Adobe Reader دانلود Adobe Reader
Mp4 Codec دانلود Mp4 Codec

آمار و اطلاعات

جهت عضــويت در خبرنامه فروشــگاه اينترنتي داتيــس ايميل صحيح خود را وارد نماييد.

عنوان : كتاب VMware Virtual SAN Cookbook

1394/07/18 - 15:15:34
كتاب راهنماي كامل پياده سازي VMware Virtual SAN و عملياتي سازي آن


دانلود كتاب VMware Virtual SAN Cookbook

آموزش شبكه داتيس

آموزش Windows Server 2012 داتيس

Book Description:

VMware Virtual SAN is a radically simple, hypervisor-converged storage, designed and optimized for vSphere virtual infrastructure. VMware introduced the software to help customers store more and more virtual machines. As data centers continue to evolve and grow, managing infrastructure becomes more challenging. Traditional storage solutions like monolithic storage arrays and complex management are often ill-suited to the needs of the modern data center. Software-defined storage solutions, like VMware Virtual SAN, integrate the storage side of the infrastructure with the server side, and can simplify management and improve flexibility


:Book Details

Publisher:    Packt Publishing
By:           Jeffrey Taylor
ISBN:         978-1-78217-454-7
Year:         2015
Pages:        208
Language:     English
File size:    5.6 MB
File format:  PDF

: CONTENTS

Chapter 1: Hardware Selection for Your VSAN Cluster

Introduction

Using the VMware Compatibility Guides

Selecting a server platform

Selecting a storage controller

Selecting a solid-state drive (SSD) for the cache tier

Selecting capacity tier disks

Deciding on a network standard

Choosing a VSAN Ready Node (an alternative option)

Chapter 2: Initial Configuration and Validation of Your VSAN Cluster

Introduction

Preparing the vCenter cluster for VSAN

Applying VSAN licensing (optional)

Configuring VSAN networking on a new standard switch

Configuring VSAN networking on an existing switch

Enabling SSH on the ESXi hosts (if applicable)

Tagging disks as local solid-state drives (if applicable)

Enabling VSAN on your cluster

Manually claiming disks for use by VSAN (if applicable)

Performing initial validation of the new VSAN cluster

Enabling vSphere HA

Chapter 3: Storage Policy-based Management

Introduction

Creating VM storage policies

Applying storage policies to a new VM or a VM deployed from a template

Applying storage policies to an existing VM migrating to VSAN

Viewing a VM's storage policies and object distribution

Changing storage policies on a VM already residing in VSAN

Modifying existing storage policies

Summary

Chapter 4: Monitoring VSAN

Introduction

Examining VSAN datastore health

Examining VSAN disk health

Examining VM object health

Creating VSAN-specific alarms 74

Examining VSAN resync activity (vSphere 6.0)

Chapter 5: VSAN Maintenance Operations

Introduction

Understanding and using VSAN Maintenance Mode

Adding disks to VSAN

Removing disks/disk groups from VSAN

Replacing disks in VSAN in the event of a disk failure

Changing VSAN networking

Permanently decommissioning a VSAN node

Recovering a VSAN cluster in the event that vCenter is lost/migrating

a VSAN cluster to a new vCenter server

Chapter 6: Ruby vSphere Console

Introduction

Launching RVC (Windows vCenter)

Launching RVC (Linux vCenter Appliance)

Navigating RVC

The vsan.cluster_info command

The vsan.disks_stats command

The vsan.vm_object_info command

The vsan.vm_perf_stats command

The vsan.resync_dashboard command

Chapter 7: Troubleshooting VSAN

Introduction

Investigating network partitions (with vSphere Web Client)

Investigating network partitions (without vSphere Web Client)

Investigating storage provider registration problems

Investigating other SPBM problems

Investigating VM provisioning or power-on failures

Investigating disk failures

Investigating VSAN performance with VSAN Observer

Chapter 8: Support Success

Introduction

Formulating a problem description

Formulating a problem summary

Collecting logging information

Collecting other diagnostic information

Chapter 9: VSAN 6.0

Introduction

Tagging disks as SSDs in vSphere 6.0

VSAN 6.0 fault domains

Upgrading to the VSAN 6.0 on-disk format

Appendix A: Chapter-specific Expansions

Chapter 1 – VSAN Capacity Planning

Chapter 2 – HA requirements for VSAN enablement

Chapter 3A – VSAN-specific storage-policy options

Chapter 3B – VSAN Default Storage Policy

Chapter 6 – vCenter inventory layout in RVC

Appendix B: Additional VSAN Information

VSAN network considerations

VSAN object distribution

vCenter object distribution view and VM snapshots

Understanding VSAN striping

Per object quorum in VSAN

VSAN synchronous I/O flow

VSAN object resynchronization

VSAN cluster expansion

VSAN rebuild logic and thresholds

RVC scripting and redirects

Third-party utilities

Index


:Preface

.VMware Virtual SAN (VSAN) is the converged storage solution for VMware vSphere
Integrated directly into the hypervisor, this is a native solution with no VM-based
intermediaries for storage delivery. As a result, VSAN is fast, simple to deploy and
.manage, and integrates tightly with the existing VMware vSphere product suite
As the solution is native to ESXi and runs on the hypervisor itself, its architecture is simplified
and the storage-delivery mechanism is tightly integrated and uniquely suited to the needs
of vSphere infrastructures. VSAN is an object-oriented storage solution, where each VM
is comprised of a number of objects physically distributed across the ESXi cluster. This
object-oriented nature means that access to your data happens natively, without the need
.for traditional intermediate storage protocols like iSCSI or Fibre Channel
VSAN's object-oriented nature also means that your VMs exist as a series of distributed
objects rather than a series of monolithic files. Whereas, with traditional storage, you have a
series of files (configuration files, virtual disks, swap, snapshots, and so on), with VSAN you
have a coordinated and related series of objects. These objects are a container for small
configuration files (the namespace object, also called VM Home), objects for each virtual
.disk, objects for each snapshot, and an object for the VM swap space
The key point when discussing VSAN's architecture, is how it integrates into the existing
hypervisor infrastructure to deliver the final service of any hypervisor: production virtual
machines. Behind this integration of the storage and compute virtualization layers is the
.notion of hyper-converged infrastructure. VSAN is one element of converged infrastructure
The goal of hyper-converged infrastructure is to abstract the traditional demarcations within
the environment (compute, network, and storage) by converging all aspects of the datacenter
.into a software-defined model with a centralized control plane and a distributed data/IO plane

VSAN is the storage element of the software-defined datacenter. User data (VMs) is abstracted
and distributed across the compute cluster. Each VM exists as a collection of related objects,
distributed optimally within the compute resources. VSAN natively integrates with vCenter
and its associated management tools. As a result, VSAN brings truly native, truly integrated
.management of the storage system into the existing and familiar vSphere operating structure
A major benefit to this new operating model of the storage system is its simplicity and
centralized management. VSAN obviates the need for traditional monolithic storage arrays
connected via traditional protocols. It also significantly improves on existing virtualization-centric
distributed storage solutions, typically delivered as virtual storage appliances (VSAs). Embedding
the distributed storage system into the hypervisor allows for gains in performance and
management. Native management through the vCenter Server means that storage for the
.virtual infrastructure can now be deployed and managed by the virtualization engineer

1394/07/18 - 15:15:34
برچسب هاي مطلب :



شما اولين نفري باشيد كه نظر ارسال مي كند.

فرم ثبت نظر

نام و نام خانوادگی
ایمیل
وبلاگ
نظر و کامنت
كد امنيتي