March 9, 2010 at 10:58 am
Hi,
On Primary, we have MOSS 2007 in Server A and it's SQL databases on Server B.
On Secondary, we have MOSS 2007 in Server C and it's SQL databases on Server D.
Now the two sites primary & DR site are similar including database names for content database. Performed below steps for configuring log shipping:
1. On secondary, Stop the MOSS services on Server C
2.On secondary, Delete the content database on Server D.
3.On primary, Take the full backup of the live content database on Server B, copy the backup file to Secondary SQL Server Server D.
4. On Secondary, Restore the content database with NORECOVERY option.
5.On primary, configure the log shipping using the Log shipping wizard.
Now evrything is working fine But we are getting the below warning on DR SQL Server continuoulsy in event viewer & SQL Server error log.
Event Type: Failure Audit
Event Source: MSSQL$INS1
Event Category: (4)
Event ID: 18456
Date: 3/9/2010
Time: 9:38:14 AM
User: 'abc\mossadmin'
Computer: DRSQL
Description:
Login failed for user 'abc\mossadmin'. [CLIENT: 10.10.10.10]
Questions:
1. Is the above performed steps correct or not?
2. Please tell me the list of services that MUST be stopped on DR MOSS server Server C connecting DR SQL Sevrer Server D
thanks
March 9, 2010 at 11:43 am
I'd say you are getting that error because your DR SQL database are being logged shipped and hence in a recovering state, and users including your DR MOSS server cannot connect to them.
Edit: Not that that answers your question, Are you expecting failover to be an automatic or manual process?
Gethyn Elliswww.gethynellis.com
March 9, 2010 at 12:10 pm
Could you please tell me the list of services that need to be stooped on DR MOSS Server?
I executed SP_WHO2 on DR server and getting below results:
55 sleeping abc\mossadminDRMOSS .SharePoint_CfgAWAITING COMMAND0003/09 11:03:30.Net SqlClient Data Provider 55 0
56 sleeping abc\mossadminDRMOSS .SharePoint_CfgAWAITING COMMAND0003/09 11:03:30Windows SharePoint Services 56 0
57 sleeping abc\mossadminDRMOSS .SharedServices1_DBAWAITING COMMAND0003/09 11:02:00Windows SharePoint Services 57 0
58 sleeping abc\mossadminDRMOSS .SharedServices1_DBAWAITING COMMAND0003/09 11:03:00Windows SharePoint Services 58 0
59 sleeping abc\mossadminDRMOSS .SharedServices1_DBAWAITING COMMAND0003/09 11:02:00Windows SharePoint Services 59 0
61 sleeping abc\mssqlsrvDRSQL .msdbAWAITING COMMAND109003/09 00:42:20SQLAgent - Generic Refresher 61 0
65 sleeping abc\mossadminDRMOSS .SharePoint_CfgAWAITING COMMAND0003/09 11:03:15Windows SharePoint Services 65 0
67 sleeping abc\mossadminDRMOSS .WSS_ContentAWAITING COMMAND0003/09 11:03:00.Net SqlClient Data Provider 67 0
68 sleeping abc\mossadminDRMOSS .WSS_Content_MYSITEAWAITING COMMAND0003/09 11:03:00.Net SqlClient Data Provider 68 0
69 sleeping abc\mossadminDRMOSS .SharePoint_CfgAWAITING COMMAND0003/09 11:03:00Windows SharePoint Services 69 0
71 sleeping abc\mssqlsrvDRSQL .msdbAWAITING COMMAND2238603/09 11:02:00SQLAgent - Job invocation engine 71 0
Here do we need to have NO connections to DR SQL Server from DR MOSS server right? i.e NO connections at all right? please advice
and we are planning for Manual failover as we have MOSS 2007 SP1.
March 9, 2010 at 1:10 pm
Login failed for user 'abc\mossadmin'. [CLIENT: 10.10.10.10]
how to find which to database the user abc\mossadmin trying to connect? Because, by running sp_who2, I'm sure that the user abc\mossadmin is NOT connecting to the logshipped content databases
thanks
March 9, 2010 at 1:21 pm
Did you try profiler? filter with user name.
March 9, 2010 at 2:35 pm
Did you try profiler? filter with user name.
Yes, I ran the profiler and from the results I did NOT see any connections to the log shipped content databases (In recovery mode). But I can see the user connections to the rest of the share point databases.
Could you please tell me what exactly I need to select in Profiler Trace to this info. I want to run it again
thanks
March 9, 2010 at 2:40 pm
pshaship (3/9/2010)
Did you try profiler? filter with user name.
Yes, I ran the profiler and from the results I did NOT see any connections to the log shipped content databases (In recovery mode). But I can see the user connections to the rest of the share point databases.
Could you please tell me what exactly I need to select in Profiler Trace to this info. I want to run it again
thanks
If it is not making a connection to database itself you won't see the user name in profiler, let me correct this the problem is authentication. Make sure the logins existed on both servers and has appropriate permission to the databases.
March 9, 2010 at 2:52 pm
If it is not making a connection to database itself you won't see the user name in profiler, let me correct this the problem is authentication.
If this is the problem with authentication, where & how can I check this to confirm?
March 9, 2010 at 2:57 pm
On your server properties do you have Login auditing (at least failed logins) enabled. If you do the failed login will be logged to the error log. This will give you the reason for the login failure.
To check the properties, in Management studio, right-click the server name, select <Properties>. Select the <Secuirty> tab and the option set will be on the Login auditing section.
Hope this helps. I still think the logins are failing because they cannot access the recovering databases.
I'm not a sharepoint guy so I don't know what services you need to stop.
Gethyn Elliswww.gethynellis.com
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply