Hi,
I am having a problem setting up log shipping for a large, 45GB,
database. I had log shipping working for this database. Then one
evening it failed because it could not apply a log file. I cleaned up
by removing log shipping from the maintenance plan, deleting the plans,
jobs, suspect destination database, log files and entries in the msdb
log shipping tables. When I try and re-establish log shipping for the
same database I get the error "unable to copy the initialization file
to the secondary server". I can see the initial backup file being
created on the source server and being copied to the destination server
but at some point it fails. What is strange is that I can still get log
shipping working for a small test database in exactly the same
environment and using the same steps.
Most of the posts on this error I have read suggest that permissions
are at the root. However, I cannot see how permissions can be causing
my problem as I can get it to work for a small database. It seems as
though size is the issue! Has anyone else experienced such a problem?
Any help would be very gratefully received as I've been struggling with
this one for a few days now.
Thanks in advance,
Gavin
have you thought about integrating backup compression software with log
shipping - like LiteSpeed, or RedGate's SQL Backup? These should be able to
get you around this size problem. I find also I have more control when I
roll my own log shipping solution as opposed to using the log shipping
wizard.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
<geetastic@.hotmail.com> wrote in message
news:1169489699.082941.198830@.l53g2000cwa.googlegr oups.com...
> Hi,
> I am having a problem setting up log shipping for a large, 45GB,
> database. I had log shipping working for this database. Then one
> evening it failed because it could not apply a log file. I cleaned up
> by removing log shipping from the maintenance plan, deleting the plans,
> jobs, suspect destination database, log files and entries in the msdb
> log shipping tables. When I try and re-establish log shipping for the
> same database I get the error "unable to copy the initialization file
> to the secondary server". I can see the initial backup file being
> created on the source server and being copied to the destination server
> but at some point it fails. What is strange is that I can still get log
> shipping working for a small test database in exactly the same
> environment and using the same steps.
> Most of the posts on this error I have read suggest that permissions
> are at the root. However, I cannot see how permissions can be causing
> my problem as I can get it to work for a small database. It seems as
> though size is the issue! Has anyone else experienced such a problem?
> Any help would be very gratefully received as I've been struggling with
> this one for a few days now.
> Thanks in advance,
> Gavin
>
|||Hi Hilary,
Thank you for this. Yes I have thought of using these tools but have
been put off by having already spent a fortune on 2 * 4CPU licences for
SQL Server 2000 Enterprise and having already had this database log
shipping happily for over 2 years in another hosting environment. If we
have to use some 3rd party software like this then we have to but it
just seems wrong.
Which of these 2 have you used? Have you found them to be reliable?
Cheers,
Gavin
Hilary Cotter wrote:
> have you thought about integrating backup compression software with log
> shipping - like LiteSpeed, or RedGate's SQL Backup? These should be able to
> get you around this size problem. I find also I have more control when I
> roll my own log shipping solution as opposed to using the log shipping
> wizard.
> --
|||I've used lite speed and it has hooks built into it that will work with the
log shipping wizard.
SQL Backup from RedGate is a highly competitive product - cheaper too.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Geetastic" <geetastic@.hotmail.com> wrote in message
news:1169541651.197139.116160@.s48g2000cws.googlegr oups.com...
> Hi Hilary,
> Thank you for this. Yes I have thought of using these tools but have
> been put off by having already spent a fortune on 2 * 4CPU licences for
> SQL Server 2000 Enterprise and having already had this database log
> shipping happily for over 2 years in another hosting environment. If we
> have to use some 3rd party software like this then we have to but it
> just seems wrong.
> Which of these 2 have you used? Have you found them to be reliable?
> Cheers,
> Gavin
> Hilary Cotter wrote:
>
|||Fixed the problem by rebooting both servers! I didn't want to do this
straight away because this is not something I want to have to do in
production. However, it works.
Thanks for your help.
On Jan 23, 1:11 pm, "Hilary Cotter" <hilary.cot...@.gmail.com> wrote:[vbcol=seagreen]
> I've used lite speed and it has hooks built into it that will work with the
> log shipping wizard.
> SQL Backup from RedGate is a highly competitive product - cheaper too.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTShttp://www.indexserverfaq.com
> "Geetastic" <geetas...@.hotmail.com> wrote in messagenews:1169541651.197139.116160@.s48g2000cws.g ooglegroups.com...
>
>
>
>
Showing posts with label failed. Show all posts
Showing posts with label failed. Show all posts
Wednesday, March 28, 2012
Monday, March 26, 2012
Log Shipping Restore Failing
**PLEASE help. Restore of Log Shippng is failing**
Job error is: sqlmaint.exe failed. [SQLSTATE 42000] (Error 22029). The step failed.
Detailed output of the job says: [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 4305: [Microsoft][ODBC SQL Server Driver][SQL Server]The log in this backup set begins at LSN 31433000001386500001, which is too late to apply to the database. An earlier lo
g backup that includes LSN 314320
00002000300001 can be restored.[Microsoft][ODBC SQL Server Driver][SQL Server]RESTORE LOG is terminating abnormally. (null) [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 4305: [Microsoft][ODBC SQL Server Driver][SQL Server]The log in this backup set be
gins at LSN 31433000001386500001, which is too late to apply to the database. An earlier log backup that includes LSN 31432000002000300001 can be restored. [Microsoft][ODBC SQL Server Driver][SQL Server]RESTORE LOG is terminating abnormally.(null) [Micros
oft SQL-DMO (ODBC SQLState: 42000)] Error 3201: [Microsoft][ODBC SQL Server Driver][SQL Server]Cannot open backup device 'D:\SHIPPEDLOGS\LVBOEProd_tlog_200406272345.TRN'. Device error or device off-line. See the SQL Server error log for more details.[Micr
osoft][ODBC SQL Server Driver][SQL Server]RESTORE LOG is terminating abnormally.(null Loaded 0 files
**All of my shares/directories are correct. I have tried this at least a dozen times. It was successfull the 1st time the restore ran, but after that it has failed every time.
VC,
have a look at your chain of log backups and the log-shipping monitor. See
if you have any logs before 27th June 11:45pm which haven't been transfered
and/or restored. Manually restoring these 'missing' logs then restarting the
logshipping job should fix the problem.
HTH,
Paul Ibison
|||Paul, thank you very much for your reply. this is very important that i get this working ASAP. i have been fighting this day in and day out.
i re-did the log shipping and it's the same problem. do you have an email account that i can email the log to. it has been appending since the 1st restore. you can email me at v_c@.hotmail.com and i'll reply with the log.
there are no files earlier than the 1st file. in fact, this time around, it was successful.
|||VC,
no need to send over the log - it won't help me solve your issue.
I suspect that someone inadvertantly truncated the transaction log before
the first backup and hence the log sequence numbers were out of sync.
Alternatively it could be that the databases themselves were initially out
of sync. You could use LogExplorer (even the evaluation edn) to test if the
former is the case - to see if there are some records missing from the log.
Still, if it's running OK now then fine.
Regards,
Paul Ibison
|||VC,
no need to send over the log - it won't help me solve your issue.
I suspect that someone inadvertantly truncated the transaction log before
the first backup and hence the log sequence numbers were out of sync.
Alternatively it could be that the databases themselves were initially out
of sync. You could use LogExplorer (even the evaluation edn) to test if the
former is the case - to see if there are some records missing from the log.
Still, if it's running OK now then fine.
Regards,
Paul Ibison
|||i was doing this all night, like 2 in the morning. i doubt anyone was truncating logs. however, this is a good suspicion. any other ideas how the log could have gotten truncated?
|||i was doing this all night, like 2 in the morning. i doubt anyone was truncating logs. however, this is a good suspicion. any other ideas how the log could have gotten truncated?
|||2am - and I thought I worked too long hours ;-)
No other ideas really about how else your log got truncated.
I'd check out the transaction log using a 3rd party tool to try to make
sense of it.
Regards,
Paul Ibison
|||2am - and I thought I worked too long hours ;-)
No other ideas really about how else your log got truncated.
I'd check out the transaction log using a 3rd party tool to try to make
sense of it.
Regards,
Paul Ibison
Job error is: sqlmaint.exe failed. [SQLSTATE 42000] (Error 22029). The step failed.
Detailed output of the job says: [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 4305: [Microsoft][ODBC SQL Server Driver][SQL Server]The log in this backup set begins at LSN 31433000001386500001, which is too late to apply to the database. An earlier lo
g backup that includes LSN 314320
00002000300001 can be restored.[Microsoft][ODBC SQL Server Driver][SQL Server]RESTORE LOG is terminating abnormally. (null) [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 4305: [Microsoft][ODBC SQL Server Driver][SQL Server]The log in this backup set be
gins at LSN 31433000001386500001, which is too late to apply to the database. An earlier log backup that includes LSN 31432000002000300001 can be restored. [Microsoft][ODBC SQL Server Driver][SQL Server]RESTORE LOG is terminating abnormally.(null) [Micros
oft SQL-DMO (ODBC SQLState: 42000)] Error 3201: [Microsoft][ODBC SQL Server Driver][SQL Server]Cannot open backup device 'D:\SHIPPEDLOGS\LVBOEProd_tlog_200406272345.TRN'. Device error or device off-line. See the SQL Server error log for more details.[Micr
osoft][ODBC SQL Server Driver][SQL Server]RESTORE LOG is terminating abnormally.(null Loaded 0 files
**All of my shares/directories are correct. I have tried this at least a dozen times. It was successfull the 1st time the restore ran, but after that it has failed every time.
VC,
have a look at your chain of log backups and the log-shipping monitor. See
if you have any logs before 27th June 11:45pm which haven't been transfered
and/or restored. Manually restoring these 'missing' logs then restarting the
logshipping job should fix the problem.
HTH,
Paul Ibison
|||Paul, thank you very much for your reply. this is very important that i get this working ASAP. i have been fighting this day in and day out.
i re-did the log shipping and it's the same problem. do you have an email account that i can email the log to. it has been appending since the 1st restore. you can email me at v_c@.hotmail.com and i'll reply with the log.
there are no files earlier than the 1st file. in fact, this time around, it was successful.
|||VC,
no need to send over the log - it won't help me solve your issue.
I suspect that someone inadvertantly truncated the transaction log before
the first backup and hence the log sequence numbers were out of sync.
Alternatively it could be that the databases themselves were initially out
of sync. You could use LogExplorer (even the evaluation edn) to test if the
former is the case - to see if there are some records missing from the log.
Still, if it's running OK now then fine.
Regards,
Paul Ibison
|||VC,
no need to send over the log - it won't help me solve your issue.
I suspect that someone inadvertantly truncated the transaction log before
the first backup and hence the log sequence numbers were out of sync.
Alternatively it could be that the databases themselves were initially out
of sync. You could use LogExplorer (even the evaluation edn) to test if the
former is the case - to see if there are some records missing from the log.
Still, if it's running OK now then fine.
Regards,
Paul Ibison
|||i was doing this all night, like 2 in the morning. i doubt anyone was truncating logs. however, this is a good suspicion. any other ideas how the log could have gotten truncated?
|||i was doing this all night, like 2 in the morning. i doubt anyone was truncating logs. however, this is a good suspicion. any other ideas how the log could have gotten truncated?
|||2am - and I thought I worked too long hours ;-)
No other ideas really about how else your log got truncated.
I'd check out the transaction log using a 3rd party tool to try to make
sense of it.
Regards,
Paul Ibison
|||2am - and I thought I worked too long hours ;-)
No other ideas really about how else your log got truncated.
I'd check out the transaction log using a 3rd party tool to try to make
sense of it.
Regards,
Paul Ibison
Log Shipping Restore Failed - How do I find out why?
I set up log shipping for a database to fire every 10 mins. All the steps on
both servers work the first two times. On the 3rd 10 min interval, the log
bkp is created on the source server and is copied to the destination server.
However, the SQL Agent step, "Log Shipping Restore for
SERVER.APPDB_logshipping" shows failure. The log bkp files are in the
appropriate destination server folder but the restore does not work any more.
Plus, the event interval on the SQL Agent jobs destination server were
showing every 10 mins but now are showing every 15 mins.
How can I determine what happened and how to fix it?
Picine Karppehd
A newbie to VB.Net,
pretty good with VB6,
Certified with SQLServer
Even I was facing the similar issue. Whenever there was huge tlog backups,
restore job in the destination server used to fail. I increased the re-try
attempts by 1 after 1 minute for copy as well as restore job in the
destination server. And it seems to be running fine since.
To do the above, go to the restore job in your destination server,
properties, step, advanced, retry attempts...
HTH
GYK
"Picine Karppehd" wrote:
> I set up log shipping for a database to fire every 10 mins. All the steps on
> both servers work the first two times. On the 3rd 10 min interval, the log
> bkp is created on the source server and is copied to the destination server.
> However, the SQL Agent step, "Log Shipping Restore for
> SERVER.APPDB_logshipping" shows failure. The log bkp files are in the
> appropriate destination server folder but the restore does not work any more.
> Plus, the event interval on the SQL Agent jobs destination server were
> showing every 10 mins but now are showing every 15 mins.
> How can I determine what happened and how to fix it?
> --
> Picine Karppehd
> A newbie to VB.Net,
> pretty good with VB6,
> Certified with SQLServer
|||Picine,
Try restoring the copied log file yourself using Query Analyzer and if
there's an error, what the message is.
Ron
Ron Talmage
SQL Server MVP
"Picine Karppehd" <PicineKarppehd@.hotmail.com.(donotspam)> wrote in message
news:2618C571-9B99-4365-94EC-B22927DF46B9@.microsoft.com...
> I set up log shipping for a database to fire every 10 mins. All the steps
on
> both servers work the first two times. On the 3rd 10 min interval, the
log
> bkp is created on the source server and is copied to the destination
server.
> However, the SQL Agent step, "Log Shipping Restore for
> SERVER.APPDB_logshipping" shows failure. The log bkp files are in the
> appropriate destination server folder but the restore does not work any
more.
> Plus, the event interval on the SQL Agent jobs destination server were
> showing every 10 mins but now are showing every 15 mins.
> How can I determine what happened and how to fix it?
> --
> Picine Karppehd
> A newbie to VB.Net,
> pretty good with VB6,
> Certified with SQLServer
both servers work the first two times. On the 3rd 10 min interval, the log
bkp is created on the source server and is copied to the destination server.
However, the SQL Agent step, "Log Shipping Restore for
SERVER.APPDB_logshipping" shows failure. The log bkp files are in the
appropriate destination server folder but the restore does not work any more.
Plus, the event interval on the SQL Agent jobs destination server were
showing every 10 mins but now are showing every 15 mins.
How can I determine what happened and how to fix it?
Picine Karppehd
A newbie to VB.Net,
pretty good with VB6,
Certified with SQLServer
Even I was facing the similar issue. Whenever there was huge tlog backups,
restore job in the destination server used to fail. I increased the re-try
attempts by 1 after 1 minute for copy as well as restore job in the
destination server. And it seems to be running fine since.
To do the above, go to the restore job in your destination server,
properties, step, advanced, retry attempts...
HTH
GYK
"Picine Karppehd" wrote:
> I set up log shipping for a database to fire every 10 mins. All the steps on
> both servers work the first two times. On the 3rd 10 min interval, the log
> bkp is created on the source server and is copied to the destination server.
> However, the SQL Agent step, "Log Shipping Restore for
> SERVER.APPDB_logshipping" shows failure. The log bkp files are in the
> appropriate destination server folder but the restore does not work any more.
> Plus, the event interval on the SQL Agent jobs destination server were
> showing every 10 mins but now are showing every 15 mins.
> How can I determine what happened and how to fix it?
> --
> Picine Karppehd
> A newbie to VB.Net,
> pretty good with VB6,
> Certified with SQLServer
|||Picine,
Try restoring the copied log file yourself using Query Analyzer and if
there's an error, what the message is.
Ron
Ron Talmage
SQL Server MVP
"Picine Karppehd" <PicineKarppehd@.hotmail.com.(donotspam)> wrote in message
news:2618C571-9B99-4365-94EC-B22927DF46B9@.microsoft.com...
> I set up log shipping for a database to fire every 10 mins. All the steps
on
> both servers work the first two times. On the 3rd 10 min interval, the
log
> bkp is created on the source server and is copied to the destination
server.
> However, the SQL Agent step, "Log Shipping Restore for
> SERVER.APPDB_logshipping" shows failure. The log bkp files are in the
> appropriate destination server folder but the restore does not work any
more.
> Plus, the event interval on the SQL Agent jobs destination server were
> showing every 10 mins but now are showing every 15 mins.
> How can I determine what happened and how to fix it?
> --
> Picine Karppehd
> A newbie to VB.Net,
> pretty good with VB6,
> Certified with SQLServer
Log Shipping Restore Failed - How do I find out why?
I set up log shipping for a database to fire every 10 mins. All the steps o
n
both servers work the first two times. On the 3rd 10 min interval, the log
bkp is created on the source server and is copied to the destination server.
However, the SQL Agent step, "Log Shipping Restore for
SERVER.APPDB_logshipping" shows failure. The log bkp files are in the
appropriate destination server folder but the restore does not work any more
.
Plus, the event interval on the SQL Agent jobs destination server were
showing every 10 mins but now are showing every 15 mins.
How can I determine what happened and how to fix it?
Picine Karppehd
A newbie to VB.Net,
pretty good with VB6,
Certified with SQLServerEven I was facing the similar issue. Whenever there was huge tlog backups,
restore job in the destination server used to fail. I increased the re-try
attempts by 1 after 1 minute for copy as well as restore job in the
destination server. And it seems to be running fine since.
To do the above, go to the restore job in your destination server,
properties, step, advanced, retry attempts...
HTH
GYK
"Picine Karppehd" wrote:
> I set up log shipping for a database to fire every 10 mins. All the steps
on
> both servers work the first two times. On the 3rd 10 min interval, the lo
g
> bkp is created on the source server and is copied to the destination serve
r.
> However, the SQL Agent step, "Log Shipping Restore for
> SERVER.APPDB_logshipping" shows failure. The log bkp files are in the
> appropriate destination server folder but the restore does not work any mo
re.
> Plus, the event interval on the SQL Agent jobs destination server were
> showing every 10 mins but now are showing every 15 mins.
> How can I determine what happened and how to fix it?
> --
> Picine Karppehd
> A newbie to VB.Net,
> pretty good with VB6,
> Certified with SQLServer|||Picine,
Try restoring the copied log file yourself using Query Analyzer and if
there's an error, what the message is.
Ron
--
Ron Talmage
SQL Server MVP
"Picine Karppehd" <PicineKarppehd@.hotmail.com.(donotspam)> wrote in message
news:2618C571-9B99-4365-94EC-B22927DF46B9@.microsoft.com...
> I set up log shipping for a database to fire every 10 mins. All the steps
on
> both servers work the first two times. On the 3rd 10 min interval, the
log
> bkp is created on the source server and is copied to the destination
server.
> However, the SQL Agent step, "Log Shipping Restore for
> SERVER.APPDB_logshipping" shows failure. The log bkp files are in the
> appropriate destination server folder but the restore does not work any
more.
> Plus, the event interval on the SQL Agent jobs destination server were
> showing every 10 mins but now are showing every 15 mins.
> How can I determine what happened and how to fix it?
> --
> Picine Karppehd
> A newbie to VB.Net,
> pretty good with VB6,
> Certified with SQLServer
n
both servers work the first two times. On the 3rd 10 min interval, the log
bkp is created on the source server and is copied to the destination server.
However, the SQL Agent step, "Log Shipping Restore for
SERVER.APPDB_logshipping" shows failure. The log bkp files are in the
appropriate destination server folder but the restore does not work any more
.
Plus, the event interval on the SQL Agent jobs destination server were
showing every 10 mins but now are showing every 15 mins.
How can I determine what happened and how to fix it?
Picine Karppehd
A newbie to VB.Net,
pretty good with VB6,
Certified with SQLServerEven I was facing the similar issue. Whenever there was huge tlog backups,
restore job in the destination server used to fail. I increased the re-try
attempts by 1 after 1 minute for copy as well as restore job in the
destination server. And it seems to be running fine since.
To do the above, go to the restore job in your destination server,
properties, step, advanced, retry attempts...
HTH
GYK
"Picine Karppehd" wrote:
> I set up log shipping for a database to fire every 10 mins. All the steps
on
> both servers work the first two times. On the 3rd 10 min interval, the lo
g
> bkp is created on the source server and is copied to the destination serve
r.
> However, the SQL Agent step, "Log Shipping Restore for
> SERVER.APPDB_logshipping" shows failure. The log bkp files are in the
> appropriate destination server folder but the restore does not work any mo
re.
> Plus, the event interval on the SQL Agent jobs destination server were
> showing every 10 mins but now are showing every 15 mins.
> How can I determine what happened and how to fix it?
> --
> Picine Karppehd
> A newbie to VB.Net,
> pretty good with VB6,
> Certified with SQLServer|||Picine,
Try restoring the copied log file yourself using Query Analyzer and if
there's an error, what the message is.
Ron
--
Ron Talmage
SQL Server MVP
"Picine Karppehd" <PicineKarppehd@.hotmail.com.(donotspam)> wrote in message
news:2618C571-9B99-4365-94EC-B22927DF46B9@.microsoft.com...
> I set up log shipping for a database to fire every 10 mins. All the steps
on
> both servers work the first two times. On the 3rd 10 min interval, the
log
> bkp is created on the source server and is copied to the destination
server.
> However, the SQL Agent step, "Log Shipping Restore for
> SERVER.APPDB_logshipping" shows failure. The log bkp files are in the
> appropriate destination server folder but the restore does not work any
more.
> Plus, the event interval on the SQL Agent jobs destination server were
> showing every 10 mins but now are showing every 15 mins.
> How can I determine what happened and how to fix it?
> --
> Picine Karppehd
> A newbie to VB.Net,
> pretty good with VB6,
> Certified with SQLServer
Log Shipping Restore Failed - How do I find out why?
I set up log shipping for a database to fire every 10 mins. All the steps on
both servers work the first two times. On the 3rd 10 min interval, the log
bkp is created on the source server and is copied to the destination server.
However, the SQL Agent step, "Log Shipping Restore for
SERVER.APPDB_logshipping" shows failure. The log bkp files are in the
appropriate destination server folder but the restore does not work any more.
Plus, the event interval on the SQL Agent jobs destination server were
showing every 10 mins but now are showing every 15 mins.
How can I determine what happened and how to fix it?
--
Picine Karppehd
A newbie to VB.Net,
pretty good with VB6,
Certified with SQLServerEven I was facing the similar issue. Whenever there was huge tlog backups,
restore job in the destination server used to fail. I increased the re-try
attempts by 1 after 1 minute for copy as well as restore job in the
destination server. And it seems to be running fine since.
To do the above, go to the restore job in your destination server,
properties, step, advanced, retry attempts...
HTH
GYK
"Picine Karppehd" wrote:
> I set up log shipping for a database to fire every 10 mins. All the steps on
> both servers work the first two times. On the 3rd 10 min interval, the log
> bkp is created on the source server and is copied to the destination server.
> However, the SQL Agent step, "Log Shipping Restore for
> SERVER.APPDB_logshipping" shows failure. The log bkp files are in the
> appropriate destination server folder but the restore does not work any more.
> Plus, the event interval on the SQL Agent jobs destination server were
> showing every 10 mins but now are showing every 15 mins.
> How can I determine what happened and how to fix it?
> --
> Picine Karppehd
> A newbie to VB.Net,
> pretty good with VB6,
> Certified with SQLServer|||Picine,
Try restoring the copied log file yourself using Query Analyzer and if
there's an error, what the message is.
Ron
--
Ron Talmage
SQL Server MVP
"Picine Karppehd" <PicineKarppehd@.hotmail.com.(donotspam)> wrote in message
news:2618C571-9B99-4365-94EC-B22927DF46B9@.microsoft.com...
> I set up log shipping for a database to fire every 10 mins. All the steps
on
> both servers work the first two times. On the 3rd 10 min interval, the
log
> bkp is created on the source server and is copied to the destination
server.
> However, the SQL Agent step, "Log Shipping Restore for
> SERVER.APPDB_logshipping" shows failure. The log bkp files are in the
> appropriate destination server folder but the restore does not work any
more.
> Plus, the event interval on the SQL Agent jobs destination server were
> showing every 10 mins but now are showing every 15 mins.
> How can I determine what happened and how to fix it?
> --
> Picine Karppehd
> A newbie to VB.Net,
> pretty good with VB6,
> Certified with SQLServer
both servers work the first two times. On the 3rd 10 min interval, the log
bkp is created on the source server and is copied to the destination server.
However, the SQL Agent step, "Log Shipping Restore for
SERVER.APPDB_logshipping" shows failure. The log bkp files are in the
appropriate destination server folder but the restore does not work any more.
Plus, the event interval on the SQL Agent jobs destination server were
showing every 10 mins but now are showing every 15 mins.
How can I determine what happened and how to fix it?
--
Picine Karppehd
A newbie to VB.Net,
pretty good with VB6,
Certified with SQLServerEven I was facing the similar issue. Whenever there was huge tlog backups,
restore job in the destination server used to fail. I increased the re-try
attempts by 1 after 1 minute for copy as well as restore job in the
destination server. And it seems to be running fine since.
To do the above, go to the restore job in your destination server,
properties, step, advanced, retry attempts...
HTH
GYK
"Picine Karppehd" wrote:
> I set up log shipping for a database to fire every 10 mins. All the steps on
> both servers work the first two times. On the 3rd 10 min interval, the log
> bkp is created on the source server and is copied to the destination server.
> However, the SQL Agent step, "Log Shipping Restore for
> SERVER.APPDB_logshipping" shows failure. The log bkp files are in the
> appropriate destination server folder but the restore does not work any more.
> Plus, the event interval on the SQL Agent jobs destination server were
> showing every 10 mins but now are showing every 15 mins.
> How can I determine what happened and how to fix it?
> --
> Picine Karppehd
> A newbie to VB.Net,
> pretty good with VB6,
> Certified with SQLServer|||Picine,
Try restoring the copied log file yourself using Query Analyzer and if
there's an error, what the message is.
Ron
--
Ron Talmage
SQL Server MVP
"Picine Karppehd" <PicineKarppehd@.hotmail.com.(donotspam)> wrote in message
news:2618C571-9B99-4365-94EC-B22927DF46B9@.microsoft.com...
> I set up log shipping for a database to fire every 10 mins. All the steps
on
> both servers work the first two times. On the 3rd 10 min interval, the
log
> bkp is created on the source server and is copied to the destination
server.
> However, the SQL Agent step, "Log Shipping Restore for
> SERVER.APPDB_logshipping" shows failure. The log bkp files are in the
> appropriate destination server folder but the restore does not work any
more.
> Plus, the event interval on the SQL Agent jobs destination server were
> showing every 10 mins but now are showing every 15 mins.
> How can I determine what happened and how to fix it?
> --
> Picine Karppehd
> A newbie to VB.Net,
> pretty good with VB6,
> Certified with SQLServer
Wednesday, March 21, 2012
log shipping not working
hello, on the destination server he says the restore job has failed
and my log shipping databases are then out of sync. where do i begin
to find out why my log shipping is no longer working? my two servers
are in differnet locations but i can ping and returns are under 50ms.
help?
thanks
APAP
Is it one log it has failed to apply or several? Sometimes
one log may fail to apply for a number of reasons. Next
time the target server tries to apply the logs it should
try to apply all logs since it last applied one. Quite
often it can catch up.
One common reason for log shipping failure is having the
restore on the target run too soon after the backup on the
source. Occasionally the restore tries to run before the
backup finishes. This may be because a big work load on
the source has caused a larger than normal log. It may be
the servers have got out of sync time wise.
Hope this helps
John|||thanks you john, it looks to me that the log shipping has never worked
since the backup was restored in the destincation server. these is a
small database like 63 mb so backup times is quick. each site has a
t1 or faster.
how do i get them back to sync?
AP
"John Bandettini" <anonymous@.discussions.microsoft.com> wrote in message news:<0ec801c3aa02$82d32cc0$a401280a@.phx.gbl>...
> AP
> Is it one log it has failed to apply or several? Sometimes
> one log may fail to apply for a number of reasons. Next
> time the target server tries to apply the logs it should
> try to apply all logs since it last applied one. Quite
> often it can catch up.
> One common reason for log shipping failure is having the
> restore on the target run too soon after the backup on the
> source. Occasionally the restore tries to run before the
> backup finishes. This may be because a big work load on
> the source has caused a larger than normal log. It may be
> the servers have got out of sync time wise.
> Hope this helps
> John|||Antonio
You will need to copy a recent full backup to your standby
server, to re-establish the log shipping.
I don't have a copy of Enterprise edition that I can look
at at the moment to see exactly how you do it. There
should be an option somewhere to re-establish it.
The fact that it has never worked suggests there is a
problem anyway. Permissions on the share on the target
server is quite a common problem. Use 'xp_cmdshell' on
your source database to check the permissions work. (Do
a 'dir' on it).
Also worth having a look at this link.
http://support.microsoft.com/default.aspx?scid=kb;en-
us;323135
Hope this helps
John|||thank you again. i did check permissions. i see on teh source and
destination server where the transaction logs are that all are on both
servers so i see this to mean that the logs are baccking up on the
source server good and they are being transmisssion to the destination
server good. it looks to me that the logs are shipping ok but not
being replayed on the destination server.
this probably changes your recommentations.
what do you think about it now?
thanks
AP
"John Bandettini" <anonymous@.discussions.microsoft.com> wrote in message news:<0adc01c3aac4$4e192ad0$a501280a@.phx.gbl>...
> Antonio
> You will need to copy a recent full backup to your standby
> server, to re-establish the log shipping.
> I don't have a copy of Enterprise edition that I can look
> at at the moment to see exactly how you do it. There
> should be an option somewhere to re-establish it.
> The fact that it has never worked suggests there is a
> problem anyway. Permissions on the share on the target
> server is quite a common problem. Use 'xp_cmdshell' on
> your source database to check the permissions work. (Do
> a 'dir' on it).
> Also worth having a look at this link.
> http://support.microsoft.com/default.aspx?scid=kb;en-
> us;323135
> Hope this helps
> John|||Antonio
Last thing I can think of suggesting is to try running the
SQL Server agent as a local domain account with the same
name and password on both servers.
I have seen this work.
Regards
John
and my log shipping databases are then out of sync. where do i begin
to find out why my log shipping is no longer working? my two servers
are in differnet locations but i can ping and returns are under 50ms.
help?
thanks
APAP
Is it one log it has failed to apply or several? Sometimes
one log may fail to apply for a number of reasons. Next
time the target server tries to apply the logs it should
try to apply all logs since it last applied one. Quite
often it can catch up.
One common reason for log shipping failure is having the
restore on the target run too soon after the backup on the
source. Occasionally the restore tries to run before the
backup finishes. This may be because a big work load on
the source has caused a larger than normal log. It may be
the servers have got out of sync time wise.
Hope this helps
John|||thanks you john, it looks to me that the log shipping has never worked
since the backup was restored in the destincation server. these is a
small database like 63 mb so backup times is quick. each site has a
t1 or faster.
how do i get them back to sync?
AP
"John Bandettini" <anonymous@.discussions.microsoft.com> wrote in message news:<0ec801c3aa02$82d32cc0$a401280a@.phx.gbl>...
> AP
> Is it one log it has failed to apply or several? Sometimes
> one log may fail to apply for a number of reasons. Next
> time the target server tries to apply the logs it should
> try to apply all logs since it last applied one. Quite
> often it can catch up.
> One common reason for log shipping failure is having the
> restore on the target run too soon after the backup on the
> source. Occasionally the restore tries to run before the
> backup finishes. This may be because a big work load on
> the source has caused a larger than normal log. It may be
> the servers have got out of sync time wise.
> Hope this helps
> John|||Antonio
You will need to copy a recent full backup to your standby
server, to re-establish the log shipping.
I don't have a copy of Enterprise edition that I can look
at at the moment to see exactly how you do it. There
should be an option somewhere to re-establish it.
The fact that it has never worked suggests there is a
problem anyway. Permissions on the share on the target
server is quite a common problem. Use 'xp_cmdshell' on
your source database to check the permissions work. (Do
a 'dir' on it).
Also worth having a look at this link.
http://support.microsoft.com/default.aspx?scid=kb;en-
us;323135
Hope this helps
John|||thank you again. i did check permissions. i see on teh source and
destination server where the transaction logs are that all are on both
servers so i see this to mean that the logs are baccking up on the
source server good and they are being transmisssion to the destination
server good. it looks to me that the logs are shipping ok but not
being replayed on the destination server.
this probably changes your recommentations.
what do you think about it now?
thanks
AP
"John Bandettini" <anonymous@.discussions.microsoft.com> wrote in message news:<0adc01c3aac4$4e192ad0$a501280a@.phx.gbl>...
> Antonio
> You will need to copy a recent full backup to your standby
> server, to re-establish the log shipping.
> I don't have a copy of Enterprise edition that I can look
> at at the moment to see exactly how you do it. There
> should be an option somewhere to re-establish it.
> The fact that it has never worked suggests there is a
> problem anyway. Permissions on the share on the target
> server is quite a common problem. Use 'xp_cmdshell' on
> your source database to check the permissions work. (Do
> a 'dir' on it).
> Also worth having a look at this link.
> http://support.microsoft.com/default.aspx?scid=kb;en-
> us;323135
> Hope this helps
> John|||Antonio
Last thing I can think of suggesting is to try running the
SQL Server agent as a local domain account with the same
name and password on both servers.
I have seen this work.
Regards
John
Monday, March 19, 2012
log shipping in sql server 2000
hi,
i have log shipping between 2 servers on sql server 2000. the log shipping failed because of some problem with transaction log backup files. somehow the files are missing and it is not able to apply transaction log. can someone please tell me how can i restore the log shipping between 2 servers. please help asap..need to fix it in couple hours
Refer the below link as i've answered
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=2159478&SiteID=1&mode=1
Thanxx
Deepak
|||
thanx it works fine now
|||Glad to hear that its working fine now pls revert if you need further assistance !Thanxx
Deepak
log shipping in sql server 2000
hi,
i have log shipping between 2 servers on sql server 2000. the log shipping failed because of some problem with transaction log backup files. somehow the files are missing and it is not able to apply transaction log. can someone please tell me how can i restore the log shipping between 2 servers. please help asap..need to fix it in couple hours
Refer the below link as i've answeredhttp://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=2159478&SiteID=1&mode=1
Thanxx
Deepak
|||
thanx it works fine now
|||Glad to hear that its working fine now pls revert if you need further assistance !Thanxx
Deepak
Friday, February 24, 2012
Log shipping alerts
the "Log Shipping alert job-restore" job keeps showing a status of "failed" ,
however the databases are in sync. and yes I do have sp3;
mrdj - are there any entries in the system error log files that may point to
something?
"mrdj" <mrdj@.discussions.microsoft.com> wrote in message
news:E3C18911-0003-48AE-8E93-9D97A4B3C25C@.microsoft.com...
> the "Log Shipping alert job-restore" job keeps showing a status of
"failed" ,
> however the databases are in sync. and yes I do have sp3;
|||The only message is it states that the database is out of sync by XXX
minutes, which again does not make sense because as I run queries the
databases are in sync.
"JD" wrote:
> mrdj - are there any entries in the system error log files that may point to
> something?
>
> "mrdj" <mrdj@.discussions.microsoft.com> wrote in message
> news:E3C18911-0003-48AE-8E93-9D97A4B3C25C@.microsoft.com...
> "failed" ,
>
>
|||another interesting thing is that when i look in the Log Shipping Monitor
properties, although it shows the last backup file to be accurate, but for
the last file copied (and the last file loaded) it shows
"first_file_0000000000.trn" and the copy/load deltas show the same number of
minutes that the alert job claims to be out of sync.
"JD" wrote:
> mrdj - are there any entries in the system error log files that may point to
> something?
>
> "mrdj" <mrdj@.discussions.microsoft.com> wrote in message
> news:E3C18911-0003-48AE-8E93-9D97A4B3C25C@.microsoft.com...
> "failed" ,
>
>
however the databases are in sync. and yes I do have sp3;
mrdj - are there any entries in the system error log files that may point to
something?
"mrdj" <mrdj@.discussions.microsoft.com> wrote in message
news:E3C18911-0003-48AE-8E93-9D97A4B3C25C@.microsoft.com...
> the "Log Shipping alert job-restore" job keeps showing a status of
"failed" ,
> however the databases are in sync. and yes I do have sp3;
|||The only message is it states that the database is out of sync by XXX
minutes, which again does not make sense because as I run queries the
databases are in sync.
"JD" wrote:
> mrdj - are there any entries in the system error log files that may point to
> something?
>
> "mrdj" <mrdj@.discussions.microsoft.com> wrote in message
> news:E3C18911-0003-48AE-8E93-9D97A4B3C25C@.microsoft.com...
> "failed" ,
>
>
|||another interesting thing is that when i look in the Log Shipping Monitor
properties, although it shows the last backup file to be accurate, but for
the last file copied (and the last file loaded) it shows
"first_file_0000000000.trn" and the copy/load deltas show the same number of
minutes that the alert job claims to be out of sync.
"JD" wrote:
> mrdj - are there any entries in the system error log files that may point to
> something?
>
> "mrdj" <mrdj@.discussions.microsoft.com> wrote in message
> news:E3C18911-0003-48AE-8E93-9D97A4B3C25C@.microsoft.com...
> "failed" ,
>
>
Log shipping alerts
the "Log Shipping alert job-restore" job keeps showing a status of "failed" ,
however the databases are in sync.
NEVER MIND!! I just read knowledge base...DUH!! I forgot to upgrade to sp3
when i set up my testing environment.
"mrdj" wrote:
> the "Log Shipping alert job-restore" job keeps showing a status of "failed" ,
> however the databases are in sync.
however the databases are in sync.
NEVER MIND!! I just read knowledge base...DUH!! I forgot to upgrade to sp3
when i set up my testing environment.
"mrdj" wrote:
> the "Log Shipping alert job-restore" job keeps showing a status of "failed" ,
> however the databases are in sync.
Log shipping alerts
the "Log Shipping alert job-restore" job keeps showing a status of "failed"
,
however the databases are in sync. and yes I do have sp3;mrdj - are there any entries in the system error log files that may point to
something?
"mrdj" <mrdj@.discussions.microsoft.com> wrote in message
news:E3C18911-0003-48AE-8E93-9D97A4B3C25C@.microsoft.com...
> the "Log Shipping alert job-restore" job keeps showing a status of
"failed" ,
> however the databases are in sync. and yes I do have sp3;|||The only message is it states that the database is out of sync by XXX
minutes, which again does not make sense because as I run queries the
databases are in sync.
"JD" wrote:
> mrdj - are there any entries in the system error log files that may point
to
> something?
>
> "mrdj" <mrdj@.discussions.microsoft.com> wrote in message
> news:E3C18911-0003-48AE-8E93-9D97A4B3C25C@.microsoft.com...
> "failed" ,
>
>|||another interesting thing is that when i look in the Log Shipping Monitor
properties, although it shows the last backup file to be accurate, but for
the last file copied (and the last file loaded) it shows
"first_file_0000000000.trn" and the copy/load deltas show the same number of
minutes that the alert job claims to be out of sync.
"JD" wrote:
> mrdj - are there any entries in the system error log files that may point
to
> something?
>
> "mrdj" <mrdj@.discussions.microsoft.com> wrote in message
> news:E3C18911-0003-48AE-8E93-9D97A4B3C25C@.microsoft.com...
> "failed" ,
>
>
,
however the databases are in sync. and yes I do have sp3;mrdj - are there any entries in the system error log files that may point to
something?
"mrdj" <mrdj@.discussions.microsoft.com> wrote in message
news:E3C18911-0003-48AE-8E93-9D97A4B3C25C@.microsoft.com...
> the "Log Shipping alert job-restore" job keeps showing a status of
"failed" ,
> however the databases are in sync. and yes I do have sp3;|||The only message is it states that the database is out of sync by XXX
minutes, which again does not make sense because as I run queries the
databases are in sync.
"JD" wrote:
> mrdj - are there any entries in the system error log files that may point
to
> something?
>
> "mrdj" <mrdj@.discussions.microsoft.com> wrote in message
> news:E3C18911-0003-48AE-8E93-9D97A4B3C25C@.microsoft.com...
> "failed" ,
>
>|||another interesting thing is that when i look in the Log Shipping Monitor
properties, although it shows the last backup file to be accurate, but for
the last file copied (and the last file loaded) it shows
"first_file_0000000000.trn" and the copy/load deltas show the same number of
minutes that the alert job claims to be out of sync.
"JD" wrote:
> mrdj - are there any entries in the system error log files that may point
to
> something?
>
> "mrdj" <mrdj@.discussions.microsoft.com> wrote in message
> news:E3C18911-0003-48AE-8E93-9D97A4B3C25C@.microsoft.com...
> "failed" ,
>
>
Log shipping alerts
the "Log Shipping alert job-restore" job keeps showing a status of "failed"
,
however the databases are in sync.NEVER MIND!! I just read knowledge base...DUH!! I forgot to upgrade to sp3
when i set up my testing environment.
"mrdj" wrote:
> the "Log Shipping alert job-restore" job keeps showing a status of "failed
" ,
> however the databases are in sync.
,
however the databases are in sync.NEVER MIND!! I just read knowledge base...DUH!! I forgot to upgrade to sp3
when i set up my testing environment.
"mrdj" wrote:
> the "Log Shipping alert job-restore" job keeps showing a status of "failed
" ,
> however the databases are in sync.
Log shipping alerts
the "Log Shipping alert job-restore" job keeps showing a status of "failed" ,
however the databases are in sync.NEVER MIND!! I just read knowledge base...DUH!! I forgot to upgrade to sp3
when i set up my testing environment.
"mrdj" wrote:
> the "Log Shipping alert job-restore" job keeps showing a status of "failed" ,
> however the databases are in sync.
however the databases are in sync.NEVER MIND!! I just read knowledge base...DUH!! I forgot to upgrade to sp3
when i set up my testing environment.
"mrdj" wrote:
> the "Log Shipping alert job-restore" job keeps showing a status of "failed" ,
> however the databases are in sync.
Log shipping alerts
the "Log Shipping alert job-restore" job keeps showing a status of "failed" ,
however the databases are in sync. and yes I do have sp3;mrdj - are there any entries in the system error log files that may point to
something?
"mrdj" <mrdj@.discussions.microsoft.com> wrote in message
news:E3C18911-0003-48AE-8E93-9D97A4B3C25C@.microsoft.com...
> the "Log Shipping alert job-restore" job keeps showing a status of
"failed" ,
> however the databases are in sync. and yes I do have sp3;|||The only message is it states that the database is out of sync by XXX
minutes, which again does not make sense because as I run queries the
databases are in sync.
"JD" wrote:
> mrdj - are there any entries in the system error log files that may point to
> something?
>
> "mrdj" <mrdj@.discussions.microsoft.com> wrote in message
> news:E3C18911-0003-48AE-8E93-9D97A4B3C25C@.microsoft.com...
> > the "Log Shipping alert job-restore" job keeps showing a status of
> "failed" ,
> > however the databases are in sync. and yes I do have sp3;
>
>|||another interesting thing is that when i look in the Log Shipping Monitor
properties, although it shows the last backup file to be accurate, but for
the last file copied (and the last file loaded) it shows
"first_file_0000000000.trn" and the copy/load deltas show the same number of
minutes that the alert job claims to be out of sync.
"JD" wrote:
> mrdj - are there any entries in the system error log files that may point to
> something?
>
> "mrdj" <mrdj@.discussions.microsoft.com> wrote in message
> news:E3C18911-0003-48AE-8E93-9D97A4B3C25C@.microsoft.com...
> > the "Log Shipping alert job-restore" job keeps showing a status of
> "failed" ,
> > however the databases are in sync. and yes I do have sp3;
>
>
however the databases are in sync. and yes I do have sp3;mrdj - are there any entries in the system error log files that may point to
something?
"mrdj" <mrdj@.discussions.microsoft.com> wrote in message
news:E3C18911-0003-48AE-8E93-9D97A4B3C25C@.microsoft.com...
> the "Log Shipping alert job-restore" job keeps showing a status of
"failed" ,
> however the databases are in sync. and yes I do have sp3;|||The only message is it states that the database is out of sync by XXX
minutes, which again does not make sense because as I run queries the
databases are in sync.
"JD" wrote:
> mrdj - are there any entries in the system error log files that may point to
> something?
>
> "mrdj" <mrdj@.discussions.microsoft.com> wrote in message
> news:E3C18911-0003-48AE-8E93-9D97A4B3C25C@.microsoft.com...
> > the "Log Shipping alert job-restore" job keeps showing a status of
> "failed" ,
> > however the databases are in sync. and yes I do have sp3;
>
>|||another interesting thing is that when i look in the Log Shipping Monitor
properties, although it shows the last backup file to be accurate, but for
the last file copied (and the last file loaded) it shows
"first_file_0000000000.trn" and the copy/load deltas show the same number of
minutes that the alert job claims to be out of sync.
"JD" wrote:
> mrdj - are there any entries in the system error log files that may point to
> something?
>
> "mrdj" <mrdj@.discussions.microsoft.com> wrote in message
> news:E3C18911-0003-48AE-8E93-9D97A4B3C25C@.microsoft.com...
> > the "Log Shipping alert job-restore" job keeps showing a status of
> "failed" ,
> > however the databases are in sync. and yes I do have sp3;
>
>
Subscribe to:
Posts (Atom)