VMware released ESXi 6.7 a little while ago, but it’s only been here recently have I started deploying it in my home and work lab environments. Below are two ways to easily upgrade your ESXi 6.5 hosts to ESXi 6.7 using the command line or by using the VMware ESXi offline bundle.
The other day, one of our volumes in the lab environment filled up. This volume has a couple large VM’s on it, coupled with a couple different Veeam backup jobs running using the native Veeam backup methods as well as using NetApp snap mirror to snapshot the volume and then using Veeam to ship it out to Azure.
At any rate the volume filled up to the point where vCenter wasn’t allowing me to migrate VM’s off the datastore. I really didn’t want to expand the volume just so I could move VM’s off of it.
Instead, I decided to delete some of the older proof of concept snapshots from SnapMirror. Below are the quick and easy steps to clear up some un-used snapshots and free up some space on the datastore.
I’ve been noticing a previous post about how to host a static site using AWS services has been gaining in popularity.
Most recently a blog post by Thom Greene (@tbgree00) had mentioned the previous article and while all the steps in the previous post are accurate and works – I wanted to share how I now host static websites using AWS S3 and Cloudflare.
While moving some VM’s from Hyper-V to VMware using VMware Converter a VM failed to convert with the error: FAILED: The VSS snapshots cannot be stored.
FAILED: The VSS snapshots cannot be stored because there is not enough space on the source volumes or because the source machine does not have any NTFS volumes. Error code: 2147754783 (0x8004231F).
Come to find out the System Reserved partition was full. Our soon to be retired Appassure backup application was nice enough to fill up the volume.
Luckily Appassure is being replaced by Veeam and fixing the above VMware Converter error is an easy fix.
I was recently tasked with migrating a Hyper-V machine to our VMware environment. However, each time VMware Converter was ran, the task would fail at 97% with an error “FAILED: Unable to find the system volume, reconfiguration is not possible.“.
Looking further into the virtual machine there were a number of concerns I had on the VM. One such issue which I believe might be causing the above error, is that the system volume drive was on drive 0 while the “C:” drive was on drive 1. Whereas these are typically on the same drive in most Windows installs.
Below are the steps I took to fix this VM and made the migration from Hyper-V to VMware a success.
Since it’s release date last month, I’ve been running Altaro VM Backup 7.6 in my home lab and one thing is for sure – Altaro VM Backup has certainly come a long way since the last time I did a Altaro VM Backup review.
Altaro is an easy to use, policy driven backup solution that is affordable for the small and medium sized businesses. VM Backup supports both Hyper-V and VMware environments and with the release of Altaro VM Backup 7.6 comes several new features that we’ll look at below.