Custom Log Shipping
-
My customer needed a second machine running SQL Server with a copy of his database in read only mode. The 2 servers are not in the same LAN. They are connected via a slow WAN connection.
The basic requirement is that the second server comes in synch with the first every 24 hours.
We started with a full backup on the first server and a full restore with standby on the second.
Then I created a command script that is scheduled to run every 24 hours with the following steps:
- invoke isql with login to the local server: backup log to disk
- call ftp on the remote server and send the result file
- rename the file on the local machine and move it to archive directory
- invoke isql with login to remote server: restore log from disk with standby
- invoke xp_cmdshell to rename the file and move it to archive directory on the remote machine
It seems to work. But when the servers enter production cycle, we need also to make a full backup of the local (active) database to tape every day.
My question is :
- does the full backup truncate the transaction log entries that were accumulated since the last log shipping operation ? In that case we would have the 2 datanbases fall out of sync. If so, does anyone have an alternative ?
Thank you !
-
Can't you set the tape to backup the log file created in line one.
WE dump our production Servers everynight which tape backup picks and we then zip and Robocopy over our wan link to our other server and then unzip and load. This is done via a automated script.
And the process is repeated every fifteen minutes via transaction logs
Hope this helps
Catrina
-
I'm using a similar solution. My two sql-servers are in the different cities with 2 MB/sec leased line between.. Full backup on the primary side won't truncate the transaction log.You can continue to apply the transaction logs after the full backup ends.
REgards,
Yalçin Gülas
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply