HDR and ER

Hi all :) I wonder if someone can give me some helpful hints about HDR and ER. Situation: Seven IDS 7.23 UC13 ( on: SCO Open Server 3.2v5.0.5) exchanging master table data via ER (update anywhere). We would now like to "mirror" each of the database machines (physically into new machines) in order to 1) gain some (hardware) redundancy and 2) let some reporting tasks run against the mirror machines instead of the primary database machines. For the uses above the mirroring must be just in time. Sadly enough we came to know that HDR would be the option of choice but ER doesnt work together with HDR. We could now run the whole thing via ER replicating all the hundreds of tables but this would mean an enormous amount of administrative work involved (i.e. making all tables ER-able, managing the whole process, doing the same thing again whenever a new table is created...). My question is if there isnt an easier approach. We also played around with completed logfiles but ontape always forces a complete physical restore before we can do a logical restore. Any ideas? Thanks in advance Heinz

I'm trying something like that. We have 2 pairs of machines, ServerA1 <-> ServerA2 and ServerB1<->ServerB2. ___________ __________ | ServerB1 | <------ HDR -------> | ServerB2 | ----------- ---------- ^ | ER | v ___________ __________ | ServerB1 | <------ HDR -------> | ServerB2 | ----------- ---------- This week we are testing this configuration and it seems to work. We must define first HDR, and then create the ER. We are not finished with the test, but by now it seems to work. I don´t know if this help you. -- Rafael G. -- Magiera wrote: > Hi all :) > > I wonder if someone can give me some helpful hints > about HDR and ER. > > Situation: Seven IDS 7.23 UC13 ( on: SCO Open Server 3.2v5.0.5) > exchanging master table data via ER (update anywhere). > > We would now like to "mirror" each of the database > machines (physically into new machines) > in order to 1) gain some (hardware) redundancy and > 2) let some reporting tasks run against the mirror > machines instead of the primary database machines. > For the uses above the mirroring must be > just in time. > > Sadly enough we came to know that HDR would be the > option of choice but ER doesnt work together with > HDR. > > We could now run the whole thing via ER replicating > all the hundreds of tables but this would mean > an enormous amount of administrative work involved > (i.e. making all tables ER-able, managing the whole > process, doing the same thing again whenever a new > table is created...). > > My question is if there isnt an easier approach. > We also played around with completed logfiles but > ontape always forces a complete physical restore > before we can do a logical restore. > > Any ideas? > > Thanks in advance > Heinz > >

Hi, you cannot use HDR and ER at the same time with current versions of the server (this should be somewhere in the manuals - I didn't check though). Even if it seems to work it won't be supported. As far as I know, this functionality may be available with a future version. As Madison is certainly the expert when it comes to ER you may want to wait for his confirmation 8-) Hope this helps, Heiko rgsanchez@jazzfree.com wrote: > I'm trying something like that. > > We have 2 pairs of machines, ServerA1 <-> ServerA2 and > ServerB1<->ServerB2. > > ___________ __________ > | ServerB1 | <------ HDR -------> | ServerB2 | > ----------- ---------- > ^ > | > ER > | > v > ___________ __________ > | ServerB1 | <------ HDR -------> | ServerB2 | > ----------- ---------- > > This week we are testing this configuration and it seems to work. > We must define first HDR, and then create the ER. > > We are not finished with the test, but by now it seems to work. > I don´t know if this help you. > > -- Rafael G. -- > > Magiera wrote: > > > Hi all :) > > > > I wonder if someone can give me some helpful hints > > about HDR and ER. > > > > Situation: Seven IDS 7.23 UC13 ( on: SCO Open Server 3.2v5.0.5) > > exchanging master table data via ER (update anywhere). > > > > We would now like to "mirror" each of the database > > machines (physically into new machines) > > in order to 1) gain some (hardware) redundancy and > > 2) let some reporting tasks run against the mirror > > machines instead of the primary database machines. > > For the uses above the mirroring must be > > just in time. > > > > Sadly enough we came to know that HDR would be the > > option of choice but ER doesnt work together with > > HDR. > > > > We could now run the whole thing via ER replicating > > all the hundreds of tables but this would mean > > an enormous amount of administrative work involved > > (i.e. making all tables ER-able, managing the whole > > process, doing the same thing again whenever a new > > table is created...). > > > > My question is if there isnt an easier approach. > > We also played around with completed logfiles but > > ontape always forces a complete physical restore > > before we can do a logical restore. > > > > Any ideas? > > > > Thanks in advance > > Heinz > > > >