Is anyone using archival logging and automating the backup process ? Would 
love to hear from you if so...TIA

Archival logging is not 24x7 .
The database engine has to be stopped to rotate the log files.

This is quite possible to do from a script of some kind.  The details
are OS specific.

For a Windows based server you can use the "net" command to stop and
start the services.  See the service manager for the specific names.
net stop "Pervasive.SQL (relational)"
net stop "Pervasive.SQL (transactional)"
<delete logs>
<do backup here>
net start "Pervasive.SQL (transactional)"
net start "Pervasive.SQL (relational)"

Novell is a little trickier.  Also note that newer versions of Novell
Netware (5.1+) use the engine for OS functions.  While I have never
actually seen stopping the database cause the OS problems I do not
recommend it because it could.  e.g. NDS can be configured to use the
Pervasive engine and I suspect NDS would not be happy if the data
store stopped.
mgrstop
bstop
btrv unlink
<delete logs (will require the Novell toolbox or other utility to do
file commands on the server at the server)>
<do backup here>
mgrstart

Linux is pretty straigtforward
/etc/rc.d/init.d/psql stop    or on newer version "service psql stop"
<delete logs>
<do backup here>
/etc/rc.d/init.d/psql start

Most backup packages will let you specify pre-backup and post-backup
scripts to run.  If so just put the part up to <do backup here> in the
pre-backup script and restarting the engine in the post backup script.
If the packade doesnot have this feature stopping and starting the
database can be scheduled using the scheduler of your choice.

Leonard

On Wed, 26 Nov 2003 15:21:00 +0000 (UTC), Carol_Cutler@brown.edu
(Carol_Cutler) wrote:

>Is anyone using archival logging and automating the backup process ? Would 
>love to hear from you if so...TIA