Operating System - HP-UX
1834660 Members
2230 Online
110069 Solutions
New Discussion

Imporatant files to protect

 
wip
Frequent Advisor

Imporatant files to protect

Hi Guys,

wonder if any one could add to my knowledge of important config files to be protected under hpux 11i and later version.Imporatant binaries as well

tia
Wip
5 REPLIES 5
harry d brown jr
Honored Contributor

Re: Imporatant files to protect

Everything a make_tape_recovery backs up.

man make_tape_recovery

live free or die
harry d brown jr
Live Free or Die
Steven E. Protter
Exalted Contributor

Re: Imporatant files to protect

tripwire is a third party tool that will protect binaries or at least notify you when they change.

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Mel Burslan
Honored Contributor

Re: Imporatant files to protect

if the purpose is a diseaster recovery, I would suggest making two copies of a recovery media with make_tape_recovery.

Also, as a written documentation reference, I woudl print out the txt output from cfg2html script and keep it in a safe place.

________________________________
UNIX because I majored in cryptology...
Jino.P.V
Frequent Advisor

Re: Imporatant files to protect

Hi,
I couldn't make out what do you mean by "to be protected". If your object is regarding backup, as others said ignite backup is the best way. Or did you mean the security?

regards,

Jino
Bill Hassell
Honored Contributor

Re: Imporatant files to protect

All the configuration files and executables for HP-UX are protected by the permissions of the directories. The only method for these files to be changed is by logging in as root. That means, no one gets the root password except a specific system administrator or two.

As far as backups, there are about 5000 files and directories that need to be saved and have restricted access. As mentioned, Ignite/UX and fbackup can copy these files to tape.


Bill Hassell, sysadmin