Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

Warm-standy for DR: Where to put the Rep Server, primary or standby site?

5 posts in General Discussion Last posting was on 2012-04-15 08:05:00.0Z
rjlpedrosa Posted on 2012-04-04 02:58:46.0Z
Sender: 6118.4f7bb7b9.1804289383@sybase.com
From: rjlpedrosa
Newsgroups: sybase.public.rep-server
Subject: Warm-standy for DR: Where to put the Rep Server, primary or standby site?
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <4f7bb8e6.614e.1681692777@sybase.com>
NNTP-Posting-Host: 172.20.134.41
X-Original-NNTP-Posting-Host: 172.20.134.41
Date: 3 Apr 2012 19:58:46 -0700
X-Trace: forums-1-dub 1333508326 172.20.134.41 (3 Apr 2012 19:58:46 -0700)
X-Original-Trace: 3 Apr 2012 19:58:46 -0700, 172.20.134.41
Lines: 9
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.rep-server:9193
Article PK: 870356

Hello,

I have a warm-standby to be installed for a DR (different
sites and not closed together) but on a not very quick
connection (100MB).
My question is where I should put the Rep Server? On the
primary site or on the standby site?

Thanks


Manish Negandhi [TeamSybase] Posted on 2012-04-11 04:34:13.0Z
From: "Manish Negandhi [TeamSybase]" <nospam_negandhi.manish@gmail.com>
Newsgroups: sybase.public.rep-server
References: <4f7bb8e6.614e.1681692777@sybase.com>
Subject: Re: Warm-standy for DR: Where to put the Rep Server, primary or standby site?
Lines: 25
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.3664
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3664
X-RFC2646: Format=Flowed; Original
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <4f8509c5@forums-1-dub>
Date: 10 Apr 2012 21:34:13 -0700
X-Trace: forums-1-dub 1334118853 10.22.241.152 (10 Apr 2012 21:34:13 -0700)
X-Original-Trace: 10 Apr 2012 21:34:13 -0700, vip152.sybase.com
X-Authenticated-User: teamsybase
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.rep-server:9194
Article PK: 870358


<rjlpedrosa> wrote in message news:4f7bb8e6.614e.1681692777@sybase.com...
> Hello,
>
> I have a warm-standby to be installed for a DR (different
> sites and not closed together) but on a not very quick
> connection (100MB).
> My question is where I should put the Rep Server? On the
> primary site or on the standby site?
>

Where is your RSSD located ?. Repserver needs to communicate to RSSD
frequently and assuming your RSSD located in primary site, it will be good
idea
to have repserver hosted on primary site as well. Having said that when you
failover you will see that repserver neeeds to communicate to RSSD residing
on other site
However this should not be a major concern if your replication volume is
not very high, you can also fix problem at primary site and failback as soon
as you can

-HTH
Manish Negandhi
[TeamSybase]


rjlpedrosa Posted on 2012-04-12 08:41:21.0Z
Sender: 20e.4f869430.1804289383@sybase.com
From: rjlpedrosa
Newsgroups: sybase.public.rep-server
Subject: Re: Warm-standy for DR: Where to put the Rep Server, primary or standby site?
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <4f869531.235.1681692777@sybase.com>
References: <4f8509c5@forums-1-dub>
NNTP-Posting-Host: 172.20.134.41
X-Original-NNTP-Posting-Host: 172.20.134.41
Date: 12 Apr 2012 01:41:21 -0700
X-Trace: forums-1-dub 1334220081 172.20.134.41 (12 Apr 2012 01:41:21 -0700)
X-Original-Trace: 12 Apr 2012 01:41:21 -0700, 172.20.134.41
Lines: 39
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.rep-server:9196
Article PK: 870359

Hi,

First of all thanks for your reply.
Because this is a new installation and to have minimal
impact on the primary, I was planning to install RSSD in the
new Standby ASE server on the replicate site.
Having this, do you think it's still better to have the
Replicate Server on the primary site or on the replicate?
I was asking this because I had a performance problem on
another installation and the solution was to move the
replication from primary to replicate.

Thanks

