Tagged in: VMware

A overview of Big Cloud Fabric

Big Switch labels Big Cloud Fabric, the ” Next-Gen Data Center Switching Fabric”

From the above Link.

”

Big Cloud Fabric™ is the next-generation data center switching fabric delivering operational velocity, network automation and visibility for cloud-native applications and software-defined data centers, while staying within flat IT budgets.

Enterprise data centers are challenged today to support cloud-native applications, drive business velocity and work within flat budgets.

Network layer is often cited as the least agile part of data center infrastructure,especially when compared to compute infrastructure. The advent of virtualization changed the server landscape and delivered operational efficiencies across management workflows via automation. Emerging cloud-native applications are expected to demand even greater agility from the underlying infrastructure.

Most data centers are built using old network architecture, a box-by-box operational paradigm that inhibits the pace of IT operations to meet the demand of modern applications and software-defined data centers. Click here for more information on the challenges.

Software-defined data center is demanding network innovation. With virtualization going mainstream, networks are required to provide visibility into virtual machines, east-west traffic across VMs, and deliver network service connectivity easily. Networks are expected to not adversely impact software-defined data center agility by mandating manual box-by-box network configuration and upgrades. Emerging cloud-native applications require rapid application and services deployment. This demands network operations to be more automated instead of relying on manual CLI and limited GUI workflows. Lastly, infrastructure budgets trends have flat-lined in most organizations. This demands an innovative approach compared to the legacy network based on proprietary hardware that increases costs.

These network demands are met by software-defined networking (SDN) solutions. Leveraging a centralized controller, the SDN networks overcome the box-by-box operational paradigm to deliver business velocity. As applications become more distributed, SDN approaches are required for networks to become agile and automated via orchestrated workflows using RESTful APIs. By leveraging open industry-standard network hardware, SDN solutions provide vendor choice and drives down costs in a flat budget environment. This cycle of innovation has been witnessed before in the server infrastructure, driven by virtualization and containers. More recently, storage infrastructure is getting transformed as well with various software-enabled architectures.

”

Lets Dig in. Below is a overview of the Clos Fabric.

What are my use cases? What type of deployments support the fabric?

Who uses the product today?

How do I deploy this with my existing data center, do I need to worry about my legacy network working with Big Switch?

What has defined customer success?

API’s are key, how do you leverage them for automation?

How do you enable me to out scale my competitors?

How do you allow me to see inside my network?

How do you support multi tenancy?

Thanks

Roger Lund

Uncategorized

Register Storage Providers for Virtual Volumes? Why VVOL’S?

April 28, 2017 Roger LundNo comments

One of the main reasons I wanted to upgrade my lab to vSphere 6.5 was to play with VVOL’s or Virtual Volumes.

Why VVOL’s? Good Question. Lets Look at what is new in Virtual Volumes.

See What’s New: vSphere Virtual Volumes

Source http://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/products/virtualvolumes/vmware-whats-new-vsphere-virtual-volumes.pdf

“By transitioning from the legacy storage model to Software-Defined Storage with Virtual Volumes, customers will gain the following benefits:

Automation of storage “class-of-service” at scale: Provision virtual machines quickly across data center using a common control plane (SPBM) for automation.

Self-Service capabilities: Empower application administrators with cloud automation tool integration (vRealize Automation, PowerCLI, OpenStack).

Simple change management using policies: Eliminate change management overhead and use policies to drive infrastructure changes.

Finer control of storage class of service: Match VM storage requirements exactly as needed with class of service delivered per VM.

Effective monitoring/troubleshooting with per VM visibility: Gain visibility on individual VM performance and storage consumption.

Non-disruptive transition: Use existing protocols (Fiber channel, ISCSI, NFS) across heterogeneous storage devices.

Safeguard existing investment: Use existing resources more efficiently with an operational model that eliminates inefficient static and rigid storage constructs.“

Sounds good, Since I have a Solidfire in my lab that supports it, and it’s enabled. Whats first?

The first step is to Register the Storage Provider.

Register Storage Providers for Virtual Volumes

Source https://pubs.vmware.com/vsphere-65/index.jsp?topic=%2Fcom.vmware.vsphere.storage.doc%2FGUID-6C8EE052-0504-4BCA-874A-7AB836361AD4.html

“Your Virtual Volumes environment must include storage providers, also called VASA providers. Typically, third-party vendors develop storage providers through the VMware APIs for Storage Awareness (VASA). Storage providers facilitate communication between vSphere and the storage side. You must register the storage provider in vCenter Server to be able to work with Virtual Volumes.

After registration, the Virtual Volumes provider communicates with vCenter Server. The provider reports characteristics of underlying storage and data services, such as replication, that the storage system provides. The characteristics appear in the VM Storage Policies interface and can be used to create a VM storage policy compatible with the Virtual Volumes datastore. After you apply this storage policy to a virtual machine, the policy is pushed to Virtual Volumes storage. The policy enforces optimal placement of the virtual machine within Virtual Volumes storage and guarantees that storage can satisfy virtual machine requirements. If your storage provides extra services, such as caching or replication, the policy enables these services for the virtual machine.

Prerequisites

Verify that an appropriate version of the Virtual Volumes storage provider is installed on the storage side. Obtain credentials of the storage provider.

Procedure

1

Browse to vCenter Server in the vSphere Web Client navigator.

2

Click the Configure tab, and click Storage Providers.

3

Click the Register a new storage provider icon ().

4

Type connection information for the storage provider, including the name, URL, and credentials.

5

Specify the security method.

Action

Description

Direct vCenter Server to the storage provider certificate

Select the Use storage provider certificate option and specify the certificate’s location.

Use a thumbprint of the storage provider certificate

If you do not direct vCenter Server to the provider certificate, the certificate thumbprint is displayed. You can check the thumbprint and approve it. vCenter Server adds the certificate to the truststore and proceeds with the connection.

The storage provider adds the vCenter Server certificate to its truststore when vCenter Server first connects to the provider.

6

To complete the registration, click OK.

vCenter Server discovers and registers the Virtual Volumes storage provider.

“

Next up. Making a Datastore within it.

Roger L

ESXi Register Storage Providers for Virtual Volumes Virtual Volumes. VMware vsphere 6.5 VVOL

Backup, VMware

Introducing Altaro VM Backup

September 9, 2015 Shawn CannonNo comments

Altaro is introducing a new version of their backup software that now adds support for VMware. The previous version was called Altaro Hyper-V Backup. The name change reflects support for backing up VMs regardless of Hyper-V or VMware. I had the opportunity to Beta test the new version and I wanted to share with you the results of my testing.

First things first, what do I install the Altaro software on? It has to be installed on one of the following operating systems:

• Windows 2008 R2
• Windows Server 2012
• Windows Server 2012 R2
• Windows 7 (64-Bit)
• Windows 8 (64-Bit)
• Windows 10 (64-Bit)

In my lab environment I had access to a Windows 2008 R2 system so that is what I installed it to.
Here are the versions of VMware that are supported in this new version:

Versions of VMware supported:
• VMware vSphere 5.0, 5.1, 5.5 and 6.0
• VMware vCenter 5.0, 5.1, 5.5 and 6.0
• VMware ESXi 5.0, 5.1, 5.5 and 6.0

In our lab we are running 6.0. All the prerequisites have been met. The installation of the Altaro software is very simple. Accept license agreement, tell it what path you want to install it and click Install. Like I said, simple!

After the software is installed, fire it up. You will be presented with the screen below:

Since this is the Altaro instance that I want, I will choose this machine and click Connect. This will send you to the dashboard. Now you need to add your VMware hosts. To do this, click on Setup > Hosts and click the Add Host button to get the wizard below.

I have a vCenter server in my lab so I am going to click on that option.

Enter your vCenter server name and admin username and password. Click Test Connection to make sure your credentials are working properly and then click Next. You will be presented with the hosts that the vCenter instance knows about.

Click Finish and the hosts will be added.

Next we need to setup our backup location. This can be a local drive on the Altaro server or a network path. For my lab test I am using a local drive on the Altaro server. To add the backup location, go to Setup > Backup Locations and click the Add Backup Location button.

I am going to click Physical Drive and click next and choose my D drive. I can specify a folder if I want the backups to always go into a certain folder. Once I have decided I just click finish and the backup location is set.

Now let’s setup a VM for this backup location. While I am on the Backup location screen there is an inventory view of all the VMs known to Altaro as shown below.

To assign VMs to my D drive backup location, I just select the VMs on the left and drag them over to the D drive. I am going to set TTYLinux to this location.

As you can see in the shot above TTYLinux will now use D as its backup location. Click SAVE CHANGES at bottom right to save these changes. If you forget to do this, the software will remind you.

Now let’s setup a backup schedule. To do this go to Setup > Schedules.

There are 2 default backup schedules already set: M-F at 10 PM and Sa-Su and 10 PM. I am going to use the Sa-Su 8 PM backup schedule. To do it, you just drag and drop the VMs to assign to that schedule. Click SAVE CHANGES to save it.

