Re: HDR Replication Requirements
Brett Simpson asked whether HDR disk requirements match those of ER. Madison Pruet said they differ and HDR only needs the same path names on the secondary. Brett summarised a setup of matching servers, sqlhosts, level 0 backup and restore. Fernando Nunes and Art Kagel confirmed it is that easy, with Art adding the restore must be physical only using ontape -p.
Auto-generated by Claude from the posts below — may be imperfect; read the full thread.
Ahh I understand now.. are the disk requirements in HDR the same as in ER ?(transaction record dbspace, row data sbspaces). the manual dosn't specifically say they are needed.
no - they are different. HDR only requires that the same path name on the secondary as on the primary. = From: "BRETT SIMPSON" <brett.simpson@actrol.com.au> = = To: ids@iiug.org = = Date: 11/10/2009 08:32 PM = = Subject: Re: HDR Replication Requirements [18045] = = Sent by: ids-bounces@iiug.org = = Ahh I understand now.. are the disk requirements in HDR the same as in ER ?(transaction record= dbspace, row data sbspaces). the manual dosn't specifically say they are needed. ***********************************************************************= ******** Forum Note: Use "Reply" to post a response in the discussion forum. =
hmm so all I need to do is make sure the secondary server is the same configuration as the primary (OS, IDS version, chunk configuration, logging etc). configure sql hosts on both servers with the correct groups and make sure primary can talk to secondary. do a level0 on the primary and restore on the secondary and start replication ? sounds too easy ....
It is easy... You can opt for the competition if you want complexity :) Regards. On Wed, Nov 11, 2009 at 3:31 AM, BRETT SIMPSON <brett.simpson@actrol.com.au>wrote: > hmm > > so all I need to do is make sure the secondary server is the same > configuration as the primary (OS, IDS version, chunk configuration, logging > etc). > > configure sql hosts on both servers with the correct groups and make sure > primary can talk to secondary. > > do a level0 on the primary and restore on the secondary > > and start replication ? > > sounds too easy .... > > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > -- Fernando Nunes Portugal http://informix-technology.blogspot.com My email works... but I don't check it frequently... --000e0cd6c9ec522c7a047816cc37
It's VERY easy actually, just as you have detailed it. Remember to do the
restore as a physical restore only with:
ontape -p
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 Tue, Nov 10, 2009 at 9:31 PM, BRETT SIMPSON
<brett.simpson@actrol.com.au>wrote:
> hmm
>
> so all I need to do is make sure the secondary server is the same
> configuration as the primary (OS, IDS version, chunk configuration, logging
> etc).
>
> configure sql hosts on both servers with the correct groups and make sure
> primary can talk to secondary.
>
> do a level0 on the primary and restore on the secondary
>
> and start replication ?
>
> sounds too easy ....
>
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
--00151747654e34bb530478243cce