RE: onbar with no-logging
Posted in 2000
Topics: Backup & Restore, Storage & Space Management, Migration, Import/Export & Data Conversion
Tina:
Let me say a few things:
- if you can stop the database for as long as you need for backup to take
place you can backup the disk space from outside the RDBMS and of course not
use any logging.
- if you cannot stop the system then you do not have any means to bypass the
logging because the RDBMS must make sure the data is consistent during the
backup process
- but if you do not care about consistent data, you could do unloads of each
and every table one at a time with some script
- you could use no logging databases and/or redirect to /dev/null your log
backup
- finally you can just backup your logs which I think is your best option.
And also the safe one.
Yours
> N. Daniel Bonesana
> SIEMENS-ITRON BUSINESS SERVICES S.A.
> Balcarce 683, (C1064AAM) Buenos Aires, Argentina.
> * 54 (11) 4320-5456 * Daniel.Bonesana@siemens-itron.com.ar
>
>
-----Original Message-----
From: Tina_Bradley@HomeDepot.COM [mailto:Tina_Bradley@HomeDepot.COM]
Sent: Tuesday, October 03, 2000 3:32 PM
To: informix-list@iiug.org
Subject: onbar with no-logging
Does anyone know of a way to use onbar to backup the database and not use
logging, and still NOT have the logs fill up?
(Simular to using /dev/null for LTAPEDEV?)
Thanks,
Tina Bradley
Tina_Bradley@HomeDepot.com
-
-
??
Just set LTAPEDEV to /dev/null and the engine should
automatically mark the logicals logs as backed up as soon as they
fill.
Daniel Bonesana wrote in message <8rdggf$pg0$1@news.xmission.com>...
>
>Tina:
>
>Let me say a few things:
>- if you can stop the database for as long as you need for backup to take
>place you can backup the disk space from outside the RDBMS and of course
not
>use any logging.
>- if you cannot stop the system then you do not have any means to bypass
the
>logging because the RDBMS must make sure the data is consistent during the
>backup process
>- but if you do not care about consistent data, you could do unloads of
each
>and every table one at a time with some script
>- you could use no logging databases and/or redirect to /dev/null your log
>backup
>- finally you can just backup your logs which I think is your best option.
>And also the safe one.
>
>Yours
>
>> N. Daniel Bonesana
>> SIEMENS-ITRON BUSINESS SERVICES S.A.
>> Balcarce 683, (C1064AAM) Buenos Aires, Argentina.
>> * 54 (11) 4320-5456 * Daniel.Bonesana@siemens-itron.com.ar
>>
>>
>
>
>-----Original Message-----
>From: Tina_Bradley@HomeDepot.COM [mailto:Tina_Bradley@HomeDepot.COM]
>Sent: Tuesday, October 03, 2000 3:32 PM
>To: informix-list@iiug.org
>Subject: onbar with no-logging
>
>
>
>
>Does anyone know of a way to use onbar to backup the database and not use
>logging, and still NOT have the logs fill up?
>(Simular to using /dev/null for LTAPEDEV?)
>
>Thanks,
>Tina Bradley
>Tina_Bradley@HomeDepot.com
>-
>-
>