Except the port used by OS drive, I have 4 more SATA ports in this server.   I had two 4TB drives before, they were almost full so I plan to migrate them to larger disks.   Assuming the 4TB disks are 4A and 4B. here was my plan:

(1)  Install a new 6TB drive (6A)
(2) Migrate from 4A to 6A
(3) Wait for retention period to pass, retire 4A
(4) Install the second new 6TB drive (6B)
(5) Migrate from 4B to 6B
(6) Wait for retention period to pass. retire 4B

 I used MigrateDatasourceDataFromDPM.ps1 to do the migration.  However something went wrong during step (2), the longest retention period in all of my protections is 10 days, but disk 4A has not been cleaned up after 90 days.  The even worse thing thing is, disk 4A is still being used for new protection groups that I creates !

So it ends up with:

port 1: 4A:  1.63 TB used, 2.06 TB Free (55% unallocated)
port 2: 4B: 2.65 TB used, 1.07 TB free  (28% unallocated)port 3: 6A: 4.87 TB used, 720GB free  (12% unallocated)
port 4: not used

As you can see, from all existing three disks I do not have space to entirely free up either disk 4A or 4B, I have to use the last available port to add in disk 6B.   But I want to make sure that I migrate both 4A and 4B to it (1.63TB + 2.65TB = 4.28 which it is capable of taking).  

Can I run MigrateDatasourceDataFromDPM.ps1 from 4A to 6B and immediately again from 4B to 6B?  If not, how do I resolve this drama ?  Eventually I only want to leave disk 6A and 6B. 

• Moved by Mike JacquetMicrosoft employee, Moderator 10 hours 41 minutes ago

Hi,

Select the 4TB disk in the storage pool to see what data sources are not migrated yet. You can use the GUI based migration script from here to migrate individual data sources that are still on the old 4TB disks.  On the disk destination page, multi-select both of the 6TB disks and DPM will be able to use both to migrate the data source.  Start with the largest DS to migrate so contiguous space is used.  After a DS is migrated it will no longer be listed on the 4TB disk. Once all the data sources are migrated - you can then remove the 4TB disks from the storage pool so they will not be used in the f

Mark,

I've done that to a point that there are two last datasources could not be moved over, with the following error.  I guess last time I was stuck at the same point, but after waiting 90 days, not only existing datasources were not deleted, more were added in... :(

****************************************
Set-ProtectionGroup : D:\ has recently been migrated. You cannot migrate D:\
again until the recovery points on the previous replica volume are available.
(ID: 31224)
At D:\Program Files\Microsoft DPM\DPM\bin\MigrateDatasourceDataFromDPM.ps1:129
char:4
+             Set-ProtectionGroup $mpg
+             ~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Set-DPMProtectionGroup], DlsE
   xception
    + FullyQualifiedErrorId : ChainedMigrationError,Microsoft.Internal.Enterpr
   iseStorage.Dls.UI.Cmdlet.ProtectionCmdLets.CommitProtectionGroup
****************************************

Hi,

There must be some dangling RP's - you can delete them using the powershell script in this post. Once they are deleted, the old volumes will be deleted, then if need be you can try to migrate again.