Re: Poor Backup Strategy???
From: Helge Petersen <petersen_at_com1.dwhl.de>
Date: 1996/01/12
Message-ID: <petersen.821426544_at_com1.dwhl.de>#1/1
>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).
Date: 1996/01/12
Message-ID: <petersen.821426544_at_com1.dwhl.de>#1/1
Steve Butler <sbut-is_at_seatimes.com> writes:
>On 10 Jan 1996, Glenn Burton wrote:
>> The system administrators of one of the systems I work with do not shut down
>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).
Note that this means you MUST use
ALTER TABLESPACE xxx BEGIN BACKUP;
host tar .... (or cp or cpio or ...)
ALTER TABLESPACE xxx END BACKUP;
for EVERY tablespace.
And you MUST run your instance in ARCHIVE LOG modus and you MUST backup the archived redologs.
Hope this helps.
Helge Petersen Datenbase- und Systemadministrator Draeger Synematic GmbH D-23558 Luebeck, Germany Tel. 0451/882-4044 Fax -3031 Email petersen_at_dwhl.de ***************************************************************************Received on Fri Jan 12 1996 - 00:00:00 CET