Re: OnArchive and logging

On Tue, 18 Feb 1997 18:53:35 -0500, Debbie Shelton <dshelton2@dbintellect.com> wrote: >Here's what we want to do: currently we have logging on, use OnArchive >to archive different dbspaces to different tapes, turn logging off, >processes the large amount of data, then turn logging on and do a level >0 archive off all dbspaces and continue normal processing. I've done >this without any problems using OnTape, but I'm unsure how OnArchive >will deal with this. Also, we're a little concerned about there being >problems during the weekend processing and having to restore from the >archive prior to turning logging off. > >What are the recovery impacts of turning logging off prior to the >weekend processing? Are there any special considerations we should be >aware of? Debbie: We used to use on-archive, and we found that the best way to turn logging off/on was to take ontape level-0 backups to /dev/null, and then continuing with the normal on-archive level-0 archive schedule. The only impact to turing logging off during this processing is that you will have no recovery to the point of failure in case of a disk problem ... It's probalbly safest to cut off other updates, if possible, while you're doing your "batch" processing. Regards, John.