RE: backing up logical logs to nul on windows nt

When you set LTAPEDEV to NUL on NT (or even to /dev/null on UNIX), then you don't have to do an ontape -- the engine is smart enough to see that you just want to throw away the logs, and does that for you. I.e., after it moves to the next log, usually after the prior one fills, it simply marks the old one with the 'B' (backed up) flag. You can test this yourself -- just do an "onmode -l" (advance to next log) and then an "onstat -l". You should see that the log immediately prior to the current one has already been (B)acked-up. HTH, Paul Mosser -----Original Message----- From: EA [mailto:appshome@geocities.com] Sent: Friday, February 11, 2000 3:19 AM To: informix-list@iiug.org Subject: backing up logical logs to nul on windows nt [Sorry if this issue has been discussed before, I just can't seem to find it in the archives...] Appparently the equivalent for /dev/null as an LTAPEDEV destination for logical logs on Unix is NUL on Windows NT. However, when I set LTAPEDEV to NUL in my onconfig file and try to ontape -a I get an error message saying Logbackup failed - Log backup to device 'nul' not allowed Is this not supported on the NT platform or what am I doing wrong? My environment: IDS 7.31 TC2 on Windows NT 4.0 SP4 Any help would be greatly appreciated. Thanks and Cheers E.

Paul, thanks a lot for your reply. Of course, you're right - I just checked on my Unix box and the server does indeed back up the logs automatically as LTAPEDEV is set to /dev/null. I just didn't find that mentioned explicitely in the documentation and I always thought that there was an ontape -c running in the background somewhere. Thanks again and Cheers Eckard <mosserp@WellsFargo.COM> wrote in message news:881hu0$1g1$1@news.xmission.com... > > When you set LTAPEDEV to NUL on NT (or even to /dev/null on UNIX), then you > don't have to do an ontape -- the engine is smart enough to see that you > just want to throw away the logs, and does that for you. I.e., after it > moves to the next log, usually after the prior one fills, it simply marks > the old one with the 'B' (backed up) flag. You can test this yourself -- > just do an "onmode -l" (advance to next log) and then an "onstat -l". You > should see that the log immediately prior to the current one has already > been (B)acked-up. > > HTH, > Paul Mosser > > -----Original Message----- > From: EA [mailto:appshome@geocities.com] > Sent: Friday, February 11, 2000 3:19 AM > To: informix-list@iiug.org > Subject: backing up logical logs to nul on windows nt > > > [Sorry if this issue has been discussed before, I just can't seem to find it > in the archives...] > > Appparently the equivalent for /dev/null as an LTAPEDEV destination for > logical logs on Unix is NUL on Windows NT. > However, when I set LTAPEDEV to NUL in my onconfig file and try to ontape -a> I get an error message saying > > Logbackup failed - Log backup to device 'nul' not allowed > > Is this not supported on the NT platform or what am I doing wrong? > My environment: IDS 7.31 TC2 on Windows NT 4.0 SP4 > > Any help would be greatly appreciated. > > Thanks and > Cheers > E. > >

I wish someone would come up with a better phrase than "backing up logical logs to nul". Maybe like 'THROWING AWAY my logs", or "making my database un-recoverable". "backing up nul" is probably one of the worst oxymorons we've got, kinda like 'Informix marketing'. Doug "EA" <appshome@geocities.com> wrote in message news:88c7tn$b0i$1@pollux.ip-plus.net... > Paul, > > thanks a lot for your reply. Of course, you're right - I just checked on my > Unix box and the server does indeed back up the logs automatically as > LTAPEDEV is set to /dev/null. I just didn't find that mentioned explicitely > in the documentation and I always thought that there was an ontape -c > running in the background somewhere. Thanks again and > > Cheers > Eckard > > > <mosserp@WellsFargo.COM> wrote in message > news:881hu0$1g1$1@news.xmission.com... > > > > When you set LTAPEDEV to NUL on NT (or even to /dev/null on UNIX), then > you > > don't have to do an ontape -- the engine is smart enough to see that you > > just want to throw away the logs, and does that for you. I.e., after it > > moves to the next log, usually after the prior one fills, it simply marks > > the old one with the 'B' (backed up) flag. You can test this yourself -- > > just do an "onmode -l" (advance to next log) and then an "onstat -l". You > > should see that the log immediately prior to the current one has already > > been (B)acked-up. > > > > HTH, > > Paul Mosser > > > > -----Original Message----- > > From: EA [mailto:appshome@geocities.com] > > Sent: Friday, February 11, 2000 3:19 AM > > To: informix-list@iiug.org > > Subject: backing up logical logs to nul on windows nt > > > > > > [Sorry if this issue has been discussed before, I just can't seem to find > it > > in the archives...] > > > > Appparently the equivalent for /dev/null as an LTAPEDEV destination for > > logical logs on Unix is NUL on Windows NT. > > However, when I set LTAPEDEV to NUL in my onconfig file and try to > ontape -a> > I get an error message saying > > > > Logbackup failed - Log backup to device 'nul' not allowed > > > > Is this not supported on the NT platform or what am I doing wrong? > > My environment: IDS 7.31 TC2 on Windows NT 4.0 SP4 > > > > Any help would be greatly appreciated. > > > > Thanks and > > Cheers > > E. > > > > > >