Re: standby instance, log recovery

Raimund Jacob wrote:
> Heinrich, Tilo wrote:

hello tilo, hello *!

i started over: created another instance, imported the complete data 
backup and made sure that i did not bring it online.

first remark: when the kernel fails to start (into admin-mode) due to 
the disk being full, you cant tell because knldiag.err is empty 
(probably because the disk is full :).

now, importing the log backup from the first instance worked. hooray.

> > if it is like you say I'm surprised, that a simple 'util_execute clear 
> > log' did not help. I should have asked for the output of 
> > db_restartinfo too.
> exporting host:
> Used LOG Page           659
> First LOG Page          0
> Restartable             1
> Id Restart Record       (db-id of exporting host)
> Id LOG Info             (db-id of exporting host)
> Consistent              1

this did not change.

> importing host:
> Used LOG Page           611
> First LOG Page          2147483647
> Restartable             1
> Id Restart Record       (db-id of importing host)
> Id LOG Info             (db-id of importing host)
> Consistent              1

but this did. now it shows:

Used LOG Page           659
First LOG Page          2147483647
Restartable             1
Id Restart Record       (db-id of exporting host)
Id LOG Info
Consistent              1

however, i still have those questions:
> may i ask what's so dangerous about going online in the standby 
> instance? is it that logs are being written? but the 'clear log' should 
> help then? is it ok for the two systems to have different db-ids?

(it seems that the standby db has no own db-id. but how could i tell?)

and i have a few more questions: (please direct me to any documentation 
that may contain the answers. would be nice if the docs would be accurate :)

1) am i supposed to never bring the standby-instance up unless i really 
want to replace the original instance? when i bring it up once, will i 
be able to import more log backups from the exporting instance?

1a) if i am forbidden to ever bring up the standby instance, can i 
"lock" db_online in any way so that it doesnt happen accidentally?

2) for a continuous standby instance i have to decide wether i should 
use some script to perform log backups at regular intervals (and import 
them) or if i should use autolog. is there any advice or practical 
experience? are there ready-made scripts (i noticed some ugly behaviour 
of the exporting instance when the log is empty).

3) can/should i mix automatic and manual log backups?

4) does it feel different to import automatic logs? does it work the 
same way?

5) does the standby instance produce logs while importing the log 
backups of the original instance?

thank you very much for any advice,
        Raimund Jacob

--
7. RedDot Anwendertagung der RedDot Usergroup e.V. am 31.1.2005
Pinuts präsentiert neue Entwicklung, http://www.pinuts.de/news

Pinuts media+science GmbH                 http://www.pinuts.de
Dipl.-Inform. Raimund Jacob               Raimund.Jacob@xxxxxxxxx
Krausenstr. 9-10                          voice : +49 30 59 00 90 322
10117 Berlin                              fax   : +49 30 59 00 90 390
Germany


--
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe:    http://lists.mysql.com/maxdb?unsub=gcdm-maxdb@xxxxxxxxxxx