- Altaro has just released a new version of their virtual machine (VM) backup solution for Hyper-V and VMware environments that now includes WAN-Optimized Replication: Altaro VM Backup v8. WAN-Optimized Replication permits a business to make an ongoing copy of its virtual machines (VMs) to a remote site and to switch to that copy with immediacy should anything go wrong with the live VMs, such as damage due to hurricanes, fires and flooding. Downtime is therefore reduced to no time at all. Some more info here and here.
- They have now also launched Altaro Office 365 Backup for MSPS! As Microsoft does not back up Office 365 subscriber data, Altaro’s new offering enables MSPs to provide their customers with robust, reliable mailbox backup and recovery services. Altaro Office 365 Backup for MSPs backs up mail items and their attachments, with backups taking place automatically several times per day to Altaro’s secure Microsoft Azure backup location. MSPs can manage and monitor the mailboxes they are handling per customer through a centralized, multi-tenant online management console. More info here and here.
Launch of Altaro Dojo Forums
We have already mentioned new Azure VM series Dv3 and Ev3 which enable running VMs inside Azure VMs or just nested virtualization. Today we are going to get it configured and to run our first nested VM in Azure.
But before we start, let’s review some Dv3 and Ev3 facts:
they introduce Hyper-Threading Technology running on the Intel® Broadwell E5-2673 v4 2.3GHz processor and Intel® Haswell 2.4 GHz E5-2673 v3
they made shift from physical core to virtual CPUs (thanks to HT technology) to support larger VM sizes
they are the first Azure VMs running on Windows Server 2016 hosts
Dv3 VMs are up to 64 vCPUs and 256 GB RAM
Ev3 VMs are up to 64 vCPUs and 432 Gb RAM
they are currently available only for certain regions (West Europe, US East, US West 2, Asia Pacific Southeast)
To get started with “nesting” you need to create one or more Dv3/Ev3 VMs in Azure within compatible region. For quick demo purposes, I created D2S_V3 VM with Windows Server 2016 DC , standard managed disk with no data disks attached.
TIP: actually you can , for instance, create 2 or more VMs , add data disks and configure storage spaces between them to achieve higher IO performance.
Then you need to install Hyper-V role and restart VM to apply changes
Install-WindowsFeature Hyper-V -IncludeManagementTools -Restart
Verify that Hyper-V role is installed and add internal switch. New adapter “vEthernet (switchname)” will be created under network connections list (ncpa.cpl)
Define a new IP address for this adapter (I’m using 192.168.0.0/24 subnet). This network will be used as a NAT gateway for new VMs in order to allow internet access from nested VMs.
#Check Hyper-V role state
Get-WindowsFeature Hyper-V|ft InstallState, PostConfigurationNeeded
#Add new internal switch
New-VMSwitch -SwitchName "NSW01" -SwitchType Internal
# IP Configuration for vNIC
New-NetIPAddress -InterfaceAlias "vEthernet (NSW01)" -IPAddress 192.168.0.23 -PrefixLength 24
Configure NAT rule to provide “access” to our nested VMs
New-NetNat -Name Nat_VM -InternalIPInterfaceAddressPrefix 192.168.0.0/24
Now our nested VMs can assign IP addresses from 192.168.0.0/24 subnet (manual assignment). If you want to have dynamic IP assignment – create add. VM and configure DHCP. Continue reading “How to enable nested virtualization in Azure”