Activity overview
Latest activity by csm
Log Shipping : Issue in GUI Activity History
Hello...
Using Log Shipping, with multiple threads on the backup.
Since changing to multiple threads, I've noticed a sporadic issue in SQL Backup GUI when viewing Activity History on the destinatio...
eddie davis wrote:
Do you want me to submit a request to include the pre and post processing tasks for the backup job appear in the "In Progress" tab?
Yes Please! This has caused much confusion too on our end... / comments
eddie davis wrote:
Do you want me to submit a request to include the pre and post processing tasks for the backup job appear in the "In Progress" tab?
Yes Please! This has caused much confusio...
GUI Exception: Timeout Expired
Hello All,
Just returned to my computer and the running SQL Backup GUI had the following exception displayed:SQLBackup v5
Timeout expired. The timeout period elapsed prior to obtaining a connecti...
Chris Auckland wrote:
What I would suggest is to take a full backup of the primary database, copy it to the DR server and restore WITH RECOVERY, OR WITH STANDBY. You could then use the log shipping wizard and select the newly restored standby database. This would mean that when you come to use the log shipping wizard the full database has already been copied across and restored, so it is just the jobs that get created through the Log Shipping Wizard.
Hi Chris,
I did not realize that using the "Overwrite existing database" would function as such --- I had incorrectly assumed that it would re-perform the initial backup/restore. The documentation backs up your direction... good to know for next time!
I basically achieved this same result by creating the backup, restoring WITH RECOVERY, and then manually creating a log backup job with copy to dr share, and manually creating the restore job with moveto. It works perfect... just wanted to advise of the issue with using the wizard... particularly the GUI -- the file copy and restore of the database appeared to work; however as the gui was hung, the wizard would not proceed to the next step of creating the jobs.
Thanks! / comments
Chris Auckland wrote:
What I would suggest is to take a full backup of the primary database, copy it to the DR server and restore WITH RECOVERY, OR WITH STANDBY. You could then use the log shipp...
Fair enough! Decision made... Share will be on destination server!
Thank you for the insightful discussion. / comments
Fair enough! Decision made... Share will be on destination server!
Thank you for the insightful discussion.
Point taken!
Question...
If the network or destination server were unavailable for 1 hour, 3-4 transaction logs backups would not make it into the queue, however the following would.
What would occur on the destination server's restore job? It would be missing 3-4 transaction logs in the sequence.
Thanks again! / comments
Point taken!
Question...
If the network or destination server were unavailable for 1 hour, 3-4 transaction logs backups would not make it into the queue, however the following would.
What would occ...
Thank you for your reply...
I agree with everything you said, and understand how the default setup, using the destination server as the share, functions in respect to reducing network traffic, copying/moving files locally, etc...
However if there was network downtime, or the destination server was unavailable, it wouldn't be as clear which files were pending shipping... the backup would complete into the local folder, but would not be able to copy to a share. So, once connectivity with the destination server was restored, it would need to be determined which logs would need to be delivered, correct?
Keeping the shipping file share on the source server would queue those up, until the destination server was ready to pull them... however, it would result in duplicate network traffic from the restore, then the move. / comments
Thank you for your reply...
I agree with everything you said, and understand how the default setup, using the destination server as the share, functions in respect to reducing network traffic, copy...
Log Shipping Wizard : SQL Backup v5.0 Bug
Hey All -
Just wanted to report some trouble we had utilizing the SQL Backup v5 Log Shipping Wizard in the GUI.
Our source server and destination server are spread across a 1.5 mb private line WAN....
Log Shipping : Multiple Databases, Same Schedule
Hello!
As I mentioned in another post, we're rolling out Log Shipping between two servers; one at each of our two locations - connected via a 1.5mb private line.
My question regards scheduling simu...
Log Shipping over WAN
Hello!
I have recently begun to roll out Log Shipping via SQL Backup between 2 SQL servers across our WAN. We have a 1.5mb private line connecting two locations, if the private line goes down the n...