Export (0) Print
Expand All

Manage protected file servers

Updated: February 16, 2015

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

Migrate between volumes

Migrate-Datasource is a command-line script that lets you continue protecting a data source (file, folder, volume, or share) to the same replica volume even after it has been migrated to a different volume on the same protected computer. You have to run the Migrate-Datasource script even if you have not changed the drive letters of the volume because System Center 2012 – Data Protection Manager (DPM) recognizes volumes by the GUID and not the drive letter.

ImportantImportant
If you have secondary DPM protection configured, you must run the Migrate-Datasource script on the secondary server also.

noteNote
Migrate-Datasource is used to migrate protected computer volumes while MigrateDatasourceDataFromDPM is used to migrate DPM volumes.

The possible reasons for moving DPM-protected data sources across volumes include the following:

  • The disk is corrupt.

  • Organization policy demands that disks be replaced at certain time intervals.

Syntax

Migrate-Datasource.ps1 [-DPMServerName] <string> [-Option [auto or manual]] [-PSName] <string>

 

Parameter Description

DPMServerName

Name of the DPM server from which you want to migrate data.

Option

Indicates whether DPM should perform an automatic or manual migration.
Automatic: If you specify the automatic option, DPM migrates all the data sources on the protected computer. Use this option if you created a new volume but retained the logical path (for example, if F:\ was reformatted on a new disk but is still called F:\, or the mount point is still the same). DPM automatically updates the mappings for the replica of F:\ to the new volume that is now called F:\.
Manual: If you specify the manual option, you have to migrate each data source individually. The script gives you a list of volumes protected by DPM that are not present and a list of unprotected volumes. You can then map the volumes individually. Use this option if the logical path was not preserved (for example, G:\ became H:\).

PSName

Name of the protected computer to which the data source is being migrated.

Things to Remember

  • Migrate-Datasource is used only for migration of file system data sources, such as volumes. For other data sources, follow the instructions in the alerts.

  • DPM does not support migration from a volume on a drive (for example, D:\) to a mounted volume (for example, E:\<mountpoint>, where mountpoint is a location on which the volume has been mounted).

  • For auto-migration of mounted volumes, the volume on the new computer should have the same mount point name as the volume on the previously protected computer. DPM does not allow you to migrate to a drive.

  • For migration of mounted volumes (where the old volume is protected by using a mount point):

    • If the protected volume has multiple mount points, at least one mount point of the volume on the new computer should have the same mount point path as before.
      Old volume: C:\mnt
      new volume: C:\mnt (may have drive letter and other mount points)

    • If the volume also has a drive letter, only the drive letter is visible while you select the new volume for migration. This should be selected manually.

  • You should migrate volumes only if you have reformatted them or if the volume GUID associated with the volume has changed.

noteNote
After migration, you cannot perform original location recovery for the recovery points created before the migration. Recovery fails with the message Couldn't find the selected volume. You can, however, recover to an alternate location.

Migrate across disks

MigrateDatasourceDataFromDPM is a command-line script that lets you migrate System Center 2012 – Data Protection Manager (DPM) data for a data source – replica volumes and recovery point volumes – across disks. Such a migration might be necessary when your disk is full and cannot expand, your disk is due for replacement, or disk errors show up.

noteNote
MigrateDatasourceDataFromDPM is used to migrate DPM volumes whereas Migrate-Datasource is used to migrate protected computer volumes.

Depending on how you have configured your environment, this could mean one of more of the following scenarios for moving data source data:

  • DPM disk to DPM disk

  • Data source to DPM disk

  • Data source to custom volume

The MigrateDatasourceDataFromDPM script moves all data for a data source or disk to the new disk or volume. After migration is complete, the original disk from where the data was migrated is not chosen for hosting any new backups. You must retain your old disks until all recovery points on them expire. After the recovery points expire, DPM automatically unallocates the replicas and recovery point volumes on these disks.

Migrating does not move recovery point data on the replica, it simply makes new replica and recovery point volumes, then copies the replica data to the new replica. VSS shadow copies are volume specific and cannot be moved or copied. So while all new recovery points are made on the migrated disk, the old replicas and recovery points on the old volume are still required. However, if you want to remove the old disk sooner, then you can reduce the retention range and wait for the old recovery points to expire.

All backup schedules continue to apply and protection of the data source continues as before.

After migrating the replica of a data source that has secondary protection enabled, you must start the Modify Protection Group wizard on the secondary DPM server, select the same data source, and complete the wizard. This reconfigures secondary backups to run from the new replica volume on the primary DPM server.

Syntax

MigrateDatasourceDataFromDPM.ps1 [-DPMServerName] <string> [-Source] <disk[]> [-Destination] <disk[]>

MigrateDatasourceDataFromDPM.ps1 [-DPMServerName] <string> [-Source] <data source> [-Destination] <disk[]>

MigrateDatasourceDataFromDPM.ps1 [-DPMServerName] <string> [-Source] <data source> [-Destination] <DPM server volume[]>

 

Parameter Description

DPMServerName

Name of the DPM server for which you want to migrate data.

Source

The location from which the data must be moved. This can be either a DPM disk (use Get-DPMDisk to retrieve the disk) or a DPM data source (use Get-Datasource to retrieve the data source). The source can be a set of disks.

