Sponsored Content
Top Forums UNIX for Advanced & Expert Users Upgrading legacy packages with patch Post 303043776 by Neo on Thursday 6th of February 2020 06:19:05 AM
Old 02-06-2020
Quote:
Originally Posted by anaigini45
All the servers are mission critical.
And in terms of risk management, we have an SLA of maximum 4 hours to bring the server back up in an event of a catastrophe.
Does not sound very "mission critical" to me.

If you define everything that can be down with an SLA for four hours as "mission critical", what would you define a server that if it went down it would cost the company 100K to 1M USD per hour?

Most people would not define a service as "MISSION CRITICAL" if it has a SLA of four hours, to be frank. But then again that depends on the "MISSION".

If you have SLA of four hours, then you can easily make a mistake and recover from it long before the four hour SLA window is reached. That is more like "A STANDARD BUSINESS SLA", for a lack of a better term.

Do you have a risk management team (normally a part of either the IT security or audit teams) responsible for the risk management of all these servers?

If so, get them involved.

The biggest loses any company has is usually a mistake by a well intended trusted employee. Often, these big mistakes are caused by trying to automate an upgrade to hundreds of devices (routers, servers, firewalls, etc).

Best to set up a test bed, work on the changes, and get it working. You cannot just take "YUM" and try to upgrade if the original installs were done manually. This is a formula for a lot of downtime!
 

9 More Discussions You Might Find Interesting

1. Programming

CMI Legacy

Is there anyone who still uses CMI to connect to the legacy system , my c applications do uses the binaries and libraries for using the CMI functionality but i do not have access to the original source code , and since this is a very old stuff , i just could not get any source to get to knwo the... (0 Replies)
Discussion started by: dino_leix
0 Replies

2. IP Networking

Patch-o-matic (patch for iptable) for linux2.4.08 & iptable1.2.7a

Hello friends I'm running Redhat 9.0 with linux kernel 2.4.20-8 & have iptables version 1.2.7a & encountering a problem that I narrate down. I need to apply patch to my iptable and netfilter for connection tracking and load balancing that are available in patch-o-matic distribution by netfilter.... (0 Replies)
Discussion started by: Rakesh Ranjan
0 Replies

3. Red Hat

upgrading packages

Hello, I am using Redhat Linux Enterprise 4 AS. To upgrade NFS, I had to browse the internet and finally I got the latest rpm https://rhn.redhat.com/errata/RHBA-2005-727.html That was a time-consuming procedure. On Solaris, I am used to go to sunfreeware.sun.com and download the latest... (3 Replies)
Discussion started by: melanie_pfefer
3 Replies

4. Programming

VERSYS Legacy System

I need help locating the tables that hold the demograhic data in this system on an AIX box. Does anyone know the path? (0 Replies)
Discussion started by: Chelcye
0 Replies

5. Slackware

Find Slackware Packages - packages.acl.org.ua

Hi! Let me introduce a project for find and download Slackware packages and browse Slackware repositories. The site provides following features: * Large, daily updated database with RPM, DEB, TGZ, TXZ packages for well-known repositories of the Slackware, Fedora, CentOS, RHEL, Debian,... (2 Replies)
Discussion started by: lystor
2 Replies

6. Solaris

Facing problem after upgrading the kernal patch level to 142900-12

I have a Solaris 10 OS having kernal patch level 138888-03 on several servers but recenlty I upgraded it into 142900-12 on some T-Series servers & v890 server after install them my syslog is increasing at a rate of 1GB on average on all servers . I believe its a bug, can somebody help me in... (1 Reply)
Discussion started by: sb200
1 Replies

7. What is on Your Mind?

Tron Legacy

Watched it. Major disappointment. (10 Replies)
Discussion started by: ni2
10 Replies

8. Ubuntu

Encountering problem on upgrading the packages

Hi folks, Ubuntu 9.04 I have an old box not running for years. I just dig it out from the store room. On running; $ sudo aptitude update ...... ...... Err http://hk.archive.ubuntu.com jaunty/main Packages 404 Not Found Err http://hk.archive.ubuntu.com jaunty/restricted Packages ... (1 Reply)
Discussion started by: satimis
1 Replies

9. Solaris

Determine if you are in a Legacy Zone?

Hi Folks, Just a quick question here, about Legacy Zones. Well more about how to determine if you are actually in one, on logging into a legacy zone - is there a quick way of checking that? Regards Gull04 (7 Replies)
Discussion started by: gull04
7 Replies
yum-verify(1)															     yum-verify(1)

NAME
yum verify plugin SYNOPSIS
yum [options] verify [package ...] DESCRIPTION
This plugin extends yum with some commands that give verification information on the installed system, much like rpm -V. You can change how the verification is done and which files it applies to. added yum commands are: * verify * verify-rpm * verify-all all of which take the same arguments as the list yum command, obviously you can only verify packages that are installed on the system. verify Is the generic verification command, and is intended to give the most useful output. It removes all false matches due to multilib and ignores changes to configuration files by default. verify-rpm Is meant to be 100% compatible with rpm -V output, and any differences should be considered as bugs. verify-all Is used to list all the differences, including some that rpm itself will ignore. GENERAL OPTIONS
These are the options added to yum that are available in the verify commands. They are: --verify-filenames This option is used to limit the filenames that the packages will perform verification. --verify-configuration-files This option is only useful in the generic verify command, and will enable/disable verification of files that are tagged as configu- ration files. EXAMPLES
To do the same as rpm -Va, use: yum verify-rpm To verify the packages starting with the name yum, use: yum verify 'yum*' To verify the binaries that are in a bin directory, use: yum verify --verify-filenames='*bin/*' To verify all include files, Eg. for multilib problems, use: yum verify-all --verify-filenames='/usr/include/*' SEE ALSO
yum (8) yum.conf (5) the verify.conf file in /etc/yum/plugins.d AUTHORS
James Antill <james.antill@redhat.com>. BUGS
Currently yum-verify does not do verify-script checking or dependency checking, only file checking. Should you find any other bugs, you should first consult the FAQ section on http://yum.baseurl.org/wiki/Faq and if unsuccessful in finding a resolution contact the mailing list: yum-devel@lists.baseurl.org. To file a bug use http://bugzilla.redhat.com for Fedora/RHEL/Centos related bugs and http://yum.baseurl.org/report for all other bugs. James Antill 01 March 2008 yum-verify(1)
All times are GMT -4. The time now is 07:04 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy