Friends, Life is not easy and every time we cannot create a fresh/new server, environment or a new configuration. What will happen if a production ssp goes corrupted or goes down. To create a new ssp with full customized configuration will take more than a week. If we would have any way to get this done in 3-4 hrs. we would be on the top of world.
Yes, we can do that: but how?
Production or any other UAT, DR environment are always supported with a regular backup of databases but how to use it in a way to get the same customization again. It is just same as restoring , but need to be done carefully and understanding the concept.
How can we do that:
1) We should have backup of ssp database and ssp search database.
2) We should have details of all the entries like ssp-url, account & mysite url.
Now the command is:
stsadm -o restoressp -title (SSP-Name) -url (http://ssp-url) -ssplogin (domain\accountname) -mysiteurl (http://mysiteurl) -indexserver (indexservername) -indexlocation (“C:\Program Files\Microsoft Office Servers\12.0\Data\Office Server\Applications”) -ssppassword (password) -sspdatabaseserver (SSP database server name) -sspdatabasename (SSP database name) -searchdatabaseserver (search database server name) -searchdatabasename (SSP Search database name)
-ssplogin: ssp account
-mysiteurl: ssp mysite url
Note: This command can be used for two purpose:
1) creating a fresh new(dev or any other) environment by using production ssp backup.
2) When the ssp got corrupted. In this case you have to create a dummy ssp with dummy ssp site and other stuff(to delete afterwards). As you cannot delete a defult ssp. Make the new dummy ssp and made it default. And then delete the corrupted ssp with it site url and my site url and db. Use the above command and it will do all for you.
Now you can made the new ssp as default and carry on with your task successfully.
Hope I was able to describe the content correctly based on my knowledge and learning.
If you liked this post, do like on Facebook at: https://www.facebook.com/Ashishsharepointblog
Filed under: MOSS 2007, SQLServerPedia