Re: Q: ontape -a to /dev/null
RVASUDEV wrote:
>
> Hi,
>
> One on of our HP-UX 10.20 machines with Informix 7.30 UC7x8,
> when TAPEDEV and LTAPEDEV are set to /dev/null, ontape -a
> gives a message that it cannot backup logical logs to /dev/null.
> Creating a link from null to null2 and setting *TAPEDEV to
> null2 works. On our other (same config) machines, though,
> null works fine. Any ideas ?
Isn't that self explanatory? You can't backup to /dev/null, the restores
take for ever. :-)
The OnTape utility did actually write to /dev/null in older versions,
but the later versions are a little more intelligent and know there is
no point.
If you set TAPEDEV to /dev/null, then you can still perform ontape -s
because this is how you change the logging mode of your databases.
However, it does not perform an archive.
If you set LTAPEDEV to /dev/null then IDS will mark your logs as backed
up as soon as they fill. Therefore there is no need to run either ontape
-a or ontape -c.
Hope that helps,
--
Mark.
+----------------------------------------------------------+-----------+
|Mark D. Stock - Informix SA http://www.informix.com |//////// /|
|mailto:mdstock@informix.com http://www.informix.com/idn |///// / //|
|http://www.iiug.org +-----------------------------------+//// / ///|
| Tel: +27 11 807 0313 |If it's slow, the users complain. |/// / ////|
| Fax: +27 838250 2325 |If it's fast, the users keep quiet.|// / /////|
|Cell: +27 83 250 2325 |Therefore, "No news: travels fast"!|/ ////////|
+----------------------+-----------------------------------+-----------+
I got around this using a symbolic link, hope this helps
On Wed, 7 Apr 1999, Mark D. Stock wrote:
>Date: Wed, 07 Apr 1999 11:34:30 +0200
>From: Mark D. Stock <mdstock@informix.com>
>Newsgroups: comp.databases.informix
>Subject: Re: Q: ontape -a to /dev/null
>
>
>RVASUDEV wrote:
>>
>> Hi,
>>
>> One on of our HP-UX 10.20 machines with Informix 7.30 UC7x8,
>> when TAPEDEV and LTAPEDEV are set to /dev/null, ontape -a
>> gives a message that it cannot backup logical logs to /dev/null.
>> Creating a link from null to null2 and setting *TAPEDEV to
>> null2 works. On our other (same config) machines, though,
>> null works fine. Any ideas ?
>
>Isn't that self explanatory? You can't backup to /dev/null, the restores
>take for ever. :-)
>
>The OnTape utility did actually write to /dev/null in older versions,
>but the later versions are a little more intelligent and know there is
>no point.
>
>If you set TAPEDEV to /dev/null, then you can still perform ontape -s
>because this is how you change the logging mode of your databases.
>However, it does not perform an archive.
>
>If you set LTAPEDEV to /dev/null then IDS will mark your logs as backed
>up as soon as they fill. Therefore there is no need to run either ontape
>-a or ontape -c.
>
>Hope that helps,
>
--
Does anyone know it will work for onbar? We are currently implementing onbar
in our servers. But we have no need to backup the logical logs on the
development and testing servers.
Fred Lee
fredlee@acm.org