On Tue, 19 Aug 1997, Elliot Smorodinsky wrote:
> What system configuration files would you keep in hard copy to
> facilitate disaster recovery if *both* your disks and your backups
> somehow fail?
Seems I spoke too soon: the volume of replies I received since I
posted the summary warrants a reposting, I think. Here is the updated
list of files, and much thanks to everyone who responded.
o /etc/passwd
o /etc/group
o /etc/inittab
o /etc/fstab
o /etc/exports
o /etc/hosts
o /etc/sysconfigtab (DIGITAL)
o /sys/conf/KERNEL (depends on which kernel you want to backup)
o the output of disklabel -rp rzX, where X is each drive number
o the output of recent 'df -k' runs
o the output of recent 'du -sk /*' runs
o An 'ls -lR' of /etc/fdmns
o A full volprint(8) listing.
o files in the SIA directory if we're using C2
o files in the path/httpd/conf directory of the webserver
o configuration files of major applications (i.e. Oracle)
o /etc/routes
o /etc/rc/config
o Anything you've changed in the /sbin/rc/rc* files
o /etc/bootptab
o /etc/inetd.conf
o /etc/services
o ls -ls on /
o ls -lR /usr/local
o /etc/vol/volboot
Alan Rollow (alan_at_nabeth.cxo.dec.com) gives the following invaluable piece
of advice: "If you use a cataloging backup product remember to keep a
backup of the catalog and core system disk that isn't in that particular
backup format." -- a piece of advice I heartily second, as this particular
problem has bitten me more than once.
Lucien HERCAUD <Lucien_HERCAUD_at_paribas.com> advises: "I would add the
/etc/vol/ full directory tree (especially /etc/vol/volboot) and a valuable
dd copy of the LSM private partitions onto the DM of the diskgroups you
defined - in case you use LSM."
Tim Mooney <mooney_at_dogbert.cc.ndsu.NoDak.edu> reiterates the importance
of /etc/vol/volboot and notes that it must be exactly 512 bytes in size,
padded out with '#' characters.
And finally, Tom Webster <webster_at_ssdpdc.lgb.cal.boeing.com> writes:
"Most, if not all of this data is captured by a utility that DEC Service
makes available called UniCensus. In addtion to creating disaster copies
of these files (and some html output as well), you can automatically
configure the utility to mail the files to a remote site. If you are
covered by DEC Service, you can e-mail the files to a DEC addres which uses
a mailbot to archive the data for you on one of their servers.
You should be able to find UniCensus on atlanta.service.digital.com in the
tools directory."
In general, thanks to the following people for a quick and precise response:
Alan Rollow (alan_at_nabeth.cxo.dec.com)
Flannon Jackson <flannon_at_du.edu>
Mathew Hennessy <hennessy_at_adone.com>
"Robert L. McMillin" <rlm_at_syseca-us.com>
Jason Neil <Jason_Neil_at_CITYMAX.CO.UK>
Tom Webster <webster_at_ssdpdc.lgb.cal.boeing.com>
Lucien HERCAUD <Lucien_HERCAUD_at_paribas.com>
Oyanarte Portilho <portilho_at_tritium.fis.unb.br>
Tim Mooney <mooney_at_dogbert.cc.ndsu.NoDak.edu>
Received on Tue Aug 26 1997 - 15:39:08 NZST