SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Custom Log Shipping Failing


Custom Log Shipping Failing

Author
Message
Jinx-640161
Jinx-640161
SSC-Addicted
SSC-Addicted (436 reputation)SSC-Addicted (436 reputation)SSC-Addicted (436 reputation)SSC-Addicted (436 reputation)SSC-Addicted (436 reputation)SSC-Addicted (436 reputation)SSC-Addicted (436 reputation)SSC-Addicted (436 reputation)

Group: General Forum Members
Points: 436 Visits: 353
Hi,

Perhaps someone can suggest a tweak, change or alternative to the custom log shipping process I have setup. A custom solution was needed because we only have Standard Edition that does not have backup compression and we need to move quite a large amount of data to a remove site.

One of the issues is that when I try to restore the full database from primary to secondary (if the log shipping process has been interrupted for some reason), the secondary is often stuck with the message 'restoring' and I cannot apply log backups after that.

The current process using SSIS is:

Backup primary
Zip backup with 7z
Copy zip to secondary
Unzip
Restore backup to secondary

For a database that is in the region of 120 gb (compresses to just a few gb) this process takes about 10.5 hours, and most often gets the database stuck with restoring message mentioned earlier.

When restoring a transaction log the size runs at about 1 - 4 gb depending on the time of day and often fails.

The whole process if not at all fault tolerant and 'falls over' with the slightest problem.

Is there anything else I should take into account, or does log shipping generally require a fair amount of manual intervention?

Any suggestion and info from the experts out there would be great!:-D

Thanks,

Jinx.
Jinx-640161
Jinx-640161
SSC-Addicted
SSC-Addicted (436 reputation)SSC-Addicted (436 reputation)SSC-Addicted (436 reputation)SSC-Addicted (436 reputation)SSC-Addicted (436 reputation)SSC-Addicted (436 reputation)SSC-Addicted (436 reputation)SSC-Addicted (436 reputation)

Group: General Forum Members
Points: 436 Visits: 353
For future reference - I have solved the biggest problem I was having with the secondary database being stuck in a restoring state for large databases. If I start the job (from remote session), and my session is disconnected it causes the database to be in this stuck restoring state.
Best plan is then to not 'kick start' the process myself but rather let a schedule take care of it.
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search