Need Feedback on Trans. Replication w/ Remote Distributor
- From: "Keith Jakobs, MCP" <elohir@xxxxxxxxxxxxxxxxxx>
- Date: Mon, 24 Oct 2005 11:56:18 -0700
Greetings:
I have been asked to set up replication between two SQL servers on our
network. Though I am primarily a network security engineer, and would
consider myself just above a novice SQL Admin, replication is definitely new
territory for me, and I was hoping I could get some help and feedback on
what I think I am trying to accomplish...
The scenario: We have a SQL server that currently serves as the backend
database for a web-based application. It consists of several databases (on
one instance) with no clustering nor data redudancy other than the RAID
structures currently housing the data. A second server has been purchased
with much more processing power, that they wish to use as a failover device,
but do not wish to make it the PRODUCTION box until/unless the current box
fails. They just want a copy of the data to be duplicated to another device
as close to real-time as possible (and without clustering).
So, because of the power of the new box compared to the old one, I had
decided based on my initial research, to set up Transactional Replication
between the two boxes, and defining the new server (Server B) as the Remote
Distributor and Subscriber with the original production server (Server A) as
only a Publisher. I also intended/hoped to use pull subscriptions. The
intent of all these decisions being to absolutely minimize the additional
overhead on the original production box. What I have not been able to find
is any documentation on how to configure an alternate snapshot location when
using a remote distributor that is the sole subscriber. Can this be done?
The reason I need to use alternate snapshots (I believe) is because when I
do implement this on the production servers, they exist in a DMZ zone that
not only has no domain, but also does not have any NetBIOS nor windows mgmt
protocols enabled (except Terminal Services for Remote Admin). There is NO
Windows SMB file sharing, so I need snapshots to be distributed to the
subscriber via FTP .... but as I said, the subscriber IS the distributor.
Can this be done? Did I inadvertently make my first replication project too
complex? Did I overlook something as to how it can be done? Basically I am
stuck at the point where I have definied my first susbscription, did NOT
create an initial snapshot yet, and am trying to figure out how to configure
the 'Snapshot Location' properties on the Publisher so that it will deploy
the snapshot to a location that the Distributor/Subscriber can access via
FTP, BEFORE running the snapshot agent for the first time.
And yes, this is all on a test environment using Virtual PC's at the moment.
My apologies for the length of this message, but I know how much it helps to
have as much detail up front as possible. And Thank you in advance for any
feedback or recommendations.
Keith C. Jakobs, MCP
[FYI... Exec mgmt has INSISTED that all System files, program files, SQL
data and transaction logs are configured on the SAME RAID-5 partition on 4
physical disks with a 5th hot spare drive... I've tried to convince them to
allocate dedicated log drives and pull swap files off the RAID-5, but they
are not interested in deploying multiple physical disk structures on a
single server]
.
- Follow-Ups:
- Re: Need Feedback on Trans. Replication w/ Remote Distributor
- From: Geoff N. Hiten
- Re: Need Feedback on Trans. Replication w/ Remote Distributor
- Prev by Date: Re: Add table to replicated database
- Next by Date: Re: can't delete a row?
- Previous by thread: Add table to replicated database
- Next by thread: Re: Need Feedback on Trans. Replication w/ Remote Distributor
- Index(es):
Relevant Pages
|