That is the basics of setting up Altaro for backing up VMware VMs. I will now cover a few other options of interest, the first one being Backup Retention.

To view the default options for backup retention, go to Setup > Retention Policy.

By default you will see the following retention policies: Never delete, 2 weeks, 1 month and 6 months. These are default policies for local and Offsite copies. You can create your own as well. You simply drag and drop the VMs to the proper retention policies that you need and click SAVE CHANGES.

You can take a backup at any time by going to Virtual Machines > Take Backup

Just click the machine you want to backup and click the red TAKE BACKUP button. I already did that and you can see in the screenshot that a backup is running for TTYLinux.

Restore options are what you would expect from backup software. You can do a full restore or a granular restore, which in Altaro’s case is file level restore or Exchange Item Level Restore.

There is also a Sandbox and Verification option so you can mount backups in a sandbox to test restores. I will show you a full restore in the sandbox so I can power a backup on to verify it was a good backup. To test in sandbox, go to Sandbox & Verification > Test & Verify Backups.

I want to test a full restore so for Step 1 I am selecting that. Click Next to proceed to Step 2.

Check the backup locations to test. In my test environment this will be the D drive so I have checked that. Click Next to process to Step 3.

The VMs you can test a full restore of are shown. I only have one VM although for some reason it is showing twice. I will just select the first one and click Next to proceed to Step 4.

Step 4 are the restore options. You can pick the backup you want to restore. If you have multiple backups of the VMs you can select the instance you want to test. You can also choose the host and datastore to restore to. I chose a different host and datastore to test with. Click Perform Test Restore to start the process.

A green notification will appear that tells you to go to the Dashboard to monitor the progress. Click the green button to head over there.

Once the test restore is complete you will see the VM in your vCenter inventory. The VM name will be similar to TTYLinux-Sandbox-2015-09-09 19-59 but it does not look like it actually puts the VM into a different network group to truly sandbox the VM off from the original. You would need to assign this VM to a different network to not interrupt the production VM. Having to do this manually is not ideal and I would recommend to Altaro that this be added into a future release. Once assigned to a “sandbox” network, power it on to make sure it works. When you are finished testing, power the VM down and delete it.

Overall Altaro is a very nice and easy to use solution for backing up VMware VMs. I like the fact that all the VMs you would assign to storage, backups, retention, etc show on the same screen as what are are trying to configure. That way you can easily select VMs from the left pane to drag and drop to the right pane. I would rate it 4 out of 5 stars as it has all the main features you would want in backup/protection software. The only negative for me is the sandbox feature missing the ability to choose a different network as part of the test restore.

For product information, please visit the Altaro VM Backup site. You can also pull up the latest user guide here.

Altaro Backup VMware

VMware, VMworld

Early peak at the #vBrownBag TechTalks Schedule at VMworld US 2015

August 26, 2015 Shawn CannonNo comments

