NHS in England being hit by cyber attack...
I think some sysadmin, somewhere in England, is having a really bad day!
They were an MSP. The selling SAN part was only a small part of what they did. Only about 200 customers, so small. But, they had their list of products and wouldn't really change from their supported model - extensive list, but static, and old. For example, the backup solution they sold to customers and installed, then managed, was file level only. Any disaster the whole server had to be rebuilt rather than an image restore. Again, because its what they knew rather than developing and using the latest tech. Makes sense for them, but bad for the tech/development and customers - That was one of the reasons I left...
This really annoyed me; a customers server kept crashing (every few hours/daily). It was their SQL server so when that went all of their applications went down. Old kit, no longer supported by HP(E) anymore. From memory it was a 2003 box. Out of warranty etc, no service, so couldn't get them the latest packs... and no support from MS as its no longer supported. All we could do is force a reboot and wait each time. So, the customer ordered a new server. Great! (They should have anyway as it was not fit for purpose anymore for a number of reasons). They were planning to have their application vendor move the SQL instances/whatever to this new box - but that was months away...
So, the new server turns up, I rack n stack it, and get 2012 r2 installed. Now its just sitting in the rack awaiting the vendor and the other box crashes again! I speak to my team and we agree that I will shutdown SQL server services, p2v the box, and bring up on the new host - great - work done and customer happy no ongoing failures until the vendor can come to site.
A few months later I go back to site - one of our techs had visited when the software vendor were planned, they had turned off the VM, installed SQL Server to the physical box and are using the physical box again! Never learn! I had told them to just create a second VM, and use that. Leave the host alone. But nope! Some people just cant be trusted. I know the vendor is happy to use a VM. I expect that decision was made as the other techs were not comfortable with 'scary VM stuff'.
Name the company...
Bring on the shame
I used to work for a small MSP in the UK called FOS.Net. Spoke to them about Starwind before and moving away from the node + SAN approach... they basically said no as "We've not had one fail before, and nobody here knows Starwind, so we will stick with what we know." - I knew Starwind otherwise would not have brought it up at all!
I think they just don't want to train people - hence rarely using VMs too!
Drooling right now! Ohhhhhhhhh, Ahhhhh...
In Windows, Remote Access/RDP etc is not enabled OOB. I assume the same in Linux? Unless you can connect to each through a command line/ssh or something, which maybe needs to be enabled/disabled etc...
I've got this working using CentOS and HAProxy. I also want to do this with Nginx, so will run with that as a lab next week. More I understand that the better. Thanks for sending me down a good path.
Ok, so, with Linux, what is best practice regarding security?
Using CentOS currently. I assume I need to install an AV, what options do I have? From a fresh install, do I need to close any holes? System update has been done already, but I reckon I am missing lots that is a best practice for Linux?
Like i'e said... totally new with Linux so any pointers would be great. Ive seen the guide to Linux admin posted on this site already and will work through that in the coming weeks... but anything I should be wary of? The 'whatever you do, don't do...' sort of thing...
NGinx and HA-Proxy are fine tools for this, just DO NOT use them as load balancers. No reason for that complexity, it will have no benefits for you, but will have negatives.
Yes, I see this now. Thank you. Wrong terminology from me. My goal then is to have multiple IIS instances running on different hardware (on VMs on different hardware), being routed to through a pair of (somethings?) which will stop routing to any of those sites that are down.
Right, yes, and that's why HA-Proxy doesn't have Load Balancing in its name, but rather High Availability. Because failover is its primary use case.
So NGINX over HAProxy? Or something else?
Looks like your connection to MangoLassi was lost, please wait while we try to reconnect.