Summary: vdump and cloned file set controversies

From: Steve Shanks <shanks_at_probita.com>
Date: Thu, 06 May 1999 11:02:59 -0600

Thanks to Alan (?), Richard Tame, Miguel Fliguer, Alan Davis, Dr. Tom Blinn
and Chris Ruhnke for the valuable insight into backups and using cloned
file sets.

The general theme is that file corruption on a restore is a danger if the
file(s), especially database files, are being written to while being copied
to tape. Cloning file sets for backup is generally recommended and the
clonfset should be done while a file set is relatively inactive and
databases can be closed temporarily.

I will continue cloning for my weekly level 0 vdumps. I am still working
on a good nightly level 9 vdump script.

You may recall the question I submitted a few weeks ago about system hangup
during the nightly vdump, likely during the unmounting of the clone at the
end of the vdump. The problem occurs with a particular clone that gets
occasional high activity during the cloning/backup period. I plan on
upgrading from v4.0B to v4.0E+ soon which may reveal some resolution.
Until then, I am still attempting ways of doing my nightly vdumps so that
they are highly reliable and can run unattended. It seems that if I assure
file set activity is quiescent while I do the clonefset command, I may
have something there. Or, cloning is flakey with my o/s, version. (Any
further ideas on this are greatly appreciated!)

Thanks again for the feedback and excellent descriptions of vdump of open
files.

Steve

-----------------------------------
Steve Shanks (shanks_at_probita.com)
Probita, Inc.
4949 Pearl East Cir. Suite 300
Boulder, CO 80301
(303) 449-7665
Received on Thu May 06 1999 - 17:07:04 NZST

This archive was generated by hypermail 2.4.0 : Wed Nov 08 2023 - 11:53:39 NZDT