This is a discussion on Enterprise Replication restore concerns within the Informix forums, part of the Database Server Software category; --> I am in the process of implementing a 7-node update anywhere ER solution. My management has successful posed a ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| I am in the process of implementing a 7-node update anywhere ER solution. My management has successful posed a few questions that I cannot answer and can't seem to find any literature on. Question #1 If a cold restore has to be done on a specific node and the last logical log was unable to be salvaged, how does ER handle this situation? Is there a manual re-synchronization that has to occur or is ER smart enough to realize that the node we just restored is "behind" and certain transactions need to be resent? I'm thinking that in this instance a manual re-sync is required, something like a repair job. Question #2 What is the best way to add another database into the ER mix? As far as I know the only way to do this is to suspend all nodes and applications, make a copy of the database, include it in ER and then restart the nodes. My boss thinks that solution is unacceptable and that there should be a more dynamic way of including a new database into the ER mix. Does anyone know of a slick method for that? If anyone has or knows of a good white paper on backups and restores involving ER Id like to read it. OS: HP-UX 11i IDS: 10.00.FC3X2 Database size: ~20 GB 5 servers are located at our HO the other 2 are off-site but in still in the US sending to informix-list |
| Thread Tools | |
| Display Modes | |
|
|