The professionalvmware.com site, the home of the #vBrownBag goodness, has posted an early look at the schedule for the #vBrownBag TechTalks in the hang space at VMworld US 2015. I wanted to re-post the schedule here to increase awareness of these talks. If you are going to hang out in the hang space, please come and support this individuals!
(Note: Info shared from http://professionalvmware.com/2015/08/vbrownbag-techtalks-schedule-vmworld-usa-2015/)

Time	Monday	Tuesday	Wednesday	Thursday
10:30	vExpert Daily	vExpert Daily	vExpert Daily	vExpert Daily
11:00	Edward Haletky @Texiwill 6-Step Program for Hybrid Cloud	Edward Haletky @Texiwill Let’s Throw in Some Security: A hybrid Cloud Security Model	Virtualization Practise Panel	Chris Wahl -Scripting and Versioning with PowerShell ISE and Git Shell
11:15	Irfan Ahmad – CloudPhysics – The Unofficial VCDX Toolchest	Irfan Ahmad – CloudPhysics – Help! My Dashboards Suck!	continued	Vaughn Stewart – Run 20% – 40% more VMs per host with Flash Storage
11:30	Michael White – Spotlight on Your Data	Kenneth Hui -The Easy Button For Turning Your vSphere Environment Into A Private Cloud	Gabriel Chapman – Solidfire – Infrastructure Agility in the Software Defined Data Center	Josh Atwell – DevOps with PowerCLI and PowerShell DSC
11:45	Andy Warfield – Coho Data	Andy Warfield – Coho Data	continued	Cody Hosterman – Space Reclamation in vSphere 6
12:00	VMUG LATAM Panel (Spanish)	Anthony Spiteri – NSX – An Unexpected Journey	VMware Communities Podcast	Eric Wright – Getting to the Core with CoreOS
12:15	continued	Ken Thomas -One Solution for All: Deploy to VMs and Physical using MDT	continued	James Brown -Virtual Design Master
12:30	Dave LeClair – Unitrends – Recover Simplicity!	Dave LeClair – Unitrends – Is your data protection and DR solution built for a cloud-driven world?	continued	continued
12:45	Joseph Griffiths – Reference Architecture for Automation	Luis Concistre – Horizon View & VMware NSX	continued	Tim Carr – Versioning deployments with Puppet, R10K, and Git
13:00	Kevin Moats – GPU virtualization in the home lab	HP Blogger Briefing	Dave Frederick – The Advantages of a Tiered Approach to VM Storage	Steve Flanders – The importance of customer experience
13:15	Gina Rosenthal (Minks) – Why you need to #BackThatSaaSUp	continued	Gabriel Maciel – VMware NSX Architecture and Components Interaction
13:30	Scott Davis – Infinio – Disruptive Storage Innovations and the Impact on Virtual Desktop Solutions	continued	vBrownBag LATAM Panel (Spanish)
13:45	Scott Davis – cont	continued	continued
14:00	Jaison Bailley and the vBrisket community	continued	Paul Braren – Home Virtualization Lab Productivity Tips	Hang Space Closed
14:15	Luke Brown – Dinosaurs Didn’t Do DR	continued	Anthony Chow – Micro-Segmentation – a perfect fit for microservices security
14:30	Craig Waters – Anatomy of an SSD	Craig Waters – How to start a user group (BYOUG)	Shruti Bhat – Liuve demo – Running your ESXi workloads in AWS
14:45	Jonathan Frappier and Tim Jabaut – Stop being an “Admin” and learn to embrace “DevOps”	Edward Haletky @Texiwill – Proper Use of RBAC to Secure your Virtual Environment	John Arrasjid – IT Architect: Foundation in the Art of IT Infrastructure Design
15:00	In Tech We Trust Podcast	Speaking in Tech Podcast	Geek Whisperers Podcast
15:15	continued	continued	continued
15:30	continued	continued	continued
15:45	continued	continued	continued
16:00	Dennis Bray and Chip Copper – Brocade – NSX based Advanced Network Architecture in SDDC to deploy highly automated IT Service Delivery	Elver Sena Sosa and Anuj Dewangan – Brocade -Scaling your cloud network: Building a massively scalable cloud infrastructure with VMware NSX & advanced physical network architectures	Tony Foster – Sizing for GPU Workloads
16:15	David Siles – Proactive Data-Awareness Inside Your VMs	David Klebanov – SDDC Gone Global with Software Defined WAN	Brian Trainor – Automatic” remediation with vRealize Operations
16:30	Michaell Rice – Rackspace – Stop testing scripts in production; Meet vCenter Simulator	Luke Huckaba – Rackspace – A distilled version of the SRM talk	David Klee – SQL Server Virtualization Gotchya’s
16:45	Michael Rice – Introduction to pyVmomi	Michael Rice – YAVIJAVA an alternative Java SDK for vSphere	Michael Rice – vCenter Simulator For Functional Testing
17:00	Hersey Cartwright – Using PowerCLI to manage SSH on ESXi	Hersey Cartwright – Managing vCenter Roles and Permissions with PowerCLI	Hang Space closed
17:15	Eric Wright – Abstract all the things! Simplifying the whole stack	James Green, Emad Younis – ”Batman” is Not A Career Strategy
17:30	Cisco Panel	Nigel Hickey – The #vExpertSpotlight
17:45	continued	Steve Flanders – Quality log messages and how to write them

vBrownBag VMware VMworld

Uncategorized, vCenter, vCenter Server, VMware

My vCenter C: drive ran out of space

August 25, 2015 Aaron GruberNo comments

I came across something interesting today. The 160 GB C: drive on my vCenter Server ran out of space today…rather embarrassing. The first thing I checked is why in the heck my alerts didn’t go off…ok..problem fixed. After a couple of Google searches I came across and interesting VMware KB. Apparently there is a bug in the vCenter 5.5 upgrade that enables debug logging on the VMware Syslog Collector service and logs to C:\ProgramData\VMware\VMware Syslog Collector\logs\debug.log. In this case, my debug log was 62GB. The fix is rather simple. Stop the ‘VMware Syslog Collector’ service and edit the C:\ProgramData\VMware\VMware Syslog Collector\vmconfig-syslog.xml file (make a copy of it first) and change the following:

Remove the debug.log file and start the service again.

After upgrading to vCenter Server 5.5, the debug.log file of syslog collector is growing without limit (2094175)

”

KB: 2094175

Updated: Mar 3, 2015

Categories:
Troubleshooting

Languages:
English

Product(s):
VMware vCenter Server

Product Version(s):
VMware vCenter Server 5.5.x

Symptoms

After upgrading to vCenter Server 5.5, the debug.log file of syslog collector is growing without limit
C:\ProgramData\VMware\VMware Syslog Collector\logs\debug.log continues to grow without being rotated

Resolution

This is a known issue affecting VMware Syslog Collector 5.5.

Currently, there is no resolution.

To work around this issue:

Stop the VMware Syslog Collector service. For more information, see Stopping, starting, or restarting VMware vCenter Server services (1003895).
On the server running the VMware Syslog Collector service, navigate to C:\ProgramData\VMware\VMware Syslog Collector and save a copy of vmconfig-syslog.xml.
In a text editor, open vmconfig-syslog.xml and modify from:

<debug> <level>1</level> </debug>

to

<debug> <level>0</level> </debug>
Start the VMware Syslog Collector service. For more information, see Stopping, starting, or restarting VMware vCenter Server services (1003895).

“

-Aaron

ESXi KB: 2094175 My vCenter C: drive ran out of space vCenter VMware

Uncategorized, VMware, VMworld, vSphere

Countdown to VMworld 2015 San Francisco

August 24, 2015 Aaron GruberNo comments

200Days

10Hours

10Minutes

10Seconds

countdown san francisco VMware VMworld vSphere

Uncategorized

Unitrends Free Edition. Protecting your assets with Asset Protection and Job Creation.

June 2, 2015 Roger Lund 3 Comments

Yesterday I write on Installing and Configuring Unitrends free edition. Today I will cover protecting your assets with Asset Protection. Then we will go over Job Creation. This allows you to have a backup of your VM’s for free!

Requirements:

For this scenario we will be using vCenter 5.5.

And we are off!

1. Browse to the UI.

2. Close the welcome to Unitrends free.

3. Navigate to Configure.

4. Click on the Protected Assets Tab.

5. Click Add, and select Virtual Host.

6. Put in your vCenter information and click save.

7. Now navigate to Protect.

8. Highlight your vCenter

9. Check the box next to the VM you would like to Backup.

10. Click Backup

11. A new window will popup, titled Create Backup Job.

12. Click Define Job Settings.

For now we are going to just run this job once. This is called a on demand job.

13. Under Schedule, Select when to run this job: check Now, and save.

Right away a job success window pops up.

Lets take a look at the job to verify the job’s running status.

14. Click view Jobs.

15. Click on the job, and click View Details.

Once it completes you will see a Successful Status.

Congrats! You have just protected your first VM!

Roger Lund

backups Free unitrends VMware vSphere

Uncategorized

Unitrends offers free backup’s with Unitrends Free

May 28, 2015 Roger LundNo comments

Product overview:

Unitrends is a software company that has been doing backup’s since 1985 according to Wikipedia. On may 12th they announced a open beta to a free version of Unitrends free..

Unitrends free is a Virtual Appliance that offers data protection in the form of a Linux based VMware or Hyper-v VM. You can protect VM’s with Full backup’s, incremental backups, on demand or scheduled. You can recover individual files, the entire vm or perform a instant recovery.

Features in Unitrends Free include:

Free vSphere and Hyper-V Backup for Unlimited Virtual Machines (VMs) and Sockets. Unlike other tools that restrict usage by number of VMs or sockets, Unitrends Free provides hypervisor-level protection for up to 1 terabyte (TB) of data.
Instant VM Recovery. Unitrends Free makes it possible to quickly run a VM directly from a backup to reduce downtime. Instant recovery also allows users to spin up copies of their VMs for recovery verification, testing and development.
Automated Daily Scheduling. The product features “set it and forget it” scheduling with daily recovery points to keep a user’s system protected at all times – even when no one is around.
Fast, Incremental Forever Backups. Unitrends Free delivers changed-block tracking and incremental forever backups to ensure that backups complete rapidly every day – without using a lot of storage.
Cloud Integration. Users can also take advantage of low cost long-term storage via integration with third-party clouds such as Google Cloud Storage, Google Nearline and Amazon Simple Storage Service (S3).
Unitrends Community Integration. Users benefit from limitless support provided by the Unitrends Community. Directly integrated into the Unitrends Free user interface, IT professionals can search the forum and collaborate to help one another, while also earning attractive rewards. Source http://www.unitrends.com/company/press-releases/2015/unitrends-redefines-free%E2%80%9D-virtualization-backup-w

Availability:

The beta version of Unitrends Free is available to download now. Here is the Unitrends Free Administrator’s Guide

In celebration of the launch, one lucky user will win a $1,500 Visa Giftcard.

UnitrendsFree

To download the software and obtain more details regarding the sweepstakes, please visit: http://www.UnitrendsFree.com.

I will be following up with installation and configuration of the product.

Roger Lund

Backup Free hyper-v unitrends VMware

Health Check, Monitoring, optimization, Opvizor, Opvizor with VMware vSphere vCenter, Performance

Opvizor Inside the Dashboard.

February 16, 2015 Roger LundNo comments

This is my first post on a series of posts about opvizor. http://www.opvizor.com/ Opvizor is a predictive analysis and issue prevention tool.

In my previous post, Getting Opvizor Working by Michael White worth a read. Michael outlines the install process. I will continue , assuming you have setup the product.

Once we login to the webpage at https://opvizor.com/login/ we see a dashboard. Where to start? That is a lot of information.

In the top left you have the environmental overview. This includes your issues per cluster, host, VM, datastore, and network. As you can see I have induced lots of issues into my lab.

vmware vsphere opvizor home

Let’s dig into each.

Overall Status

Overall Statistics

Statistics by Upload

Issues by by Upload

Top 5 Largest Datastores

Top 5 Entities by Issue Rate

Top 5 VMs by Snapshot Usage

Yikes, that seems a little large doesn’t it?

Top 5 BMs by Memory Usage

These are fairly self explanatory. But we can dig into each to get more information from this screen.

If we click the small table icon next to Top 5 Larges Datastores

Here we can see more information on the Datastores in my lab.

This is our first look into Opvizor, of the series.

Roger Lund

Opvizor Opvizor ESXi Opvizor Health Check Opvizor Performance Opvizor reporting Opvizor vSphere Opvizor vSphere Health Check reporting VMware VMware Opvizor VMware vSphere vSphere reporting

Uncategorized, Virtual San, VMware, VSAN, VSAN 6.0, vSphere

VMware Virtual SAN 6.0

February 11, 2015 Roger Lund 1 Comment

The following Blog post is about VMware VSAN or Virtual San. http://www.vmware.com/products/virtual-san

The following post was made with pre GA , Beta content.

All performance numbers are subject to final benchmarking results. Please refer to guidance published at GA

All Content and media is from VMWare, as part of the blogger program.

Please also read vSphere 6 – Clarifying the misinformation http://blogs.vmware.com/vsphere/2015/02/vsphere-6-clarifying-misinformation.html

Here is the published What’s New: VMware Virtual SAN 6.0 http://www.vmware.com/files/pdf/products/vsan/VMware_Virtual_SAN_Whats_New.pdf

Here is the published VMware Virtual SAN 6.0 http://www.vmware.com/files/pdf/products/vsan/VMware_Virtual_SAN_Datasheet.pdf

Whats New?

Disk Format

New On-Disk Format
New delta-disk type vsanSparse
Performance Based snapshots and clones

VSAN 5.5 to 6.0

In-Place modular rolling upgrade
Seamless In-place Upgrade
Seamless Upgrade Rollback Supported
Upgrade performed from RVC CLI
PowerCLI integration for automation and management

Disk Serviceability Functions

Ability to manage flash-based and magnetic devices.
Storage consumption models for policy definition
Default Storage Policies
Resync Status dashboard in UI
VM capacity consumption per VMDK
Disk/Disk group evacuation

VSAN Platform

New Caching Architecture for all-flash VSAN
Virtual SAN Health Services
Proactive Rebalance
Fault domains support
High Density Storage Systems with Direct Attached Storage
File Services via 3rd party
Limited support hardware encryption and checksum

Virtual SAN Performance and Scale Improvements

2x VMs per host

Larger Consolidation Ratios
Due to increase of supported components per hosts
9000 Components per Host

62TB Virtual Disks

Greater capacity allocations per VMDK
VMDK >2TB are supported

Snapshots and Clone

Larger supported capacity of snapshots and clones per VMs
32 per Virtual Machine

Host Scalability

Cluster support raised to match vSphere
Up to 64 nodes per cluster in vSphere

VSAN can scale up to 64 nodes

Enterprise-Class Scale and Performance

vsan02

VMware Virtual SAN : All-Flash

Flash-based devices used for caching as well as persistence

Cost-effective all-flash 2-tier model:oCache is 100% write: using write-intensive, higher grade flash-based devices
Persistent storage: can leverage lower cost read-intensive flash-based devices

Very high IOPS: up to 100K(1)IOPS/Host
Consistent performance with sub-millisecond latencies

30K IOPS/Host100K IOPS/Hostpredictable sub-millisecond latency

Virtual SAN FlashCaching Architectures

All-FlashCache Tier Sizing

Cache tier should have 10% of the anticipated consumed storage capacity

Measurement Requirements	Values
Projected VM space usage	20GB
Projected number of VMs	1000
Total projected space consumption per VM	20GB x 1000 = 20,000 GB = 20 TB
Target flash cache capacity percentage	10%
Total flash cache capacity required	20TB x .10 = 2 TB

Cache is entirely write-buffer in all-flash architecture
Cache devices should be high write endurance models: Choose 2+ TBW/day or 3650+/5 year
Total cache capacity percentage should be based on use case requirements.

–For general recommendation visit the VMware Compatibility Guide.

–For write-intensive workloads a higher amount should be configured.

–Increase cache size if expecting heavy use of snapshots

New On-Disk Format

Virtual SAN 6.0 introduces a new on-disk format.
The new on-disk format enables:

–Higher performance characteristics

–Efficient and scalable high performance snapshots and clones

–Online migration to new (RVC only)

The object store will continue to mount the volumes from all hosts in a cluster and presents them as a single shared datastore.
The upgrade to the new on-disk format is optional; the on-disk format for Virtual SAN 5.5 will continue to be supported

Performance Snapshots and Clones

Virtual SAN 6.0 new on-disk format introduces a new VMDK type

–Virtual SAN 5.5 snapshots were based on vmfsSparse (redo logs)

vsanSparse based snapshots are expected to deliver performance comparable to native SAN snapshots.

–vsanSparse takes advantage of the new on-disk format writing and extended caching capabilities to deliver efficient performance.

All disks in a vsanSparse disk-chain need to be vsanSparse (except base disk).

–Cannot create linked clones of a VM with vsanSparse snapshots on a non-vsan datastore.

–If a VM has existing redo log based snapshots, it will continue to get redo log based snapshots until the user consolidates and deletes all current snapshots.

Hardware Requirements

Flash Based Devices In Virtual SAN hybrid ALL read and write operations always go directly to the Flash tier.
Flash based devices serve two purposes in Virtual SAN hybrid architecture

1.Non-volatile Write Buffer (30%)
–Writes are acknowledged when they enter prepare stage on the flash-based devices.
–Reduces latency for writes2.

2. Read Cache (70%)
– Cache hits reduces read latency
– Cache miss – retrieve data from the magnetic devices

Flash Based Devices In Virtual SAN all-flash read and write operations always go directly to the Flash devices.

Flash based devices serve two purposes in Virtual SAN All Flash:

1 .Cache Tier
–High endurance flash devices.
–Listed on VCG2.
2. Capacity Tier
–Low endurance flash devices
–Listed on VCG
Network

•1Gb / 10Gb supported
–10Gb shared with NIOC for QoS will support most environments
–If 1GB then recommend dedicated links for Virtual SAN
–Layer 3network configuration supported in 6.0

•Jumbo Frames will provide nominal performance increase
–Enable for greenfield deployments
–Enable in large deployments to reduce CPU overhead

•Virtual SAN supports both VSS & VDS–NetIOC requires VDS
•Network bandwidth performance has more impact on host evacuation, rebuild times than on workload performance

High Density Direct Attached Storage

–Manage disks in enclosures – helps enable blade environment
–Flash acceleration provided on the server or in thesubsystem
–Data services delivered via the VSAN Data Services and platform capabilities
–Direct attached and disks (flash devices, and magnetic devices) are Supports combination of direct attached disks and high density attached disks (SSDs and HDDs) per disk group.

Users are expected to configure the HDDAS switch such that each disk is only seen by one host.

–VSAN protects against misconfigured HDDASs (a disk is seen by more than 1 host).
–The owner of a disk group can be explicitly changedby unmounting and restamping the disk group from the new owner.

•If a host who own a disk group crashes, manual re-stamping can be done on another host

.–Supported HDDASs will be tightly controlled by the HCL (exact list TBD).•Applies to HDDASs and controllers

FOLLOW the VMware HCL. www.vmware.com/go/virtualsan-hcl

Upgrade

Virtual SAN 6.0 has a new on disk format for disk groups and exposes a new delta-disk type, so upgrading from 1.0 to 2.0 involves more than upgrading the ESX/VC software.

Upgrades are performed in multiple phases

Phase 1: Fresh deployment or upgrade of to vSphere 6.0

vCenter Server

ESXi Hypervisor

Phase 2: Disk format conversion (DFC)

Reformat disk groups

Object upgrade

Disk/Disk Group Evacuation

In Virtual SAN 5.5 in order to remove a disk/disk group without data lost, hosts were placed in maintenance mode with the full data evacuation mode from all disk/disk groups.
Virtual SAN 6.0 Introduces the support and ability to evacuate data from individual disk/disk groups before removing a disk/disk group from the Virtual SAN.
Supported in the UI, esxcli and RVC.

Check box in the “Remove disk/disk group” UI screen

Disks Serviceability

Virtual SAN 6.0 introduces a new disk serviceability feature to easily map the location of magnetic disks and flash based devices from the vSphere Web Client.

Light LED on failures
When a disk hits a permanent error, it can be challenging to find where that disk sits in the chassis to find and replace it.
When SSD or MD encounters a permanent error, VSAN automatically turns the disk LED on.
Turn disk LED on/off
User might need to locate a disk so VSAN supports manually turning a SSD or MD LED on/off.
Marking a disk as SSD
Some SSDs might not be recognized as SSDs by ESX.
Disks can be tagged/untagged as SSDs
Marking a disk as local
Some SSDs/MDs might not be recognized by ESX as local disks.
Disks can be tagged/untagged as local disks.

Virtual SAN Usability Improvements

What-if-APIs (Scenarios)
Adding functionality to visualize Virtual SAN datastore resource utilization when a VM Storage Policy is created or edited.

–Creating Policies

–Reapplying a Policy

Default Storage Policies

A Virtual SAN Default Profile is automatically created in SPBM when VSAN is enabled on a cluster.

–Default Profiles are utilized by any VM created without an explicit SPBM profile assigned.

vSphere admins to designate a preferred VM Storage Policy as the preferred default policy for the Virtual SAN cluster

vCenter can manage multiple vsanDatastores with different sets of requirements.
Each vsanDatastore can have a different default profile assigned.

Virtual Machine Usability Improvements

Virtual SAN 6.0 adds functionality to visualize Virtual SAN datastore resource utilization when a VM Storage Policy is created or edited.
Virtual SAN’s free disk space is raw capacity.

–With replication, actual usable space is lesser.

New UI shows real usage on

–Flash Devices

–Magnetic Disks

Displayed in the vSphere Web Client and RVC

Virtual Machine >2TB VMDKs

In VSAN 5.5, the max size of a VMDK was limited to 2TB.

–Max size of a VSAN component is 255GB.

–Max number of stripes per object was 12.

In VSAN 6.0 the limit has been increased to allow VMDK up to 62TB.

–Objects are still striped at 255GB.

62TB limit is the same as VMFS and NFS so VMDK can be

There it is. I tried to lay it out as best I could.

Want to try it? Try the Virtual SAN Hosted Evaluation https://my.vmware.com/web/vmware/evalcenter?p=vsan6-hol

What’s New in Virtual SAN 6

Learn how to deploy, configure, and manage VMware’s latest hypervisor-converged storage solution.

HOL-SDC-1408-testdrive .

– See more at: https://my.vmware.com/web/vmware/evalcenter?p=vsan6-hol#sthash.OcuO1gXQ.dpuf

Roger Lund

Virtual SAN VMware VSAN VSAN 6.0 vSphere

vBrainstorm.com

Tagged in: VMware

Big Switch – Big Cloud Fabric

Register Storage Providers for Virtual Volumes? Why VVOL’S?

Introducing Altaro VM Backup

Early peak at the #vBrownBag TechTalks Schedule at VMworld US 2015

My vCenter C: drive ran out of space

After upgrading to vCenter Server 5.5, the debug.log file of syslog collector is growing without limit (2094175)

Symptoms

Resolution

“

Countdown to VMworld 2015 San Francisco

Unitrends Free Edition. Protecting your assets with Asset Protection and Job Creation.

Unitrends offers free backup’s with Unitrends Free

Opvizor Inside the Dashboard.

VMware Virtual SAN 6.0

What’s New in Virtual SAN 6