Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Question about initial backup for Log Shipping Expand / Collapse
Author
Message
Posted Wednesday, July 2, 2014 12:33 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Sunday, July 13, 2014 10:51 PM
Points: 4, Visits: 17
Hi All, I'm in the process of setting up log shipping for several SQL 2008 DB's. Everything works fine using a small test DB, but for the next step, I need to configure Log shipping for a 100+GB DB that will be backed up and shipped across a 35Mbps WAN link. If I select to backup that DB using the Log Shipping Wizard and it takes 8+ hours, do I need to be concerned about any changes that have occurred since the start of the backup or will it automatically know which transaction logs to apply after the backup completes? If you've setup something similar, are there any gotchas or best practices I should be aware of when setting up log shipping for a large DB across a WAN link? *This DB gets moderate use and we don't need an aggressive RPO so I'll probably opt for a 30 minute schedule for Log Shipping jobs.

Thanks!
Post #1588594
Posted Wednesday, July 2, 2014 12:47 PM This worked for the OP Answer marked as solution
SSC Eights!

SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!

Group: General Forum Members
Last Login: Friday, October 31, 2014 4:01 PM
Points: 835, Visits: 1,192
You can take a backup and restore it manually on DR site and choose option "Secondary database is already initialized."

Keep in mind that that you have to restore DB with No Recovery option on DR site.
Post #1588601
Posted Thursday, July 3, 2014 6:44 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Yesterday @ 3:38 PM
Points: 6,637, Visits: 14,220
Neeraj Dwivedi (7/2/2014)
Keep in mind that that you have to restore DB with No Recovery option on DR site.

Or standby\readonly


-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs"
Post #1588836
Posted Thursday, July 3, 2014 8:02 AM
SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Yesterday @ 1:35 AM
Points: 5,886, Visits: 13,044
logshipping will know which logs to apply but they must be available to it in the defined directory.

Personally I always do the initial full restore in norecovery and then allow the log restores to set norecovery or read only\standby. Gives me an instant visual prompt the log has restored.


---------------------------------------------------------------------

Post #1588916
Posted Tuesday, July 8, 2014 11:59 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Sunday, July 13, 2014 10:51 PM
Points: 4, Visits: 17
Thanks guys... so I did the manual backup/restore w/ No Recovery and then setup log shipping. All seemed to proceed without error. However, I'm not sure how to tell if it's truly working properly. When I run a log shipping status report, I'm seeing a Red Alert, but when I look at the LSBackup, LSCopy and LSRestore job history, everything is green and happy?

Another question, after log shipping has been setup, can you change between No Recovery and Standby mode or do you need to start all over?

Post #1590454
Posted Tuesday, July 8, 2014 2:06 PM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Yesterday @ 3:38 PM
Points: 6,637, Visits: 14,220
david 81886 (7/8/2014)
Thanks guys... so I did the manual backup/restore w/ No Recovery and then setup log shipping. All seemed to proceed without error. However, I'm not sure how to tell if it's truly working properly. When I run a log shipping status report, I'm seeing a Red Alert, but when I look at the LSBackup, LSCopy and LSRestore job history, everything is green and happy?

Yes the jobs will always usually show success. Check the individual step output for each step, errors will be listed here.



david 81886 (7/8/2014)
Another question, after log shipping has been setup, can you change between No Recovery and Standby mode

Yes you can


-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs"
Post #1590510
Posted Wednesday, July 9, 2014 3:47 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Sunday, July 13, 2014 10:51 PM
Points: 4, Visits: 17
Thanks Guys, I think I figured out what's happening. The restore job is skipping all the log files. I believe this is occurring because there is another job that was previously setup that backs up the same DB transaction logs and it's conflicting with the log shipping. So from what I can gather, I'll need to stop the other log back up job, perform a new full backup and then restore to DR with No Recovery and setup log shipping from scratch?
Post #1590959
Posted Wednesday, July 9, 2014 4:37 PM This worked for the OP Answer marked as solution


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Yesterday @ 3:38 PM
Points: 6,637, Visits: 14,220
david 81886 (7/9/2014)
Thanks Guys, I think I figured out what's happening. The restore job is skipping all the log files. I believe this is occurring because there is another job that was previously setup that backs up the same DB transaction logs and it's conflicting with the log shipping. So from what I can gather, I'll need to stop the other log back up job, perform a new full backup and then restore to DR with No Recovery and setup log shipping from scratch?

If no full backup has been taken on the primary a differential backup will do the job


-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs"
Post #1590966
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse