Messy backup procedures
Posted in 2004
Topics: Backup & Restore, Transactions, Locking & Isolation, Logging & Checkpoints, Platform-Specific Issues
have just come onboard here and the backup processes are in a
shambles. We are running 9.20HC3 on an HP-UX 11 box with 1 tape drive.
Currently we manually run a Level 0, but sometimes they don't even get done.
My plan is to automate the backup process using ontape and run a Level 0
backup Monday thru Friday. We at least have a large window of time for backups.
I then need to turn on transaction logging for all databases, of which there
are 1000 of them. Is there a way to start logging for all db's at once? I
couldn't find any reference to that situation in the docs. It just says use
ontape -s -U dbname as an example.
Then I need to create a logical log backup procedure. I would like to use
continuous backup to minimize data re-entry in case of a crash. Can I do the
backup and restore to/from disk? The docs lead me to believe that I can't.
Any ideas appreciated.
Thanks.
Kevin Struckhoff
Customer Analytics Mgr.
NewRoads West
Office 818.253.3819 * Fax 818.253.3880
kevin.struckhoff@newroads.com
9.20 is
very old now. I would look at upgrading to 9.40.
To change the logging of a number of database just continue the list of
databases - ontape -s -U db1 db2 db3 db4 etc ...
You can backup/restore to/from disk, but in 9.20 you are limited to 2Gb for
each file you create - 9.40 has no such limit. You can use ALARMPROG in
$ONCONFIG to backup logical logs to disk - log_full.sh comes partly set up for
code 23 (logical log full), but you need to configure for ontape and your
environment.
You need to plan how you are going to do if you have a disk failure.
MW
> -----Original Message-----
> From: forum.subscriber@iiug.org [mailto:forum.subscriber@iiug.org]On
> Behalf Of KEVIN STRUC....
> Sent: Wednesday, 26 May 2004 5:05 a.m.
> To: ids@iiug.org
> Subject: Messy backup procedures [3019]
>
>
> have just come onboard here and the backup processes are in a
> shambles. We are running 9.20HC3 on an HP-UX 11 box with 1 tape
> drive. Currently we manually run a Level 0, but sometimes they
> don't even get done. My plan is to automate the backup process
> using ontape and run a Level 0 backup Monday thru Friday. We at
> least have a large window of time for backups.
>
> I then need to turn on transaction logging for all databases, of
> which there are 1000 of them. Is there a way to start logging for
> all db's at once? I couldn't find any reference to that situation
> in the docs. It just says use ontape -s -U dbname as an example.
>
> Then I need to create a logical log backup procedure. I would
> like to use continuous backup to minimize data re-entry in case
> of a crash. Can I do the backup and restore to/from disk? The
> docs lead me to believe that I can't.
>
> Any ideas appreciated.
>
> Thanks.
> Kevin Struckhoff
> Customer Analytics Mgr.
> NewRoads West
> Office 818.253.3819 * Fax 818.253.3880
> kevin.struckhoff@newroads.com
>
>
You can try ondblog to change logging mode of
database.
-Ajay Gupta
Kevin,
I have always used the ontape -s -U <dbname> method, but the doc mention the
ondblog command which seems to be able to take database name from a file. You
can take a look at this command in the administrator reference.
Noting that logging needs only to be turned on once, during backups there is
no need to turn off the logging.
I my opinion you need to install another tape drive just for the logs, in case
you are using ontape. (command ontape -c) In case you loose the disk as well.
To automate daily backups you can create a backup script that sets up the
needed environment variables and invoke ontape -s and put it in cron. You
should start backups in off peak periods. To get more details of the cron
command. (man crontab)
Regards
Kenneth
Kevin,
We have been doing archives and logbackups to disk for several years now --
no problems. Just make sure that those disk files are backed up to tape
somewhere along the way (ours are gathered up during the nightly filesystem
backup).
We use "expect" in the archive scripts to "change tapes", and we have a
logbackup script that is kicked off via ALARMPROGRAM each time a logical log
fills.
Let me know if you need more info...
HTH,
Paul Mosser
> -----Original Message-----
> From: forum.subscriber@iiug.org
> [mailto:forum.subscriber@iiug.org] On Behalf Of KEVIN STRUC....
> Sent: Tuesday, May 25, 2004 10:05 AM
> To: ids@iiug.org
> Subject: Messy backup procedures [3019]
>
>
> have just come onboard here and the backup processes are in
> a shambles. We are running 9.20HC3 on an HP-UX 11 box with 1
> tape drive. Currently we manually run a Level 0, but
> sometimes they don't even get done. My plan is to automate
> the backup process using ontape and run a Level 0 backup
> Monday thru Friday. We at least have a large window of time
> for backups.
>
> I then need to turn on transaction logging for all databases,
> of which there are 1000 of them. Is there a way to start
> logging for all db's at once? I couldn't find any reference
> to that situation in the docs. It just says use ontape -s -U
> dbname as an example.
>
> Then I need to create a logical log backup procedure. I would
> like to use continuous backup to minimize data re-entry in
> case of a crash. Can I do the backup and restore to/from
> disk? The docs lead me to believe that I can't.
>
> Any ideas appreciated.
>
> Thanks.
> Kevin Struckhoff
> Customer Analytics Mgr.
> NewRoads West
> Office 818.253.3819 * Fax 818.253.3880
> kevin.struckhoff@newroads.com
>
>