HDR
Question: on an IDS 7.31 HDR pair, if the primary is taken down ~2 hours for maintenance and the secondary is switched to standard/primary, must logical logs be restored to the primary afterwards? Answers: normally no — bring the old primary back as secondary and it pulls the needed logs from the other server, provided the logs since the split haven't been overwritten/wrapped there and nothing was changed on the primary during maintenance. If the logs are gone, restore from the log backups (keep backing logs up on the standard server) or re-restore the primary from a backup of the other node, then switch roles back. The poster was satisfied with this advice.
Auto-generated by DrWatson from the posts below — may be imperfect; read the full thread.
Hi Would anyone tell me on a HDR pair in IDS 7.31, if I bring down the primary server (say for 2 hours appx for maintenance ) and make the secondary server as STANDARD, after primary server comes up, do I need to restore logical logs from secondary server? I want to bring the primary server in its original state as PRIMARY. In the PRIMARY pair logical logs are backed up through Netbackup Prabal
As long as your logical logs have not cycled all the way through and been over written, when you bring the primary back up and move the secondary from standard to secondary, the primary will pull the logs it needs from the secondary to sync up. Larry > To: ids@iiug.org > From: d.prabal@gmail.com > Subject: HDR [17420] > Date: Thu, 8 Oct 2009 05:49:09 -0400 > > Hi > > Would anyone tell me > > on a HDR pair in IDS 7.31, if I bring down the primary server (say for 2 hours > appx for maintenance ) and make the secondary server as STANDARD, after > primary server comes up, do I need to restore logical logs from secondary > server? > > I want to bring the primary server in its original state as PRIMARY. > > In the PRIMARY pair logical logs are backed up through Netbackup > > Prabal > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. >
I'm assuming you are doing physical maintenance on the hardware not the server or its contents. Two choices: 1. Put the secondary into PRIMARY mode, then when you have finished working on the old primary bring the old primary in secondary mode and let it catch up. Once it is in sync switch roles back to normal. This will work if: 1. The logical logs haven't wrapped on the original secondary during the maintenance cycle. 2. You haven't changed any data or structure on the original primary durin maintenance. 2. After you are done with maintenance, back up the original seconary and restore it to the original primary putting it into secondary mode. Once the the new secondary is online switch roles back to normal. Art Art S. Kagel Oninit (www.oninit.com) IIUG Board of Directors (art@iiug.org) Disclaimer: Please keep in mind that my own opinions are my own opinions and do not reflect on my employer, Oninit, the IIUG, nor any other organization with which I am associated either explicitly or implicitly. 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 Thu, Oct 8, 2009 at 5:49 AM, PRABAL DAS <d.prabal@gmail.com> wrote: > Hi > > Would anyone tell me > > on a HDR pair in IDS 7.31, if I bring down the primary server (say for 2 > hours > appx for maintenance ) and make the secondary server as STANDARD, after > primary server comes up, do I need to restore logical logs from secondary > server? > > I want to bring the primary server in its original state as PRIMARY. > > In the PRIMARY pair logical logs are backed up through Netbackup > > Prabal > > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > --0023545bda28faea9e04756d9d09
Thanks for responding Just I am not clear with No. 1 The logical logs haven't wrapped on the original secondary during the maintenance cycle. --Do you mean I should not backup the logs on the secondary ? Actually this is the point I am not clear about Prabal
You should be able to just start your instances in the primary and secondary modes as they were when you took them off-line and the logs will catch up the secondary from the primary, if the logs on the primary have not been written over. Thanks, ******************************************************************* Ernie Knox IT Database Administrator Specialist Sears Holdings 3333 Beverly Rd., B4-266A Hoffman Estates, IL. 60179 Office: (847) 286-5735 Email: Ernest.Knox@searshc.com Blackberry: 2244650553@messaging.sprintpcs.com Page via Skytel: 2244650553@sprint.skytel.com Informix or MySQL Primary: 9110210@skytel.com Informix or MySQL Secondary: 7276872@skytel.com " Yes we can make a Change! " " It's always a great day to watch Sports - GO LIONS, TIGERS, and BEARS! " " Lets not forget - GO Pistons and Red Wings! " GSU ******************************************************************* -----Original Message----- From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of PRABAL DAS Sent: Thursday, October 08, 2009 10:22 AM To: ids@iiug.org Subject: Re: HDR [17436] Thanks for responding Just I am not clear with No. 1 The logical logs haven't wrapped on the original secondary during the maintenance cycle. --Do you mean I should not backup the logs on the secondary ? Actually this is the point I am not clear about Prabal ************************************************************************ ******* Forum Note: Use "Reply" to post a response in the discussion forum.
No, by example: If the last logid at the time you drop replication is say 2001, then if log # 2001 is still available on the original secondary you are good to go. If the lowest log number is higher than 2001 (so higher than the highest log on the original primary), you'd have to restore the original primary from the original secondary. Art S. Kagel Oninit (www.oninit.com) IIUG Board of Directors (art@iiug.org) Disclaimer: Please keep in mind that my own opinions are my own opinions and do not reflect on my employer, Oninit, the IIUG, nor any other organization with which I am associated either explicitly or implicitly. 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 Thu, Oct 8, 2009 at 11:21 AM, PRABAL DAS <d.prabal@gmail.com> wrote: > Thanks for responding > > Just I am not clear with No. 1 > > The logical logs haven't wrapped on the original secondary during > the maintenance cycle. > > --Do you mean I should not backup the logs on the secondary ? > > Actually this is the point I am not clear about > > Prabal > > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > --0015174760aa68243504756e9f7d
You should backup logical logs at the standard server. When you restart your old primary instance, it will connect to the current standard-changed-to-secondary server and request logs to get back in sync. Secondary server will be able to send the requested logs if it has one. If not, then primary server will request you to restore logs from the log backup of standard/secondary server. - Nilesh - ids-bounces@iiug.org wrote on 10/08/2009 10:21:42 AM: > [image removed] > > Re: HDR [17436] > > PRABAL DAS > > to: > > ids > > 10/08/2009 10:23 AM > > Sent by: > > ids-bounces@iiug.org > > Please respond to ids > > Thanks for responding > > Just I am not clear with No. 1 > > The logical logs haven't wrapped on the original secondary during > the maintenance cycle. > > --Do you mean I should not backup the logs on the secondary ? > > Actually this is the point I am not clear about > > Prabal > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. >
Hi All, Thanx for you suggestions. Reversal of Replication is a fantastic idea Thanx again Prabal