A while back I wrote a post on Hyper-V replication to Azure. At the time, the only options available to me were to create storage accounts outside of Europe. This worked but I thought it could be faster if it … Read More »
Since setting up Hyper-V Azure replication, the next step was to add this to the PRTG dashboard. To do this create a PowerShell file (Hyper-V Replication.ps1 or similar) and store it in: C:\Program Files (x86)\PRTG Network Monitor\Custom Sensors\EXE Enter the … Read More »
I had a Dell Precision T1700 running Windows 8.1 with client Hyper-V running just fine. However, after upgrading to Windows 10 whenever I started a VM I got the error: Virtual machine [VM Name] could not be started because the … Read More »
I think you’ll agree that you can never have enough backups and the thought of going back to the days of swapping out tapes on a regular basis and storing them in secure off-site locations is hopefully just a distant memory … Read More »
This is just a very simple PowerShell script to backup a given VM to a network path:
#PowerShell to backup a given VM
$vmname = "VMName"
$exportpath = "\\ComputerName\Archive$\Hyper-V Backups"
#if it already exists, remove it
if(Test-Path ($exportpath + "\" + $vmname))
Remove-Item -Path ($exportpath + "\" + $vmname) -Recurse
#export the vm
Export-VM -Name $vmname -Path $exportpath
So Windows Media Centre (WMC) has been killed off, but I’m bringing it back to life, ish. From my previous posts you will have seen my setup. It’s basically a single server at home running 2012R2 with a few VM’s … Read More »
A long time back I wrote an article on installing ZoneMinder inside a Hyper-V VM, well I recently had another go and it was much easier this time around and all the bugs seem to have been fixed too. Firstly, … Read More »
I recently was working on a 2012 cluster that had some issues. When a lot of live migrations were taking place, a node would just drop out of the cluster with the error:
HOSTNAME: The Cluster service is shutting down because quorum was lost. This could be due to the loss of network connectivity between some or all nodes in the cluster, or a failover of the witness disk.
Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapter. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.
Cluster node 'HOSTNAME' was removed from the active failover cluster membership. The Cluster service on this node may have stopped. This could also be due to the node having lost communication with other active nodes in the failover cluster. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapters on this node. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.
It seemed that the heartbeat was … Read More »
This was an interesting issue, one of my hosts was low on memory on Monday morning which flagged an alert to me via PRTG. Upon investigation, one of the virtual desktop machines was using around 65GB RAM. The machine itself … Read More »