Eric Sloof - NTPRO.NL

With no faltering in capacity demand, the solid-state memory industry finds itself in interesting times. Exciting times from a development and research perspective, with new technologies reaching mass production, and a steady pace of improvement from a capacity and performance perspective.

But also, uncertain times: massive investments made to satisfy demand, combined with strategic developments in Asia may put the industry at risk of oversupplying the market and causing steep price declines. Or could a significant price drop drive more flash adoption and bring balance?

This TECHunplugged Industry Insights research covers the major events in the solidstate memory industry in 2018 and provides outlook about trends and expected developments in 2019 and beyond.

This eBook is written by Nigel Hickey and David Stamen especially for vSphere administrators looking for additional information to help plan and execute the upgrade process.

The book contains reference scenarios that explain upgrade concepts that can be applied to nearly every situation, including upgrading from vSphere 6.0 and vSphere 6.5 to vSphere 6.7.

Also look at: Now Available – Upgrading to VMware vSphere 6.7 eBook

Download here!

The .vmsn file includes the current configuration (.vmx) and bios setting (.nvram). The memory is stored in the .vmem file. 

Maybe the virtual machine overhead and the delta page with memory changes made during the creation of the VMEM dump are also included so there’s no need for stunning the VM for a long time.  It could also include the memory of the VGA card.

This KB article contains misleading information the VMEM file is not mentioned and the VMSN file doesn't contain memory.

The vmsn also has CPU state, contents of CPU registers, GPU state, all needed for restoring back the exact state of your VM on when the snapshot was taken. The CPU flag list is not only for EVC, but also if you resume a VM on another host. You'll get a warning that CPU changed.

— Wil van Antwerpen (@wilva) January 11, 2019

It is my understanding that the screenshot you see on snapshotting/suspending a VM is also in the vmsn. But I've not confirmed that myself.

— Wil van Antwerpen (@wilva) January 11, 2019

In this three-day class, you learn to use VMware PowerCLI to automate major VMware vSAN tasks. You learn the basics of the vSphere Web Services API, which is the central interface through which all VMware automation tasks can be performed.

You gain hands-on knowledge about installing and configuring PowerCLI and learn the basic and advanced syntax. You also learn how to automate various tasks, such as reporting, health checks, configuration, maintenance, and troubleshooting of a vSAN cluster by using PowerCLI cmdlets.

By the end of the course, you should be able to meet the following objectives:

• Identify the function of an API and the Managed Object Browser (MOB)
• Explain the basics of PowerCLI 
• Describe the structure of PowerCLI objects 
• Describe how to use PowerCLI cmdlets 
• Describe how to write a script
• Explain the concept of loops in PowerCLI
• Perform advanced PowerCLI operations like Get-View
• Describe the fundamentals of vSAN
• Use cmdlets to run a report on vSAN
• Use cmdlets to configure the settings in vSAN
• Use cmdlets to troubleshoot vSAN and describe the syntax
• Describe advanced concepts with the vSAN management API