Re: Mirroring

Chris, I had the same "problem" here, to simulate a device error I had to have my sysadmin physically pull the disk out, quite a simulation :) Once the link is resolved informix will not recognize the rm of the link until it needs to resolve it again (when you bounce the engine). Let me know your results as I am running similar tests myself on 8.10 jim james_t_ford@fleet.com cburton@gte.net wrote: } } I am currently on 7.11.UC1 on HP-UX 9.04 } } To experiment (before implementing), I created a mirror of the } root_dbs. Both the root and the mirror are seperate logical (and } physical) devices. The links to the devices were created in } /usr/informix/dev. t_root_dbs and t_root_mir } } After recovery of the root had taken place (watched the log), I did a } level 0 to make sure everything was in sync. Then I deleted the } symbolic link in /usr/informix/dev to t_root_dbs so it would be on the } mirror. I then waited for onstat -d or the log to report the root_dbs } was down. I then did update stats on a table. Dropped and recreated } another table. Created a stored procedure. (All should of had } activity on the root_dbs space). onstat -d showed reads and writes } from the now (supposedly missing) root_dbs. Again I waited. Two } check points; another hour. NO MESSAGES that I now have a (simulated) } device error. I called INFORMIX help, and their answer was that I had } to bounce the server (at least once a week, according to their } guidelines) in order to find a problem. If I have a 24x7 system, & } cannot bounce the server, the mirroring is a moot point. } } Someone please tell me this is wrong. } } TIA } } Chris