Re: UK IUG Meeting
One major difference: IDS HDR secondary server allows read access (selects), while DB2 HADR does not. Karl Ostner RollForward Wizard <rollforward@roll To forward.com> informix-list@iiug.org Sent by: cc owner-informix-li st@iiug.org Subject Re: UK IUG Meeting 11/10/2005 03:05 PM Please respond to rollforward Hi, I have a question for you regarding High Availability Data Replication, a feature found in DB2. How does Informix's feature set of replication and HA compare with DB2 HADR? We are currently evaluating DB2 HADR and were curious if Informix had different/better/other features worth investigating. We like what DB2 has, is Informix better? Thanks in advance! PS DB2 also has the redirected-restore feature, where you can restore a database on to a different machine from a backup. david@smooth1.co.uk wrote: > I missed the start due to traffic - only allowed 2.5 hours to get > there, silly me! > > I caught the end of the talk by the IBM senior person (senior North > Europe Sales I think) - did anyone get her name? > > The end of her talk mentioned > > - DB/s and IDS Development Labs are seperate but can share ideas. > - The hot thing is "Master Data". We can read from lots of data > repositories but we also need to be able to keep the duplicate data > across the repositories in sync in realtime! > > There was another "name change" but I missed what it was. > > Carlton Doe replaced Mark Scranton due to a family emergency. > > Carlton did a good job of going through the important new stuff in IDS > 10 but did skip over the lesser bits as I think he had too > many slides from Mark! Carlton definitely listened to what people > wanted and tried to cover the bits that are important to the > people in the room and certainly kept our interest! > > Madison did a great presentation on replication including a live demo > on how to setup ER for a database with just a few commands > and how to add a node to replication with just a few commands. ER can > now create databases/tables on the other nodes for you! > > Also in IDS 10 ER has commands to > > a) verify the ER setup across all nodes in one go rather than starting > ER and waiting for stuff to fail! > > b) detect inconsistent rows across all nodes and produce a report of > missing/different rows on each node and > > c) repair inconsistent rows on all nodes! > > Finally the Q&A session at the end answered everything that anyone > raised. > > One question on OLDB support was deferred for a more detailed answer > but the person who took it was high up in UK support > (email me mate I didn't get the name!) so except an answer soon! > Apparently OLDB needs to be installed in the IDS server but > then the question is what happens if the clients are running different > versions than the server. Watch this space for more info... > > The main questions from the floor included > > - Connectivity questions - OLDB, .NET what is being done about > improving these. > - How do people know when fixpack (UC1 UC2 UC3 etc) releases come out - > answer check IBM's website for the Product > Availablity Spreadsheet and Release Notes/Evaluation copies. Andy Legge > mentioned the spreadsheet has been updated > something like 8 times this year so it is being actively maintained > now! > > Two cool IDS 10 features I missed before are > > a) archecker and table level restore can be used to restore from > archives on a different platform! You could restore a complete > database from an archive on a different platform! > > b) If you setup groupnames in your sqlhosts file you can connect to the > groupname. In an HDR setup this will always connect to > whatever node is the primary. It talks to both nodes and finds which > one is currently the primary. One HDR weakness is the "split > brain " syndrome where the two nodes can no longer talk to one another > and both become primary but they can both talk to the > clients. Perhaps this should be resolved outside the IDS server by an > arbitrator(?) so potentially > look for more work in this area in future versions!! > > The slides should be getting sent to all committee members soon and > we'll see what we do about making them available. sending to informix-list