Go 4 Sharepoint

Search:

Welcome: Guest!

Sharepoint Forum

Home » Forum » Sharepoint

Ask a question

RSS Feeds

Best practices for moving content from dev or staging to production

Asked By: Julianne Luna Date: Mar 26, 2010 Category: Sharepoint Views: 1040

I am attempting to move content from a dev server to a production
server.
In the past I have used stsadm -o backup on the original server and
stsadm -o restore on the new server..that usually works, but I have
also seen some security errors surface..in addition, this method has
caused problems with items that exist in the style library not "moving"
over and being referenced properly.

I tried content deployment from Central Admin. and I can't seem to get
that to work either..I get an error that the folder /style library
already exists.

What is the recommended best practice?

Tagged:best practices for moving content from dev or staging to production

2 Answers Found

Answer #1 Answered By: Khushi Srivastava Answered On: Mar 26, 2010

Your problem with content Deployment is that the first time you use content
deployment the destination website needs to be either a Blank Site or an empty
site (built using STSADM with no template). But the first thing you need to
consider is whether everything you are trying to deploy is actually "content".
Backup/Restore, Export/Import, and Content deployment will only move content
that is stored in the content database. Web part assemblies stored in the bin
folder or GAC and other files like Features deployed to the 12 hive will not be
moved using any of these methods. To move these file system based files to
another server you will need to create one or more Solutions (WSP) files.

Answer #2 Answered By: Arti Patel Answered On: Mar 26, 2010

Best way I have seen are 3rd party tools. Something Like DocAve allows you to do
that really easily.

Didn't find what you were looking for? Find more on Best practices for moving content from dev or staging to production Or get search suggestion and latest updates.