RSS Secondary - 1000 Miles Away

Good Afternoon, IDS 11.50.FC9X1 OS AIX 6.1 I have an upcoming move in which the production server will be restored to another server 1000 miles away. My plan was to make the "new" production server an RSS secondary of the "old" server and then once caught up, I would turn the RSS secondary into a stand-alone and point all the apps there.My problem is that this system is heavily used so the logs are going to be written to a lot between the time it takes to grab an archive, get it to the new site, and restore it. IE... the logs will be cycled through. I can never get them transferred there to become current enough to restore them and get current with the promary.My network bandwidth between the 2 sites is terrible so I am looking for help. Do I "have" to have the logs on the RSS secondary to restore them or can I do it from the primary? I have played around with a media-less archive/restore (which is pretty slick_ but I am not sure if this will work for me to establish the replication.I am still playing with that scenario but could use some practical advise if anyone else has faced this.I would even appreciate a boot in the rear if I am missing something obvious (-; Thanx, Dan

After shipping the archive to the new server and restoring it using ontape -p, you can then ship over the logical log backups and restore them using ontape -l -C once you have caught up with the primary so that all of thelogical logs that are no longer on the primary have been restored, then you can make the new server an RSS secondary server and it will finish catching up with the primary automatically. Art Art S. Kagel Advanced DataTools (www.advancedatatools.com) Blog: http://informix-myview.blogspot.com/ Disclaimer: Please keep in mind that my own opinions are my own opinions and do not reflect on my employer, Advanced DataTools, the IIUG, nor any other organization with which I am associated either explicitly, implicitly, or by inference. Neither do those opinions reflect those of other individuals affiliated with any entity with which I am affiliated nor those of the entities themselves. On Mon, Oct 24, 2011 at 2:13 PM, DAN MUELLER <dan.mueller@trnswrks.com>wrote: > Good Afternoon, > > IDS 11.50.FC9X1 > OS AIX 6.1 > > I have an upcoming move in which the production server will be restored to > another server 1000 miles away. My plan was to make the "new" production > server an RSS secondary of the "old" server and then once caught up, I > would > turn the RSS secondary into a stand-alone and point all the apps there.My > problem is that this system is heavily used so the logs are going to be > written to a lot between the time it takes to grab an archive, get it to > the > new site, and restore it. IE... the logs will be cycled through. I can > never > get them transferred there to become current enough to restore them and get > current with the promary.My network bandwidth between the 2 sites is > terrible > so I am looking for help. > > Do I "have" to have the logs on the RSS secondary to restore them or can I > do > it from the primary? I have played around with a media-less archive/restore > (which is pretty slick_ but I am not sure if this will work for me to > establish the replication.I am still playing with that scenario but could > use > some practical advise if anyone else has faced this.I would even appreciate > a > boot in the rear if I am missing something obvious (-; > > Thanx, > Dan > > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > --90e6ba6e868e6c889204b0164f42

Dan, If I understand this correctly, your "issue" is that by the time you fedex or ftp the archive and logical logs to the new site the logs have already wrapped on the primary making it virtually impossible to bring this server current. However the logs can be recovered from the primary in a sort of indirect way. What I would consider doing is adding more logs to the current primary (they can always be dropped later, be sure to allocate the space needed on the secondary). Use a pipe to physically restore the secondary from the primary. Once the secondary is restored (given your bandwith this may take some time) take the secondary offine and follow the procedures/commands for RSS or HDR setup. Use ontape -p -e (external restore). This will "assume" you are externally restoring the secondary when in reality your not going to since you just restored it.(This command will just prepare the secondary server for an expected logical recovery). When the prompt returns, enter ontape -r -l and IF and ONLY IF the logs on the primary have not wrapped the engine should connect to the primary and start recovering the logs from the primary since you told the engine this server is a HDR or RSS server . If they have already wrapped you will be or should be prompted to insert the tape with the logs which will be your queue that the logs wrapped. In that case, go back to the primary , add more logs and try again. Best advised to do this when things are relatively slow transaction wise. One thing to keep in mind that given your slow bandwith you may need to add more logs anyway otherwise you may get into log wraps and this does not bode well with HA/RSS.