Backing up Logical Logs

I have a quick question: backing up logical logs... right now I am using ontape to backup my logs. I have the "Onconfig set to /dev/null right now ( I know if I where to restore my data it would only be good from my last Archive). Is there a better way such a ontape -a. What is the difference? Are there any performance issues?

What's your question? Do you have your LTAPEDEV onconfig parameter set to /dev/null? If so, then you are not backing up logical logs at all. As soon as a log fills, OnLine marks the log as "backed up", but the data is never copied anywhere. As soon as the log is overwritten, the original transaction data cannot be recovered from. Is this a production system, or dev/QA? An ontape -a performs an "automatic" or manual backup of the logical logs. This is only valid if your LTAPEDEV is set to something other than /dev/null. The operator puts a tape in, issues an ontape -a which copies all full but not backed up logs to the device, the tape is removed, and the process is repeated when more logs are full and need to be backed up. There is also ontape -c, which performs continuous log backup to a tape device. This too, requires the device to be something other than /dev/null. As soon as a log fills, OnLine will copy the data out to the device specified. As long as there is an ontape -c running for the instance, this process continues automatically (until the tape fills, of course, then you have to insert a new tape and start continuous logging again). Robert Moayedzadeh <Moayedzadeh@email.msn.com> wrote in message news:OlXnL66s#GA.407@cpmsnbbsa02... > I have a quick question: > > backing up logical logs... right now I am using ontape to backup my logs. > I have the "Onconfig set to /dev/null right now ( I know if I where to > restore my data it would only be good from my last Archive). Is there a > better way such a ontape -a. What is the difference? Are there any > performance issues? > >