Re: HDR Replication Requirements
Posted in 2009
I'm not sure what you're thinking when you say "recovery". Technically, the secondary server is permanently in recover mode. But we can dig this further... After you restore (physical restore) the server will ask for the logs generated after the backup on the primary. After applying all these logs it will be synchronyzed and availbale for queries. If during normal processing you have replication issues (for example network breaks) it will be out of synch, but still available for queries. It will try to catch up as soon as network comes up. The problem is that if you stop the secondary server, when you restart it it will only allow queries after becoming in synch with the primary. I'd love to see an option to start the secondary in "open mode" even if it has lagged behind the primary. But this isn't possible. Regards. On Mon, Nov 9, 2009 at 5:52 AM, BRETT SIMPSON <brett.simpson@actrol.com.au>wrote: > Hi > > I'm am still evaluation replication of my IDS 9.4 database. > > The reason we want to do replication is that we want to read data from the > secondary server for reporting purposes (to alleviate some of the load from > the primary server) > > I was thinking of doing ER replication but now I have found a server with > the > same spec as the primary server. > > So I can look at HDR replication as well (as apparently its easier) > > In HDR > > Both servers need the same OS and version of IDS. > > Both servers need to have (or be close) to the same spec. > > The chunks need to be the same on both servers. > > The log space needs to be same on both servers. > > This I can satisfy. > > The question I have is if the secondary server is in recovery can I read > from > it for reporting purposes ? > > thanks > > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > -- Fernando Nunes Portugal http://informix-technology.blogspot.com My email works... but I don't check it frequently... --000e0cd5ca54fe869c0477ef3b49