Review your favorite Linux distribution.
Go Back > Forums > Linux Forums > Linux - Newbie
User Name
Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question? If it is not in the man pages or the how-to's this is the place!


  Search this Thread
Old 06-12-2015, 11:08 AM   #1
LQ Newbie
Registered: Jun 2015
Posts: 8

Rep: Reputation: Disabled
Want to know

Hi all,
I am new to VMware. And new to my job. There are about 20 linux Redhat servers attached to VMware. I need to patch them. How can I do that ? Do i do each individually or all at once ?
Old 06-12-2015, 11:13 AM   #2
LQ 5k Club
Registered: Jan 2011
Location: Nowhere near you, thank God.
Distribution: OSX Sierra
Posts: 8,573
Blog Entries: 15

Rep: Reputation: Disabled
Welcome to LQ!

Log in to each host as root, or get root and run yum update.
Old 06-12-2015, 11:16 AM   #3
LQ Newbie
Registered: Jun 2015
Posts: 8

Original Poster
Rep: Reputation: Disabled
Are you saying that VMware cannot collect the patches and deploy them to the linux servers ? There is an equivalent in windows ! JHow about if I had over 100 servers ?
Old 06-13-2015, 09:20 PM   #4
Senior Member
Registered: Aug 2010
Location: Near Edinburgh, Scotland
Distribution: Cinnamon Mint 17.3 and 18.2 at present.
Posts: 1,293

Rep: Reputation: 301Reputation: 301Reputation: 301Reputation: 301
Is that 20 RHEL VMs on one VMware host? Patching an OS generally means you have to reboot the system which implies downtime and loss of service to your customers. If you went ahead and patched 100 servers all at once and the patch failed, what's your back out plan? How big a disaster to your company would that be?
Are all the 20 RHEL VMs EXACTLY the same? Same version of Oracle (or whatever database you may have) Same applications on them all? I rather think not. To remediate the risk you need to gather all the relevant information on EACH VM and check it against the patch. This probably includes checking against firmware patch levels for Array controllers, BIOS, nics, HBAs and disks on the host server. Pain huh?

Prove the patch works against a development or test system first, then I'd patch the DR system (preferably before a DR fail over test) then if when you fail the production system over to the patched DR system, if you have problems, you can just fail it back again.

In major commercial companies, patching a live system is a real pain in the aspidistra as you have to get all the resources needed in place; SysAdmins, DBAs, Application Analysts and business owners plus you need to include backout plans for when it doesn't go as it should. You did run a system backup before you started didn't you? That's one per VM plus the host server if you're patching it as well!

Patching a DR system (not live, no mounted databases, no disruption to services when rebooted.) needs less resources so is easier to manage. All this is to manage the risk involved in patching a system.

The problem is bigger than just setting something up to automatically patch a load of servers whether VMs or bare metal.

Anyway... that's my thoughts for what they're worth. ?

Play Bonny!

Last edited by Soadyheid; 06-13-2015 at 09:23 PM.
1 members found this post helpful.


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off > Forums > Linux Forums > Linux - Newbie

All times are GMT -5. The time now is 03:50 AM.

Main Menu
Write for LQ is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration