|
My real question here is... is there a tool I can use? (E.g. I have a lot to do, and would prefer not to script it all up myself!) Anyone using the redgate (hmmm, they had a tool for this, but I do not see it on their web site now...) I have a primary web app at rackspace. Am setting up a backup copy of the app in another data center. I want to use SQL log replication to sync the db. Using SQL Server Web Edition. TIA for suggestions and insight! |
||||
|
This question is unlikely to help any future visitors; it is only relevant to a small geographic area, a specific moment in time, or an extraordinarily narrow situation that is not generally applicable to the worldwide audience of the internet. For help making this question more broadly applicable, see the FAQ.
|
Log Shipping is a feature in Standard, Enterprise, or Workgroup editions. Web edition does not support it. |
|||
|
|
Even if Web edition did support Log Shipping (see icelava's answer), you can log ship without a mapped drive. We do it all the time. You just ship to a UNC share (\\server\share). You can set it all up using the Log Shipping wizard in the SQL Server Management Console, no need to script it if you don't want (or, it will generate the script for you I believe and you can just modify it appropriately for each instance you want to run it on). Looking at more detail in your question, sounds like what you mean is "How do I log-ship without using a share" (i.e. your 2nd web server is not on the same network). AFAIK, you can't, but what you can do fairly easilly is set up a VPN between the two. If you own both the servers (or they are VPS's), then setting up a VPN is as easy as installing a program called Hamachi at both ends and then you can communicate between the two using the IP address as your sharename (e.g. \\5.x.x.x\share). Edit: I see that your question now reflects the UNC path part of the answer |
|||||
|
|
what connectivity do you have between the datacenters? The end result should be that you have a copy of of log backup that's being taken at your primary, copied somehow to your secondary. The easiest way to do this in a windows environment is to share out a UNC path and do an xcopy. But, of course if you cannot do that, you may be able to figure out more creative ways. Here are some other ways besides using CFS/SMB to move the transaction log backup:
In all of these cases you will need to setup an additional service on the primary db server, and a client on the secondary db server & script the copy of the files, as well as poke the right holes through your filewall. |
|||
|
|
|
Well, this did not get the answer I was really looking for... I was hoping to get a reference to either:
That could use http, ftp, or other protocol to move the logs around. The answer seems to be:
I would STILL like to find a real tool... but for now, this seems to be the best that can be done... |
|||
|
|
|
The most straightforward out of the box approach is to use Red Gate SQL Backup, which has full log shipping support, and support for various log file transfer methods built in. When I asked this question, I was hoping to learn of other commercial/foss solutions short of coding it all up myself. |
|||
|
|
