We are testing the canned log shipping built into sqlserver2k ent. Somehow,
the monitor db that tracks what has been backed-up, shipped, etc is out of
sync. The primary and secondary DBs are synced up and the shipping is
working fine but the monitor doesnt seem to know that. We suspect we know
what happened (sqlAgent was stopped when log shipping was started) but this
raises a bigger question.
If the monitor db should get out of sync (say, for example, it is stopped
for some time), how to we resync it? Conceptually, we want to tell it that
the primary and secondary are in sync (which we can separately verify). Any
ideas? Is this even the right news group?
-alanNever mind. It was an NT domain security issue. We just needed to make the
userName match for all the services (sqlserver and agent) on all the
machines.
"Alan Berezin" <aberezin@.drillinginfo.com> wrote in message
news:eEjNKJkRDHA.1924@.TK2MSFTNGP12.phx.gbl...
> We are testing the canned log shipping built into sqlserver2k ent.
Somehow,
> the monitor db that tracks what has been backed-up, shipped, etc is out of
> sync. The primary and secondary DBs are synced up and the shipping is
> working fine but the monitor doesnt seem to know that. We suspect we know
> what happened (sqlAgent was stopped when log shipping was started) but
this
> raises a bigger question.
> If the monitor db should get out of sync (say, for example, it is stopped
> for some time), how to we resync it? Conceptually, we want to tell it
that
> the primary and secondary are in sync (which we can separately verify).
Any
> ideas? Is this even the right news group?
> -alan
>sql
Showing posts with label monitor. Show all posts
Showing posts with label monitor. Show all posts
Friday, March 30, 2012
Wednesday, March 21, 2012
Log Shipping out of sync
Hi everyone,
We have set up a log shipping between two SQL 2000 servers with a monitor
server as well.
The problem is that I've been on holidays, and the people that should check
the databases didn't do it. The result is that the log shipping has been out
ot sync since 18th april till now.
We get the following error:
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3242: [Microsoft][ODBC SQL
Server Driver][SQL Server]The file on device
'C:\xx\LogShipIN\TRNs\xx_tlog_200704180300.TRN' is not a valid Microsoft Tape
Format backup set.
[Microsoft][ODBC SQL Server Driver][SQL Server]RESTORE LOG is terminating
abnormally.
I've check the file and already exist in backup server, but it seems it
wasn't copied correctly. Because it's a lot of days since the file fail to
restore (it's from 18 th april), we don't have it on production server (we
have only from 2 days ago).
Does anybody knows how could I re-sync the log shipping on backup server
again?
Thansk a lot,
Alex.You need to recreate the Log Shipping Maintenance plan for the desired
database.
In order to deleted the current plan, you'll need to remove LS from the plan
first.
If the latest full db backup that you have was created after the error
occurred and you still have all of the log (and/or differential) backups
since the latest db backup then you can use these files to reinitialize db on
the secondary server instead of having to take a full backup of the db. This
would allow you to set up log shipping without having to impact performance
on your primary db.
check out these articles
http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/logship1.mspx
http://www.microsoft.com/technet/prodtechnol/sql/2000/reskit/part4/c1361.mspx?mfr=true
MG
"Alex Delgado" wrote:
> Hi everyone,
> We have set up a log shipping between two SQL 2000 servers with a monitor
> server as well.
> The problem is that I've been on holidays, and the people that should check
> the databases didn't do it. The result is that the log shipping has been out
> ot sync since 18th april till now.
> We get the following error:
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3242: [Microsoft][ODBC SQL
> Server Driver][SQL Server]The file on device
> 'C:\xx\LogShipIN\TRNs\xx_tlog_200704180300.TRN' is not a valid Microsoft Tape
> Format backup set.
> [Microsoft][ODBC SQL Server Driver][SQL Server]RESTORE LOG is terminating
> abnormally.
> I've check the file and already exist in backup server, but it seems it
> wasn't copied correctly. Because it's a lot of days since the file fail to
> restore (it's from 18 th april), we don't have it on production server (we
> have only from 2 days ago).
> Does anybody knows how could I re-sync the log shipping on backup server
> again?
> Thansk a lot,
> Alex.|||Hi Hurme,
Thanks a lot for your help.
I still have a doubt.
When you say:
" If the latest full db backup that you have was created after the error
occurred and you still have all of the log (and/or differential) backups
since the latest db backup then you can use these files to reinitialize db on
the secondary server instead of having to take a full backup of the db. This
would allow you to set up log shipping without having to impact performance
on your primary db. "
I have full db backup created after the error that we can restore on
secondary server. About the log backups, I understand you mean the trn files
that log shipping copies to secondary server and that it tries to restore,
don't you? If so, then my answer is yes, I also have them.
Should I run the restore with the following parameter: restore
"Hurme" wrote:
> You need to recreate the Log Shipping Maintenance plan for the desired
> database.
> In order to deleted the current plan, you'll need to remove LS from the plan
> first.
> If the latest full db backup that you have was created after the error
> occurred and you still have all of the log (and/or differential) backups
> since the latest db backup then you can use these files to reinitialize db on
> the secondary server instead of having to take a full backup of the db. This
> would allow you to set up log shipping without having to impact performance
> on your primary db.
> check out these articles
> http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/logship1.mspx
> http://www.microsoft.com/technet/prodtechnol/sql/2000/reskit/part4/c1361.mspx?mfr=true
>
> --
> MG
>
> "Alex Delgado" wrote:
> > Hi everyone,
> >
> > We have set up a log shipping between two SQL 2000 servers with a monitor
> > server as well.
> >
> > The problem is that I've been on holidays, and the people that should check
> > the databases didn't do it. The result is that the log shipping has been out
> > ot sync since 18th april till now.
> >
> > We get the following error:
> >
> > [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3242: [Microsoft][ODBC SQL
> > Server Driver][SQL Server]The file on device
> > 'C:\xx\LogShipIN\TRNs\xx_tlog_200704180300.TRN' is not a valid Microsoft Tape
> > Format backup set.
> > [Microsoft][ODBC SQL Server Driver][SQL Server]RESTORE LOG is terminating
> > abnormally.
> >
> > I've check the file and already exist in backup server, but it seems it
> > wasn't copied correctly. Because it's a lot of days since the file fail to
> > restore (it's from 18 th april), we don't have it on production server (we
> > have only from 2 days ago).
> >
> > Does anybody knows how could I re-sync the log shipping on backup server
> > again?
> >
> > Thansk a lot,
> >
> > Alex.|||Hi Hurme,
Thanks a lot for your help.
I still have a doubt.
When you say:
" If the latest full db backup that you have was created after the error
occurred and you still have all of the log (and/or differential) backups
since the latest db backup then you can use these files to reinitialize db on
the secondary server instead of having to take a full backup of the db. This
would allow you to set up log shipping without having to impact performance
on your primary db. "
I have full db backup created after the error that we can restore on
secondary server. About the log backups, I understand you mean the trn files
that log shipping copies to secondary server and that it tries to restore,
don't you? If so, then my answer is yes, I also have them.
Should I run the restore with the following parameter: restore with standby'
How should be the exact command to restore?
Thanks again,
Alex.
"Hurme" wrote:
> You need to recreate the Log Shipping Maintenance plan for the desired
> database.
> In order to deleted the current plan, you'll need to remove LS from the plan
> first.
> If the latest full db backup that you have was created after the error
> occurred and you still have all of the log (and/or differential) backups
> since the latest db backup then you can use these files to reinitialize db on
> the secondary server instead of having to take a full backup of the db. This
> would allow you to set up log shipping without having to impact performance
> on your primary db.
> check out these articles
> http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/logship1.mspx
> http://www.microsoft.com/technet/prodtechnol/sql/2000/reskit/part4/c1361.mspx?mfr=true
>
> --
> MG
>
> "Alex Delgado" wrote:
> > Hi everyone,
> >
> > We have set up a log shipping between two SQL 2000 servers with a monitor
> > server as well.
> >
> > The problem is that I've been on holidays, and the people that should check
> > the databases didn't do it. The result is that the log shipping has been out
> > ot sync since 18th april till now.
> >
> > We get the following error:
> >
> > [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3242: [Microsoft][ODBC SQL
> > Server Driver][SQL Server]The file on device
> > 'C:\xx\LogShipIN\TRNs\xx_tlog_200704180300.TRN' is not a valid Microsoft Tape
> > Format backup set.
> > [Microsoft][ODBC SQL Server Driver][SQL Server]RESTORE LOG is terminating
> > abnormally.
> >
> > I've check the file and already exist in backup server, but it seems it
> > wasn't copied correctly. Because it's a lot of days since the file fail to
> > restore (it's from 18 th april), we don't have it on production server (we
> > have only from 2 days ago).
> >
> > Does anybody knows how could I re-sync the log shipping on backup server
> > again?
> >
> > Thansk a lot,
> >
> > Alex.|||Yes, by log I meant the .trn files.
If you don't use standby, the backup database will be left offline and not
readable so that successive .trn (backup log) files can be restored.
If you restore with standby the backup db will be accessable in Read-Only
mode and still be able to have successive .trn files restored to it. The only
issue with this is that exclussive access to the db is still need to restore
a .trn so if some one is accessing the db they need to be kicked out of the
db before a restore can happen.
The restore with standby command should look like:
restore database <db_name>
from disk = 'c:\<backup>.BAK'
with standby = <undo_file_name>
likewise for .trn files
restore log <db_name>
from disk = 'c:\<log_backup>.trn'
with standby = <undo_file_name>
If you're not using it, try using Enterprise Manager to set up Log Shipping.
--
MG
"Alex Delgado" wrote:
> Hi Hurme,
> Thanks a lot for your help.
> I still have a doubt.
> When you say:
> " If the latest full db backup that you have was created after the error
> occurred and you still have all of the log (and/or differential) backups
> since the latest db backup then you can use these files to reinitialize db on
> the secondary server instead of having to take a full backup of the db. This
> would allow you to set up log shipping without having to impact performance
> on your primary db. "
> I have full db backup created after the error that we can restore on
> secondary server. About the log backups, I understand you mean the trn files
> that log shipping copies to secondary server and that it tries to restore,
> don't you? If so, then my answer is yes, I also have them.
> Should I run the restore with the following parameter: restore with standby'
> How should be the exact command to restore?
> Thanks again,
> Alex.
>
> "Hurme" wrote:
> > You need to recreate the Log Shipping Maintenance plan for the desired
> > database.
> > In order to deleted the current plan, you'll need to remove LS from the plan
> > first.
> >
> > If the latest full db backup that you have was created after the error
> > occurred and you still have all of the log (and/or differential) backups
> > since the latest db backup then you can use these files to reinitialize db on
> > the secondary server instead of having to take a full backup of the db. This
> > would allow you to set up log shipping without having to impact performance
> > on your primary db.
> >
> > check out these articles
> > http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/logship1.mspx
> >
> > http://www.microsoft.com/technet/prodtechnol/sql/2000/reskit/part4/c1361.mspx?mfr=true
> >
> >
> > --
> > MG
> >
> >
> > "Alex Delgado" wrote:
> >
> > > Hi everyone,
> > >
> > > We have set up a log shipping between two SQL 2000 servers with a monitor
> > > server as well.
> > >
> > > The problem is that I've been on holidays, and the people that should check
> > > the databases didn't do it. The result is that the log shipping has been out
> > > ot sync since 18th april till now.
> > >
> > > We get the following error:
> > >
> > > [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3242: [Microsoft][ODBC SQL
> > > Server Driver][SQL Server]The file on device
> > > 'C:\xx\LogShipIN\TRNs\xx_tlog_200704180300.TRN' is not a valid Microsoft Tape
> > > Format backup set.
> > > [Microsoft][ODBC SQL Server Driver][SQL Server]RESTORE LOG is terminating
> > > abnormally.
> > >
> > > I've check the file and already exist in backup server, but it seems it
> > > wasn't copied correctly. Because it's a lot of days since the file fail to
> > > restore (it's from 18 th april), we don't have it on production server (we
> > > have only from 2 days ago).
> > >
> > > Does anybody knows how could I re-sync the log shipping on backup server
> > > again?
> > >
> > > Thansk a lot,
> > >
> > > Alex.|||On Apr 24, 1:50 pm, Alex Delgado
<AlexDelg...@.discussions.microsoft.com> wrote:
> Hi everyone,
> We have set up a log shipping between two SQL 2000 servers with a monitor
> server as well.
> The problem is that I've been on holidays, and the people that should check
> the databases didn't do it. The result is that the log shipping has been out
> ot sync since 18th april till now.
> We get the following error:
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3242: [Microsoft][ODBC SQL
> Server Driver][SQL Server]The file on device
> 'C:\xx\LogShipIN\TRNs\xx_tlog_200704180300.TRN' is not a valid Microsoft Tape
> Format backup set.
> [Microsoft][ODBC SQL Server Driver][SQL Server]RESTORE LOG is terminating
> abnormally.
> I've check the file and already exist in backup server, but it seems it
> wasn't copied correctly. Because it's a lot of days since the file fail to
> restore (it's from 18 th april), we don't have it on production server (we
> have only from 2 days ago).
> Does anybody knows how could I re-sync the log shipping on backup server
> again?
> Thansk a lot,
> Alex.
You should have valid backup. If backup on tape is not O.K then you
can not restore next subsequent log backups. You have to setup
logshipping again,
Regards
Amish Shah
http://shahamishm.tripod.com|||Hi Hurme,
Thanks againg for your help.
I still have a doubt. Before performing the restore on secondary server,
should I disable/delete logshipping, or could I restore the database on
secondary without disabling/deleting logshipping?
If I had to disable/delete logshipping, should I delete the trn log files
that are on secondary and that have been copied before recreating the
logshipping? I understand yes.
I had to restore with standby, because there are users that access this
database in read mode on secondary server.
Thanks,
Alex.
"Hurme" wrote:
> Yes, by log I meant the .trn files.
> If you don't use standby, the backup database will be left offline and not
> readable so that successive .trn (backup log) files can be restored.
> If you restore with standby the backup db will be accessable in Read-Only
> mode and still be able to have successive .trn files restored to it. The only
> issue with this is that exclussive access to the db is still need to restore
> a .trn so if some one is accessing the db they need to be kicked out of the
> db before a restore can happen.
> The restore with standby command should look like:
> restore database <db_name>
> from disk = 'c:\<backup>.BAK'
> with standby = <undo_file_name>
> likewise for .trn files
> restore log <db_name>
> from disk = 'c:\<log_backup>.trn'
> with standby = <undo_file_name>
> If you're not using it, try using Enterprise Manager to set up Log Shipping.
> --
> MG
>
> "Alex Delgado" wrote:
> > Hi Hurme,
> >
> > Thanks a lot for your help.
> >
> > I still have a doubt.
> >
> > When you say:
> >
> > " If the latest full db backup that you have was created after the error
> > occurred and you still have all of the log (and/or differential) backups
> > since the latest db backup then you can use these files to reinitialize db on
> > the secondary server instead of having to take a full backup of the db. This
> > would allow you to set up log shipping without having to impact performance
> > on your primary db. "
> >
> > I have full db backup created after the error that we can restore on
> > secondary server. About the log backups, I understand you mean the trn files
> > that log shipping copies to secondary server and that it tries to restore,
> > don't you? If so, then my answer is yes, I also have them.
> >
> > Should I run the restore with the following parameter: restore with standby'
> >
> > How should be the exact command to restore?
> >
> > Thanks again,
> >
> > Alex.
> >
> >
> > "Hurme" wrote:
> >
> > > You need to recreate the Log Shipping Maintenance plan for the desired
> > > database.
> > > In order to deleted the current plan, you'll need to remove LS from the plan
> > > first.
> > >
> > > If the latest full db backup that you have was created after the error
> > > occurred and you still have all of the log (and/or differential) backups
> > > since the latest db backup then you can use these files to reinitialize db on
> > > the secondary server instead of having to take a full backup of the db. This
> > > would allow you to set up log shipping without having to impact performance
> > > on your primary db.
> > >
> > > check out these articles
> > > http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/logship1.mspx
> > >
> > > http://www.microsoft.com/technet/prodtechnol/sql/2000/reskit/part4/c1361.mspx?mfr=true
> > >
> > >
> > > --
> > > MG
> > >
> > >
> > > "Alex Delgado" wrote:
> > >
> > > > Hi everyone,
> > > >
> > > > We have set up a log shipping between two SQL 2000 servers with a monitor
> > > > server as well.
> > > >
> > > > The problem is that I've been on holidays, and the people that should check
> > > > the databases didn't do it. The result is that the log shipping has been out
> > > > ot sync since 18th april till now.
> > > >
> > > > We get the following error:
> > > >
> > > > [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3242: [Microsoft][ODBC SQL
> > > > Server Driver][SQL Server]The file on device
> > > > 'C:\xx\LogShipIN\TRNs\xx_tlog_200704180300.TRN' is not a valid Microsoft Tape
> > > > Format backup set.
> > > > [Microsoft][ODBC SQL Server Driver][SQL Server]RESTORE LOG is terminating
> > > > abnormally.
> > > >
> > > > I've check the file and already exist in backup server, but it seems it
> > > > wasn't copied correctly. Because it's a lot of days since the file fail to
> > > > restore (it's from 18 th april), we don't have it on production server (we
> > > > have only from 2 days ago).
> > > >
> > > > Does anybody knows how could I re-sync the log shipping on backup server
> > > > again?
> > > >
> > > > Thansk a lot,
> > > >
> > > > Alex.
We have set up a log shipping between two SQL 2000 servers with a monitor
server as well.
The problem is that I've been on holidays, and the people that should check
the databases didn't do it. The result is that the log shipping has been out
ot sync since 18th april till now.
We get the following error:
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3242: [Microsoft][ODBC SQL
Server Driver][SQL Server]The file on device
'C:\xx\LogShipIN\TRNs\xx_tlog_200704180300.TRN' is not a valid Microsoft Tape
Format backup set.
[Microsoft][ODBC SQL Server Driver][SQL Server]RESTORE LOG is terminating
abnormally.
I've check the file and already exist in backup server, but it seems it
wasn't copied correctly. Because it's a lot of days since the file fail to
restore (it's from 18 th april), we don't have it on production server (we
have only from 2 days ago).
Does anybody knows how could I re-sync the log shipping on backup server
again?
Thansk a lot,
Alex.You need to recreate the Log Shipping Maintenance plan for the desired
database.
In order to deleted the current plan, you'll need to remove LS from the plan
first.
If the latest full db backup that you have was created after the error
occurred and you still have all of the log (and/or differential) backups
since the latest db backup then you can use these files to reinitialize db on
the secondary server instead of having to take a full backup of the db. This
would allow you to set up log shipping without having to impact performance
on your primary db.
check out these articles
http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/logship1.mspx
http://www.microsoft.com/technet/prodtechnol/sql/2000/reskit/part4/c1361.mspx?mfr=true
MG
"Alex Delgado" wrote:
> Hi everyone,
> We have set up a log shipping between two SQL 2000 servers with a monitor
> server as well.
> The problem is that I've been on holidays, and the people that should check
> the databases didn't do it. The result is that the log shipping has been out
> ot sync since 18th april till now.
> We get the following error:
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3242: [Microsoft][ODBC SQL
> Server Driver][SQL Server]The file on device
> 'C:\xx\LogShipIN\TRNs\xx_tlog_200704180300.TRN' is not a valid Microsoft Tape
> Format backup set.
> [Microsoft][ODBC SQL Server Driver][SQL Server]RESTORE LOG is terminating
> abnormally.
> I've check the file and already exist in backup server, but it seems it
> wasn't copied correctly. Because it's a lot of days since the file fail to
> restore (it's from 18 th april), we don't have it on production server (we
> have only from 2 days ago).
> Does anybody knows how could I re-sync the log shipping on backup server
> again?
> Thansk a lot,
> Alex.|||Hi Hurme,
Thanks a lot for your help.
I still have a doubt.
When you say:
" If the latest full db backup that you have was created after the error
occurred and you still have all of the log (and/or differential) backups
since the latest db backup then you can use these files to reinitialize db on
the secondary server instead of having to take a full backup of the db. This
would allow you to set up log shipping without having to impact performance
on your primary db. "
I have full db backup created after the error that we can restore on
secondary server. About the log backups, I understand you mean the trn files
that log shipping copies to secondary server and that it tries to restore,
don't you? If so, then my answer is yes, I also have them.
Should I run the restore with the following parameter: restore
"Hurme" wrote:
> You need to recreate the Log Shipping Maintenance plan for the desired
> database.
> In order to deleted the current plan, you'll need to remove LS from the plan
> first.
> If the latest full db backup that you have was created after the error
> occurred and you still have all of the log (and/or differential) backups
> since the latest db backup then you can use these files to reinitialize db on
> the secondary server instead of having to take a full backup of the db. This
> would allow you to set up log shipping without having to impact performance
> on your primary db.
> check out these articles
> http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/logship1.mspx
> http://www.microsoft.com/technet/prodtechnol/sql/2000/reskit/part4/c1361.mspx?mfr=true
>
> --
> MG
>
> "Alex Delgado" wrote:
> > Hi everyone,
> >
> > We have set up a log shipping between two SQL 2000 servers with a monitor
> > server as well.
> >
> > The problem is that I've been on holidays, and the people that should check
> > the databases didn't do it. The result is that the log shipping has been out
> > ot sync since 18th april till now.
> >
> > We get the following error:
> >
> > [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3242: [Microsoft][ODBC SQL
> > Server Driver][SQL Server]The file on device
> > 'C:\xx\LogShipIN\TRNs\xx_tlog_200704180300.TRN' is not a valid Microsoft Tape
> > Format backup set.
> > [Microsoft][ODBC SQL Server Driver][SQL Server]RESTORE LOG is terminating
> > abnormally.
> >
> > I've check the file and already exist in backup server, but it seems it
> > wasn't copied correctly. Because it's a lot of days since the file fail to
> > restore (it's from 18 th april), we don't have it on production server (we
> > have only from 2 days ago).
> >
> > Does anybody knows how could I re-sync the log shipping on backup server
> > again?
> >
> > Thansk a lot,
> >
> > Alex.|||Hi Hurme,
Thanks a lot for your help.
I still have a doubt.
When you say:
" If the latest full db backup that you have was created after the error
occurred and you still have all of the log (and/or differential) backups
since the latest db backup then you can use these files to reinitialize db on
the secondary server instead of having to take a full backup of the db. This
would allow you to set up log shipping without having to impact performance
on your primary db. "
I have full db backup created after the error that we can restore on
secondary server. About the log backups, I understand you mean the trn files
that log shipping copies to secondary server and that it tries to restore,
don't you? If so, then my answer is yes, I also have them.
Should I run the restore with the following parameter: restore with standby'
How should be the exact command to restore?
Thanks again,
Alex.
"Hurme" wrote:
> You need to recreate the Log Shipping Maintenance plan for the desired
> database.
> In order to deleted the current plan, you'll need to remove LS from the plan
> first.
> If the latest full db backup that you have was created after the error
> occurred and you still have all of the log (and/or differential) backups
> since the latest db backup then you can use these files to reinitialize db on
> the secondary server instead of having to take a full backup of the db. This
> would allow you to set up log shipping without having to impact performance
> on your primary db.
> check out these articles
> http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/logship1.mspx
> http://www.microsoft.com/technet/prodtechnol/sql/2000/reskit/part4/c1361.mspx?mfr=true
>
> --
> MG
>
> "Alex Delgado" wrote:
> > Hi everyone,
> >
> > We have set up a log shipping between two SQL 2000 servers with a monitor
> > server as well.
> >
> > The problem is that I've been on holidays, and the people that should check
> > the databases didn't do it. The result is that the log shipping has been out
> > ot sync since 18th april till now.
> >
> > We get the following error:
> >
> > [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3242: [Microsoft][ODBC SQL
> > Server Driver][SQL Server]The file on device
> > 'C:\xx\LogShipIN\TRNs\xx_tlog_200704180300.TRN' is not a valid Microsoft Tape
> > Format backup set.
> > [Microsoft][ODBC SQL Server Driver][SQL Server]RESTORE LOG is terminating
> > abnormally.
> >
> > I've check the file and already exist in backup server, but it seems it
> > wasn't copied correctly. Because it's a lot of days since the file fail to
> > restore (it's from 18 th april), we don't have it on production server (we
> > have only from 2 days ago).
> >
> > Does anybody knows how could I re-sync the log shipping on backup server
> > again?
> >
> > Thansk a lot,
> >
> > Alex.|||Yes, by log I meant the .trn files.
If you don't use standby, the backup database will be left offline and not
readable so that successive .trn (backup log) files can be restored.
If you restore with standby the backup db will be accessable in Read-Only
mode and still be able to have successive .trn files restored to it. The only
issue with this is that exclussive access to the db is still need to restore
a .trn so if some one is accessing the db they need to be kicked out of the
db before a restore can happen.
The restore with standby command should look like:
restore database <db_name>
from disk = 'c:\<backup>.BAK'
with standby = <undo_file_name>
likewise for .trn files
restore log <db_name>
from disk = 'c:\<log_backup>.trn'
with standby = <undo_file_name>
If you're not using it, try using Enterprise Manager to set up Log Shipping.
--
MG
"Alex Delgado" wrote:
> Hi Hurme,
> Thanks a lot for your help.
> I still have a doubt.
> When you say:
> " If the latest full db backup that you have was created after the error
> occurred and you still have all of the log (and/or differential) backups
> since the latest db backup then you can use these files to reinitialize db on
> the secondary server instead of having to take a full backup of the db. This
> would allow you to set up log shipping without having to impact performance
> on your primary db. "
> I have full db backup created after the error that we can restore on
> secondary server. About the log backups, I understand you mean the trn files
> that log shipping copies to secondary server and that it tries to restore,
> don't you? If so, then my answer is yes, I also have them.
> Should I run the restore with the following parameter: restore with standby'
> How should be the exact command to restore?
> Thanks again,
> Alex.
>
> "Hurme" wrote:
> > You need to recreate the Log Shipping Maintenance plan for the desired
> > database.
> > In order to deleted the current plan, you'll need to remove LS from the plan
> > first.
> >
> > If the latest full db backup that you have was created after the error
> > occurred and you still have all of the log (and/or differential) backups
> > since the latest db backup then you can use these files to reinitialize db on
> > the secondary server instead of having to take a full backup of the db. This
> > would allow you to set up log shipping without having to impact performance
> > on your primary db.
> >
> > check out these articles
> > http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/logship1.mspx
> >
> > http://www.microsoft.com/technet/prodtechnol/sql/2000/reskit/part4/c1361.mspx?mfr=true
> >
> >
> > --
> > MG
> >
> >
> > "Alex Delgado" wrote:
> >
> > > Hi everyone,
> > >
> > > We have set up a log shipping between two SQL 2000 servers with a monitor
> > > server as well.
> > >
> > > The problem is that I've been on holidays, and the people that should check
> > > the databases didn't do it. The result is that the log shipping has been out
> > > ot sync since 18th april till now.
> > >
> > > We get the following error:
> > >
> > > [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3242: [Microsoft][ODBC SQL
> > > Server Driver][SQL Server]The file on device
> > > 'C:\xx\LogShipIN\TRNs\xx_tlog_200704180300.TRN' is not a valid Microsoft Tape
> > > Format backup set.
> > > [Microsoft][ODBC SQL Server Driver][SQL Server]RESTORE LOG is terminating
> > > abnormally.
> > >
> > > I've check the file and already exist in backup server, but it seems it
> > > wasn't copied correctly. Because it's a lot of days since the file fail to
> > > restore (it's from 18 th april), we don't have it on production server (we
> > > have only from 2 days ago).
> > >
> > > Does anybody knows how could I re-sync the log shipping on backup server
> > > again?
> > >
> > > Thansk a lot,
> > >
> > > Alex.|||On Apr 24, 1:50 pm, Alex Delgado
<AlexDelg...@.discussions.microsoft.com> wrote:
> Hi everyone,
> We have set up a log shipping between two SQL 2000 servers with a monitor
> server as well.
> The problem is that I've been on holidays, and the people that should check
> the databases didn't do it. The result is that the log shipping has been out
> ot sync since 18th april till now.
> We get the following error:
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3242: [Microsoft][ODBC SQL
> Server Driver][SQL Server]The file on device
> 'C:\xx\LogShipIN\TRNs\xx_tlog_200704180300.TRN' is not a valid Microsoft Tape
> Format backup set.
> [Microsoft][ODBC SQL Server Driver][SQL Server]RESTORE LOG is terminating
> abnormally.
> I've check the file and already exist in backup server, but it seems it
> wasn't copied correctly. Because it's a lot of days since the file fail to
> restore (it's from 18 th april), we don't have it on production server (we
> have only from 2 days ago).
> Does anybody knows how could I re-sync the log shipping on backup server
> again?
> Thansk a lot,
> Alex.
You should have valid backup. If backup on tape is not O.K then you
can not restore next subsequent log backups. You have to setup
logshipping again,
Regards
Amish Shah
http://shahamishm.tripod.com|||Hi Hurme,
Thanks againg for your help.
I still have a doubt. Before performing the restore on secondary server,
should I disable/delete logshipping, or could I restore the database on
secondary without disabling/deleting logshipping?
If I had to disable/delete logshipping, should I delete the trn log files
that are on secondary and that have been copied before recreating the
logshipping? I understand yes.
I had to restore with standby, because there are users that access this
database in read mode on secondary server.
Thanks,
Alex.
"Hurme" wrote:
> Yes, by log I meant the .trn files.
> If you don't use standby, the backup database will be left offline and not
> readable so that successive .trn (backup log) files can be restored.
> If you restore with standby the backup db will be accessable in Read-Only
> mode and still be able to have successive .trn files restored to it. The only
> issue with this is that exclussive access to the db is still need to restore
> a .trn so if some one is accessing the db they need to be kicked out of the
> db before a restore can happen.
> The restore with standby command should look like:
> restore database <db_name>
> from disk = 'c:\<backup>.BAK'
> with standby = <undo_file_name>
> likewise for .trn files
> restore log <db_name>
> from disk = 'c:\<log_backup>.trn'
> with standby = <undo_file_name>
> If you're not using it, try using Enterprise Manager to set up Log Shipping.
> --
> MG
>
> "Alex Delgado" wrote:
> > Hi Hurme,
> >
> > Thanks a lot for your help.
> >
> > I still have a doubt.
> >
> > When you say:
> >
> > " If the latest full db backup that you have was created after the error
> > occurred and you still have all of the log (and/or differential) backups
> > since the latest db backup then you can use these files to reinitialize db on
> > the secondary server instead of having to take a full backup of the db. This
> > would allow you to set up log shipping without having to impact performance
> > on your primary db. "
> >
> > I have full db backup created after the error that we can restore on
> > secondary server. About the log backups, I understand you mean the trn files
> > that log shipping copies to secondary server and that it tries to restore,
> > don't you? If so, then my answer is yes, I also have them.
> >
> > Should I run the restore with the following parameter: restore with standby'
> >
> > How should be the exact command to restore?
> >
> > Thanks again,
> >
> > Alex.
> >
> >
> > "Hurme" wrote:
> >
> > > You need to recreate the Log Shipping Maintenance plan for the desired
> > > database.
> > > In order to deleted the current plan, you'll need to remove LS from the plan
> > > first.
> > >
> > > If the latest full db backup that you have was created after the error
> > > occurred and you still have all of the log (and/or differential) backups
> > > since the latest db backup then you can use these files to reinitialize db on
> > > the secondary server instead of having to take a full backup of the db. This
> > > would allow you to set up log shipping without having to impact performance
> > > on your primary db.
> > >
> > > check out these articles
> > > http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/logship1.mspx
> > >
> > > http://www.microsoft.com/technet/prodtechnol/sql/2000/reskit/part4/c1361.mspx?mfr=true
> > >
> > >
> > > --
> > > MG
> > >
> > >
> > > "Alex Delgado" wrote:
> > >
> > > > Hi everyone,
> > > >
> > > > We have set up a log shipping between two SQL 2000 servers with a monitor
> > > > server as well.
> > > >
> > > > The problem is that I've been on holidays, and the people that should check
> > > > the databases didn't do it. The result is that the log shipping has been out
> > > > ot sync since 18th april till now.
> > > >
> > > > We get the following error:
> > > >
> > > > [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3242: [Microsoft][ODBC SQL
> > > > Server Driver][SQL Server]The file on device
> > > > 'C:\xx\LogShipIN\TRNs\xx_tlog_200704180300.TRN' is not a valid Microsoft Tape
> > > > Format backup set.
> > > > [Microsoft][ODBC SQL Server Driver][SQL Server]RESTORE LOG is terminating
> > > > abnormally.
> > > >
> > > > I've check the file and already exist in backup server, but it seems it
> > > > wasn't copied correctly. Because it's a lot of days since the file fail to
> > > > restore (it's from 18 th april), we don't have it on production server (we
> > > > have only from 2 days ago).
> > > >
> > > > Does anybody knows how could I re-sync the log shipping on backup server
> > > > again?
> > > >
> > > > Thansk a lot,
> > > >
> > > > Alex.
Log Shipping Monitor Shows Problems when there aren't any
I Have setup a pair of server with log shipping, it works perfectly, logs are
backed up every 2 mins and restored succesfully to the destination server. My
only problem is that the monitor (running on the backup server) thinks that
things are not working correctly. It shows the correct times for the copy and
load jobs but the backup job time never gets updated. I have read the MS KB
article 292586 which states that this could be a permissions issue that the
source server does not have permissions to update the msdb database on the
destination server, however I have tried changing things in this area by
having the sql account running with full admin privs (both domain admin and
sql admin) this didnt work, I also tried running sql in mixed auth mode and
then configurung log shipping to use SQL authentication, it correctly created
the new log_shipping_monitor account, but still the log shipping monitor
refuses to work. Can somebody help me before I pull all my hair out.
Brett
Hello Brett,
My suggestion is that you reset password for log_shipping_monitor_probe
account on all shipping databases (both secondary and primary) and removed
and
reapplied permissions to the log shipping tables on both primary and
secondary servers. If log_shipping_monitor_prob does not exist, create the
login, set the default
database to msdb, and grant it access to msdb.
On both Primary / Secondary server, right click the log shipping database,
select properties. In the general tab, click the details button for log
shipping. Select "Use SQL Server Authentication" and change the password
to log_shipping_monitor_prob account.
More related information:
321247 How To Configure Security for Log Shipping
http://support.microsoft.com/?id=321247
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
--
>Thread-Topic: Log Shipping Monitor Shows Problems when there aren't any
>thread-index: AcX4xD/DRKnfVG7nSZmLj/7UPPi8Vg==
>X-WBNR-Posting-Host: 194.109.239.116
>From: "=?Utf-8?B?QnJldHQgQ2Fycg==?=" <brettcarr@.news.postalias>
>Subject: Log Shipping Monitor Shows Problems when there aren't any
>Date: Sun, 4 Dec 2005 03:17:01 -0800
>Lines: 15
>Message-ID: <0E563B60-3095-4635-BC0A-3153BEB87CDB@.microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
>charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>Newsgroups: microsoft.public.sqlserver.replication
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFT NGXA03.phx.gbl
>Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.sqlserver.replication:67206
>X-Tomcat-NG: microsoft.public.sqlserver.replication
>I Have setup a pair of server with log shipping, it works perfectly, logs
are
>backed up every 2 mins and restored succesfully to the destination server.
My
>only problem is that the monitor (running on the backup server) thinks
that
>things are not working correctly. It shows the correct times for the copy
and
>load jobs but the backup job time never gets updated. I have read the MS
KB
>article 292586 which states that this could be a permissions issue that
the
>source server does not have permissions to update the msdb database on the
>destination server, however I have tried changing things in this area by
>having the sql account running with full admin privs (both domain admin
and
>sql admin) this didnt work, I also tried running sql in mixed auth mode
and
>then configurung log shipping to use SQL authentication, it correctly
created
>the new log_shipping_monitor account, but still the log shipping monitor
>refuses to work. Can somebody help me before I pull all my hair out.
>Brett
>
|||"Peter Yang [MSFT]" wrote:
> Hello Brett,
> My suggestion is that you reset password for log_shipping_monitor_probe
> account on all shipping databases (both secondary and primary) and removed
> and
> reapplied permissions to the log shipping tables on both primary and
> secondary servers. If log_shipping_monitor_prob does not exist, create the
> login, set the default
> database to msdb, and grant it access to msdb.
> On both Primary / Secondary server, right click the log shipping database,
> select properties. In the general tab, click the details button for log
> shipping. Select "Use SQL Server Authentication" and change the password
> to log_shipping_monitor_prob account.
>
Ok. I've done the following:
1. log_shipping_monitor_prob did not exist on the primary server so I
created it.
2. I reset the password for log_shipping_monitor_prob on both primary and
secondary.
3. On both primary and secondary servers I have set
log_shipping_monitor_prob to have select,insert,update and delete permissions
on all tables starting with log_shipping in the msdb database.
However I'm afraid the 'Last Backup' date and time listed in the monitor is
still the date and time I set it up originally. The Last copy and Last
restore dates are still being updated correctly.
Brett..
|||Hello Brett,
Going forward, I'd like to confirm if Windows Authentication option is
selected on the Specify The Log Shipping Monitor Server Information screen
during log shipping setup.
If so, you may want to check if the SQL Server Service startup account on
the primary server of a log shipping pair does not have sufficient
privileges to update table msdb..log_shipping_primaries on the monitor
server.
Also, please check if the value in primary_server_name column in
log_shipping_primaries does not match the <@.@.servername> of the primary
server.
If the issue persists, please use SQL profiler on the monitor server to see
if the update operation on log_shipping_primaries occurs or if there is any
related errors in error log.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
--
>Thread-Topic: Log Shipping Monitor Shows Problems when there aren't any
>thread-index: AcX5iaV+Rf+MfqKZTvqVdLuPrgGVlw==
>X-WBNR-Posting-Host: 193.0.2.180
>From: "=?Utf-8?B?QnJldHQgQ2Fycg==?=" <brettcarr@.news.postalias>
>References: <0E563B60-3095-4635-BC0A-3153BEB87CDB@.microsoft.com>
<VAQE#gX#FHA.1236@.TK2MSFTNGXA02.phx.gbl>[vbcol=seagreen]
>Subject: RE: Log Shipping Monitor Shows Problems when there aren't any
>Date: Mon, 5 Dec 2005 02:50:03 -0800
>Lines: 35
>Message-ID: <33C3B088-9CA3-4C3E-98B1-86E784833DDC@.microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
>charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>Newsgroups: microsoft.public.sqlserver.replication
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGXA03.phx.gbl
>Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.sqlserver.replication:67231
>X-Tomcat-NG: microsoft.public.sqlserver.replication
>"Peter Yang [MSFT]" wrote:
removed[vbcol=seagreen]
the[vbcol=seagreen]
database,[vbcol=seagreen]
password
>Ok. I've done the following:
>1. log_shipping_monitor_prob did not exist on the primary server so I
>created it.
>2. I reset the password for log_shipping_monitor_prob on both primary and
>secondary.
>3. On both primary and secondary servers I have set
>log_shipping_monitor_prob to have select,insert,update and delete
permissions
>on all tables starting with log_shipping in the msdb database.
>However I'm afraid the 'Last Backup' date and time listed in the monitor
is
>still the date and time I set it up originally. The Last copy and Last
>restore dates are still being updated correctly.
>Brett..
>
>
backed up every 2 mins and restored succesfully to the destination server. My
only problem is that the monitor (running on the backup server) thinks that
things are not working correctly. It shows the correct times for the copy and
load jobs but the backup job time never gets updated. I have read the MS KB
article 292586 which states that this could be a permissions issue that the
source server does not have permissions to update the msdb database on the
destination server, however I have tried changing things in this area by
having the sql account running with full admin privs (both domain admin and
sql admin) this didnt work, I also tried running sql in mixed auth mode and
then configurung log shipping to use SQL authentication, it correctly created
the new log_shipping_monitor account, but still the log shipping monitor
refuses to work. Can somebody help me before I pull all my hair out.
Brett
Hello Brett,
My suggestion is that you reset password for log_shipping_monitor_probe
account on all shipping databases (both secondary and primary) and removed
and
reapplied permissions to the log shipping tables on both primary and
secondary servers. If log_shipping_monitor_prob does not exist, create the
login, set the default
database to msdb, and grant it access to msdb.
On both Primary / Secondary server, right click the log shipping database,
select properties. In the general tab, click the details button for log
shipping. Select "Use SQL Server Authentication" and change the password
to log_shipping_monitor_prob account.
More related information:
321247 How To Configure Security for Log Shipping
http://support.microsoft.com/?id=321247
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
--
>Thread-Topic: Log Shipping Monitor Shows Problems when there aren't any
>thread-index: AcX4xD/DRKnfVG7nSZmLj/7UPPi8Vg==
>X-WBNR-Posting-Host: 194.109.239.116
>From: "=?Utf-8?B?QnJldHQgQ2Fycg==?=" <brettcarr@.news.postalias>
>Subject: Log Shipping Monitor Shows Problems when there aren't any
>Date: Sun, 4 Dec 2005 03:17:01 -0800
>Lines: 15
>Message-ID: <0E563B60-3095-4635-BC0A-3153BEB87CDB@.microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
>charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>Newsgroups: microsoft.public.sqlserver.replication
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFT NGXA03.phx.gbl
>Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.sqlserver.replication:67206
>X-Tomcat-NG: microsoft.public.sqlserver.replication
>I Have setup a pair of server with log shipping, it works perfectly, logs
are
>backed up every 2 mins and restored succesfully to the destination server.
My
>only problem is that the monitor (running on the backup server) thinks
that
>things are not working correctly. It shows the correct times for the copy
and
>load jobs but the backup job time never gets updated. I have read the MS
KB
>article 292586 which states that this could be a permissions issue that
the
>source server does not have permissions to update the msdb database on the
>destination server, however I have tried changing things in this area by
>having the sql account running with full admin privs (both domain admin
and
>sql admin) this didnt work, I also tried running sql in mixed auth mode
and
>then configurung log shipping to use SQL authentication, it correctly
created
>the new log_shipping_monitor account, but still the log shipping monitor
>refuses to work. Can somebody help me before I pull all my hair out.
>Brett
>
|||"Peter Yang [MSFT]" wrote:
> Hello Brett,
> My suggestion is that you reset password for log_shipping_monitor_probe
> account on all shipping databases (both secondary and primary) and removed
> and
> reapplied permissions to the log shipping tables on both primary and
> secondary servers. If log_shipping_monitor_prob does not exist, create the
> login, set the default
> database to msdb, and grant it access to msdb.
> On both Primary / Secondary server, right click the log shipping database,
> select properties. In the general tab, click the details button for log
> shipping. Select "Use SQL Server Authentication" and change the password
> to log_shipping_monitor_prob account.
>
Ok. I've done the following:
1. log_shipping_monitor_prob did not exist on the primary server so I
created it.
2. I reset the password for log_shipping_monitor_prob on both primary and
secondary.
3. On both primary and secondary servers I have set
log_shipping_monitor_prob to have select,insert,update and delete permissions
on all tables starting with log_shipping in the msdb database.
However I'm afraid the 'Last Backup' date and time listed in the monitor is
still the date and time I set it up originally. The Last copy and Last
restore dates are still being updated correctly.
Brett..
|||Hello Brett,
Going forward, I'd like to confirm if Windows Authentication option is
selected on the Specify The Log Shipping Monitor Server Information screen
during log shipping setup.
If so, you may want to check if the SQL Server Service startup account on
the primary server of a log shipping pair does not have sufficient
privileges to update table msdb..log_shipping_primaries on the monitor
server.
Also, please check if the value in primary_server_name column in
log_shipping_primaries does not match the <@.@.servername> of the primary
server.
If the issue persists, please use SQL profiler on the monitor server to see
if the update operation on log_shipping_primaries occurs or if there is any
related errors in error log.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
--
>Thread-Topic: Log Shipping Monitor Shows Problems when there aren't any
>thread-index: AcX5iaV+Rf+MfqKZTvqVdLuPrgGVlw==
>X-WBNR-Posting-Host: 193.0.2.180
>From: "=?Utf-8?B?QnJldHQgQ2Fycg==?=" <brettcarr@.news.postalias>
>References: <0E563B60-3095-4635-BC0A-3153BEB87CDB@.microsoft.com>
<VAQE#gX#FHA.1236@.TK2MSFTNGXA02.phx.gbl>[vbcol=seagreen]
>Subject: RE: Log Shipping Monitor Shows Problems when there aren't any
>Date: Mon, 5 Dec 2005 02:50:03 -0800
>Lines: 35
>Message-ID: <33C3B088-9CA3-4C3E-98B1-86E784833DDC@.microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
>charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>Newsgroups: microsoft.public.sqlserver.replication
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGXA03.phx.gbl
>Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.sqlserver.replication:67231
>X-Tomcat-NG: microsoft.public.sqlserver.replication
>"Peter Yang [MSFT]" wrote:
removed[vbcol=seagreen]
the[vbcol=seagreen]
database,[vbcol=seagreen]
password
>Ok. I've done the following:
>1. log_shipping_monitor_prob did not exist on the primary server so I
>created it.
>2. I reset the password for log_shipping_monitor_prob on both primary and
>secondary.
>3. On both primary and secondary servers I have set
>log_shipping_monitor_prob to have select,insert,update and delete
permissions
>on all tables starting with log_shipping in the msdb database.
>However I'm afraid the 'Last Backup' date and time listed in the monitor
is
>still the date and time I set it up originally. The Last copy and Last
>restore dates are still being updated correctly.
>Brett..
>
>
Log Shipping Monitor server - has to be own server ?
Hi,
I see that Microsoft recommend that the monitor server isn't the source
server when using log shipping. I have 2 sql servers - 1 live and 1 standby
with which I would like to implement log shipping. Do I therfore need to buy
a seperate server for monitoring the log shipping ?(!) or can I use the
standby server ?
Thanks,
Shane.
No, a third server is not required.
Andrew J. Kelly
SQL Server MVP
"Shane Daniels" <shanedaniels101@.yahooo.com> wrote in message
news:Ox1RdXaQEHA.1048@.tk2msftngp13.phx.gbl...
> Hi,
> I see that Microsoft recommend that the monitor server isn't the source
> server when using log shipping. I have 2 sql servers - 1 live and 1
standby
> with which I would like to implement log shipping. Do I therfore need to
buy
> a seperate server for monitoring the log shipping ?(!) or can I use the
> standby server ?
> Thanks,
> Shane.
>
sql
I see that Microsoft recommend that the monitor server isn't the source
server when using log shipping. I have 2 sql servers - 1 live and 1 standby
with which I would like to implement log shipping. Do I therfore need to buy
a seperate server for monitoring the log shipping ?(!) or can I use the
standby server ?
Thanks,
Shane.
No, a third server is not required.
Andrew J. Kelly
SQL Server MVP
"Shane Daniels" <shanedaniels101@.yahooo.com> wrote in message
news:Ox1RdXaQEHA.1048@.tk2msftngp13.phx.gbl...
> Hi,
> I see that Microsoft recommend that the monitor server isn't the source
> server when using log shipping. I have 2 sql servers - 1 live and 1
standby
> with which I would like to implement log shipping. Do I therfore need to
buy
> a seperate server for monitoring the log shipping ?(!) or can I use the
> standby server ?
> Thanks,
> Shane.
>
sql
Log Shipping Monitor server - has to be own server ?
Hi,
I see that Microsoft recommend that the monitor server isn't the source
server when using log shipping. I have 2 sql servers - 1 live and 1 standby
with which I would like to implement log shipping. Do I therfore need to buy
a seperate server for monitoring the log shipping ?(!) or can I use the
standby server ?
Thanks,
Shane.No, a third server is not required.
Andrew J. Kelly
SQL Server MVP
"Shane Daniels" <shanedaniels101@.yahooo.com> wrote in message
news:Ox1RdXaQEHA.1048@.tk2msftngp13.phx.gbl...
> Hi,
> I see that Microsoft recommend that the monitor server isn't the source
> server when using log shipping. I have 2 sql servers - 1 live and 1
standby
> with which I would like to implement log shipping. Do I therfore need to
buy
> a seperate server for monitoring the log shipping ?(!) or can I use the
> standby server ?
> Thanks,
> Shane.
>
I see that Microsoft recommend that the monitor server isn't the source
server when using log shipping. I have 2 sql servers - 1 live and 1 standby
with which I would like to implement log shipping. Do I therfore need to buy
a seperate server for monitoring the log shipping ?(!) or can I use the
standby server ?
Thanks,
Shane.No, a third server is not required.
Andrew J. Kelly
SQL Server MVP
"Shane Daniels" <shanedaniels101@.yahooo.com> wrote in message
news:Ox1RdXaQEHA.1048@.tk2msftngp13.phx.gbl...
> Hi,
> I see that Microsoft recommend that the monitor server isn't the source
> server when using log shipping. I have 2 sql servers - 1 live and 1
standby
> with which I would like to implement log shipping. Do I therfore need to
buy
> a seperate server for monitoring the log shipping ?(!) or can I use the
> standby server ?
> Thanks,
> Shane.
>
Log Shipping Monitor server - has to be own server ?
Hi,
I see that Microsoft recommend that the monitor server isn't the source
server when using log shipping. I have 2 sql servers - 1 live and 1 standby
with which I would like to implement log shipping. Do I therfore need to buy
a seperate server for monitoring the log shipping ?(!) or can I use the
standby server ?
Thanks,
Shane.No, a third server is not required.
--
Andrew J. Kelly
SQL Server MVP
"Shane Daniels" <shanedaniels101@.yahooo.com> wrote in message
news:Ox1RdXaQEHA.1048@.tk2msftngp13.phx.gbl...
> Hi,
> I see that Microsoft recommend that the monitor server isn't the source
> server when using log shipping. I have 2 sql servers - 1 live and 1
standby
> with which I would like to implement log shipping. Do I therfore need to
buy
> a seperate server for monitoring the log shipping ?(!) or can I use the
> standby server ?
> Thanks,
> Shane.
>
I see that Microsoft recommend that the monitor server isn't the source
server when using log shipping. I have 2 sql servers - 1 live and 1 standby
with which I would like to implement log shipping. Do I therfore need to buy
a seperate server for monitoring the log shipping ?(!) or can I use the
standby server ?
Thanks,
Shane.No, a third server is not required.
--
Andrew J. Kelly
SQL Server MVP
"Shane Daniels" <shanedaniels101@.yahooo.com> wrote in message
news:Ox1RdXaQEHA.1048@.tk2msftngp13.phx.gbl...
> Hi,
> I see that Microsoft recommend that the monitor server isn't the source
> server when using log shipping. I have 2 sql servers - 1 live and 1
standby
> with which I would like to implement log shipping. Do I therfore need to
buy
> a seperate server for monitoring the log shipping ?(!) or can I use the
> standby server ?
> Thanks,
> Shane.
>
Log shipping Monitor server
Hi,
Can separate monitor server for SQL 2000 Log Shipping
high-availability configuration be SQL 2000 Standard
Edtion?
Or must be SQL 2000 Server Enterprise Edition?
Thanks for answers
MilanYou cant have log shipping for SQL Standard, not quite sure what ur
question is?
Regards
J
"Milan Ojstersek" <milan.ojstersek@.hermes-plus.si> wrote in message
news:083101c34c5d$25531fe0$a601280a@.phx.gbl...
> Hi,
> Can separate monitor server for SQL 2000 Log Shipping
> high-availability configuration be SQL 2000 Standard
> Edtion?
> Or must be SQL 2000 Server Enterprise Edition?
> Thanks for answers
> Milan
Can separate monitor server for SQL 2000 Log Shipping
high-availability configuration be SQL 2000 Standard
Edtion?
Or must be SQL 2000 Server Enterprise Edition?
Thanks for answers
MilanYou cant have log shipping for SQL Standard, not quite sure what ur
question is?
Regards
J
"Milan Ojstersek" <milan.ojstersek@.hermes-plus.si> wrote in message
news:083101c34c5d$25531fe0$a601280a@.phx.gbl...
> Hi,
> Can separate monitor server for SQL 2000 Log Shipping
> high-availability configuration be SQL 2000 Standard
> Edtion?
> Or must be SQL 2000 Server Enterprise Edition?
> Thanks for answers
> Milan
Log Shipping Monitor Reqs
Greetings:
Does anyone know if I can install/run the Log Shipping Monitor Utility on
SQL 2000 Standard Edition, or do I need to actually have THREE copies of SQL
Enterprise Edition in order to configure Log Shipping?
I realize the recommendation is to NOT install the monitor utility on the
source server, but can it be installed on the Destination server?
Thanks!
Keith C. Jakobs, MCP
Hello mate,
You DON'T need to have Enterprise Edition to host the log shipping monitor -
I have and use exactly the model your trying to work towards in my
organisation.
Regards
Paul.
"Keith Jakobs, MCP" wrote:
> Greetings:
> Does anyone know if I can install/run the Log Shipping Monitor Utility on
> SQL 2000 Standard Edition, or do I need to actually have THREE copies of SQL
> Enterprise Edition in order to configure Log Shipping?
> I realize the recommendation is to NOT install the monitor utility on the
> source server, but can it be installed on the Destination server?
> Thanks!
> Keith C. Jakobs, MCP
>
>
Does anyone know if I can install/run the Log Shipping Monitor Utility on
SQL 2000 Standard Edition, or do I need to actually have THREE copies of SQL
Enterprise Edition in order to configure Log Shipping?
I realize the recommendation is to NOT install the monitor utility on the
source server, but can it be installed on the Destination server?
Thanks!
Keith C. Jakobs, MCP
Hello mate,
You DON'T need to have Enterprise Edition to host the log shipping monitor -
I have and use exactly the model your trying to work towards in my
organisation.
Regards
Paul.
"Keith Jakobs, MCP" wrote:
> Greetings:
> Does anyone know if I can install/run the Log Shipping Monitor Utility on
> SQL 2000 Standard Edition, or do I need to actually have THREE copies of SQL
> Enterprise Edition in order to configure Log Shipping?
> I realize the recommendation is to NOT install the monitor utility on the
> source server, but can it be installed on the Destination server?
> Thanks!
> Keith C. Jakobs, MCP
>
>
log shipping monitor report error
I have SQL Server 2005 log shipping setup with primary/secondary configuration. I can confirm from the logs that log shipping is working without issue, however, reports generated from the monitor server show this message:
Violation of PRIMARY KEY constraint 'PK__#log_shipping_mo__3ABBDC91'. Cannot insert duplicate key in object 'dbo.#log_shipping_monitor'. The statement has been terminated.
There is nothing special about the configuration. Any ideas?
Clear out the log on Log shipping monitor and ensure the log shipping is working properly on secondary server too.|||Log shipping is working properly on the secondary server. The error is generated when I try to view the Log Shipping Status report on the secondary server. The monitor server instance is also throwing incorrect alerts.|||I think the problem you are seeing is related to some old information being present in the tables used to store log shipping configuration. There are some scenarios where this can happen and it causes the problem you reported in your first post. We are working on correcting this in a future release.
As you can tell from the error, the problem is caused by an insert to a temp table causing a PK constraint violation. The PK for the temp table is server name and database name. This error is normally caused by old configuration being present in the tables log_shipping_monitor_primary and/or log_shipping_monitor_secondary. You can view the contents of these tables directly (in msdb) or use some supplied help SP's (see BOL topic titled "Log Shipping Tables and Stored Procedures").
The workaround is to remove the old rows from log_shipping_monitor_primary and/or log_shipping_monitor_secondary tables. Can you determine that you do indeed have stale data in the log shipping tables. If this is the case I can work with you on how to remove the old rows.
The old configuration data is probably causing the incorrect alerts you are seeing.
|||Hi, Is that possible for you to show how to delete the old data in the tables log_shipping_monitor_primary and/or log_shipping_monitor_secondary.
Thank you
|||Hi Mark,
I am getting a similar error when I try to run the report on the primary server. The report on the secondary server which is also the monitor runs fine.
I queried the tables mentioned by you and got one row in each. FYI, I have only one DB on the primary server being log shipped to the secondary.
For,
select * from dbo.log_shipping_monitor_secondary
I am geeting null values for last_copied_file, last_copied_date, last_copied_date_utc and last restored_file. However, I know that the log shipping is working well for the database.
So How do I go about correcting the report? Should I delete the row in log_shipping_monitor_secondary? In log_shipping_monitor_primary the information is up to date and correct.
Thanks in anticipation.
Amit
sqllog shipping monitor report error
I have SQL Server 2005 log shipping setup with primary/secondary configuration. I can confirm from the logs that log shipping is working without issue, however, reports generated from the monitor server show this message:
Violation of PRIMARY KEY constraint 'PK__#log_shipping_mo__3ABBDC91'. Cannot insert duplicate key in object 'dbo.#log_shipping_monitor'. The statement has been terminated.
There is nothing special about the configuration. Any ideas?
Clear out the log on Log shipping monitor and ensure the log shipping is working properly on secondary server too.|||Log shipping is working properly on the secondary server. The error is generated when I try to view the Log Shipping Status report on the secondary server. The monitor server instance is also throwing incorrect alerts.|||I think the problem you are seeing is related to some old information being present in the tables used to store log shipping configuration. There are some scenarios where this can happen and it causes the problem you reported in your first post. We are working on correcting this in a future release.
As you can tell from the error, the problem is caused by an insert to a temp table causing a PK constraint violation. The PK for the temp table is server name and database name. This error is normally caused by old configuration being present in the tables log_shipping_monitor_primary and/or log_shipping_monitor_secondary. You can view the contents of these tables directly (in msdb) or use some supplied help SP's (see BOL topic titled "Log Shipping Tables and Stored Procedures").
The workaround is to remove the old rows from log_shipping_monitor_primary and/or log_shipping_monitor_secondary tables. Can you determine that you do indeed have stale data in the log shipping tables. If this is the case I can work with you on how to remove the old rows.
The old configuration data is probably causing the incorrect alerts you are seeing.
|||Hi, Is that possible for you to show how to delete the old data in the tables log_shipping_monitor_primary and/or log_shipping_monitor_secondary.
Thank you
|||Hi Mark,
I am getting a similar error when I try to run the report on the primary server. The report on the secondary server which is also the monitor runs fine.
I queried the tables mentioned by you and got one row in each. FYI, I have only one DB on the primary server being log shipped to the secondary.
For,
select * from dbo.log_shipping_monitor_secondary
I am geeting null values for last_copied_file, last_copied_date, last_copied_date_utc and last restored_file. However, I know that the log shipping is working well for the database.
So How do I go about correcting the report? Should I delete the row in log_shipping_monitor_secondary? In log_shipping_monitor_primary the information is up to date and correct.
Thanks in anticipation.
Amit
log shipping monitor report error
I have SQL Server 2005 log shipping setup with primary/secondary configuration. I can confirm from the logs that log shipping is working without issue, however, reports generated from the monitor server show this message:
Violation of PRIMARY KEY constraint 'PK__#log_shipping_mo__3ABBDC91'. Cannot insert duplicate key in object 'dbo.#log_shipping_monitor'. The statement has been terminated.
There is nothing special about the configuration. Any ideas?
Clear out the log on Log shipping monitor and ensure the log shipping is working properly on secondary server too.|||Log shipping is working properly on the secondary server. The error is generated when I try to view the Log Shipping Status report on the secondary server. The monitor server instance is also throwing incorrect alerts.|||I think the problem you are seeing is related to some old information being present in the tables used to store log shipping configuration. There are some scenarios where this can happen and it causes the problem you reported in your first post. We are working on correcting this in a future release.
As you can tell from the error, the problem is caused by an insert to a temp table causing a PK constraint violation. The PK for the temp table is server name and database name. This error is normally caused by old configuration being present in the tables log_shipping_monitor_primary and/or log_shipping_monitor_secondary. You can view the contents of these tables directly (in msdb) or use some supplied help SP's (see BOL topic titled "Log Shipping Tables and Stored Procedures").
The workaround is to remove the old rows from log_shipping_monitor_primary and/or log_shipping_monitor_secondary tables. Can you determine that you do indeed have stale data in the log shipping tables. If this is the case I can work with you on how to remove the old rows.
The old configuration data is probably causing the incorrect alerts you are seeing.
|||Hi, Is that possible for you to show how to delete the old data in the tables log_shipping_monitor_primary and/or log_shipping_monitor_secondary.
Thank you
|||Hi Mark,
I am getting a similar error when I try to run the report on the primary server. The report on the secondary server which is also the monitor runs fine.
I queried the tables mentioned by you and got one row in each. FYI, I have only one DB on the primary server being log shipped to the secondary.
For,
select * from dbo.log_shipping_monitor_secondary
I am geeting null values for last_copied_file, last_copied_date, last_copied_date_utc and last restored_file. However, I know that the log shipping is working well for the database.
So How do I go about correcting the report? Should I delete the row in log_shipping_monitor_secondary? In log_shipping_monitor_primary the information is up to date and correct.
Thanks in anticipation.
Amit
log shipping monitor report error
I have SQL Server 2005 log shipping setup with primary/secondary configuration. I can confirm from the logs that log shipping is working without issue, however, reports generated from the monitor server show this message:
Violation of PRIMARY KEY constraint 'PK__#log_shipping_mo__3ABBDC91'. Cannot insert duplicate key in object 'dbo.#log_shipping_monitor'. The statement has been terminated.
There is nothing special about the configuration. Any ideas?
Clear out the log on Log shipping monitor and ensure the log shipping is working properly on secondary server too.|||Log shipping is working properly on the secondary server. The error is generated when I try to view the Log Shipping Status report on the secondary server. The monitor server instance is also throwing incorrect alerts.|||I think the problem you are seeing is related to some old information being present in the tables used to store log shipping configuration. There are some scenarios where this can happen and it causes the problem you reported in your first post. We are working on correcting this in a future release.
As you can tell from the error, the problem is caused by an insert to a temp table causing a PK constraint violation. The PK for the temp table is server name and database name. This error is normally caused by old configuration being present in the tables log_shipping_monitor_primary and/or log_shipping_monitor_secondary. You can view the contents of these tables directly (in msdb) or use some supplied help SP's (see BOL topic titled "Log Shipping Tables and Stored Procedures").
The workaround is to remove the old rows from log_shipping_monitor_primary and/or log_shipping_monitor_secondary tables. Can you determine that you do indeed have stale data in the log shipping tables. If this is the case I can work with you on how to remove the old rows.
The old configuration data is probably causing the incorrect alerts you are seeing.
|||Hi, Is that possible for you to show how to delete the old data in the tables log_shipping_monitor_primary and/or log_shipping_monitor_secondary.
Thank you
|||Hi Mark,
I am getting a similar error when I try to run the report on the primary server. The report on the secondary server which is also the monitor runs fine.
I queried the tables mentioned by you and got one row in each. FYI, I have only one DB on the primary server being log shipped to the secondary.
For,
select * from dbo.log_shipping_monitor_secondary
I am geeting null values for last_copied_file, last_copied_date, last_copied_date_utc and last restored_file. However, I know that the log shipping is working well for the database.
So How do I go about correcting the report? Should I delete the row in log_shipping_monitor_secondary? In log_shipping_monitor_primary the information is up to date and correct.
Thanks in anticipation.
Amit
Monday, March 19, 2012
Log shipping monitor our of sync SQL Server 2005
I have set up log shipping between two servers with a third serving as a monitoring server. Recently the monitoring for the eight databases that I am log shipping began to indicate that everything was failing. Upon further inventigation of the log_shipping_monitor_history_detail tables on the prinary and secondary everthing appears to working properly but I have been unable to resyncronize the monitoring. I have attempted to use the stored procedure sp_refresh_log_shipping_monitor to no avail, it does not appear to do anything with respect to the data in the dbo.log_shipping_primary_databases and log_shipping_monitor_primary tables on the primary server or the log_shipping_monitor_secondary and dbo.log_shipping_secondary_databases tables on the secondary. I have also manually updated the records in these tables in an attempt to syncronize but after the next sucessful backup, copy and restore this monitoring data is not updating. Does anyone have any ideas as to what I am doing wrong or how I might rectify this situation.Moving to availability forum.|||
I took a shot at reproducing this issue. I could not reproduce the scenario that you describe, but here is some information that may help.
1) Executing sp_refresh_log_shipping_monitor probably hurt more than it helped in this case. There is a bug in this stored procedure that is fixed in SP2 which results in the data that is supposed to be refreshed on the monitor server actually being deleted.
2) After getting my local test monitor server into a bad state, the only way to recover was to remove log shipping and then add it again. When adding it back, you could bypass initializing the secondary database because the primary and secondary are already in synch. After doing this and running through one cycle of backing up a tlog, copy, and restore the monitor server once again had current information on the log shipped database.
Tom
This posting is provided "AS IS" with no warranties, and confers no rights.
Log shipping monitor our of sync SQL Server 2005
I have set up log shipping between two servers with a third serving as a monitoring server. Recently the monitoring for the eight databases that I am log shipping began to indicate that everything was failing. Upon further inventigation of the log_shipping_monitor_history_detail tables on the prinary and secondary everthing appears to working properly but I have been unable to resyncronize the monitoring. I have attempted to use the stored procedure sp_refresh_log_shipping_monitor to no avail, it does not appear to do anything with respect to the data in the dbo.log_shipping_primary_databases and log_shipping_monitor_primary tables on the primary server or the log_shipping_monitor_secondary and dbo.log_shipping_secondary_databases tables on the secondary. I have also manually updated the records in these tables in an attempt to syncronize but after the next sucessful backup, copy and restore this monitoring data is not updating. Does anyone have any ideas as to what I am doing wrong or how I might rectify this situation.Moving to availability forum.|||
I took a shot at reproducing this issue. I could not reproduce the scenario that you describe, but here is some information that may help.
1) Executing sp_refresh_log_shipping_monitor probably hurt more than it helped in this case. There is a bug in this stored procedure that is fixed in SP2 which results in the data that is supposed to be refreshed on the monitor server actually being deleted.
2) After getting my local test monitor server into a bad state, the only way to recover was to remove log shipping and then add it again. When adding it back, you could bypass initializing the secondary database because the primary and secondary are already in synch. After doing this and running through one cycle of backing up a tlog, copy, and restore the monitor server once again had current information on the log shipped database.
Tom
This posting is provided "AS IS" with no warranties, and confers no rights.
Log shipping monitor our of sync SQL Server 2005
I have set up log shipping between two servers with a third serving as a monitoring server. Recently the monitoring for the eight databases that I am log shipping began to indicate that everything was failing. Upon further inventigation of the log_shipping_monitor_history_detail tables on the prinary and secondary everthing appears to working properly but I have been unable to resyncronize the monitoring. I have attempted to use the stored procedure sp_refresh_log_shipping_monitor to no avail, it does not appear to do anything with respect to the data in the dbo.log_shipping_primary_databases and log_shipping_monitor_primary tables on the primary server or the log_shipping_monitor_secondary and dbo.log_shipping_secondary_databases tables on the secondary. I have also manually updated the records in these tables in an attempt to syncronize but after the next sucessful backup, copy and restore this monitoring data is not updating. Does anyone have any ideas as to what I am doing wrong or how I might rectify this situation.Moving to availability forum.|||
I took a shot at reproducing this issue. I could not reproduce the scenario that you describe, but here is some information that may help.
1) Executing sp_refresh_log_shipping_monitor probably hurt more than it helped in this case. There is a bug in this stored procedure that is fixed in SP2 which results in the data that is supposed to be refreshed on the monitor server actually being deleted.
2) After getting my local test monitor server into a bad state, the only way to recover was to remove log shipping and then add it again. When adding it back, you could bypass initializing the secondary database because the primary and secondary are already in synch. After doing this and running through one cycle of backing up a tlog, copy, and restore the monitor server once again had current information on the log shipped database.
Tom
This posting is provided "AS IS" with no warranties, and confers no rights.
Log Shipping Monitor - 2005
Is the "Log Shipping Monitor" that was avaialable in SQL Server 2000
Enterprise Manager still available with SQL Server 2005. I installed Log
Shipping on a 2005 server and selected the monitor option but I can not find
the nice Log Shipping monitor that give you status on log shipping. I also
searched through the Books Online documentation and several online resources
and I have not found a definitive answer.
Please help.
Thanks!
ChrisHi Chris
"Cgal" wrote:
> Is the "Log Shipping Monitor" that was avaialable in SQL Server 2000
> Enterprise Manager still available with SQL Server 2005. I installed Log
> Shipping on a 2005 server and selected the monitor option but I can not find
> the nice Log Shipping monitor that give you status on log shipping. I also
> searched through the Books Online documentation and several online resources
> and I have not found a definitive answer.
> Please help.
> Thanks!
> Chris
In SQLServer 2005 there is a standard report called "Transaction Log
Shipping Status" that gives you the current status.
http://msdn2.microsoft.com/en-us/library/ms181149.aspx (steps 1-4) currently
gives information on how to show the report prior to SP2. You will need to
show the Object Explorer tab (view menu and select Object Explorer detals) to
get the reports button (on the tab's toolbar). The list of reports are
sensitive to the context which you have selected in the object explorer (F8)
so if you don't see this report you are probably not on the node for the
instance.
After SP2 you can right click the node for the instance and select
Reports/Standard Reports/Transaction Log Shipping Status
HTH
john|||John,
Thanks for the quick response.
I knew about the report that you referenced but I was hoping that there was
more. The report has no where near the functionality and usability of the
"Log Shipping Monitor" that came with SQL Server 2000.
Please let me know if there are any other tools for monitoring Log Shipping
beyond the report.
Thanks!
Chris
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:9C6B2961-67CB-4B3A-A822-C73899577EBD@.microsoft.com...
> Hi Chris
> "Cgal" wrote:
>> Is the "Log Shipping Monitor" that was avaialable in SQL Server 2000
>> Enterprise Manager still available with SQL Server 2005. I installed Log
>> Shipping on a 2005 server and selected the monitor option but I can not
>> find
>> the nice Log Shipping monitor that give you status on log shipping. I
>> also
>> searched through the Books Online documentation and several online
>> resources
>> and I have not found a definitive answer.
>> Please help.
>> Thanks!
>> Chris
> In SQLServer 2005 there is a standard report called "Transaction Log
> Shipping Status" that gives you the current status.
> http://msdn2.microsoft.com/en-us/library/ms181149.aspx (steps 1-4)
> currently
> gives information on how to show the report prior to SP2. You will need to
> show the Object Explorer tab (view menu and select Object Explorer detals)
> to
> get the reports button (on the tab's toolbar). The list of reports are
> sensitive to the context which you have selected in the object explorer
> (F8)
> so if you don't see this report you are probably not on the node for the
> instance.
> After SP2 you can right click the node for the instance and select
> Reports/Standard Reports/Transaction Log Shipping Status
> HTH
> john|||Hi, Chris,
I guess that you would like to add a monitor server in your log shipping
environment.
If I have misunderstood, please let me know.
In SQL Server 2005, to monitor log shipping configuration, adding the
monitor server is required. If you do not have a monitor server, you may
need to manually run the system procedures such as
sp_help_log_shipping_primary_database,
sp_help_log_shipping_primary_secondary,
sp_help_log_shipping_secondary_database, and
sp_help_log_shipping_secondary_primary etc to query the status of your log
shipping.
For more detailed information, you can refer to this article:
How to: Enable Log Shipping (SQL Server Management Studio)
http://msdn2.microsoft.com/en-us/library/ms190640.aspx
Understanding Log Shipping
http://msdn2.microsoft.com/en-us/library/ms187103.aspx
Monitoring Log Shipping
http://msdn2.microsoft.com/en-us/library/ms190224.aspx
Hope this helps. If you have any other questions or concerns, please feel
free to let me know. It is my pleasure to be of assistance.
Best regards,
Charles Wang
Microsoft Online Community Support
=====================================================Get notification to my posts through email? Please refer to:
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications
If you are using Outlook Express, please make sure you clear the check box
"Tools/Options/Read: Get 300 headers at a time" to see your reply promptly.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
======================================================When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
======================================================This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================|||Hi, Chris
Just check with you to see if the suggestions were helpful. Please let us
know if you would like further assistance.
Have a great day!
Charles Wang
Microsoft Online Partner Support
PLEASE NOTE: The partner managed newsgroups are provided
to assist with break/fix issues and simple how to questions.
We also love to hear your product feedback!
Let us know what you think by posting
- from the web interface: Partner Feedback
- from your newsreader:
microsoft.private.directaccess.partnerfeedback.
We look forward to hearing from you!
======================================================When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
======================================================This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================
Enterprise Manager still available with SQL Server 2005. I installed Log
Shipping on a 2005 server and selected the monitor option but I can not find
the nice Log Shipping monitor that give you status on log shipping. I also
searched through the Books Online documentation and several online resources
and I have not found a definitive answer.
Please help.
Thanks!
ChrisHi Chris
"Cgal" wrote:
> Is the "Log Shipping Monitor" that was avaialable in SQL Server 2000
> Enterprise Manager still available with SQL Server 2005. I installed Log
> Shipping on a 2005 server and selected the monitor option but I can not find
> the nice Log Shipping monitor that give you status on log shipping. I also
> searched through the Books Online documentation and several online resources
> and I have not found a definitive answer.
> Please help.
> Thanks!
> Chris
In SQLServer 2005 there is a standard report called "Transaction Log
Shipping Status" that gives you the current status.
http://msdn2.microsoft.com/en-us/library/ms181149.aspx (steps 1-4) currently
gives information on how to show the report prior to SP2. You will need to
show the Object Explorer tab (view menu and select Object Explorer detals) to
get the reports button (on the tab's toolbar). The list of reports are
sensitive to the context which you have selected in the object explorer (F8)
so if you don't see this report you are probably not on the node for the
instance.
After SP2 you can right click the node for the instance and select
Reports/Standard Reports/Transaction Log Shipping Status
HTH
john|||John,
Thanks for the quick response.
I knew about the report that you referenced but I was hoping that there was
more. The report has no where near the functionality and usability of the
"Log Shipping Monitor" that came with SQL Server 2000.
Please let me know if there are any other tools for monitoring Log Shipping
beyond the report.
Thanks!
Chris
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:9C6B2961-67CB-4B3A-A822-C73899577EBD@.microsoft.com...
> Hi Chris
> "Cgal" wrote:
>> Is the "Log Shipping Monitor" that was avaialable in SQL Server 2000
>> Enterprise Manager still available with SQL Server 2005. I installed Log
>> Shipping on a 2005 server and selected the monitor option but I can not
>> find
>> the nice Log Shipping monitor that give you status on log shipping. I
>> also
>> searched through the Books Online documentation and several online
>> resources
>> and I have not found a definitive answer.
>> Please help.
>> Thanks!
>> Chris
> In SQLServer 2005 there is a standard report called "Transaction Log
> Shipping Status" that gives you the current status.
> http://msdn2.microsoft.com/en-us/library/ms181149.aspx (steps 1-4)
> currently
> gives information on how to show the report prior to SP2. You will need to
> show the Object Explorer tab (view menu and select Object Explorer detals)
> to
> get the reports button (on the tab's toolbar). The list of reports are
> sensitive to the context which you have selected in the object explorer
> (F8)
> so if you don't see this report you are probably not on the node for the
> instance.
> After SP2 you can right click the node for the instance and select
> Reports/Standard Reports/Transaction Log Shipping Status
> HTH
> john|||Hi, Chris,
I guess that you would like to add a monitor server in your log shipping
environment.
If I have misunderstood, please let me know.
In SQL Server 2005, to monitor log shipping configuration, adding the
monitor server is required. If you do not have a monitor server, you may
need to manually run the system procedures such as
sp_help_log_shipping_primary_database,
sp_help_log_shipping_primary_secondary,
sp_help_log_shipping_secondary_database, and
sp_help_log_shipping_secondary_primary etc to query the status of your log
shipping.
For more detailed information, you can refer to this article:
How to: Enable Log Shipping (SQL Server Management Studio)
http://msdn2.microsoft.com/en-us/library/ms190640.aspx
Understanding Log Shipping
http://msdn2.microsoft.com/en-us/library/ms187103.aspx
Monitoring Log Shipping
http://msdn2.microsoft.com/en-us/library/ms190224.aspx
Hope this helps. If you have any other questions or concerns, please feel
free to let me know. It is my pleasure to be of assistance.
Best regards,
Charles Wang
Microsoft Online Community Support
=====================================================Get notification to my posts through email? Please refer to:
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications
If you are using Outlook Express, please make sure you clear the check box
"Tools/Options/Read: Get 300 headers at a time" to see your reply promptly.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
======================================================When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
======================================================This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================|||Hi, Chris
Just check with you to see if the suggestions were helpful. Please let us
know if you would like further assistance.
Have a great day!
Charles Wang
Microsoft Online Partner Support
PLEASE NOTE: The partner managed newsgroups are provided
to assist with break/fix issues and simple how to questions.
We also love to hear your product feedback!
Let us know what you think by posting
- from the web interface: Partner Feedback
- from your newsreader:
microsoft.private.directaccess.partnerfeedback.
We look forward to hearing from you!
======================================================When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
======================================================This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================
Log Shipping Monitor - 2005
Is the "Log Shipping Monitor" that was avaialable in SQL Server 2000
Enterprise Manager still available with SQL Server 2005. I installed Log
Shipping on a 2005 server and selected the monitor option but I can not find
the nice Log Shipping monitor that give you status on log shipping. I also
searched through the Books Online documentation and several online resources
and I have not found a definitive answer.
Please help.
Thanks!
Chris
Hi Chris
"Cgal" wrote:
> Is the "Log Shipping Monitor" that was avaialable in SQL Server 2000
> Enterprise Manager still available with SQL Server 2005. I installed Log
> Shipping on a 2005 server and selected the monitor option but I can not find
> the nice Log Shipping monitor that give you status on log shipping. I also
> searched through the Books Online documentation and several online resources
> and I have not found a definitive answer.
> Please help.
> Thanks!
> Chris
In SQLServer 2005 there is a standard report called "Transaction Log
Shipping Status" that gives you the current status.
http://msdn2.microsoft.com/en-us/library/ms181149.aspx (steps 1-4) currently
gives information on how to show the report prior to SP2. You will need to
show the Object Explorer tab (view menu and select Object Explorer detals) to
get the reports button (on the tab's toolbar). The list of reports are
sensitive to the context which you have selected in the object explorer (F8)
so if you don't see this report you are probably not on the node for the
instance.
After SP2 you can right click the node for the instance and select
Reports/Standard Reports/Transaction Log Shipping Status
HTH
john
|||John,
Thanks for the quick response.
I knew about the report that you referenced but I was hoping that there was
more. The report has no where near the functionality and usability of the
"Log Shipping Monitor" that came with SQL Server 2000.
Please let me know if there are any other tools for monitoring Log Shipping
beyond the report.
Thanks!
Chris
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:9C6B2961-67CB-4B3A-A822-C73899577EBD@.microsoft.com...
> Hi Chris
> "Cgal" wrote:
>
> In SQLServer 2005 there is a standard report called "Transaction Log
> Shipping Status" that gives you the current status.
> http://msdn2.microsoft.com/en-us/library/ms181149.aspx (steps 1-4)
> currently
> gives information on how to show the report prior to SP2. You will need to
> show the Object Explorer tab (view menu and select Object Explorer detals)
> to
> get the reports button (on the tab's toolbar). The list of reports are
> sensitive to the context which you have selected in the object explorer
> (F8)
> so if you don't see this report you are probably not on the node for the
> instance.
> After SP2 you can right click the node for the instance and select
> Reports/Standard Reports/Transaction Log Shipping Status
> HTH
> john
|||Hi, Chris,
I guess that you would like to add a monitor server in your log shipping
environment.
If I have misunderstood, please let me know.
In SQL Server 2005, to monitor log shipping configuration, adding the
monitor server is required. If you do not have a monitor server, you may
need to manually run the system procedures such as
sp_help_log_shipping_primary_database,
sp_help_log_shipping_primary_secondary,
sp_help_log_shipping_secondary_database, and
sp_help_log_shipping_secondary_primary etc to query the status of your log
shipping.
For more detailed information, you can refer to this article:
How to: Enable Log Shipping (SQL Server Management Studio)
http://msdn2.microsoft.com/en-us/library/ms190640.aspx
Understanding Log Shipping
http://msdn2.microsoft.com/en-us/library/ms187103.aspx
Monitoring Log Shipping
http://msdn2.microsoft.com/en-us/library/ms190224.aspx
Hope this helps. If you have any other questions or concerns, please feel
free to let me know. It is my pleasure to be of assistance.
Best regards,
Charles Wang
Microsoft Online Community Support
================================================== ===
Get notification to my posts through email? Please refer to:
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications
If you are using Outlook Express, please make sure you clear the check box
"Tools/Options/Read: Get 300 headers at a time" to see your reply promptly.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
================================================== ====
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
================================================== ====
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== ====
|||Hi, Chris
Just check with you to see if the suggestions were helpful. Please let us
know if you would like further assistance.
Have a great day!
Charles Wang
Microsoft Online Partner Support
PLEASE NOTE: The partner managed newsgroups are provided
to assist with break/fix issues and simple how to questions.
We also love to hear your product feedback!
Let us know what you think by posting
- from the web interface: Partner Feedback
- from your newsreader:
microsoft.private.directaccess.partnerfeedback.
We look forward to hearing from you!
================================================== ====
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
================================================== ====
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== ====
Enterprise Manager still available with SQL Server 2005. I installed Log
Shipping on a 2005 server and selected the monitor option but I can not find
the nice Log Shipping monitor that give you status on log shipping. I also
searched through the Books Online documentation and several online resources
and I have not found a definitive answer.
Please help.
Thanks!
Chris
Hi Chris
"Cgal" wrote:
> Is the "Log Shipping Monitor" that was avaialable in SQL Server 2000
> Enterprise Manager still available with SQL Server 2005. I installed Log
> Shipping on a 2005 server and selected the monitor option but I can not find
> the nice Log Shipping monitor that give you status on log shipping. I also
> searched through the Books Online documentation and several online resources
> and I have not found a definitive answer.
> Please help.
> Thanks!
> Chris
In SQLServer 2005 there is a standard report called "Transaction Log
Shipping Status" that gives you the current status.
http://msdn2.microsoft.com/en-us/library/ms181149.aspx (steps 1-4) currently
gives information on how to show the report prior to SP2. You will need to
show the Object Explorer tab (view menu and select Object Explorer detals) to
get the reports button (on the tab's toolbar). The list of reports are
sensitive to the context which you have selected in the object explorer (F8)
so if you don't see this report you are probably not on the node for the
instance.
After SP2 you can right click the node for the instance and select
Reports/Standard Reports/Transaction Log Shipping Status
HTH
john
|||John,
Thanks for the quick response.
I knew about the report that you referenced but I was hoping that there was
more. The report has no where near the functionality and usability of the
"Log Shipping Monitor" that came with SQL Server 2000.
Please let me know if there are any other tools for monitoring Log Shipping
beyond the report.
Thanks!
Chris
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:9C6B2961-67CB-4B3A-A822-C73899577EBD@.microsoft.com...
> Hi Chris
> "Cgal" wrote:
>
> In SQLServer 2005 there is a standard report called "Transaction Log
> Shipping Status" that gives you the current status.
> http://msdn2.microsoft.com/en-us/library/ms181149.aspx (steps 1-4)
> currently
> gives information on how to show the report prior to SP2. You will need to
> show the Object Explorer tab (view menu and select Object Explorer detals)
> to
> get the reports button (on the tab's toolbar). The list of reports are
> sensitive to the context which you have selected in the object explorer
> (F8)
> so if you don't see this report you are probably not on the node for the
> instance.
> After SP2 you can right click the node for the instance and select
> Reports/Standard Reports/Transaction Log Shipping Status
> HTH
> john
|||Hi, Chris,
I guess that you would like to add a monitor server in your log shipping
environment.
If I have misunderstood, please let me know.
In SQL Server 2005, to monitor log shipping configuration, adding the
monitor server is required. If you do not have a monitor server, you may
need to manually run the system procedures such as
sp_help_log_shipping_primary_database,
sp_help_log_shipping_primary_secondary,
sp_help_log_shipping_secondary_database, and
sp_help_log_shipping_secondary_primary etc to query the status of your log
shipping.
For more detailed information, you can refer to this article:
How to: Enable Log Shipping (SQL Server Management Studio)
http://msdn2.microsoft.com/en-us/library/ms190640.aspx
Understanding Log Shipping
http://msdn2.microsoft.com/en-us/library/ms187103.aspx
Monitoring Log Shipping
http://msdn2.microsoft.com/en-us/library/ms190224.aspx
Hope this helps. If you have any other questions or concerns, please feel
free to let me know. It is my pleasure to be of assistance.
Best regards,
Charles Wang
Microsoft Online Community Support
================================================== ===
Get notification to my posts through email? Please refer to:
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications
If you are using Outlook Express, please make sure you clear the check box
"Tools/Options/Read: Get 300 headers at a time" to see your reply promptly.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
================================================== ====
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
================================================== ====
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== ====
|||Hi, Chris
Just check with you to see if the suggestions were helpful. Please let us
know if you would like further assistance.
Have a great day!
Charles Wang
Microsoft Online Partner Support
PLEASE NOTE: The partner managed newsgroups are provided
to assist with break/fix issues and simple how to questions.
We also love to hear your product feedback!
Let us know what you think by posting
- from the web interface: Partner Feedback
- from your newsreader:
microsoft.private.directaccess.partnerfeedback.
We look forward to hearing from you!
================================================== ====
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
================================================== ====
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== ====
Log Shipping Monitor - 2005
Is the "Log Shipping Monitor" that was avaialable in SQL Server 2000
Enterprise Manager still available with SQL Server 2005. I installed Log
Shipping on a 2005 server and selected the monitor option but I can not find
the nice Log Shipping monitor that give you status on log shipping. I also
searched through the Books Online documentation and several online resources
and I have not found a definitive answer.
Please help.
Thanks!
ChrisHi Chris
"Cgal" wrote:
> Is the "Log Shipping Monitor" that was avaialable in SQL Server 2000
> Enterprise Manager still available with SQL Server 2005. I installed Log
> Shipping on a 2005 server and selected the monitor option but I can not fi
nd
> the nice Log Shipping monitor that give you status on log shipping. I als
o
> searched through the Books Online documentation and several online resourc
es
> and I have not found a definitive answer.
> Please help.
> Thanks!
> Chris
In SQLServer 2005 there is a standard report called "Transaction Log
Shipping Status" that gives you the current status.
http://msdn2.microsoft.com/en-us/library/ms181149.aspx (steps 1-4) currently
gives information on how to show the report prior to SP2. You will need to
show the Object Explorer tab (view menu and select Object Explorer detals) t
o
get the reports button (on the tab's toolbar). The list of reports are
sensitive to the context which you have selected in the object explorer (F8)
so if you don't see this report you are probably not on the node for the
instance.
After SP2 you can right click the node for the instance and select
Reports/Standard Reports/Transaction Log Shipping Status
HTH
john|||John,
Thanks for the quick response.
I knew about the report that you referenced but I was hoping that there was
more. The report has no where near the functionality and usability of the
"Log Shipping Monitor" that came with SQL Server 2000.
Please let me know if there are any other tools for monitoring Log Shipping
beyond the report.
Thanks!
Chris
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:9C6B2961-67CB-4B3A-A822-C73899577EBD@.microsoft.com...
> Hi Chris
> "Cgal" wrote:
>
> In SQLServer 2005 there is a standard report called "Transaction Log
> Shipping Status" that gives you the current status.
> http://msdn2.microsoft.com/en-us/library/ms181149.aspx (steps 1-4)
> currently
> gives information on how to show the report prior to SP2. You will need to
> show the Object Explorer tab (view menu and select Object Explorer detals)
> to
> get the reports button (on the tab's toolbar). The list of reports are
> sensitive to the context which you have selected in the object explorer
> (F8)
> so if you don't see this report you are probably not on the node for the
> instance.
> After SP2 you can right click the node for the instance and select
> Reports/Standard Reports/Transaction Log Shipping Status
> HTH
> john|||Hi, Chris,
I guess that you would like to add a monitor server in your log shipping
environment.
If I have misunderstood, please let me know.
In SQL Server 2005, to monitor log shipping configuration, adding the
monitor server is required. If you do not have a monitor server, you may
need to manually run the system procedures such as
sp_help_log_shipping_primary_database,
sp_help_log_shipping_primary_secondary,
sp_help_log_shipping_secondary_database,
and
sp_help_log_shipping_secondary_primary etc to query the status of your log
shipping.
For more detailed information, you can refer to this article:
How to: Enable Log Shipping (SQL Server Management Studio)
http://msdn2.microsoft.com/en-us/library/ms190640.aspx
Understanding Log Shipping
http://msdn2.microsoft.com/en-us/library/ms187103.aspx
Monitoring Log Shipping
http://msdn2.microsoft.com/en-us/library/ms190224.aspx
Hope this helps. If you have any other questions or concerns, please feel
free to let me know. It is my pleasure to be of assistance.
Best regards,
Charles Wang
Microsoft Online Community Support
========================================
=============
Get notification to my posts through email? Please refer to:
http://msdn.microsoft.com/subscript...ault.aspx#notif
ications
If you are using Outlook Express, please make sure you clear the check box
"Tools/Options/Read: Get 300 headers at a time" to see your reply promptly.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscript...t/default.aspx.
========================================
==============
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
========================================
==============
This posting is provided "AS IS" with no warranties, and confers no rights.
========================================
==============|||Hi, Chris
Just check with you to see if the suggestions were helpful. Please let us
know if you would like further assistance.
Have a great day!
Charles Wang
Microsoft Online Partner Support
PLEASE NOTE: The partner managed newsgroups are provided
to assist with break/fix issues and simple how to questions.
We also love to hear your product feedback!
Let us know what you think by posting
- from the web interface: Partner Feedback
- from your newsreader:
microsoft.private.directaccess.partnerfeedback.
We look forward to hearing from you!
========================================
==============
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
========================================
==============
This posting is provided "AS IS" with no warranties, and confers no rights.
========================================
==============
Enterprise Manager still available with SQL Server 2005. I installed Log
Shipping on a 2005 server and selected the monitor option but I can not find
the nice Log Shipping monitor that give you status on log shipping. I also
searched through the Books Online documentation and several online resources
and I have not found a definitive answer.
Please help.
Thanks!
ChrisHi Chris
"Cgal" wrote:
> Is the "Log Shipping Monitor" that was avaialable in SQL Server 2000
> Enterprise Manager still available with SQL Server 2005. I installed Log
> Shipping on a 2005 server and selected the monitor option but I can not fi
nd
> the nice Log Shipping monitor that give you status on log shipping. I als
o
> searched through the Books Online documentation and several online resourc
es
> and I have not found a definitive answer.
> Please help.
> Thanks!
> Chris
In SQLServer 2005 there is a standard report called "Transaction Log
Shipping Status" that gives you the current status.
http://msdn2.microsoft.com/en-us/library/ms181149.aspx (steps 1-4) currently
gives information on how to show the report prior to SP2. You will need to
show the Object Explorer tab (view menu and select Object Explorer detals) t
o
get the reports button (on the tab's toolbar). The list of reports are
sensitive to the context which you have selected in the object explorer (F8)
so if you don't see this report you are probably not on the node for the
instance.
After SP2 you can right click the node for the instance and select
Reports/Standard Reports/Transaction Log Shipping Status
HTH
john|||John,
Thanks for the quick response.
I knew about the report that you referenced but I was hoping that there was
more. The report has no where near the functionality and usability of the
"Log Shipping Monitor" that came with SQL Server 2000.
Please let me know if there are any other tools for monitoring Log Shipping
beyond the report.
Thanks!
Chris
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:9C6B2961-67CB-4B3A-A822-C73899577EBD@.microsoft.com...
> Hi Chris
> "Cgal" wrote:
>
> In SQLServer 2005 there is a standard report called "Transaction Log
> Shipping Status" that gives you the current status.
> http://msdn2.microsoft.com/en-us/library/ms181149.aspx (steps 1-4)
> currently
> gives information on how to show the report prior to SP2. You will need to
> show the Object Explorer tab (view menu and select Object Explorer detals)
> to
> get the reports button (on the tab's toolbar). The list of reports are
> sensitive to the context which you have selected in the object explorer
> (F8)
> so if you don't see this report you are probably not on the node for the
> instance.
> After SP2 you can right click the node for the instance and select
> Reports/Standard Reports/Transaction Log Shipping Status
> HTH
> john|||Hi, Chris,
I guess that you would like to add a monitor server in your log shipping
environment.
If I have misunderstood, please let me know.
In SQL Server 2005, to monitor log shipping configuration, adding the
monitor server is required. If you do not have a monitor server, you may
need to manually run the system procedures such as
sp_help_log_shipping_primary_database,
sp_help_log_shipping_primary_secondary,
sp_help_log_shipping_secondary_database,
and
sp_help_log_shipping_secondary_primary etc to query the status of your log
shipping.
For more detailed information, you can refer to this article:
How to: Enable Log Shipping (SQL Server Management Studio)
http://msdn2.microsoft.com/en-us/library/ms190640.aspx
Understanding Log Shipping
http://msdn2.microsoft.com/en-us/library/ms187103.aspx
Monitoring Log Shipping
http://msdn2.microsoft.com/en-us/library/ms190224.aspx
Hope this helps. If you have any other questions or concerns, please feel
free to let me know. It is my pleasure to be of assistance.
Best regards,
Charles Wang
Microsoft Online Community Support
========================================
=============
Get notification to my posts through email? Please refer to:
http://msdn.microsoft.com/subscript...ault.aspx#notif
ications
If you are using Outlook Express, please make sure you clear the check box
"Tools/Options/Read: Get 300 headers at a time" to see your reply promptly.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscript...t/default.aspx.
========================================
==============
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
========================================
==============
This posting is provided "AS IS" with no warranties, and confers no rights.
========================================
==============|||Hi, Chris
Just check with you to see if the suggestions were helpful. Please let us
know if you would like further assistance.
Have a great day!
Charles Wang
Microsoft Online Partner Support
PLEASE NOTE: The partner managed newsgroups are provided
to assist with break/fix issues and simple how to questions.
We also love to hear your product feedback!
Let us know what you think by posting
- from the web interface: Partner Feedback
- from your newsreader:
microsoft.private.directaccess.partnerfeedback.
We look forward to hearing from you!
========================================
==============
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
========================================
==============
This posting is provided "AS IS" with no warranties, and confers no rights.
========================================
==============
Log shipping monitor
Hello,
I am just setting up log shipping on our new web servers. I have S1
primary, S2 secondary and S3 monitoring. The log shipping is working OK.
Logs are being backed up on S1, being copied to S2 and then loaded
successfully.
In my Log Shipping Monitor, on the Log Shipping Pair Properties Status tab,
the last backup file is still showing first_file_00000000000.trn. The last
file copied and Last file loaded on the are correct. When I am viewing the
monitor thru' EM on S3, and on the Source tab try to view the Backup
Schedule, the button is not disabled but does not display anything. If I
view the monitor thru' EM on S1 and view the Backup Schedule it displays the
schedule.
The only thing I have noticed is that the graphic at the top of the monitor
is showing (LOCAL).dbname --> S2.dbname. I would have expected it to show
S1.dbname --> S2.dbname. Is it trying to look at the backup on (LOCAL) so
looking on S3 which is just the monitoring server.
Anyone else seen this? Thanks for any help you can give me.
ClaireB
Sorry - meant to add I am looking at the graphic on S3.
"ClaireB" wrote:
> Hello,
> I am just setting up log shipping on our new web servers. I have S1
> primary, S2 secondary and S3 monitoring. The log shipping is working OK.
> Logs are being backed up on S1, being copied to S2 and then loaded
> successfully.
> In my Log Shipping Monitor, on the Log Shipping Pair Properties Status tab,
> the last backup file is still showing first_file_00000000000.trn. The last
> file copied and Last file loaded on the are correct. When I am viewing the
> monitor thru' EM on S3, and on the Source tab try to view the Backup
> Schedule, the button is not disabled but does not display anything. If I
> view the monitor thru' EM on S1 and view the Backup Schedule it displays the
> schedule.
> The only thing I have noticed is that the graphic at the top of the monitor
> is showing (LOCAL).dbname --> S2.dbname. I would have expected it to show
> S1.dbname --> S2.dbname. Is it trying to look at the backup on (LOCAL) so
> looking on S3 which is just the monitoring server.
> Anyone else seen this? Thanks for any help you can give me.
> ClaireB
I am just setting up log shipping on our new web servers. I have S1
primary, S2 secondary and S3 monitoring. The log shipping is working OK.
Logs are being backed up on S1, being copied to S2 and then loaded
successfully.
In my Log Shipping Monitor, on the Log Shipping Pair Properties Status tab,
the last backup file is still showing first_file_00000000000.trn. The last
file copied and Last file loaded on the are correct. When I am viewing the
monitor thru' EM on S3, and on the Source tab try to view the Backup
Schedule, the button is not disabled but does not display anything. If I
view the monitor thru' EM on S1 and view the Backup Schedule it displays the
schedule.
The only thing I have noticed is that the graphic at the top of the monitor
is showing (LOCAL).dbname --> S2.dbname. I would have expected it to show
S1.dbname --> S2.dbname. Is it trying to look at the backup on (LOCAL) so
looking on S3 which is just the monitoring server.
Anyone else seen this? Thanks for any help you can give me.
ClaireB
Sorry - meant to add I am looking at the graphic on S3.
"ClaireB" wrote:
> Hello,
> I am just setting up log shipping on our new web servers. I have S1
> primary, S2 secondary and S3 monitoring. The log shipping is working OK.
> Logs are being backed up on S1, being copied to S2 and then loaded
> successfully.
> In my Log Shipping Monitor, on the Log Shipping Pair Properties Status tab,
> the last backup file is still showing first_file_00000000000.trn. The last
> file copied and Last file loaded on the are correct. When I am viewing the
> monitor thru' EM on S3, and on the Source tab try to view the Backup
> Schedule, the button is not disabled but does not display anything. If I
> view the monitor thru' EM on S1 and view the Backup Schedule it displays the
> schedule.
> The only thing I have noticed is that the graphic at the top of the monitor
> is showing (LOCAL).dbname --> S2.dbname. I would have expected it to show
> S1.dbname --> S2.dbname. Is it trying to look at the backup on (LOCAL) so
> looking on S3 which is just the monitoring server.
> Anyone else seen this? Thanks for any help you can give me.
> ClaireB
Log Shipping Monitor
Hello,
I have configured a SQL Server for Log Shipping using the Database Maintenan
ce Planner Wizard. Now a Log Shipping Monitor object appears below the Manag
ement folder. How do I reverse this process, and make the Log Shipping Monit
or disappear? In other word
s I want to revert back to the state SQL Server was in before I ran the Data
base Maintenance Planner.
Thanks,
Jerome SmithHello all,
I'll answer my own question for everybody's benefit. Eliminating the Log Shi
pping Monitor is equivalent to eliminating all Log Shipping pairs from the L
og Shipping system database. This is done with the stored procedure:
sp_delete_log_shipping_primary
located in the msdb system database.
Following is the help article.
Cheers,
Jerome
sp_delete_log_shipping_primary
Deletes the primary server from the log_shipping_primaries table.
Syntax
sp_delete_log_shipping_primary
[ @.primary_server_name = ] 'primary_server_name' ,
[ @.primary_database_name = ] 'primary_database_name' ,
{ [ @.delete_secondaries = ] delete_secondaries }
Arguments
[@.primary_server_name =] 'primary_server_name'
Is the name of the primary server. primary_server_name is sysname.
[@.primary_database_name =] 'primary_database_name'
Is the name of the secondary server. primary_database_name is sysname.
[@.delete_secondaries =] delete_secondaries
Specifies that the delete action is also applied to log_shipping_secondaries
table. delete_secondaries is bit, with a default of zero (0).
Return Code Values
0 (success) or 1 (failure)
Remarks
This stored procedure only removes the primary and secondary server from the
monitor. Log shipping still has to be removed from the primary and secondar
y servers.
sp_delete_log_shipping_primary deletes a log shipping primary table. If ther
e are corresponding rows in the log_shipping_databases table, delete_seconda
ries must be set to one (1) or the stored procedure will fail.
Permissions
Only members of the sysadmin fixed server role can execute sp_delete_log_shi
pping_primaries.
Examples
This example deletes the source database "pubs" from the server "source". Th
ere are no corresponding rows in log_shipping_secondaries table.
EXEC sp_delete_log_shipping_primary @.primary_server_name = N'source', @.pri
mary_database_name = N'pubs'
?1988-2000 Microsoft Corporation. All Rights Reserved.|||Actually, when nothing has gone wrong, the easiest way is in Enterprise
Manager:
Management->Database Maintenance Plans->Right-Click->Properties->Log
Shipping->Remove Log Shipping.
Then delete Plan.
Jerome
"Jerome Smith" <jerosmith@.hotmail.com> escribi en el mensaje
news:3B6447C3-7819-4F31-983B-7BDD84D2311F@.microsoft.com...
> Hello all,
> I'll answer my own question for everybody's benefit. Eliminating the Log
Shipping Monitor is equivalent to eliminating all Log Shipping pairs from
the Log Shipping system database. This is done with the stored procedure:
> sp_delete_log_shipping_primary
> located in the msdb system database.
> Following is the help article.
> Cheers,
> Jerome
> sp_delete_log_shipping_primary
> Deletes the primary server from the log_shipping_primaries table.
> Syntax
> sp_delete_log_shipping_primary
> [ @.primary_server_name = ] 'primary_server_name' ,
> [ @.primary_database_name = ] 'primary_database_name' ,
> { [ @.delete_secondaries = ] delete_secondaries }
> Arguments
> [@.primary_server_name =] 'primary_server_name'
> Is the name of the primary server. primary_server_name is sysname.
> [@.primary_database_name =] 'primary_database_name'
> Is the name of the secondary server. primary_database_name is sysname.
> [@.delete_secondaries =] delete_secondaries
> Specifies that the delete action is also applied to
log_shipping_secondaries table. delete_secondaries is bit, with a default of
zero (0).
> Return Code Values
> 0 (success) or 1 (failure)
> Remarks
> This stored procedure only removes the primary and secondary server from
the monitor. Log shipping still has to be removed from the primary and
secondary servers.
> sp_delete_log_shipping_primary deletes a log shipping primary table. If
there are corresponding rows in the log_shipping_databases table,
delete_secondaries must be set to one (1) or the stored procedure will fail.
> Permissions
> Only members of the sysadmin fixed server role can execute
sp_delete_log_shipping_primaries.
> Examples
> This example deletes the source database "pubs" from the server "source".
There are no corresponding rows in log_shipping_secondaries table.
> EXEC sp_delete_log_shipping_primary @.primary_server_name = N'source',
@.primary_database_name = N'pubs'
> 1988-2000 Microsoft Corporation. All Rights Reserved.
>
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.629 / Virus Database: 403 - Release Date: 17-03-2004
I have configured a SQL Server for Log Shipping using the Database Maintenan
ce Planner Wizard. Now a Log Shipping Monitor object appears below the Manag
ement folder. How do I reverse this process, and make the Log Shipping Monit
or disappear? In other word
s I want to revert back to the state SQL Server was in before I ran the Data
base Maintenance Planner.
Thanks,
Jerome SmithHello all,
I'll answer my own question for everybody's benefit. Eliminating the Log Shi
pping Monitor is equivalent to eliminating all Log Shipping pairs from the L
og Shipping system database. This is done with the stored procedure:
sp_delete_log_shipping_primary
located in the msdb system database.
Following is the help article.
Cheers,
Jerome
sp_delete_log_shipping_primary
Deletes the primary server from the log_shipping_primaries table.
Syntax
sp_delete_log_shipping_primary
[ @.primary_server_name = ] 'primary_server_name' ,
[ @.primary_database_name = ] 'primary_database_name' ,
{ [ @.delete_secondaries = ] delete_secondaries }
Arguments
[@.primary_server_name =] 'primary_server_name'
Is the name of the primary server. primary_server_name is sysname.
[@.primary_database_name =] 'primary_database_name'
Is the name of the secondary server. primary_database_name is sysname.
[@.delete_secondaries =] delete_secondaries
Specifies that the delete action is also applied to log_shipping_secondaries
table. delete_secondaries is bit, with a default of zero (0).
Return Code Values
0 (success) or 1 (failure)
Remarks
This stored procedure only removes the primary and secondary server from the
monitor. Log shipping still has to be removed from the primary and secondar
y servers.
sp_delete_log_shipping_primary deletes a log shipping primary table. If ther
e are corresponding rows in the log_shipping_databases table, delete_seconda
ries must be set to one (1) or the stored procedure will fail.
Permissions
Only members of the sysadmin fixed server role can execute sp_delete_log_shi
pping_primaries.
Examples
This example deletes the source database "pubs" from the server "source". Th
ere are no corresponding rows in log_shipping_secondaries table.
EXEC sp_delete_log_shipping_primary @.primary_server_name = N'source', @.pri
mary_database_name = N'pubs'
?1988-2000 Microsoft Corporation. All Rights Reserved.|||Actually, when nothing has gone wrong, the easiest way is in Enterprise
Manager:
Management->Database Maintenance Plans->Right-Click->Properties->Log
Shipping->Remove Log Shipping.
Then delete Plan.
Jerome
"Jerome Smith" <jerosmith@.hotmail.com> escribi en el mensaje
news:3B6447C3-7819-4F31-983B-7BDD84D2311F@.microsoft.com...
> Hello all,
> I'll answer my own question for everybody's benefit. Eliminating the Log
Shipping Monitor is equivalent to eliminating all Log Shipping pairs from
the Log Shipping system database. This is done with the stored procedure:
> sp_delete_log_shipping_primary
> located in the msdb system database.
> Following is the help article.
> Cheers,
> Jerome
> sp_delete_log_shipping_primary
> Deletes the primary server from the log_shipping_primaries table.
> Syntax
> sp_delete_log_shipping_primary
> [ @.primary_server_name = ] 'primary_server_name' ,
> [ @.primary_database_name = ] 'primary_database_name' ,
> { [ @.delete_secondaries = ] delete_secondaries }
> Arguments
> [@.primary_server_name =] 'primary_server_name'
> Is the name of the primary server. primary_server_name is sysname.
> [@.primary_database_name =] 'primary_database_name'
> Is the name of the secondary server. primary_database_name is sysname.
> [@.delete_secondaries =] delete_secondaries
> Specifies that the delete action is also applied to
log_shipping_secondaries table. delete_secondaries is bit, with a default of
zero (0).
> Return Code Values
> 0 (success) or 1 (failure)
> Remarks
> This stored procedure only removes the primary and secondary server from
the monitor. Log shipping still has to be removed from the primary and
secondary servers.
> sp_delete_log_shipping_primary deletes a log shipping primary table. If
there are corresponding rows in the log_shipping_databases table,
delete_secondaries must be set to one (1) or the stored procedure will fail.
> Permissions
> Only members of the sysadmin fixed server role can execute
sp_delete_log_shipping_primaries.
> Examples
> This example deletes the source database "pubs" from the server "source".
There are no corresponding rows in log_shipping_secondaries table.
> EXEC sp_delete_log_shipping_primary @.primary_server_name = N'source',
@.primary_database_name = N'pubs'
> 1988-2000 Microsoft Corporation. All Rights Reserved.
>
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.629 / Virus Database: 403 - Release Date: 17-03-2004
Subscribe to:
Comments (Atom)