Upgrading SharePoint versions

Updated: November 1, 2013

Applies To: System Center 2012 - Data Protection Manager, System Center 2012 R2 Data Protection Manager, System Center 2012 SP1 - Data Protection Manager

If you upgrade an earlier version of Microsoft SharePoint to a later version, then you must reconfigure protection of the data.

The Microsoft SharePoint farm is updated in the following two scenarios:

  • During SQL Server hardware upgrade

  • When instances of SQL Server do not change

SQL Server hardware upgrade

If the hardware of the computer that runs the SQL Server is upgraded, then the databases are moved from one instance of the SQL Server to another. During the upgrade process, both farms are online, and the older farm is read-only (databases are moved in phases). You can protect the new SharePoint farm during the upgrade. To do this, perform the following steps:

  1. Install the DPM protection agents on the new SharePoint farm servers.

  2. Protect the SharePoint farm as a new SharePoint farm.

  3. Move databases from the old farm to the new farm.

    DPM will automatically discover the databases that were moved in the new farm and will start to protect them. DPM generates a warning - Farm Configuration Changed for the old SharePoint farm. You can ignore this warning.

  4. When all the databases are moved to the new server, perform Stop protection of the old SharePoint farm, by selecting the retain data option.

When instances of SQL Server do not change

When instances of SQL Server do not change, and databases are detached from the existing farm and are added to the upgraded farm, follow these steps:

  1. Create a recovery point for the SharePoint farm on the DPM server. For example, DPMServer1.

  2. Perform Stop protection of the SharePoint farm on DPMServer1 by selecting the Retain Replica option.

  3. Run SetDPMServer.exe on all the servers of the SharePoint farm to point the DPM agent to another DPM server, for example, to DPMServer2.

  4. Protect the SharePoint farm by using DPMServer2.

  5. When the retention range for all the recovery points expires on DPMServer1, delete the protected data on DPMServer1 by using the Remove Inactive Protection option.