|
|
You're in the
sql server replication
group:Log Shipping with MSDE
sql server replication:
I'm trying to set up a warm standby between 2 Windows 2003 Web edition
servers running MSDE across the web. The idea is to do a DB backup once a week , ftp the file to a backup FTP server, then ftp it up to the warm standby server and restore it. Then, each our do much the same with a log backup. The idea being that the intermediate server will provide an 'offsite' backup in case of disaster. It's a bit like simple log shipping in the resource kits, but with FTP between the sites. And it works. Well, the patient is not surviving, but the code is working! The problem seems to be that when the first log is restored the remote server complains that there was a previous one. This even occurs after I do the backup and restore manually, haveing deleted the original database. 'Server: Msg 3013, Level 16, State 1, Line 1 RESTORE LOG is terminating abnormally. Server: Msg 4305, Level 16, State 1, Line 1The log in this backup set begins at LSN 6000000010200001, which is too late to apply to the database. An earlier log backup that includes LSN 5000000046600001 can be restored.' If there's a commercial program, I'll buy it (if it's not to expensive!) this has already taken too long (though I'd like to get it going, I've still got to write the main controller). Iain
You're applying the transaction logs out of sequence it
appears, since it's expecting the next logical LSN in the transaction log file. The databases must start at the same point ONCE, and then all you do is transaction log backups. If you're restoring the full once a week, you need to basically reinit log shipping or fix your process to account for this and look for the right log file. You could always take the version of log shipping in the SQL 2K High Availability book and customize it. [quoted text, click to view] >-----Original Message-----
>I'm trying to set up a warm standby between 2 Windows 2003 Web edition >servers running MSDE across the web. > >The idea is to do a DB backup once a week , ftp the file to a backup FTP >server, then ftp it up to the warm standby server and restore it. > >Then, each our do much the same with a log backup. > >The idea being that the intermediate server will provide an 'offsite' backup >in case of disaster. > >It's a bit like simple log shipping in the resource kits, but with FTP >between the sites. > >And it works. Well, the patient is not surviving, but the code is working! > >The problem seems to be that when the first log is restored the remote >server complains that there was a previous one. > >This even occurs after I do the backup and restore manually, haveing deleted >the original database. > >'Server: Msg 3013, Level 16, State 1, Line 1 >RESTORE LOG is terminating abnormally. >Server: Msg 4305, Level 16, State 1, Line 1The log in this backup set begins >at LSN 6000000010200001, which is too late to apply to the database. An >earlier log backup that includes LSN 5000000046600001 can be restored.' > >If there's a commercial program, I'll buy it (if it's not to expensive!) >this has already taken too long (though I'd like to get it going, I've still >got to write the main controller). > >Iain > > >.
Thanks, Allan.
'reinit log shipping' ? As mentioned it's my own hack (oops code) - I'm not using any of the SQL Server log shipping options and I'm not sure what yo umean by reinit. Is this a restore log or restore database option? Can the log shipping be configured to use FTP? Or is there a way of specifying a share across the internet (I'm sure something with IPSEC could be done, but, so many components, so little time!)? Iain [quoted text, click to view] "Allan Hirt" <allanh@NOSPAMavanade.com> wrote in message news:098301c3ba71$4e371790$a501280a@phx.gbl... > You're applying the transaction logs out of sequence it > appears, since it's expecting the next logical LSN in the > transaction log file. > > > The databases must start at the same point ONCE, and then > all you do is transaction log backups. If you're > restoring the full once a week, you need to basically > reinit log shipping or fix your process to account for > this and look for the right log file. > > You could always take the version of log shipping in the > SQL 2K High Availability book and customize it. > > >-----Original Message----- > >I'm trying to set up a warm standby between 2 Windows > 2003 Web edition > >servers running MSDE across the web. > > > >The idea is to do a DB backup once a week , ftp the file > to a backup FTP > >server, then ftp it up to the warm standby server and > restore it. > > > >Then, each our do much the same with a log backup. > > > >The idea being that the intermediate server will provide > an 'offsite' backup > >in case of disaster. > > > >It's a bit like simple log shipping in the resource kits, > but with FTP > >between the sites. > > > >And it works. Well, the patient is not surviving, but > the code is working! > > > >The problem seems to be that when the first log is > restored the remote > >server complains that there was a previous one. > > > >This even occurs after I do the backup and restore > manually, haveing deleted > >the original database. > > > >'Server: Msg 3013, Level 16, State 1, Line 1 > >RESTORE LOG is terminating abnormally. > >Server: Msg 4305, Level 16, State 1, Line 1The log in > this backup set begins > >at LSN 6000000010200001, which is too late to apply to > the database. An > >earlier log backup that includes LSN 5000000046600001 can > be restored.' > > > >If there's a commercial program, I'll buy it (if it's not > to expensive!) > >this has already taken too long (though I'd like to get > it going, I've still > >got to write the main controller). > > > >Iain > > > > > >. > >
Whether it is your own version of coded log shipping
(which I have done as well), or the stuff which only comes with SQL 2K EE, if you are doing what you say, you will have to start all over (i.e. reinitialize things). Log shipping is meant to start from a single point in time DB, and then just have the transaction logs applied, not restore the main DB all the time. As long as you can code it, you can do FTP, but you'd have to do it through xp_cmdshell [quoted text, click to view] >-----Original Message-----
>Thanks, Allan. > >'reinit log shipping' ? > >As mentioned it's my own hack (oops code) - I'm not using any of the SQL >Server log shipping options and I'm not sure what yo umean by reinit. Is >this a restore log or restore database option? > >Can the log shipping be configured to use FTP? Or is there a way of >specifying a share across the internet (I'm sure something with IPSEC could >be done, but, so many components, so little time!)? > >Iain >"Allan Hirt" <allanh@NOSPAMavanade.com> wrote in message >news:098301c3ba71$4e371790$a501280a@phx.gbl... >> You're applying the transaction logs out of sequence it >> appears, since it's expecting the next logical LSN in the >> transaction log file. >> >> >> The databases must start at the same point ONCE, and then >> all you do is transaction log backups. If you're >> restoring the full once a week, you need to basically >> reinit log shipping or fix your process to account for >> this and look for the right log file. >> >> You could always take the version of log shipping in the >> SQL 2K High Availability book and customize it. >> >> >-----Original Message----- >> >I'm trying to set up a warm standby between 2 Windows >> 2003 Web edition >> >servers running MSDE across the web. >> > >> >The idea is to do a DB backup once a week , ftp the file >> to a backup FTP >> >server, then ftp it up to the warm standby server and >> restore it. >> > >> >Then, each our do much the same with a log backup. >> > >> >The idea being that the intermediate server will provide >> an 'offsite' backup >> >in case of disaster. >> > >> >It's a bit like simple log shipping in the resource kits, >> but with FTP >> >between the sites. >> > >> >And it works. Well, the patient is not surviving, but >> the code is working! >> > >> >The problem seems to be that when the first log is >> restored the remote >> >server complains that there was a previous one. >> > >> >This even occurs after I do the backup and restore >> manually, haveing deleted >> >the original database. >> > >> >'Server: Msg 3013, Level 16, State 1, Line 1 >> >RESTORE LOG is terminating abnormally. >> >Server: Msg 4305, Level 16, State 1, Line 1The log in >> this backup set begins >> >at LSN 6000000010200001, which is too late to apply to >> the database. An >> >earlier log backup that includes LSN 5000000046600001 can >> be restored.' >> > >> >If there's a commercial program, I'll buy it (if it's not >> to expensive!) >> >this has already taken too long (though I'd like to get >> it going, I've still >> >got to write the main controller). >> > >> >Iain >> > >> > >> >. >> > > > >.
Thanks for this. I go it working (though I'm not quite sure WHY).
the trick seems to be to use the correct flags with the restore and backup. The backup of Database and Log needs to be WITH INIT and the REstore of the Log also with REPLACE. Maybe only one of these fixes the issues, but I don't care. The components work. (I've yet to run a system test - I was happy to get the main procedure to 'compile'). Iain [quoted text, click to view] "Allan Hirt" <allanh@NOSPAMavanade.com> wrote in message news:000301c3bb41$95ef4460$a101280a@phx.gbl... > Whether it is your own version of coded log shipping > (which I have done as well), or the stuff which only comes > with SQL 2K EE, if you are doing what you say, you will > have to start all over (i.e. reinitialize things). Log > shipping is meant to start from a single point in time DB, > and then just have the transaction logs applied, not > restore the main DB all the time. > > As long as you can code it, you can do FTP, but you'd have > to do it through xp_cmdshell
Don't see what you're looking for? Try a search.
|
April 2003
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
| home · blog · groups | Questions? Comments? Contact the dn |