Translating with DrWatson… this can take a few seconds the first time.
This is a genuine, complex translation. DrWatson protects commands, error codes, and log output while naturally translating the surrounding text. It’s translated once and saved.
Neil Truby — — source: Usenet: comp.databases.informix
"Art S. Kagel" <kagel@bloomberg.net> wrote in message
news:mailman.117.1153145197.873.informix-list@iiug.org...
> bozon wrote:
>> Interesting, we were wondering if you could run ontape on the secondary
>> to back up the database but I have been so busy I haven't been able to
>> investigate or test it. (I just realized it would probably only take a
>> minute to check the c.d.i archives, but then I couldn't implement it
>> for 6 months anyway.)
> <SNIP>
> Yes you can run ontape on the secondary to get a consistent archive of the
> servers. The operation would not block or otherwise affect concurrent
> updates from the primary except as any resource usage on the machine and
> server would. The archive would be restorable onto either host.
Really? How can this be? The replicate, sitting there as it is waiting
eitther for further transactions or fast recovery, may be physically
consistent but how can it be logically consistent?
If I try it it doesn't work, just as I'd expect:
$ onstat -g driIBM Informix Dynamic Server Version 10.00.FC3 -- Read-Only (Sec) -- Up
22 days 18:08:36 -- 3347456 Kbytes
Data Replication:
Type State Paired server Last DR CKPT (id/pg)
secondary on ifx_tcp_1_leeds 10616 / 3562
DRINTERVAL 30
DRTIMEOUT 30
DRAUTO 0
DRLOSTFOUND /opt/informix/dbspaces1/dr.lostfound
DRIDXAUTO 1$ ontape -sServer is in an incompatible state or user authentication failed.
Program over.
We use strictly necessary cookies to make this site work. With your
consent we’d also use optional cookies for analytics and marketing. You can accept all,
reject all, or choose. Read our Cookie Policy.