April 23, 2008 at 5:52 am
Current SQL 2005 config:
SQL Server 2005 SP1 installed on Windows 2003 Server Std edition incl SP1
ALL SQL databases are on two separate disk volumes (Provided by Netapp) namely D: (Data) and E: (Logs)
Plan:
Detach the NAS storage from the current SQL server and re-attach to a new SQL server with the same name.
use the same Active Directory service accounts to startup the services on the new SQL server
Situation:
On disk presentation, I cannot get the sql services to startup, i get the following error from the SQL server configuration manager: The service could not start error msg - 1906, this number might be incorrect, as i did this a while back and lost the details.
Can anybody forsee any issues as to why the services wont start? Sid's? File permissions? etc
Thanks
Gino
April 23, 2008 at 9:51 am
Hi Gino,
SQL Server can not start most probably because it could not find system databases.
Check the registry and modify the path to the startup parameters accordingly after making sure that these 2 NetApp NAS volumes available to the server.
Registry Key for Startup Parameters for default installation (modify as appropriate for your installation)
Key Name: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.1\MSSQLServer\Parameters
Class Name:
Last Write Time: 7/5/2007 - 12:14 PM
Value 0
Name: SQLArg0
Type: REG_SZ
Data: -dC:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf
Value 1
Name: SQLArg1
Type: REG_SZ
Data: -eC:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG
Value 2
Name: SQLArg2
Type: REG_SZ
Data: -lC:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
Regards,Yelena Varsha
April 24, 2008 at 2:42 am
Hi, thanks for the response.
On the "new" SQL server, i have setup two local drives D and E (Data and Logs) and have already moved the system databases to these drives, so that it is exactly the same file path as the "old" server.
When I present the 2 Netapp volumes, i stop the sql services, change the local drive letters to G and H, present the Netapp volumes as D and E and then try to start the services, which at this point fails.
April 24, 2008 at 10:17 am
Could you post here any error messages?
From SQL Server log or from Event Logs - anything.
Regards,Yelena Varsha
April 25, 2008 at 1:50 am
There were no entries in the NT eventlogs referring to SQL events, only an error number (which i cant remember) that referred to the actaul service and it unable to start.
I am going to be running this exercise again tomorrow and will hopefully get some screenshots and more detail
Everything is exactly the same on both servers, its just as soon as i want to start the new one, it doesnt do anything
April 25, 2008 at 8:55 am
Hi,
Yes, write all errors down or make screenshots.
Also make sure that your storage is started before you rebooting the server. We did have issues once and now the support enginners know that they have to start the storage first and then the server.
Regards,Yelena Varsha
May 8, 2008 at 3:03 am
Ok, so i got it all sorted, apologies for taking so long to post my findings, but have been a bit busy, here goes:
Background:
I had a HP DL360 server which contained SQL 2005 Standard edition and 6 x 146GB local disks, also presented via iSCSI to this server were our Netapp (Lan Storage) disks, namely D (SQL Data Volume) and E (SQL Log Volume).
We wanted to upgrade the current hardware as we had 3 instances installed on it and the age of this hardware was starting to take its toll, this idea proved too costly so we purchased a whole new HP DL 380 G5 server.
I installed SQL 2005 std Sp1 on the new box and the plan was to replicate the install from the old server.
Solution to original post:
The initial error of the SQL services not starting was caused by a conjunction of permissions by the service login account, these had to be reapplied to the Lan Storage disks And the starup parameters of the Errorlog path was not the same as the original server, hence SQL was trying to create a folder called ERRORLOG and i was defining the Errorlog folder in the startup parameters as well.
After all of this, the process was seemless, this is defenitely the way to have all your data (incl Sys db's) on Lan Storage and just presenting your disk where ever you please, especially in a DR scenario as we do now, so much easier.
thanks for all your postings
Cheers
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply