Help with my first Hyper-V setup

LJ

@black3dynamite I like it so far. I can't remember why I tried it instead of Veeam but to seems to work fine. I haven't tried a restore from it yet.

DustinB3403

@lj said in Help with my first Hyper-V setup:

@dustinb3403 Any reason you would prefer UrBackup over Altaro Free or Veeam free?

A bit more flexibility with open source software compared to free but closed source software is all.

FATeknollogee

@dustinb3403 said in Help with my first Hyper-V setup:

@LJ when you install the drivers into the VM's the hypervisor will be able to manage the RAM allocated to each VM. This way you can over-allocate (to a reasonable degree) and be pretty safe and not have to worry about not allowing enough RAM for Dom0.

Dude, don't make statements like this if you're not sure of what you are talking about!

BRRABill

@black3dynamite said in Help with my first Hyper-V setup:

I use Altaro VM Backup (Free Edition) and works great. Free edition allows up to 2 VM which you are currently using anyway. If you will need more, the standard is $515 per host for up to 5 VMs.
https://www.altaro.com/vm-backup/pricing.php

Does that include file-level restore?

And what do you do to get the backups offsite?

black3dynamite

@brrabill said in Help with my first Hyper-V setup:

@black3dynamite said in Help with my first Hyper-V setup:

I use Altaro VM Backup (Free Edition) and works great. Free edition allows up to 2 VM which you are currently using anyway. If you will need more, the standard is $515 per host for up to 5 VMs.
https://www.altaro.com/vm-backup/pricing.php

Does that include file-level restore?

And what do you do to get the backups offsite?

File-level restore is only available with Standard, Unlimited and Unlimited Plus.

You have a couple of options to have backups offsite.
Local backups can be copied to an Altaro Offsite Server over a WAN/Internet Connection. Or local backups can be copied to one or more rotating drives.

LJ

Thanks for everyone for everything I've learned so far. Here is my next problem. I decided to expand my volume the Hyper-V OS is on. I was able to use Diskpart to shrink the other volume but was unable to extend the OS volume. They must not be adjacent but without Disk Management I don't have a visual. I tried booting Gparted and Partition Wizard mini tool. Neither would boot. They may be a few years old. How can I extend the volume?

Obsolesce

@lj said in Help with my first Hyper-V setup:

Thanks for everyone for everything I've learned so far. Here is my next problem. I decided to expand my volume the Hyper-V OS is on. I was able to use Diskpart to shrink the other volume but was unable to extend the OS volume. They must not be adjacent but without Disk Management I don't have a visual. I tried booting Gparted and Partition Wizard mini tool. Neither would boot. They may be a few years old. How can I extend the volume?

You can use disk management remotely.

Open up compmgmt.msc on Win10 computer, then right-click to connect to another computer. Connect to your Hyper-V host, then under Storage, select Disk Management.

But yeah, if they aren't adjacent, you won't be able to extend, but you may be able to span or whatever if you convert it to a Dynamic disk... but if you dont' have any production VMs going, I'd start over.

Make your partition like 65-85 GB, and for partition, use the rest of it for VM storage.

LJ

@obsolesce That is the one thing I haven't been able to get working. computer management will allow some of the functions like users and groups but the disk management won't work and I've tried a lot of googled solutions. Most of them are Powershell commands to run on both machines. None of them have worked.
Starting over may be good experience anyway. I will backup my VMs with Altaro and also with Hyper-V manager if I figure out how. If I lose the VMs I still wouldn't be in too bad a shape.

LJ

@lj The message when attempting Disk Management is "You do not have access rights to Logical Disk Manager on...

Obsolesce

@lj said in Help with my first Hyper-V setup:

@lj The message when attempting Disk Management is "You do not have access rights to Logical Disk Manager on...

Is your Win10 computer and Hyper-v host joined to a MS AD domain?

LJ

@obsolesce The Win10 is and the HyperV host is not.

Obsolesce

There's things you need to do like allow remote access to the Plug and Play interface, open up some firewall rules, allow remote server management through WinRM, automatic startup of Plug and Play service and Windows Remote Management (WS-Management) service, etc.

Obsolesce

Also, run winrm qc on both.

Obsolesce

Isn't it a PITA if you're not accustomed to it all?

This is why KVM is so nice.

LJ

@obsolesce Thanks. I've done a lot of those but actually can't remember all of them right this second. I think most of those were required for Hyper-V manager, Windows Admin Center and the parts of Computer mangement that do work.
I'll start through your list and try to see what I've missed.

LJ

@lj Just ran winrm qc on both. Each one said "WinRM
service is already running on this machine. WinRm is already setup for remote management on this computer"

LJ

@obsolesce I have considered KVM but for now am trying Hyper-V. I still plan to load KVM on an old desktop when I get a chance.

LJ

@obsolesce Windows Remote Management was already set to automatic. Plug and Play was running but wasn't set to automatic.
How do I allow remote access to Plug and Play interface?
(BTW I plan to archive this whole thread for reference)

Obsolesce

@lj said in Help with my first Hyper-V setup:

How do I allow remote access to Plug and Play interface?

Open up mmc on your desktop, and add the Group Policy Object Editor, connecting to your Hyper-V host.

Browse to: Computer Configuration/Administrative Templates/System/Device Installation then enable Allow remote access to the Plug and Play interface.

But is that the error you get when trying to access Disk Management of your Hyper-V host remotely?

Are you connecting as a user that has permissions on the Hyper-V host?

There are also some firewall rules that need to be opened for remote Disk Management (on your Hyper-V host).

Remote Volume Management - Virtual Disk Service (RPC)
Remote Volume Management - Virtual Disk Service Loader (RPC)
Remote Volume Management (RPC-EPMAP)

Enable-NetFirewallRule -name RVM-RPCSS-In-TCP,RVM-VDSLDR-In-TCP,RVM-VDS-In-TCP

LJ

@obsolesce I think I'm getting closer. I updated the local group policy and on the desktop and ran your commands on the host. Now instead of You do not have access rights to Logical Disk Manager on..I am getting "unable to connect to virtual disk service"

Are you connecting as a user that has permissions on the Hyper-V host? Not sure. I am logged into my domain user on the desktop and created a user with same name and password on host. that may not be enough. Is there a run as option for opening computer management?