wss 2.0 disaster recovery
-
Thursday, March 08, 2012 6:08 PMI have a wss 2.0 installation and would like to know how to recover my sharepoint installation if my web server is unrecoverable and all I have are full database backups. In this scenario I'm assuming I would have to rebuild the web server completely and install wss 2.0 again and connect to the databases. I'm looking for specific steps as I can't find any information for this scenario. The disaster recovery I've seen for 2.0 assumes you have stsadmn backups. Any info would be appreciated.
All Replies
-
Thursday, March 08, 2012 6:38 PM
Microsoft has few articles for SPS 2003 since it is built on top on WSS 2.0, the concepts must be the same.
http://technet.microsoft.com/en-us/office/sharepointserver/bb267364
http://office.microsoft.com/en-us/sharepoint-portal-server-it/
I hope this helps.
Regards, Mahesh
-
Thursday, March 08, 2012 7:39 PMAn additional useful link http://support.microsoft.com/kb/894164 How to move the databases that are used by SharePoint Portal Server 2003 to a computer that is running SQL Server
MCITP|MCTS SharePoint| SharePoint Performance blog
-
Tuesday, March 13, 2012 9:34 AM
Hey buddy,
I would like to suggest you SharePoint Recovery Tool. You won't need to rebuild web server or install it again. Recently I too was facing the same situation, I searched for solution on google and found this software. it has resolved my issue completely and Recover SharePoint Database.
HERE'S the link : http://www.sharepointrecoverytool.com/
hope you'll be benefitted by this.
- Edited by Lance Joseph Tuesday, March 13, 2012 9:36 AM
-
Thursday, March 22, 2012 6:39 PMThank you for all the replies. I set up a test environment and tested this out. Assuming the databases are all in place on the server all I had to do was reinstall sharepoint on a new server and connect it to an existing config database. Updated to the correct sharepoint sp level with hotfixes as the old server and then extended the virtual server and connected to an existing installation. It appears to have to worked in my test environment.

