| Author |
Multi Tier design question (SQL Remote)
|
|
|
| Sybase Adaptive Server Anywhere Database Engine Version 8.0.2.4258
I would like to develop a multi tier replication system that will have 3 consolidated databases using SQL Remote
----------------------------------------------------------------------------------------------------------------------------------------------------------------
Development Consolidated
DR1 DR2 DR3 DR4 (remotes of development)
Testing Consolidated (remote of development)
Production Consolidated (remote of testing)
R1 R2 R3 R4 R5 R6 R7 R8 R9 R.... (remotes of production)
----------------------------------------------------------------------------------------------------------------------------------------------------------------
Development consolidated will have automatic (every XX minutes) 2 way replication with the DR# remote users
Development consolidated will have automatic (every XX minutes) 1 way replication with the Testing consolidated
Testing consolidated will have manual (replicate and close) 1 way replication with the production consolidated.
Production consolidated will have automatic (every XX minutes) 2 way replication with the R# users (Multiple tables will replicate down
to the remotes while only 1 table will replicate back to the production consolidated)
----------------------------------------------------------------------------------------------------------------------------------------------------------------
Questions:
a.. Will this design work
b.. Where do the "consolidated" users go
c.. What addresses are used for the consolidated users
d.. Where do the "publisher" users go
e.. What addresses are used for the publisher users
f.. Is there any white papers or other forms of documentation that discusses back up strategies in a multi tier design?
Thanks
TPS
| |
| Rob Waywell 2005-11-17, 9:23 am |
| >>see below
--
-----------------------------------------------
Robert Waywell
Sybase Adaptive Server Anywhere Developer - Version 8
Sybase Certified Professional
Sybase's iAnywhere Solutions
Please respond ONLY to newsgroup
EBF's and Patches: http://downloads.sybase.com
choose SQL Anywhere Studio >> change 'time frame' to all
To Submit Bug Reports:
http://case-express.sybase.com/cx/c...sc?CASETYPE=Bug
SQL Anywhere Studio Supported Platforms and Support Status
http://my.sybase.com/detail?id=1002288
"TPS" <ts@scientexlc.com> wrote in message news:437c03f6@forums
-1-dub...
Sybase Adaptive Server Anywhere Database Engine Version 8.0.2.4258
I would like to develop a multi tier replication system that will have 3
consolidated databases using SQL Remote
----------------------------------------------------------------------------------------------------------------------------------------------------------------
Development Consolidated
DR1 DR2 DR3 DR4
(remotes of development)
Testing Consolidated (remote of development)
Production Consolidated (remote of testing)
R1 R2 R3 R4 R5 R6 R7 R8 R9 R....
(remotes of production)
----------------------------------------------------------------------------------------------------------------------------------------------------------------
Development consolidated will have automatic (every XX minutes) 2 way
replication with the DR# remote users
Development consolidated will have automatic (every XX minutes) 1 way
replication with the Testing consolidated
Testing consolidated will have manual (replicate and close) 1 way
replication with the production consolidated.
Production consolidated will have automatic (every XX minutes) 2 way
replication with the R# users (Multiple tables will replicate down
to the remotes while only 1 table will replicate back to the
production consolidated)
----------------------------------------------------------------------------------------------------------------------------------------------------------------
Questions:
Will this design work[color=darkred]
Where do the "consolidated" users go[color=darkred]
What addresses are used for the consolidated users[color=darkred]
Where do the "publisher" users go[color=darkred]
What addresses are used for the publisher users[color=darkred]
Is there any white papers or other forms of documentation that discusses
back up strategies in a multi tier design?[color=darkred]
Thanks
TPS
| |
|
| "I don't see anything that can't be done, although it is *very* strange to
have your production consolidated as a remote to a test consolidated,
this creates a dependency between the production and test servers and
that certainly feels contrary to the intent of isolating the test
environment and then staging to production when you have a stable release
of changes"
I am not sure what you are saying here.
The replication between the development to test is 1 way replication and the
replication between the testing and production is also 1 way replication.
Changes are made on the development and replicated to test automatically.
Once the testing is done on test to validate the changes the project manager
will manully run dbremote to replicate to the production consolidated (No
users connect to production). Than production consolidated automatically
replicates to the remote users in the field. These updates may occur every
day. The remotes in the field do not have the ability to make updates to the
"support" data and the "user" data is not replicated anywhere in the system.
TPS
| |
| Rob Waywell 2005-11-18, 11:23 am |
| Are you expecting schema changes to be replicated? While this can be
implemented through PASSTHROUGH, that would not be the recommended approach
for deploying changes from the development to test to production
consolidated database.
--
-----------------------------------------------
Robert Waywell
Sybase Adaptive Server Anywhere Developer - Version 8
Sybase Certified Professional
Sybase's iAnywhere Solutions
Please respond ONLY to newsgroup
EBF's and Patches: http://downloads.sybase.com
choose SQL Anywhere Studio >> change 'time frame' to all
To Submit Bug Reports:
http://case-express.sybase.com/cx/c...sc?CASETYPE=Bug
SQL Anywhere Studio Supported Platforms and Support Status
http://my.sybase.com/detail?id=1002288
"TPS" <ts@scientexlc.com> wrote in message news:437cb81a$1@foru
ms-1-dub...
> "I don't see anything that can't be done, although it is *very* strange to
> have your production consolidated as a remote to a test consolidated,
> this creates a dependency between the production and test servers and
> that certainly feels contrary to the intent of isolating the test
> environment and then staging to production when you have a stable release
> of changes"
>
> I am not sure what you are saying here.
> The replication between the development to test is 1 way replication and
> the replication between the testing and production is also 1 way
> replication. Changes are made on the development and replicated to test
> automatically. Once the testing is done on test to validate the changes
> the project manager will manully run dbremote to replicate to the
> production consolidated (No users connect to production). Than production
> consolidated automatically replicates to the remote users in the field.
> These updates may occur every day. The remotes in the field do not have
> the ability to make updates to the "support" data and the "user" data is
> not replicated anywhere in the system.
>
> TPS
>
|
|
|
|