Sharepoint 2007 copy production farm to test


two new servers, one db and one sharepoint
I have seen 101 articles on this but nothing definitive. I'm looking for a step by step procedure which will let me take a copy of my production environment and and restore it to my two new servers as my test environment.
can any one help, do i use stsadm, a step by step guide please, many thanks
Who is Participating?
ambot13Connect With a Mentor Commented:
1. Document your existing installation. Record such items as:

    * third-party web parts
    * specialized DLLs – make sure there is a version compiled for 64-bit OS
    * templates (stsadm -o enumtemplates)
    * packages (stsadm -o enumsolutions)
    * presence of static paths
    * which web applications are linked to which databases

2. Prepare the existing Windows 2003 server:
Make sure it is at least upgraded to MOSS SP1. If possible, update it to the latest cumulative update.
The Sharepoint installer account will need to be a local administrator on the SQL server, and you will need to log into the SharePoint server as that account during the installation process.
3. Prepare the new Windows 2003 sever:
a. Use these instructions to install MOSS 2007 on the new server:
b. Add any web parts or other specialized components recorded in Step 1.
c. Configure the permissions.
d. Configure the SSP. It is theoretically possible to migrate an SSP, but I found the procedure to be more trouble than comparing the two side-by-side and replicating the setttings.
4. Perform a test site migration:
here are the specialized instructions for moving between AD domains.  See the first comment:
a. Make a SQL backup of the content database.
b. Create a blank database with a new database name.
c. Restore the backup into the new database.
d. Create a web application on the new server, and specify the new database name during the creation process.
e. Check the site collection administrators to make sure you are there.
f. If required, do an IIS reset (”iisreset /noforce” at the command line).
g. If using a host header for the site (, create a DNS entry pointing to the new server with a test site name (
5. After testing of the migration is complete, perform the production migration:
a. Notify users that there will be some downtime.
b. Check that no timer jobs are running.
c. Quiesce the farm for five minutes.
d. Run the preparetomove command for your content database.
e. Make a SQL backup of the content database.
f. Restore the SQL backup over the top of the test database for the new farm.
g. In Central Administration, remove and re-add the content database to the web application.
h. IIS reset.
i. Test internal and external (if applicable) access to the site. Also do some functionality checks: alerts, search (after a full crawl), navigation (static links). Check the Windows event logs for errors.
6. Cleanup:
a. Remove the web application and IIS site from the original farm.
b. Remove the SharePoint installer account from the local administrators on the SQL server.
c. Remove the DNS entry for the testing site.
7. Back up your new environment as soon as it is in a satisfactory state.

No one is going to be able to provide you a step by step guide since every SP environment is different (custom application/web parts/features/etc).

Creating and maintaining a SP Test environment that matches your production environment can be complex and very tedious to maintain.

What exactly do you want to "test" or what do you really care about matching up?

thclipper1Author Commented:
I will be migrating everything to two new servers, but obviously want to test everything on the two new servers first before switching off the current live environment.,
Improve Your Query Performance Tuning

In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!

So you are not really building out a test environment, you want to migrate your env to two new servers (new hardware, different domain)?

You should treat it as a Disaster Recovery scenario then.
thclipper1Author Commented:
Corrent, it will be a migration.
It is a different domain also yes, with new hardware
That's a very complex scenario. I'm going to step back and let someone else give it a try.
I did a gradual cutover while also upgrading to Windows 2008 64-bit (great idea, by the way).  Here is how I did it:

thclipper1Author Commented:
Any further details on this by any chance.
surely it can't be that difficult, it's just an app and a db :-(
What OS are you migrating from and to.  If you provide more details, I can customize my step by step list for your instance.
thclipper1Author Commented:
Hi Ambot,

Both OS's are Windows 2003 so no change in the OS.

So it's literally just two new machines in a different location that I'm migrating to.
While I'm migrating, I don't want any downtime if possible on the current live environment.

thclipper1Author Commented:
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.