Destination

The location to which the data must be moved.
This can be either a DPM disk array (use Get-DPMDisk to retrieve the array of disks) or an array of two DPM volumes (use Get-DPMVolume to retrieve the list of DPM volumes on the server). The first element of the array is the destination replica volume and the second the recovery point volume.
The destination disks must be added to the DPM disk pool before migration.

noteNote
The numbering for the disk array starts with 0.

Examples

The following examples show how the script works.

Example 1: Disk D1 contains the replica and recovery points for the data source DS1.

 

Disk Replica Recovery Point

D1

R1

RP1

To do a disk to disk migration of the volumes on D1 to another disk D2, do the following:

$disk = Get-DPMDisk –DPMServerName DPMTestServer
./MigrateDatasourceDataFromDPM.ps1 –DPMServerName DPMTestServer –Source $disk[0] –Destination $disk[1]

This results in the following:

 

Disk Replica Recovery Point

D1

R1

RP1

D2

R1’

RP1’

You need to retain D1 for the retention range of the latest recovery point on it, usually one month. After the latest recovery point expires, DPM will deallocate the replicas and recovery points on disk D1 automatically.

Example 2: Disk D1 contains the replica of the data source DS1 and the recovery point for data source DS2. Disk 2 contains the replica of DS2 and the recovery point for DS1.

 

Disk Replica Recovery Point

D1

R1

RP2

D2

R2

RP1

If you do a DPM disk to DPM disk migration to a third disk (Disk 3), this disk will have four volumes, replicas and recovery points for DS1 and DS2.

$disk = Get-DPMDisk –DPMServerName DPMTestServer
./MigrateDatasourceDataFromDPM.ps1 –DPMServerName DPMTestServer –Source $disk[0] –Destination $disk[2]

This results in the following:

 

Disk Replica Recovery Point

D1

R1

RP2

D2

R2

RP1

D3

R1’ and R2’

RP1’ and RP2’

This happens because DPM cannot move just a replica or a recovery point, it will always move them in pairs, hence even though the command only moves the volumes from D1, DPM will move also the related replica and recovery point.

Example 3: Disk D1 contains the replica of the data source DS1 and the recovery point for data source DS2. Disk D2 contains the replica of DS2 and the recovery point for DS1.

 

Disk Replica Recovery Point

D1

R1

RP2

D2

R2

RP1

If you choose to migrate only the data for DS1 to a third disk (Disk 3), this disk will have two volumes, the replica and recovery point for DS1.

$pg = Get-ProtectionGroup DPMTestServer
$ds = Get-Datasource $pg[0]
$disk = Get-DPMDisk –DPMServerName DPMTestServer
./MigrateDatasourceDataFromDPM.ps1 –DPMServerName DPMTestServer –Source $ds[0] –Destination $disk[2]

 

Disk Replica Recovery Point

D1

R1

RP2

D2

R2

RP1

D3

R1’

RP1’

Manage server clusters

On planned failover of a cluster, System Center 2012 – Data Protection Manager (DPM) continues protection. On unplanned failover, DPM issues an alert that a consistency check is required.

For a non-shared disk cluster, planned failover may also require a consistency check.

Change file server cluster members

When you make changes to a server cluster that is protected by System Center 2012 – Data Protection Manager (DPM), DPM takes the following actions:

  • When a new server is added to a cluster, DPM issues an alert to install a protection agent on the new cluster node and protection fails.

  • When a server is removed from a cluster, DPM detects that a node has left the cluster and the server now appears separate from the cluster with no data protected on it.

For example, assume you have a server cluster that contains four computers: Node1, Node2, Node3, and Node4. You need to replace computer Node4 with a new computer, named Node5.

You use the administration console for your cluster service to add Node5 to the cluster and configure the resources that can be failed over to Node5.

DPM issues an alert that protection of the server cluster will fail until a protection agent is installed on Node5. You install the protection agent on Node5.

You fail over the resources from Node4 to other nodes in the cluster. When no resources remain on Node4, you remove it from the cluster. DPM detects the failovers and continues protection of the cluster.

DPM detects that Node4 has left the cluster—it appears as a stand-alone node now. If it no longer exists on the network, you can remove the record for this server in DPM Administrator Console.

Change resource groups

A cluster node can have any number of resource groups. Moving a DPM protected data source to a resource group, between resource groups, or out of a resource group can cause protection job failures. To successfully make any of those changes to resource group membership, perform the following steps:

  1. Stop existing protection of the data source. The data source could belong to a protection group as a single data source on a protected server or as a data source as a member of a resource group.

  2. Begin protection of the data source according to its new status, either as a single data source on a protected server or as a data source as a member of a resource group. This will allocate a new replica for the data source.

Changing the name of a resource group will affect the protection of all data sources in the resource group. To change the name of a resource group, perform the following steps:

  1. Stop protection of the resource group.

  2. Change the name of the resource group.

  3. Begin protection of the resource group under its new name.

-----
For additional resources, see Information and Support for System Center 2012.

Tip: Use this query to find online documentation in the TechNet Library for System Center 2012. For instructions and examples, see Search the System Center 2012 Documentation Library.
-----
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2015 Microsoft