July 13, 2010 at 1:36 am
i want to configure log shipping in my production database and want to keep a secondry server 30 km far from production. as i knw in log shiping trsn log backup get restored on secondry server and to do so the jobs are defined on each server. if network line got down for some hours and trn log backups will not be copied to secondry server. then will this work auto matically as usual when net line will come up again???
July 13, 2010 at 4:21 am
Provided that you have scheduled (for example hourly) jobs for the...
- Transaction Log Backup
- Transaction Log Copy
- Transaction Log Restore
then when network connectivity is restored, these jobs will continue to execute (and pick-up where they left off) provided the SQL Server Service and Agents are running on the respective servers.
July 13, 2010 at 9:10 am
LogShipping jobs runs continuously as the way they are configured. If network goes down for what ever reason, the copy job will fail. As soon as the network comes up, the copy job (those were running as per their schedule) will start copying files. Once the files gets copied, the next time when the restore job will run, will take care of the copied files.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply