Security is such a broad topic, there is no such thing as THE BEST cert. You have to be way more specific

For live stats - hatop -s /run/haproxy/admin.sock -i 1
For historical data - prometheus and grafana

VMware tools start after the OS is up. Sounds like your issue has nothing to do with your hypervisor and has everything to do with your OS.

@Obsolesce said in 16TB spinning rust is here:

@PhlipElder said in 16TB spinning rust is here:

JBODs

Totally fine is its some kind of RAIN. Actually i'm looking at building a CEPH cluster, Dell&RedHat recommend using single-drive RAID0s

Hi guys,

we're looking into building a CEPH cluster and while bonding multiple 10Gb interfaces should do it at the beginning, we should outgrow it pretty soon. Adding more storage nodes will complicate things even further.
The next step up is 25Gb or 40Gb. We use Nexus 3172 10Gb+40Gb uplinks refurbs in prod that we get for cheap (~$4k). Cisco gets pretty expensive at full 25Gb/40Gb though.
Both Melanox and FS have cheaper options for that, however Melanox cost 2-3x more for a similar spec switch. Is there an obvious reason for that?
Wondering if any of you had experience with either. Quality in general, support and warranty, etc.
Currently we have smartnets, so we get decent support and they answer pretty much any question and help with config if we're lucky to hit CCIE right away or wait until it gets escalated high enough.
How is this different when going with Melanox/FS?
Also, is there a big difference between Cisco IOS and Melanox Onyx, Cumulus linux, etc. configuration?
Thanks

That "harmful light blocking" coating for prescription lenses really helps. My eyes get sore after a full day of looking at my screen if i forget them at home. Also, i used to wear Gunnar glasses. Could not believe how blue the screen looked if i took them off after wearing them for a couple of hours. I looked funny with them though, because the actual glass was yellow. https://gunnar.com/product/emissary/
Can't say much about their clear glass - never tried them. But i assume it has a similar "harmful light blocking" coating applied.

I highly doubt they track all the part serials. You always have to provide server service tags.

According to Veeam:

If you plan to back up VMs running Microsoft Windows Server 2012 R2 and later, and Data Deduplication is enabled for some VM volumes, it is recommended that you deploy the Veeam Backup & Replication console and mount server on a machine running same or later version of Microsoft Windows Server with Data Deduplication feature enabled. Otherwise, some types of restore operations for these VMs (such as Microsoft Windows File Level Recovery) may fail.

www.winamp.com

@dustinb3403 said in Small colo infrastructure for SaaS:

@pete-s said in Small colo infrastructure for SaaS:

This is how @dustinb3403 suggested replicating VMs between hosts:

While this is accurate, it also misses on the fact that he would still have his NLS server sitting, collecting backups on whatever schedule.

Other than that it is accurate. In Scott's proposal you are making the shift from migrating the entire workload (which is essentially instant) to migrating the database only.

In his case, the load balancer is the weak link in the chain. Granted these don't fail often but it isn't something you have control over either unless you provide your own for the COLO.

2 haproxy VMs (one per host) and keepalived for failover