Logshipping issue

We are using SQL2005 Logshipping between our primary and secondary SQL
server. It works great but we do have one problem.
The systemdatabases can't be configured for logshipping by design. If I
create a new user or change something on an exsisting user this is not been
updated on my secondary server, because this is saved in the master database.
I can't just create the same user on the secondary server because all
userdatabase is readonly so I can't grant a user access on userdatabases.
How do you handle this issue? Do I have to reconfigure Logshipping everytime
I make changed in my master database?There is no problem if you just add a new user in a user database for an
existing login. But you have to manage any change you may make to the master
database. This includes adding a new login or any change to a login SID that
may screw up the mapping between the login and its users.
Take a look at these two KB articles and the discussions of sp_resolve_logins:
http://support.microsoft.com/kb/321247/en-us
http://support.microsoft.com/kb/314515/en-us
Linchi
"Thomas" wrote:
> We are using SQL2005 Logshipping between our primary and secondary SQL
> server. It works great but we do have one problem.
> The systemdatabases can't be configured for logshipping by design. If I
> create a new user or change something on an exsisting user this is not been
> updated on my secondary server, because this is saved in the master database.
> I can't just create the same user on the secondary server because all
> userdatabase is readonly so I can't grant a user access on userdatabases.
> How do you handle this issue? Do I have to reconfigure Logshipping everytime
> I make changed in my master database?

Logshipping Help Needed

I am setting up log shipping between a primary server and two secondaries.

The first (secondary ) is applying the logs fine but the second is generating the following error.

[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3154: [Microsoft][ODBC SQL Server Driver][SQL Server]The backup set holds a backup of a database other than the existing 'CDE2' database.
[Microsoft][ODBC SQL Server Driver][SQL Server]RESTORE LOG is terminating abnormally.

the logshipping monitor says it failes to apply first_file_0000000000...Trn

I have seen this listed on MS KB Base Article - 311801 .

and have followed all the suggestions to resolve this issue including seperate folders for each log ship but to no avail.

Any help would be greatly appreciated.

Thanks in advanceDIsable the LS and apply full backup on secondary server, then enable LS again.sql

Logshipping From a Cluster to a Cluster

Currently have 2 clusters for sql server 2000 enterprise
edition with one being my primary database server and
another at a DR site.
Is there any limitation which would prevent me from
logshipping my primary cluster to the secondary cluster?
Any violation of a best practice that you might see.
The clusters are configured as an active/passive cluster.
Any special tips or concerns/recommendations?I have never done that , but I think you should probably make sure that the
network share for the backups is a clustered network share, so it will be
available during failover...
--
Wayne Snyder, MCDBA, SQL Server MVP
Computer Education Services Corporation (CESC), Charlotte, NC
www.computeredservices.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Jack Snow" <mrbrew5510@.hotmail.com> wrote in message
news:OABNb.57764$G04.12571479@.news4.srv.hcvlny.cv.net...
> Currently have 2 clusters for sql server 2000 enterprise
> edition with one being my primary database server and
> another at a DR site.
> Is there any limitation which would prevent me from
> logshipping my primary cluster to the secondary cluster?
> Any violation of a best practice that you might see.
> The clusters are configured as an active/passive cluster.
> Any special tips or concerns/recommendations?
>|||jack,
a couple of comments :-
if you are running statements like SELECT INTO or BCP into
on your primary server - these will not be log shipped as
they are 'non-logged' or 'minimally logged' operations.
Also, think how you would change your application to point
at the standby server if you did ever need to fail over ?
Normal log-shipping practice would be to rename your SQL
Server on the standby to be the same as the offline
primary server - this would be more complicated on a
cluster - you would probably have to repoint all your
application connections to the existing name of the
standby SQL Server. Would this mean changes on your
middle-tier, or changes on each SQL user's client network
utility ?
Hope this helps.
>--Original Message--
>Currently have 2 clusters for sql server 2000 enterprise
>edition with one being my primary database server and
>another at a DR site.
>Is there any limitation which would prevent me from
>logshipping my primary cluster to the secondary cluster?
>Any violation of a best practice that you might see.
> The clusters are configured as an active/passive cluster.
>Any special tips or concerns/recommendations?
>
>.
>

Logshipping From a Cluster to a Cluster

Currently have 2 clusters for sql server 2000 enterprise
edition with one being my primary database server and
another at a DR site.
Is there any limitation which would prevent me from
logshipping my primary cluster to the secondary cluster?
Any violation of a best practice that you might see.
The clusters are configured as an active/passive cluster.
Any special tips or concerns/recommendations?I have never done that , but I think you should probably make sure that the
network share for the backups is a clustered network share, so it will be
available during failover...
Wayne Snyder, MCDBA, SQL Server MVP
Computer Education Services Corporation (CESC), Charlotte, NC
www.computeredservices.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Jack Snow" <mrbrew5510@.hotmail.com> wrote in message
news:OABNb.57764$G04.12571479@.news4.srv.hcvlny.cv.net...

quote:

---

> Currently have 2 clusters for sql server 2000 enterprise
> edition with one being my primary database server and
> another at a DR site.
> Is there any limitation which would prevent me from
> logshipping my primary cluster to the secondary cluster?
> Any violation of a best practice that you might see.
> The clusters are configured as an active/passive cluster.
> Any special tips or concerns/recommendations?
>

---

sql