ontape and LTAPEDEV = /dev/null

Hello, I have two instances where LTAPEDEV is set to /dev/null. I did this because I do not care about restoring to a point in time doing logical restores, I only need to be able to restore to a specific point in time (in this case when the backup was taken). I have not tested this yet, so I was wondering if any of you could answer these questions for me: 1.- Will I be able to restore if I have LTAPEDEV set to /dev/null and the method to do backups is ontape -s -L 0 ? 2.- Can users be working on the system while I do the backup??? 3.- Does onbar support the same configuration??? (That is taking snapshots of the database and sending the logs to null) Thanks!!! Sent via Deja.com http://www.deja.com/ Before you buy.

1. Yes 2. Yes 3. Yes <rsalido@my-deja.com> ''''' ' ''''''''':8sjc63$2gg$1@nnrp1.deja.com... > Hello, > > I have two instances where LTAPEDEV is set to /dev/null. I did this > because I do not care about restoring to a point in time doing logical > restores, I only need to be able to restore to a specific point in time > (in this case when the backup was taken). > > I have not tested this yet, so I was wondering if any of you could > answer these questions for me: > > 1.- Will I be able to restore if I have LTAPEDEV set to /dev/null and > the method to do backups is ontape -s -L 0 ? > > 2.- Can users be working on the system while I do the backup??? > > 3.- Does onbar support the same configuration??? (That is taking > snapshots of the database and sending the logs to null) > > > Thanks!!! > > > Sent via Deja.com http://www.deja.com/ > Before you buy.

rsalido@my-deja.com wrote: > > 2.- Can users be working on the system while I do the backup??? > Keep in mind that the backup will be consistent as at the time that it was started. That is, all changes after the Archive checkpoint will NOT be in the backup. Rudy