replication over internet

Hi
I want to set up a replication between servers over the internet. I know
there are 3 ways to do this, using VPN,proxy server or TCP/IP (FTP). but I
don't know the advantages of each one. could you tell me what are the
differences between these ways in performance and security?
and could you tell me what will happen if the servers disconnect from each
other during the process of replication?
Thanks
Tajik,
connectivity is really a choice between VPN or non-trusted connectivity. The
way I see these breaking down are...
using a VPN is secure and you'll be able to use fileshares ie there's no
need to enable FTP. So, although you're operating over the internet things
are much the same as per usual.
The proxy server is an element of the connectivity to a network by acting as
a firewall and blocking traffic on non-essential ports, and possibly
allowing traffic from only assigned IP addresses.
TCP/IP & FTP is the method used if you are replicating across non-trusted
domains - ie in the absence of a VPN. You can have it operate securely by
using a certificate and encrypting the TCP/IP traffic.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Paul, I am getting the following error when I attempt to download the
snapshot files from the Replication FTP Site:
Date11/30/2005 1:20:22 PM
LogJob History
(28053-DB-inventory_master-inventory_master_a-S-HUNLEY-inventory_master-5007D5E3-0C82-47A1-A26A-5E8F52E68F83)
Step ID1
ServerS-HUNLEY
Job
Name28053-DB-inventory_master-inventory_master_a-S-HUNLEY-inventory_master-5007D5E3-0C82-47A1-A26A-5E8F52E68F83
Step NameRun agent.
Duration00:20:24
Sql Severity0
Sql Message ID0
Operator Emailed
Operator Net sent
Operator Paged
Retries Attempted0
Message
-XSERVER S-HUNLEY
-XCMDLINE 0
-XCancelEventHandle 00000828
2005-11-30 18:40:37.661 Startup Delay: 4093 (msecs)
2005-11-30 18:40:41.757 Connecting to Subscriber 'S-HUNLEY'
2005-11-30 18:40:42.008 Connecting to Distributor '28053-DB'
2005-11-30 18:40:42.729 Initializing
2005-11-30 18:40:42.919 Parameter values obtained from agent profile:
-bcpbatchsize 100000
-commitbatchsize 100
-commitbatchthreshold 1000
-historyverboselevel 1
-keepalivemessageinterval 300
-logintimeout 15
-maxbcpthreads 1
-maxdeliveredtransactions 0
-pollinginterval 10000
-querytimeout 300
-skiperrors
-transactionsperhistory 100
2005-11-30 18:40:44.121 Snapshot files will be downloaded via ftp
2005-11-30 18:40:44.301 Connecting to ftp site '28053-DB'
2005-11-30 18:40:46.334 Agent message code 20033. The process could not
retrieve file
'28053-DB_inventory_master_inventory_master_articles\2005 1130120007\Purchase_Order_Line_Items_1.sch' from the FTP site '28053-DB'.
The Publisher is a SQL Server 2000 Database (SP3A) running on Windows 2000
Advanced Server and the Subscriber is a SQL Server 2005 database running on
Windows XP Pro SP2. These databases on in diferent domains. I can ping the
machines from one another and I can see the FTP folder from the subscriber as
well as on the publisher.
Any ideas?
Scott E. Hunley (MCAD)
Measure Twice, Cut Once...
"Paul Ibison" wrote:

> Tajik,
> connectivity is really a choice between VPN or non-trusted connectivity. The
> way I see these breaking down are...
> using a VPN is secure and you'll be able to use fileshares ie there's no
> need to enable FTP. So, although you're operating over the internet things
> are much the same as per usual.
> The proxy server is an element of the connectivity to a network by acting as
> a firewall and blocking traffic on non-essential ports, and possibly
> allowing traffic from only assigned IP addresses.
> TCP/IP & FTP is the method used if you are replicating across non-trusted
> domains - ie in the absence of a VPN. You can have it operate securely by
> using a certificate and encrypting the TCP/IP traffic.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>
|||Scott,
perhaps it is the path you are using to the ftp folder.
When I set this up I used the path
'c:\inetpub\ftproot\trsnapshot'
as the alternative snapshot location on the publisher (snapshot location
tab) - and
\trsnapshot\ftp
as the 'client path to this folder'.
Pls can you tell us what are the corresponding settings on your publisher.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Paul,
I have the following settings in my Publisher:
Alternate Path (Default Path unchecked) -
'\\28053-DB\D$\inetpub\ftproot\replication\inventory_master \'
Ftp Client path -
'\replication\inventory_master\'
The Server that I remote into, automatically assigns the \\28053-DB\D$\
qualifier. I didn't include the ftp subdirectory that you did, it was
created by the process however.
Is this explanation concise enough? If more details are needed please let
me know and I will provide them ASAP.
Thanks in advance for any help or advice you might have.
Scott E. Hunley (MCAD)
Measure Twice, Cut Once...
"Paul Ibison" wrote:

> Scott,
> perhaps it is the path you are using to the ftp folder.
> When I set this up I used the path
> 'c:\inetpub\ftproot\trsnapshot'
> as the alternative snapshot location on the publisher (snapshot location
> tab) - and
> \trsnapshot\ftp
> as the 'client path to this folder'.
> Pls can you tell us what are the corresponding settings on your publisher.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>
>
|||Paul, by the time I was finished writing the first post/response.. I realized
what i had done wrong. I had forgot to put the subdirectory /ftp/ in my
Client Ftp path. Once i did, I reran the process and it worked. Now, I'm
not sure how well replication of anything other than the tables will work,
going from 2000 to 2005, but at least the Data Warehouse is populating
correctly, and transactionally.
I greatly appreciate your time and look forward to discussing other items in
the future.
Respectfully,
Scott E. Hunley (MCAD)
Measure Twice, Cut Once...
"Paul Ibison" wrote:

> Scott,
> perhaps it is the path you are using to the ftp folder.
> When I set this up I used the path
> 'c:\inetpub\ftproot\trsnapshot'
> as the alternative snapshot location on the publisher (snapshot location
> tab) - and
> \trsnapshot\ftp
> as the 'client path to this folder'.
> Pls can you tell us what are the corresponding settings on your publisher.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>
>