> <rjlpedrosa> wrote in message
> > news:4f7bb8e6.614e.1681692777@sybase.com... Hello,
> >
> > I have a warm-standby to be installed for a DR
> > (different sites and not closed together) but on a not
> > very quick connection (100MB).
> > My question is where I should put the Rep Server? On
> > the primary site or on the standby site?
> >
>
> Where is your RSSD located ?. Repserver needs to
> communicate to RSSD frequently and assuming your RSSD
> located in primary site, it will be good idea
> to have repserver hosted on primary site as well. Having
> said that when you failover you will see that repserver
> neeeds to communicate to RSSD residing on other site
> However this should not be a major concern if your
> replication volume is not very high, you can also fix
> problem at primary site and failback as soon as you can
>
> -HTH
> Manish Negandhi
> [TeamSybase]
>
>


"Mark A. Parsons" <iron_horse Posted on 2012-04-12 23:01:07.0Z
From: "Mark A. Parsons" <iron_horse@no_spamola.compuserve.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7
MIME-Version: 1.0
Newsgroups: sybase.public.rep-server
Subject: Re: Warm-standy for DR: Where to put the Rep Server, primary or standby site?
References: <4f8509c5@forums-1-dub> <4f869531.235.1681692777@sybase.com>
In-Reply-To: <4f869531.235.1681692777@sybase.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <4f875eb3@forums-1-dub>
Date: 12 Apr 2012 16:01:07 -0700
X-Trace: forums-1-dub 1334271667 10.22.241.152 (12 Apr 2012 16:01:07 -0700)
X-Original-Trace: 12 Apr 2012 16:01:07 -0700, vip152.sybase.com
Lines: 68
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.rep-server:9197
Article PK: 870360

There's no single/simple answer to your question ...

How much data loss are you willing to accept at the RDS? If the PDS and RS are co-located and they go down at the same
time, then you lose the transactions in the PDB log and anything still sitting in the RS queues. If the RS is
co-located with the RDS then an outage at the PDS will still lose the PDB log records but you'll still have the
transactions in the RS queues.

Do you have a slow network? Are you replicating a lot of transactions for tables with a lot of columns and no repdefs?
The repagent sends fairly compact data to the RS, while the RS/DSI connection would be sending large volumes of SQL
text. If you have a slow network you may benefit from co-locating the RS with the RDS so that the heavier volume of
network activity (RS/DSI connection into RDS) is on a short/fast(?) connection.

Do you suffer from a lot of network outages? In this scenario co-locating the RS with the PDS may be of more benefit
since you can allow transactions to backup in the PDB log *AND* the RS queues. If you co-locate the RS with the RDS,
and you have a lot of network outages, then you'll only be able to support the backlog that can reside in the PDB log.

Do you plan on using this WS pair for anything else (eg, using the logical connection to feed/receive MSA connections)?

Where to locate your RS is doing to depend on your business requirements, DR requirements, replication volumes,
replication topology and design, technical limitations (if any) of the hardware and network, and on and on ...

-----

As for your past performance issue and co-locating the RS with the RDS ... sorry, this doesn't really tell us anything
useful. What was the performance issue? How did co-locating the RS with the RDS improve performance? Even if you
provide this info it doesn't necessarily tell us if you'll have performance issues in the new setup.

On 04/12/2012 02:41, rjlpedrosa wrote:
> Hi,
>
> First of all thanks for your reply.
> Because this is a new installation and to have minimal
> impact on the primary, I was planning to install RSSD in the
> new Standby ASE server on the replicate site.
> Having this, do you think it's still better to have the
> Replicate Server on the primary site or on the replicate?
> I was asking this because I had a performance problem on
> another installation and the solution was to move the
> replication from primary to replicate.
>
> Thanks
>
>> <rjlpedrosa> wrote in message
>>> news:4f7bb8e6.614e.1681692777@sybase.com... Hello,
>>>
>>> I have a warm-standby to be installed for a DR
>>> (different sites and not closed together) but on a not
>>> very quick connection (100MB).
>>> My question is where I should put the Rep Server? On
>>> the primary site or on the standby site?
>>>
>>
>> Where is your RSSD located ?. Repserver needs to
>> communicate to RSSD frequently and assuming your RSSD
>> located in primary site, it will be good idea
>> to have repserver hosted on primary site as well. Having
>> said that when you failover you will see that repserver
>> neeeds to communicate to RSSD residing on other site
>> However this should not be a major concern if your
>> replication volume is not very high, you can also fix
>> problem at primary site and failback as soon as you can
>>
>> -HTH
>> Manish Negandhi
>> [TeamSybase]
>>
>>


