Hello everyone, first of all,thanks for any ideas on this. We are trying to clone our production Sharepoint install to our development install. This will be done frequently as per common software development practices. Anyway, there are apps that will do this for us, but I was looking at the stsadm application to try to do this. I can run the following backup command and backup to a file... stsadm -o backup -url http://sharepoint1 -filename d:\backup\March12 I copy the file over to the dev server and then run the following... stsadm -o restore -url http://devsharepoint1 -filename d:\backup\March12 When I do this, several items are missing including custom shortcuts and all the personal sites. Is it possible to use the stsadm command and grab everything including all the site collections, personal sites and these custom shortcuts? Again, thanks for any help on this. Mike

Mike, Did you find an answer to this? I am looking to do the same thing, but I am also wondering about the configuration database as well because I have a decent number of settings that I would prefer not to have to recreate. Chris

I've been working on a document for the past two weeks that walks through (in ridiculous detail) the steps needed to restore our environment starting with installing Windows all the way up to reinstalling custom features, dual-authentication sites, integrated reporting services etc. Though not done yet, I expect to complete it in the next couple of days. If you want a copy just send me an email and I will forward it to you. You will have to customize it to your exact specifications because I get into detail for my systems admin to be able to restore in the case that anything ever happens to me, but it is a compilation of probably two dozen articles/blogs that I've read along with my own experiencesover a couple of weeks in setting up a development environmentthat should also work inrestoring in the case of a disaster. cprime at medmarc dot com

Hi Chris Can i get a copy of the Document you mentioned? Thanks. genemagerr@hotmail.com

I have at least a couple more days of work until the document can be publicly sent out (still working on getting the reporting services piece working and then I have to go back and remove some private information to protect my company's data).After that I will be able to email it to anyone that needs it.

hi Cris! Can i get a copy of the document too? please :) my e-mail andrey.gorohov@globus.ru thanks in advance

Hi Audrey, I'll remove any personal information from my document and later this week I'll send you a copy of what worked for me. Terry

Its pretty simple and if its a temporary PROD In SQL make FULL Backups of your Dbs. Copy Baks to DEV Environment DEV In SQL Rename the Content Dbs while Restoring Dbs Install SharePoint Create your DEV Web Applications (Match PROD but use DEV naming Conventions) Remove the Content Dbs Add the Restored Content Dbs Perform Restore of SSP using the Restored Dbs Add Solutions or Features to Farm Run the following for the Content Dbs so yu will not have any errors STSADMINo sync STSADMINo preparetomove Naming Conventions The SharePoint WebApplication, IIS WebSite, and Application Pool should all use the HostHeader of the WebApplication The Content Dbs should be named WSS_Content_DEV_NetBios name of the WebApplication This will help when you to keep the different Dbs, IIS WebSites, SharePoint WebApplications, Application Pools clear in your head. The jist of this is you shopuld know off the top ogf your head What DBs go with Which AppsAs long as you know which apps and dbs go together its painless. DEV Refresh After you have completed the above steps all that is required to refresh DEV is to back up your Content Dbs from PROD an Restore them to DEV, Keep the APPs up to date andrun the STSADM commands after Restoring the Dbs Also, you can Script this entire process usingQueries,STSADM, and a CMD to RoboCopy the BAKs to DEV. I hope this helps its not that complicated. Have Fun... :)-Ivan Ivan Sanders http://linkedin.com/in/iasanders http://dimension-si.com/blog

I had to clone the top level site (customisations et all) from one environment ot another. What I did was to copy the templates and resources folder from one WFE to the other and then backup and restored the site. We have some custom master pages which needed to be migrated over an this resolved the issue for me (if this is what you mean by customisations). If you need prsonal sites, you would need to replicate the database from one environment to another as stated in this blog. The method used by me was for only the top level site with custom master pages.

Hello Chris !!I'm very interesting by your document. Can you send me a copy at yanolezard@gmail.comThanks a lot by advanceHave a nice dayRegards-YES-

Hi, ChrisI appreciate sending your document,ah_ammar@hotmail.comThank you in advanceBest Regards, Ammar MCT

Hi Chris,Could you also send me a copy of the document?petargk@gmail.comThanks in advance,Petar Korudhziev

I have inherited an infrastructure with these exact needs. Can I get the document as well at rglickler@umassp.edu? Thank you