Re: SharePoint and SQL Sercer replication

sorry Steven , used PH through habit apologies.

Steve Smith


"Steve Smith" <steve@xxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:OS7rWfUNGHA.720@xxxxxxxxxxxxxxxxxxxxxxx
For DR yes Stephen , but the standby SQL server in the Resource kit leaves
the DR SQL server in non useable mode. ie. standby. I appreciate that you
can then turn the standby SQL server into recieving requests but again the
resource kit states that users should not be connected to the standby SQL
server when replication takes place and even after the farm fails the
standby SQL and farm should be left in read only. My take on this is fine
use Log Shipping soley for DR but not as a Geo replicated model where the
two SQL servers are live and being accessed by different sets of users and
effectively mirrored farms.
I would love to know if someone has achieved this though in the real
world.

Steve Smith
www.combined-knowledge.com

"Steven Collier [MVP]" <steven.collier@xxxxxxxx> wrote in message
news:%23C%23KifNNGHA.3408@xxxxxxxxxxxxxxxxxxxxxxx
Actually log shipping is a supported method for SharePoint DR, you'll
find details here :-

http://www.microsoft.com/technet/prodtechnol/sppt/reskit/c2861881x.mspx

Steven Collier

"Steve Smith" <steve@xxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:etR794FNGHA.2916@xxxxxxxxxxxxxxxxxxxxxxx
You will not find any documentation on what you are trying to do as it
is not a supported method for Sharepoint which does not include support
for Geo replication. In order to access your replicated databases you
could start by creating a new config database and then joining your
sharepoint servers at Site B to the new config db and see if that helps.
The only company I know of that has a product that does this type of
replication is Syntergy so it may be worth seeing to what level their
replication works to.

Steve Smith
www.combined-knowledge.com
UK Sharepoint Training


"Jørn Jørgensen" <jorn@xxxxxxxxxxx> wrote in message
news:%23d7UT9DNGHA.3924@xxxxxxxxxxxxxxxxxxxxxxx
Hi,

We have the following scenario:

Sites A and B at geographically remote locations, connected by VPN over
Internet (relatively low bandwidth). The servers are in different
domains (no trusts).

At Site A we have installed SharePoint Portal Server on MS SQL 2005,
created a portal site and this works fine locally. We have then set up
SQL replication between database servers at Site A and Site B,
replicating the config database and the three portal databases. Site A
is acting as publisher and distributor. Anyway, the replication seems
to work fine - no errors and all data seem to be present in the tables.

Now at Site B, we have installed SPS but when we try to connect to the
replicated config db we only get the error message "Unexpected error
occurred".

Questions:
1. Is our approach correct - ie. using SQL Server replication to
synchronize the local SPS db's?
2. "Unexpected error" - what can be wrong?

Any input appreciated!

Jorn









.

Relevant Pages