| Author |
Topic |
|
bogey
Posting Yak Master
166 Posts |
 Posted - 2006-05-03 : 13:23:16
|
| Here is the error I'm getting.[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 4326: [Microsoft][ODBC SQL Server Driver][SQL Server]The log in this backup set terminates at LSN 409000000009900001, which is too early to apply to the database. A more recent log backup that includes LSN 410000000030400001 can be restored.[Microsoft][ODBC SQL Server Driver][SQL Server]RESTORE LOG is terminating abnormally.I did a backup on the primary, then restored to the failover. I've been at this since yesterday and need some help. If I try to do a backup and restore during the setup of Log Shipping it always errors out on me. thanks. |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2006-05-03 : 13:39:14
|
| Please describe everything that you have done. The error message indicates that you need to restore prior tlogs first. Do you have any maintenance plans that are backing up the transaction log or jobs that are doing this? If so, those need to be deleted as log shipping will handle this now.Tara Kizeraka tduggan |
 |
|
|
bogey
Posting Yak Master
166 Posts |
Posted - 2006-05-03 : 14:21:45
|
quote:
Originally posted by tkizer
Please describe everything that you have done. The error message indicates that you need to restore prior tlogs first. Do you have any maintenance plans that are backing up the transaction log or jobs that are doing this? If so, those need to be deleted as log shipping will handle this now.Tara Kizeraka tduggan
I'll start the log shipping again from scratch and make sure to remove the trans log backup from my daily maint plan.thanks Tara |
|
|
|
bogey
Posting Yak Master
166 Posts |
Posted - 2006-05-03 : 15:33:27
|
| Tara - No errors this time but it seems as if my changes are not being applied to my standby server. Any clues? |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2006-05-03 : 15:46:05
|
| What does the log shipping monitor show? Are the files being copied over to the destination server in the directory that you specified?Tara Kizeraka tduggan |
|
|
|
bogey
Posting Yak Master
166 Posts |
Posted - 2006-05-03 : 16:27:12
|
| I'm looking at the SQL Server log on the primary server and its showing Error: 14421 Out of Sync. I've backed up and restored.Looking at the Secondary Server Log Shipping History the only file name that's showing in the Last File column is "first_file_00000000000.trn". My Status/Error column is showing "Succeeded". I've altered the data but its not showing up on my failover.I do have a BIG RED X showing in the "Log Shipping Pair" column |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2006-05-03 : 16:32:29
|
| Log shipping is definitely not working properly. You need to confirm if the files are even being copied over to the destination server. When setting up log shipping, you tell it the destination using a share, such as:\\DestinationServerName\LogShippingFolderShareLog into the source server using the MSSQLSERVER service account. See if you can access this share from there. If you can't, then that's the problem.Tara Kizeraka tduggan |
|
|
|
bogey
Posting Yak Master
166 Posts |
Posted - 2006-05-03 : 16:49:51
|
quote:
Log into the source server using the MSSQLSERVER service account. See if you can access this share from there. If you can't, then that's the problem.
Tara - This is the startup service account, correct? |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2006-05-03 : 16:54:09
|
| Yes. If it is the Local System Account, then that's why it is broken. A domain account that has local admin privileges on both boxes should be used.Tara Kizeraka tduggan |
|
|
|
bogey
Posting Yak Master
166 Posts |
Posted - 2006-05-03 : 16:57:07
|
quote:
Originally posted by tkizer
Yes. If it is the Local System Account, then that's why it is broken. A domain account that has local admin privileges on both boxes should be used.Tara Kizeraka tduggan
I was using a domain account without priv's to the "other" machine. Lets see if I can get this working now. By the way. Will anyone, yourself included Tara, be attending Microsoft's Tech Ed in Boston?Thanks for all your help. |
|
|
|
bogey
Posting Yak Master
166 Posts |
Posted - 2006-05-03 : 21:11:35
|
I think I found what the problem is/was. Our servers are in differenct domains and I assumed that the primary pushed the log files down to the failover. Its just the opposite. The failover grabs the transaction logs and applies them and this is where the problem resides. Our firewall rules state that the primary can talk to the failover but the failover cannot communicate with the primary.thanks for all your help  |
|
|
|
|
Log Shipping Help