January 19, 2009 at 10:18 pm
Comments posted to this topic are about the item Log Shipping Cannot Access the File
January 20, 2009 at 8:28 am
Great job and nicely done. We will be doing some log shipping soon and it's nice to know what to look out for.
Rudy
Rudy
May 8, 2009 at 7:21 am
Great article, i've stretched the copy and restore delays as far as i can within the sync limit though our log size surges seem fairly random so I can't schedule around them. This should resolve that issue.
Out of interest would it work if I simply ran the entire log shipping process within an SSIS package. Will the next task in the SSIS control flow not wait for the previous one to complete before executing thus avoiding the contention caused by the tasks stepping on each others toes?
Thanks
Chris
June 22, 2009 at 8:37 am
I apologize for the delay in responding. No excuses, just the life of a DBA
The package I designed was for the destination server which means that it is assumed that the log backup and log shipping from the source server was already being managed through SQL Server, A third party backup software or through an SSIS package on the source server. The package I wrote takes files that were successfully copied and moves them to a new directory (on the same drive) for restoring. If you wanted to restore the logs within the same SSIS package, I would do the following:
Create a main SSIS Package to:
Execute the package (now a sub package) to move the log backup files (in this article) from the shipped logs directory to the Restore Directory.
Add a For Each Loop container that restores the transaction logs and then moves them into the Transaction log directory (for all completed restored logs).
Call this main package from a job. The job will not run unless the previous execution is completed.
If this is not what you were looking for please reply with new requirements.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply