@Dashrender said in Planning for New ESXi Hosts - Which CPU Metrics Should I Use?:

@Pete-S said in Planning for New ESXi Hosts - Which CPU Metrics Should I Use?:

@wrx7m said in Planning for New ESXi Hosts - Which CPU Metrics Should I Use?:

@Pete-S said in Planning for New ESXi Hosts - Which CPU Metrics Should I Use?:

@wrx7m said in Planning for New ESXi Hosts - Which CPU Metrics Should I Use?:

@Pete-S They list both the 61xx and 62xx as options for the R740XD.

Good!

What CPUs do you have in the R720 today? 1 or 2 CPUs?

Do you want the new ones to be faster or just capable of running more VMs?

I have 2 x E5-2609 CPUs in each server. I would like faster, but more VMs would be the priority.

The E5-2609 CPUs are at the low end of what was available at the time so no problem there.

Actually, are you looking to keep the old servers around for testing and such?
In that case you could just drop in refurbished CPUs that are faster and/or has more cores for very little money. If the server can take E5-2600 V2 you can get up to 12 core CPUs.

yeah, but Windows licensing is an issue, assuming multiple CPUs... for a test server, not likely worth going over the 16 cores. Not to mention the test server might require licensing (if needed beyond the 90 day test period for something).

Two 8-cores would be an option. For instance two E5-2690. They are 2.9 GHz base frequency and have 8 cores. About $100 each when buying refurbished.

About 50% faster per core (2609 have no turbo) and about 3 times faster multicore performance. Has more cache and faster memory transfer speed. Was a very high end CPU at the time. Was listed at $2000 while the E5-2609 was $300.

The fastest 8-core E5-2600 V2 CPU is the E5-2667 V2. 8 cores and base frequency of 3.3 GHz. It will likely also be an option for the R720XD. V2 uses 22nm technology so uses less power with the same clock speed and can fit more cores or run higher frequencies.

@scottalanmiller I was considering rolling them back to last night as a last-ditch scenario is all fails since it is on Veeam and I have a Full from last night.

@JaredBusch said in Error - SELinux is Preventing Vmtoolsd From Entrypoint Access On the File /usr/bin/bash:

@wrx7m said in Error - SELinux is Preventing Vmtoolsd From Entrypoint Access On the File /usr/bin/bash:

My question - Is this permanent?

Yes

Thanks!

@DustinB3403 said in Troubleshooting Help Requested:

@wrx7m said in Troubleshooting Help Requested:

VLANs?

No, and this VM is on the same vlan as other VMs on the same host.

PS I've restored this VM to a completely different hypervisor and the issue persists. So either its the VM or the gateway.

Have you tried a different IP, or even power down this machine and assign the same IP to another host to see if it gets blocked? Is the restored VM using the same MAC address as the original or has the restored version got a reinitialised MAC?

Do you have access to check the logs on the gateway / edge / router to see if it's blocking / intercepting / messing with your host

@DustinB3403 said in With ESXi Licensing what happens if I let it lapse:

Microsoft started pulling Security patches off of their servers after your contract expires but the platform is still supported.

Microsoft no longer provides patches for XP Server 2003 unless you pay them a lot of extra money. It's basically a license with security updates for a fixed interval that can be extended for a ton of money...

@maximus
I believe you can take as a basis the script, published in this article: https://www.starwindsoftware.com/resource-library/starwind-virtual-san-gentle-shutdown-with-powerchute
I hope it will be useful for you 🙂
Merry Christmas!

@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!

I'm sorry to say but this is a terrible article. It's all marketing fluff... I'd like to see some implementation specifics outside of "we did this so you should too" marketing bs.

Interesting read. I hope I never need to use it. Though, I would rather have it and not need it...

@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?