We have a procedure to backup archived logs and then purge them. The
backup product we use is Syncsort's Backup Express 2.1.5. We use a user
exit (db2uext2) to copy logs to the archive directory. The backup
procedure is essentially

1. force current log to be archived
2. Backup the archive directory
3. run "rm *" to purge the logs

I have concern that there is the possibility of a log being generated
after step 2 begins, not being backed up, and then being deleted by step
3. Is my convern valid?

One other question while I'm at it. What happens if the disk where the
archive directory fills up and db2 needs to archive another file? Will
the db hang?
--
Chuck
Remove "_nospam" to reply by email