@black3dynamite said in Reconsidering ProxMox:

It’s supports multiple storage types like nfs or cifs

Obligatory - https://blog.fosketts.net/2012/02/16/cifs-smb/

(Saying CIFS is my pet peeve).

@scottalanmiller said in Reconsidering ProxMox:

Not ideal, but with compression and dedupe, not the problem it seems to be. And it is far less risky that continuous partials that always depend on rehydration.

2TB of data and a large backup window? Not a huge deal.

50TB of data, and 100% 24/7 workloads? Not going to fly.

@wrx7m said in VMware Host Cannot Connect from vSphere Client:

Could also be an issue if a vendor-specific ISO was used to initially install ESXi. I ran into a similar problem with Dell; I had to get the Dell ISO from their downloads for the specific server model/service tag.

For 6.0 this is fine (you'll use this to get ASNC drivers). You can also add the dell VIB depot to get them this way also.
For 6.7 Dell has (thankfully) stopped shipping ASYNC drivers and moved 100% to inbox. It's all for 3rd party management VIBs. Honestly I've seen 3rd party VIBs be a culprit for updates before. I'd make sure you are updating the BIOS/FIrmware also when updating ESXi (People forget this sometimes).

@Dashrender said in ESXi 6.7 Troubleshooting:

by making it a card - it just seems like a way to charge more money, but yeah.. that's what I'm talking about.. Nice to see it's an option.

"By putting it on the motherboard, it just seems like a way to charge everyone who doesn't use for it

An H330 is going to cost you about the same, and wastes 2 drive slots.
FWIW VxRAIL uses BOSS for boot as of 14Gen so there is a decent volume of them in production (For 13Gen they used a high endurance SATADOM device).

@pmoncho said in ESXi 6.7 Troubleshooting:

I have not seen any M.2 on dell servers yet

All 14G servers AFAIK support adding in a "BOSS" card that has 2 M.2 slots.
https://i.dell.com/sites/doccontent/shared-content/data-sheets/en/Documents/Dell-PowerEdge-Boot-Optimized-Storage-Solution.pdf

@scottalanmiller said in Veeam Company Announcement:

@nadnerB said in Veeam Company Announcement:

@scottalanmiller said in Veeam Company Announcement:

@StorageNinja said in Veeam Company Announcement:

Google does all the #[email protected]% time. (Basically to destroy potential competitors). Precog antitrust actions have killed Inbox, and tons of great products.

Yeah, but Google doesn't buy companies like this. Google buys little unheard of things, not market leaders.

Ahem, Fitbit

Fitbit isn't a market leader. It's not tiny, but it's the largest, non-innovative company in the space. It's just a big, but basic, watch builder. They have a big brand name, but they don't lead the market in sales (they are in third, maybe), and they don't build their own tech. Both bigger brands don't just make their own hardware, they make their own processors!

Serious runners use Garmin. Smart watch leaders are apple and samsung.
Google wanted to pay for a device that would generate location data?

@pmoncho said in ESXi 6.7 Troubleshooting:

I get it, although, to even sell an H330 on a Dell PowerEdge R840 is like selling standard breaks on a Audi A6 and making the driver request anti-lock breaks.

The H330 is at least 10x better than the dumpster fire that was the H300 (256 vs. like 25 QD). Still no cache, bastard megaraid on a HBA blah blah blah is all true.

@pmoncho said in ESXi 6.7 Troubleshooting:

You really only need a 4GB USB key but I like to use 8GB or higher as they are still cheap for a higher quality USB key.

If your doing embedded installs PLEASE get at least 32GB. Your going to have issues with a crash dump partition either now or in the future with 4/8GB at some point.

@travisdh1 said in ESXi 6.7 Troubleshooting:

Does your Dell have the SD card reader? If so, it runs the SD cards as a RAID1 array.

SD Card raid controller are "Kinda raid" there's no patrol read, there's no scrubbing, and it they have ugly habbit of not always flagging failure correctly (forcing you to rip out the bad card).

@pmoncho said in ESXi 6.7 Troubleshooting:

ESXi is loaded all into memory after boot up. Other than USB disk checks, nothing is stored on the USB key after the hypervisor is loaded. It mostly writes to the USB key on reboot/shutdown.

It is on embedded installs. (not on full version installs).