My customers sharepoint server crashed and i need to recreate on a new server
Hi,I have a customer who's sharepoint server crashed and they didn't have a backup schedule. I have been able to recover the drive and I need to rebuild on a new server. I am quite new to Sharepoint and never saw their configuration before.Basically on the new server I have installed sharepoint wss 3.0 and i need to restore, is there a way of doing this if i can access their .mdf, .ldf files and also the IIS directories on the old server? I have installed Management studio SQL 2005 so i can maybe re-attach the databases. Does anyone have a procedure or suggestion as to how I could go about this?Simon
March 16th, 2009 6:35pm

So they have no backup, and they had a local database? Sounds like a real nightmare. The first thing I would do is work inside of SQL Server Management Studio to get the databases back up and running. Get the db instance running, find the files and re-attach the databases. When the databases are running, then run the SharePoint Configuration Wizard and try to connect to the databases.If at all possible, I would try and use the farm administrator account to do the work. I would also use it to try and connect to the db instance in SQL Server Mgt Studio to verify that it has access to the databases which will be necesary in order to rebuild the farm. SharePoint Developer | Administrator | Evangelist -- Twitter - https://twitter.com/next_connect -- Blog - http://nextconnect.blogspot.com
Free Windows Admin Tool Kit Click here and download it now
March 16th, 2009 7:18pm

Thanks for that! What databases do i need to bring across from the old server, i can see WSS_Content_blah and WSS_Search, whats important? also do i need to bring across any other files for IIS or configurations etc? This is a total nightmare and I have no idea where to start with this one.Simon
March 16th, 2009 7:29pm

Getting the dbs is the first step. Names are customizable so its hard to say, but I would guess all of them in that server.There should be a configuration one, 1 or more Content DBs, a search one, and one for the Central Administration site.One of the good things about SharePoint is that it stores the configuration data inside of that Config database so if configuration was applied correctly you should be able to connect back to the Config DB and Content DBs and be close if not there. Based on the messages or errors you will know what to check/fix next.Any custom or 3rd party web parts may beed to be reapplied depending on how they were installed, again the messages will let you know when you go to open the site/app. SharePoint Developer | Administrator | Evangelist -- Twitter - https://twitter.com/next_connect -- Blog - http://nextconnect.blogspot.com
Free Windows Admin Tool Kit Click here and download it now
March 16th, 2009 7:36pm

Mike I now have the same issue but I am out of ideas. No we did not have a backup of the Sharepoint DB But the other servers in the farm still have the Sharepoint Identies in IIS The server that housed SQL 2005 and the Sharepoint DB Server went down forcing our techs to recreate active directoryNow that the server is back up and connected to AD we tried to reconnect the SQL server. The old server instance would not reconnect. The new server Instance did openI found the data files in the SQL folder (i.e. ldf and mdf files)I don't have any idea how the old server was configured with respect to which .mdf and .ldf belong to which site Can you help.
April 28th, 2012 2:12pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics