Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
DaveFromIll
Starting Member
1 Post |
 Posted - 2009-12-09 : 15:39:44
|
| I am attempting to create log shipping between our production server and a server that has been created as out standby source. The primary database BACKUP file is approximately 157 GB. It is taking us about twenty five minutes to do a FULL BACKUP and about another fifty minutes to send the the BACKUP file over to the secondary server. From there it takes about another thirty five minutes to RESTORE the database in STANDBY. Upon completion I have been attempting to use the Log Shipping Wizard on the primary server to set up the log shipping between the primary and secondary servers. Upon completing the required information for the wizard to set up the log shipping I can see the three SQL jobs created (lsbackup on the primary and lscopy and lsrestore on the secondary) but the backup job fails from the start. I have set up smaller log shipping jobs without much difficulty. However, this one has me completely stumped as to what to do. I have tried scripting based on other succesful log shipping jobs, re-doing the STANDBY database while the rest of the log shipping jobs remain in place. I have tried breaking everything and scripting the jobs one by one. Nothing seems to work. Does anyone have any suggestions how I can establish log shipping for this database?Your help would be greatly appreciated.dave from Ill |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
khermann
Starting Member
10 Posts |
Posted - 2009-12-11 : 17:25:04
|
| If you are designing a simple log shipping scenario (server A to Server B standby) where you do not need to delay the transaction shipping or require the backup files for some other purpose I suggest you consider Database Mirroring which is much simpler to set up and maintain. |
 |
|
|
|
|
|
Log Shipping Problems for a large db