Re: Poor Backup Strategy???
Date: 1996/01/11
Message-ID: <Pine.SUN.3.91.960111095156.25043D-100000_at_seatimes>#1/1
On 10 Jan 1996, Glenn Burton wrote:
> The system administrators of one of the systems I work with do not shut down
> the Oracle instance to take a cold backup. Instead they simply copy the
If they follow the approved hot backup strategy then everything should be fine. This strategy flags the database that indicated tablespaces are being copied. The database will then re-synch the thread counters in the tablespace header when the script indicates the backup is finished (with the ALTER command).
> datafiles during the night. The reasoning behind this is that "the system
> is quiet at that time of day, so there is really no reason shut down the
> instance".
What if some change is still in progress or the redo files haven't been checkpointed? If it is so quiet, why can't they shut down the instance?
> Assuming that there really is no user activity in the database, is this a
> sound backup strategy or should the instance be shut-down before copying
> the files?
Why take chances? It's only your career? Either shut down the instance or implement the hot backup strategy that Oracle supports.
+----------------------------------------------------+ | Steve Butler Voice: 206-464-2998 | | The Seattle Times Fax: 206-382-8898 | | PO Box 70 Internet: sbut-is_at_seatimes.com | | Seattle, WA 98111 Packet: KG7JE_at_N6EQZ.WA | +----------------------------------------------------+All standard and non-standard disclaimers apply. All other sources are annonymous. Received on Thu Jan 11 1996 - 00:00:00 CET