How to manually delete NetApp SnapMirror snapshots

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.

Continue reading…


How to fix VMware Converter error “FAILED: The VSS snapshots cannot be stored”

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.

Continue reading…


How-to fix VMware Converter error FAILED: Unable to find the system volume, reconfiguration is not possible.

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.“.

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.

Continue reading…


Fixing, This host currently has no management network redundancy

host no management network redundancy

I recently redid my VMware home lab environment and after enabling HA the warning message “This host currently has no management network redundancy” started displaying on each of my ESXi hosts.

This warning happens because in a HA cluster there is a requirement for the management network to have redundant NICs, but in my case I’m using Intel NUCs which only have a single NIC and since this is only a lab I don’t care to see the warning so lets disable it.

Continue reading…