Hot answers tagged staging
8
There are a couple of options here:
Use STSADM -o backup/restore
Use STSADM -o export/import
Use Content Deployment, perhaps with the SharePoint Content Deployment Wizard (a tool I wrote)
When you use backup/restore, you get everything - including recycle bin content, running workflows, alerts etc etc. This may or may not be what you want. Such ...
2
What are you looking to stage? Content or functionality?
I'm absolutely for having multiple environments available for testing functionality, but I don't see value in duplicating complete content sets for an entire environment. In addition to the pain and time involved with setting it up or synchronizing it, you have the cost for storage. In the ...
2
You'll need to detach and re-attach your content database.
If you go to the central administration and your site collection information are missing do the following (Post restoration of your database)
Stsadm -o deletecontentdb -url {Site Url} -databasename {Content Database Name}
Stsadm -o addcontentdb -url {Site Url} -databasename {Content Database Name}
...
1
That command is correct, but you need to make sure you run it on all servers.
"When the process account for the Windows SharePoint Services Timer service (SPAdmin) is disabled (necessary in some installations for security reasons), the execadmsvcjobs operation must be run on all computers to perform provisioning and other administrative tasks that would ...
1
We use the SharePoint Deployment Content Wizard to migrate content from prod to staging. It is good for the QA testers to work with actual data and it is good to test staging with as close an environment as production (amount of data, load, etc.).
For key sites that require a more frequent refresh we will script the content refresh and schedule it. To ...
1
There are several SharePoint ISV's making great products out there for this type of scenario, depending upon your failover limits and the type of output storage needed.
The 2 best are Quest's and AvePoint's recovery tools for ease-of-use and cost, but there are also several others (e.g. Symantec, Microsoft, etc.) depending upon how much infrastructure you ...
Only top voted, non community-wiki answers of a minimum length are eligible
