08-31-2013
Well for patching, first thing you learn is backup then you learn repositories (IPS).
Having local repositories is a major advantage.
In Solaris 11, if you do major patching the pkg will patch the inactive boot environment then it will be active after next reboot (utilizing zfs clone ability on root zpool).
That helps you, since if things go berserk, you can always reboot the host and revert to old environment.
On HPUX, the tool for patching is swinstall and for backup/repositories it's Ignite.
Great help here is HPSIM tool with SWA (Software assistant), which generates reports what to patch, connecting to HP site and your HP machines.
For linux, for major kernel patches, you will have your last couple of kernels to boot from if things go wrong. For backup i use tar/gzip (read full drive backup for your distribution).
And the final piece of advice (not OS related) is to have test environments to try patching first.
Nothing can substitute that.
Hope that helps
Regards
Peasant.
These 2 Users Gave Thanks to Peasant For This Post:
9 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
I have a suse linux 9(SLES 9)
I have configured "YOU" (yast online update) and it all working fine, synchronising on a daily base with http://sdb.suse.de/download but I would like to know if they is a tools or scripts that inform you of any patches that has not been applied and notify you via... (0 Replies)
Discussion started by: hassan1
0 Replies
2. Linux
Does anyone know who to centrally manage the distribution and application of patches to multiple Linux platforms ? Is there software for this ? (0 Replies)
Discussion started by: jimthompson
0 Replies
3. Linux
I was wondering how everyone else manages patching/upgrades for apache.
Latest doesnt mean greatest, we typically dont install the newest patches for our OS's. We typically run 3-6 months behind, to let fixes get fixed before installing them.
Does anyone here have a written detailed plan... (0 Replies)
Discussion started by: Ikon
0 Replies
4. UNIX for Advanced & Expert Users
Does anyone know of any tools that manage the rollout of patches across multiple types of Unix platform ( eg Solaris, Aix etc ).
I am looking for something that does a similiar job to SMS or WSUS in the Windows world (3 Replies)
Discussion started by: jimthompson
3 Replies
5. Red Hat
I've inherited about 10 RHEL 3 boxes that are located in Europe behind a corporate firewall with no access to rhn.redhat.com
I've been tasked with patching all of these systems but I ask, Does redhat issue patch bundles? In AIX, there are maintenance levels and Sun has patch clusters available... (4 Replies)
Discussion started by: Steelysteel
4 Replies
6. Solaris
Hello Friends..
I have not tried anything related to Solaris patch and wish to learn more about it. I just wanted to try the patchadd and patchrm commands and how they work, just for educational purpose. I tried to download Solaris 10 patches, it asked me to register at sunsolve.com and i... (5 Replies)
Discussion started by: saagar
5 Replies
7. UNIX for Advanced & Expert Users
We have a mix of AIX, HP-UX, Linux (RHEL and SLES), and Solaris in our environment. Currently we have seperate patch management systems for each platform (NIM, SD, Spacewalk, etc), but have started looking for a centralized patch management solution that would work for most, if not all, of our... (0 Replies)
Discussion started by: kknigga
0 Replies
8. HP-UX
HI all,
As per the audit policy, patch has to be apply periodically, but in my scenerio, it has been applied lastly in the year 2010.
Using HP UX 11.11, 11.21 and 11.31
I would like to know, how to identify the patches which are need to update, what will be the procedure to update, how to... (5 Replies)
Discussion started by: selvaforum
5 Replies
9. Cybersecurity
I'm searching for COMPREHENSIVE ID management security guideline to manage user administration in my current job. I couldn't find it online or the books that could help.
What I need to know:
User security directories and how to use it.
How user should be managed.
How the standard user... (0 Replies)
Discussion started by: blinkingdan
0 Replies
LEARN ABOUT DEBIAN
backup.d
BACKUP.D(5) backupninja package BACKUP.D(5)
NAME
BACKUP.D - Action configuration files for backupninja(1).
SYNOPSIS
/etc/backup.d/*
DESCRIPTION
To preform the actual backup actions, backupninja processes each action configuration file in /etc/backup.d according to the file's suffix.
.sh run this file as a shell script.
.rdiff backup action for rdiff-backup.
.dup backup action for duplicity.
.maildir backup action for slow, incremental rsyncs of tens of thousands of maildirs.
.mysql backup action for safe MySQL dumps.
.pgsql backup action for safe PostgreSQL dumps.
.sys backup action for general system reports and hardware information.
.svn backup action for safe backups of subversion repositories.
.trac backup action for safe backups of trac repositories.
.makecd backup action for burning backups to CD/DVD or creating ISOs.
These files must be owned by root and must not be world or group readable/writable. Support for additional configuration types can be added
by dropping bash scripts with the name of the suffix into /usr/share/backupninja.
The configuration files are processed in alphabetical order. However, it is suggested that you name the config files in "sysvinit style."
For example:
10-local.pgsql.disabled
15-runthisfirst.sh
20-runthisnext.mysql
90-runthislast.rdiff
Typically, you will put a '.rdiff' config file last, so that any database dumps you make are included in the filesystem backup. Action con-
figurations which end with .disabled are skipped.
Example templates for the action configuration files can be found in /usr/share/doc/backupninja/examples. You can also use ninjahelper(1),
a console based "wizard" for creating backup actions.
SCHEDULING
By default, each configuration file is processed everyday at 01:00 (1 AM). This can be changed by specifying the 'when' option in a backup
action's config file or in the global configuration file. Special value 'manual' will disable scheduling for the backup action. It is pos-
sible to run the backup action manually by invoking ninjahelper(1) with --run command line argument.
For example:
when = sundays at 02:00
when = 30th at 22
when = 30 at 22:00
when = everyday at 01
when = Tuesday at 05:00
when = hourly
when = manual
These values for "when" are invalid:
when = tuesday at 2am
when = tuesday at 2
when = tues at 02
A configuration file will be processed at the time(s) specified by the "when" option. If multiple "when" options are present, then they all
apply. If two configurations files are scheduled to run in the same hour, then we fall back on the alphabetical ordering specified above.
The "when" must occur before any sections in the action configuration file.
FILE FORMAT
The file format of the action configuration files is "ini style." Sections are created by using square bracket. Long lines are connected
with a backslash. For example:
# this is a comment
[fishes]
fish = red
fish = blue
[fruit]
apple = yes
pear = no thanks
i will not have a pear.
SEE ALSO
backupninja(1), ninjahelper(1), backupninja.conf(5),
AUTHOR
BACKUPNINJA was written by the riseup.net collective.
riseup October 10, 2005 BACKUP.D(5)