Log shipping using Enterpirse Ed. Monitor DB getting out of sync

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

Log Shipping Question

Using Log shipping via SQL Ent Edition, do all your users have to be disconnected from the destination server the logs are being pushed to?

Say, user x is pulling a report from the server, and it takes 2 minutes, after 1 minutes the scedualed log ship needs to take place, will the log ship fail? will the user get kicked off? or will the logs be applied like nothing happend since its read only?

Anyones that used log shipping alot let me know! Thanks

ChrisI believe because you leave the destination database in recoverable mode, users can not query it - see links for more details

http://support.microsoft.com/default.aspx?scid=kb;en-us;314515

http://www.sql-server-performance.com/sql_server_log_shipping.asp

http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/logship1.mspx

HTH|||And also this Q&A - http://www.sql-server-performance.com/q&a37.asp|||With Log Shipping, the destination db's are read only. Your users can query them as much as they like - the only stipulation is that they can't have an active connection to a database while it's logs are being restored - I simply have a process that kills any connections to the db before I restore the logs - and that takes care of the issue. Hope this helps.

Nick DeAngelo|||Refer to the link provided by me to kill those SPIDs before restoring the log.|||Thanks for pointing that out Nick, I forgot about that

Log Shipping (SQL 2000) btwn OS versions?

Has anyone noticed any problems logshipping in a SQL 2k Ent. Ed.
environment with Windows 2k to a SQL 2k Ent. Ed. with Windows 2003?
Thanks!yellowbug wrote:
> Has anyone noticed any problems logshipping in a SQL 2k Ent. Ed.
> environment with Windows 2k to a SQL 2k Ent. Ed. with Windows 2003?
> Thanks!
>
Care to be more specific? What sort of problems?
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||We are doing a data center migration to a new location and I was hoping
to upgrade our disaster recovery servers to windows 2003 during this
migration. However the front end machines will be on Windows 2000 for
at least a few more months. So I thought I'd throw a feeler out there
and see if anyone has had any problems with this type of configuration.
Thanks |||yellowbug wrote:
> We are doing a data center migration to a new location and I was hoping
> to upgrade our disaster recovery servers to windows 2003 during this
> migration. However the front end machines will be on Windows 2000 for
> at least a few more months. So I thought I'd throw a feeler out there
> and see if anyone has had any problems with this type of configuration.
> Thanks
>
SQL backups are just files to the OS, nor does the OS have anything to
do with the restore of those backups. Are you using a home-grown log
shipping method, or the wizard-driven stuff that SQL provides? Either
way, I don't foresee that you'd have any problems due to the different
OS versions.
Tracy McKibben
MCDBA
http://www.realsqlguy.com

Log Shipping (SQL 2000) btwn OS versions?

Has anyone noticed any problems logshipping in a SQL 2k Ent. Ed.
environment with Windows 2k to a SQL 2k Ent. Ed. with Windows 2003?
Thanks!yellowbug wrote:
> Has anyone noticed any problems logshipping in a SQL 2k Ent. Ed.
> environment with Windows 2k to a SQL 2k Ent. Ed. with Windows 2003?
> Thanks!
>
Care to be more specific? What sort of problems?
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||We are doing a data center migration to a new location and I was hoping
to upgrade our disaster recovery servers to windows 2003 during this
migration. However the front end machines will be on windows 2000 for
at least a few more months. So I thought I'd throw a feeler out there
and see if anyone has had any problems with this type of configuration.
Thanks :)|||yellowbug wrote:
> We are doing a data center migration to a new location and I was hoping
> to upgrade our disaster recovery servers to windows 2003 during this
> migration. However the front end machines will be on windows 2000 for
> at least a few more months. So I thought I'd throw a feeler out there
> and see if anyone has had any problems with this type of configuration.
> Thanks :)
>
SQL backups are just files to the OS, nor does the OS have anything to
do with the restore of those backups. Are you using a home-grown log
shipping method, or the wizard-driven stuff that SQL provides? Either
way, I don't foresee that you'd have any problems due to the different
OS versions.
Tracy McKibben
MCDBA
http://www.realsqlguy.com