@Obsolesce said in Hyper-V Node Failover Cluster Control:

@JaredBusch said in Hyper-V Node Failover Cluster Control:

@Obsolesce said in Hyper-V Node Failover Cluster Control:

@DustinB3403 said in Hyper-V Node Failover Cluster Control:

How can I migrate my VM's from Host 1 to Host 2 and ensure that the VMs don't attempt to automatically migrate back to their preferred host?

Migration? It's definitely not automatic in the least.

Planned failover? There's a checkbox to uncheck if you don't want automatic reverse replication and the VM to automatically start up. Could that be what you meant?

Of course it is. In an actual cluster. Which involves System Center Configuraiton Manager (SCCM).

@DustinB3403 used the word cluster, but he does not have one.

Oh shit, I missed that it was about a cluster. I was thinking Hyper-V Manager, right-click, live migration. Totally spaced there.

Yeah, that was my point, it is not a cluster.

It's been a while, so I missed some. Here's a much better break-down:
https://www.petri.com/new-file-types-windows-server-2016-hyper-v-vms

@BRRABill said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:

@scottalanmiller said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:

@Dashrender said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:

@scottalanmiller said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:

@Dashrender said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:

@scottalanmiller said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:

@Dashrender said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:

@scottalanmiller said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:

@Dashrender said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:

@scottalanmiller said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:

@Dashrender said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:

@scottalanmiller said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:

@Dashrender said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:

@scottalanmiller said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:

@JaredBusch said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:

@scottalanmiller said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:

Think of the alternative... how much hardware and man hours are going into working around extracting the data?

No where near as much as reverse engineering the database to create the output needed.

This is something I have done more than one time. It is not that easy.

Depends on the database. But it's something we do from time to time and often is pretty basic. I mean days of work, yes. But maintaining all that stuff is also days of work, plus the cost of hardware, isolation, risk, etc. On top of maintaining all that old stuff, we assume that there is no support should something break, either.

The system is basically in a static state. So if it breaks - restore to a known good working state and move on.

The problem I see running into over time is hardware and hypervisor tech that can support this until the kill date of 2036.

we can manually use the built system to do what is called a CCD export of the children's files - while this will be extremely manual in nature, it will likely be less expensive than hiring NTG or whomever to learn the DB layouts and extract the desired data.

Maybe, personally I think this seems very unlikely given 2036. That's 18 more years of dealing with stuff already in a ridiculous state today. Remember that you are going to be dealing with people that are not you and have no memory or knowledge of this system decades from now, a system already insanely old, trying to do restores or run systems 30 years old.

I doubt that that stuff will be cheap at that point, or anytime between now and then. A one time conversion to text files or PDF is over and done. Yeah, it's a bigger up front cost, but it is a single cost that never comes back to haunt you.

Oh believe me - I completely agree with you. Personally, we need to run a report to find all patients who were under 13 years old, export those. Then we can kill this system off in 2023 for all patients, and we'll have the children who have a longer hold requirement already exported.

Once you can export one, export all of them. The cost of one is the same as the cost of all.

With a script, you're right - I'm not looking to hire someone to make said script at this time.

You mean doing it manually? That'll likely take a really long time.

Well - the report will tell us how many patients we have, then management can make the determination if they want to hire someone to script it all - or just do it manually.

Any idea how long manually takes? Is that like just taking a screen shot of the current output?

No, the manual for children will likely be 1-4 mins, likely more on the 1 min side. But that's only a guess, I haven't done the process in years.

Oh, that's really fast. If it is that simple, let's say you have 10,000 customers. That's 10,000 - 40,000 minutes. I bet that it gets faster with someone doing one after another. That's a maximum of 33 weeks of full time work for 10,000 customers to be transferred.

And that is a lot of customers. And that is assuming four minutes per customer. And assuming that you realistically get four productive hours of doing a task like that per day.

wow - you really do build in the 'a person wastes half their work day away' don't you?

LOL, you have to, especially with a tedious task. You can't do that eight hours a day without bleeding from your ears.

Try it sometime. Time a task like that once. Then try to keep it up for an hour. Then realistically think about eight times that in a day. Then think about how hard it would be to do in an isolation chamber versus the real world with interruptions and other tasks that happen. Four hours in an eight hour day is actually quite hard.

I couldn't even read this post without checking my phone and buying something on Amazon.

Exactly!

Hmmm, forced reset and I can get into command prompt now

@hobbit666 said in Unable to Connect to Hyper-V 2016 Remotely:

I gave up on using hyperv manager and used Windows Admin Center instead.

https://docs.microsoft.com/en-us/windows-server/manage/windows-admin-center/understand/windows-admin-center

Not sure if I had mentioned it, but that's what we normally used but it broke first. Then we went to Hyper-V manager and it was broken as well. WAC is our normal tool for this stuff.

@emad-r said in Nested hypervisors?:

also as vendor they dont want the complexity advantages of Virtualization

ftfy

Create a new folder in the root of the data partition being used, if any, and call it something like Hyper-V-2018.

Copy the VHDX file(s) from their current location to that (assuming there is enough space to do so).

Run the following in an elevated PowerShell where X is the destination partition:

Set-VMHost -VirtualHardDiskPath "X:\Hyper-V-2018\Virtual Hard Disks" –VirtualMachinePath "X:\Hyper-V-2018"
Get-VMHost | fl VirtualHardDiskPath,VirtualMachinePath

Create a new VM and configure its settings using the existing OS VHDX. After that is complete, open the VM's properties and add the second VHDX if it exists.

Try and start the VM. If it starts, it will require some tweaking at the network level as the vNIC's GUID and MAC will be different.

Good stuff. Thanks for pointing this up and writing it up.

@phlipelder said in Use Hyper-V to replicate Linux vm file share:

@scottalanmiller said in Use Hyper-V to replicate Linux vm file share:

@phlipelder said in Use Hyper-V to replicate Linux vm file share:

Hyper-V Replica would work in this situation with a few caveats.

There is a 15 second limit on replication cycles. If the VMs are running database/active services this could be a problem.

That would be handled earlier in the process by the backup job. If the backup is good, the replication won't cause an issue. If the backup is bad, the replication can't fix it, of course, but will replicate the bad backup. But the only place that this can be addressed is in the backup step, the replication is of backup files, so not at a point in the process where it matters.

"Garbage in garbage out" never seems to go away. It's been the bane of our existence since the switch to image/block based backups. :S

File backups suffered from this, too. Databases are just hard to back up.

@jaredbusch said in Backup server - Software layout:

I use teams, even if there is only one NIC in the team most of the time, because I can add and remove NICs without impacting the higher layers.

Good idea. This server I just got has the onboard GB NICs, but also 2 dual port Intel GB NICs as well. I could create a BIG team if I wanted.

@lj said in Microsoft Hyper-V server 2016 and RD1000 backup:

Reading the Veeam Backup Free Edition it appears it installs the console on windows Server or Windows Desktop. Does that sound right? I installed Altaro on the Hyper-V host itself. I don't know which setup would be better though. Comments appreciated.

Yes, it goes on Windows.

@jaredbusch said in Ubuntu Set Default Resolution Through GRUB for VM:

@scottalanmiller said in Ubuntu Set Default Resolution Through GRUB for VM:

@aaronstuder said in Ubuntu Set Default Resolution Through GRUB for VM:

@scottalanmiller Ubuntu is a surprising choice for you 😉

Runs ScreenConnect.

So does Fedora.

Always fail when I do it, there is some trick to it. Happen to know what's needed so that it doesn't just put hashes on the screen for forever?

You can restart the Hyper-V Virtual Machine Management service or the Windows Remote Management service and it should work.

I ended up starting over from bare metal. Second attempt was A LOT better. Thank you everyone for all of your help.