June 20, 2012 at 10:27 pm
Hi,
We are planning to configure Logshipping between 2 sql server instances.
ServerA\ins1 -- Primary instance
ServerB\ins1 --Secondary instance.
Question:
does the communication between 2 instances is two way? or ServerA\INS1 just sends the data (copying the transaction log backup) to secondary instance serverB\INS1?
Our requirement is NO data flow allowed from ServerB\INS1 to ServerB\ins1 for securiy reasons? Is that possible with Logshipping?
Thanks
June 21, 2012 at 1:54 am
Log shipping is one way as you cannot modify data in ServerB while in a log shipping setup.
ServerA does the backup and stores the TRN file locally.
ServerB then opens a UNC connection to the UNC path you specify to copy the file from ServerA to ServerB.
ServerB then restores the transaction log to the database.
As the DB is either in NoRecovery mode (no commands allowed) or Standby mode (only SELECT's allowed) you cant send data from ServerB to ServerA as you physically cannot change the data in ServerB.
June 21, 2012 at 8:12 am
Anthony is spot on here, all communications are essentially triggered from the secondary server. Just a note to bear in mind, the backup folder for the primary server does not have to be a local folder. If you're on a domain you may be using a remote file share like so
ServerA backup job runs backup to fileserver share "\\MyCorpFileserver\ServerA\Backups"
ServerB copy job connects to "\\MyCorpFileserver\ServerA\Backups" and moves any backups to local folder "H:\logShipping\ServerA"
ServerB restore job restores log backups from "H:\logShipping\ServerA"
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply