SharePoint Pros

We recently migrated a SharePoint farm from one domain to another domain. Basically, our task was to migrate everything over from the old domain to the new domain. Our farm consists of 50 or so content databases (DBs) and well over 200 site collections plus Mysite site collections. We migrated from one set of servers to new set of servers.

The pre migration activities were as follows:

Create a new farm

Provision CA on the new farm

Provision SSP on the new farm

Provision site collections on the new farm

Delete content DBs from the new farm (stsadm –o deletecontentdb)

Back up and delete content DBs on the new farm (SQL BU and drop DB).

The only DBs we kept were iShare_config and central administration DB.

Mirror (SQL mirroring) content DBs from old farm to the new farm. This was done to reduce the down time. Doing content DB backup from the old and restore to the new will also work but would have taken a lot longer.

During the migration the follow steps were followed:

Lock content DBs on the old farm (stsadm –o setsitelock –url http://mydomain.com–lock noaddition)

Break SQL mirroring on SSP content DB.

Add old farm SSP content DB (stsadm –o addcontentdb) to the new farm

Restore SSP (stsadm -o restoressp. -title <SSP name>) on the new farm

Break SQL mirroring on Project server DBs (ProjectServer_Archive, ProjectServer_Draft, ProjectServer_Published, ProjectServer_Reporting)

Add Project server content DBs (stsadm –o addcontentdb) on the new farm

Delete /pwa from managed path and site collection on the new farm

Provision Project Server on the new farm

Re-link Project Workspaces on the new farm

Break the SQL mirror on the rest of the content DBs

Attach the old farm content DBs to the new farm

Verify sites

Unlock content DBs on the new farm (stsadm –o setsitelock –url http://mydomain.com –lock none)

Configure Reporting Services

        Re-deploy broken solutions

Re-publish infopath forms

Next time, I’ll go over some lessons learned from this project.