rjlpedrosa Posted on 2012-04-15 08:05:00.0Z
Sender: 192f.4f8a7ec9.1804289383@sybase.com
From: rjlpedrosa
Newsgroups: sybase.public.rep-server
Subject: Re: Warm-standy for DR: Where to put the Rep Server, primary or standby site?
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <4f8a812b.1990.1681692777@sybase.com>
References: <4f875eb3@forums-1-dub>
NNTP-Posting-Host: 172.20.134.41
X-Original-NNTP-Posting-Host: 172.20.134.41
Date: 15 Apr 2012 01:05:00 -0700
X-Trace: forums-1-dub 1334477100 172.20.134.41 (15 Apr 2012 01:05:00 -0700)
X-Original-Trace: 15 Apr 2012 01:05:00 -0700, 172.20.134.41
Lines: 104
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.rep-server:9198
Article PK: 870362

Many thanks for your reply it clarifies my doubts even with
all the questions... ;)
I wasn't directly envolved on the project where they moved
the rep server from primary to replicate but I think the
reason was the network being slow and your first
explaination will fit into it because the queues were
building after some time.

The new installation of Rep Server will be only for DR (and
not to feed MSA) and taking in account that the connection
is a 100MB shared with other things, probably setting it in
the replicate site will be the best option for performance.

Thanks once again

> There's no single/simple answer to your question ...
>
> How much data loss are you willing to accept at the RDS?
> If the PDS and RS are co-located and they go down at the
> same time, then you lose the transactions in the PDB log
> and anything still sitting in the RS queues. If the RS is
> co-located with the RDS then an outage at the PDS will
> still lose the PDB log records but you'll still have the
> transactions in the RS queues.
>
> Do you have a slow network? Are you replicating a lot of
> transactions for tables with a lot of columns and no
> repdefs?
> The repagent sends fairly compact data to the RS, while
> the RS/DSI connection would be sending large volumes of
> SQL text. If you have a slow network you may benefit
> from co-locating the RS with the RDS so that the heavier
> volume of network activity (RS/DSI connection into RDS)
> is on a short/fast(?) connection.
>
> Do you suffer from a lot of network outages? In this
> scenario co-locating the RS with the PDS may be of more
> benefit since you can allow transactions to backup in the
> PDB log *AND* the RS queues. If you co-locate the RS with
> the RDS, and you have a lot of network outages, then
> you'll only be able to support the backlog that can reside
> in the PDB log.
>
> Do you plan on using this WS pair for anything else (eg,
> using the logical connection to feed/receive MSA
> connections)?
>
> Where to locate your RS is doing to depend on your
> business requirements, DR requirements, replication
> volumes, replication topology and design, technical
> limitations (if any) of the hardware and network, and on
> and on ...
>
> -----
>
> As for your past performance issue and co-locating the RS
> with the RDS ... sorry, this doesn't really tell us
> anything useful. What was the performance issue? How
> did co-locating the RS with the RDS improve performance?
> Even if you provide this info it doesn't necessarily tell
> us if you'll have performance issues in the new setup.
>
>
> On 04/12/2012 02:41, rjlpedrosa wrote:
> > Hi,
> >
> > First of all thanks for your reply.
> > Because this is a new installation and to have
> > minimal impact on the primary, I was planning to install
> > RSSD in the new Standby ASE server on the replicate
> > site. Having this, do you think it's still better to
> > have the Replicate Server on the primary site or on the
> > replicate? I was asking this because I had a
> > performance problem on another installation and the
> > solution was to move the replication from primary to
> replicate. >
> > Thanks
> >
> >> <rjlpedrosa> wrote in message
> >>> news:4f7bb8e6.614e.1681692777@sybase.com... Hello,
> >>>
> >>> I have a warm-standby to be installed for a DR
> >>> (different sites and not closed together) but on a not
> >>> very quick connection (100MB).
> >>> My question is where I should put the Rep Server?
> On >>> the primary site or on the standby site?
> >>>
> >>
> >> Where is your RSSD located ?. Repserver needs to
> >> communicate to RSSD frequently and assuming your RSSD
> >> located in primary site, it will be good idea
> >> to have repserver hosted on primary site as well.
> Having >> said that when you failover you will see that
> repserver >> neeeds to communicate to RSSD residing on
> other site >> However this should not be a major concern
> if your >> replication volume is not very high, you can
> also fix >> problem at primary site and failback as soon
> as you can >>
> >> -HTH
> >> Manish Negandhi
> >> [TeamSybase]
> >>
> >>