Lambton
asked on
Sharepoint's SQL Server and DC crashed, need help to get back online
So as you can tell by the subject of this one that we're in a bit of a Pickle. So we had 2 servers that we acquired quite a while back, one was a win2k3 Domain controller with SQL 2005 running on it, the other server was the same OS with Sharepoint 2007, they were both VM's on an older VMware esxi server. This weekend we had a fairly catastropic SAN failure, and this forced us to try to move the VM's to a new ESX server on a new SAN - however a couple of the vmdk files didn't make it in the move and we lost our DC/SQL server. Luckily we ad good backups of the SQL databases, but unfortunately we were not so lucky with the windows server backups for the system itself. So in the end, we were able to move the Sharepoint server to a new host fine, but we lost our domain controller and SQL server (but not databases).
SO - Here's what we've done so far... As I've said, we have the sharepoint server in good shape (other than not having a DC or Database to attach too). We've restored all the Databases to another existing SQL 2008 server. We've created new Sharepoint and SQL accounts on our corporate domain (this is a different domain than the one we lost) and we've given all the appropriate permissions to these accounts for the SQL DB's. We've removed the sharepoint server from the old lost domain, and added to the corp domain.
Here's what we need to do - we need to modify the Sharepoint server to use the new corp domain accounts we created and also to use the new SQL server name and instance.
But here's what happens: When we run the SP config Wizard, and it asked for the SQL names and credentials, etc.. it says something like "you need to use the same farm account "old.domain\user" to connect" (I'll get the exact error for you in the next comment, sorry). So how or what do we need to do to get this working?
Sorry for the long description, but hopefully I included enough information in here - Please let me know if you require any more information/details and I'll try to get those to you right away.
Thanks very much! We have a lot of pressure on us to get this resolved asap (of course) soany help at all will be appreciated!
Thanks everyone!
/Steve
SO - Here's what we've done so far... As I've said, we have the sharepoint server in good shape (other than not having a DC or Database to attach too). We've restored all the Databases to another existing SQL 2008 server. We've created new Sharepoint and SQL accounts on our corporate domain (this is a different domain than the one we lost) and we've given all the appropriate permissions to these accounts for the SQL DB's. We've removed the sharepoint server from the old lost domain, and added to the corp domain.
Here's what we need to do - we need to modify the Sharepoint server to use the new corp domain accounts we created and also to use the new SQL server name and instance.
But here's what happens: When we run the SP config Wizard, and it asked for the SQL names and credentials, etc.. it says something like "you need to use the same farm account "old.domain\user" to connect" (I'll get the exact error for you in the next comment, sorry). So how or what do we need to do to get this working?
Sorry for the long description, but hopefully I included enough information in here - Please let me know if you require any more information/details and I'll try to get those to you right away.
Thanks very much! We have a lot of pressure on us to get this resolved asap (of course) soany help at all will be appreciated!
Thanks everyone!
/Steve
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
We've opened MS Support case - I'll update the question here after the case is closed - thanks for everyone's support so far.
So far we've setup a new server in our production domain, installed SP 2007 SP3, and are attempting to connect the previous database backups. We are having trouble finding out which databases were for which sites, so if anyone has any way to find that out (without access to the previous SP server) please let me know.
thanks!
/Steve
So far we've setup a new server in our production domain, installed SP 2007 SP3, and are attempting to connect the previous database backups. We are having trouble finding out which databases were for which sites, so if anyone has any way to find that out (without access to the previous SP server) please let me know.
thanks!
/Steve
ASKER
we have been able to rebuild the server, attach the databases with Microsoft's help, but the layout and webparts appear to be missing. I don't quite understand why, the SharePoint server was still ok and the databases are back, where would the web parts code be stored? it was a very custom web site built on share point so I have the structure and the basic "SharePoint" look, but how can I get the customized look back?
Steve.
Steve.
ASKER
OK - here's the update - we managed to rebuild the server and attached the correct DB, and the site didn't look right, however there were a lot of customisation from an external company, so it was difficult to know what was what and which web parts and solutions were installed/applied... but we finally found the correct solution and applied this - we have our site back!
Thanks everyone for your advice and assistance!
/Steve
Thanks everyone for your advice and assistance!
/Steve
Glad to hear it. Good job!
ASKER
thanks everyone for the advice and assistance!
If you do not have a system state backup (ad DC info and sysvol share) it would require that you setup a new DC, create all the relavent usernames and rejoin the sharepoint server, and then go through a process........ Best handled as mentioned above.