This is all simple.  Just drop the LUNs from the file server, give them to the cluster and assign them as pass through disk to the guest OS.  Simple…

Except, I kept getting the following errors when I try to do the import:

An online pack already exists.

The operation failed, because an online pack object already exists.

The provider encountered an error while merging two packs.

I mean really…  what does all that mean.  I couldn’t find anything pertinent in my searches, I tried working in Diskpart, and got some of the same errors.

After lots of searches, I couldn’t find anything to help.  So I opened a ticket with Microsoft.  I got a very helpful person who told me that it basically sounds like a driver issue, but he couldn’t say for certain.  He couldn’t find much on it either.

So on a whim, I moved my test LUN from my production file server to another 2003 server.  That worked just fine, so I then moved it from there to the 2008 R2 machine that I had been working with.  That worked just fine.  Weird…

So I checked the driver for the production file server:

and compared that to the other 2003 server:

As you can tell, the culprit seems to be an outdated driver on the current file server.  Seems I don’t keep things as up to date as I should.

Well, if you have a new DPM server and not a lot of protection groups created, and you haven’t been protecting anything much, you can just click on the link in the warning message that says “Allocate more disk space for replica…”  That pulls up a pretty window that looks like the one below:

So you go ahead an make the number in the “Replica Volume” field a little bigger, hit ok and go on about your business.  Unless..

Sometimes you may need to go and use DISKPART to manually add space to the volume.  If you try the above method, and you get a failed message instead of success, you are either out of disk space, or it could be that you have more than one disk on your DPM server and one of the disks becomes full.  In order to extend the volume onto another disk, you have to use DISKPART.  DPM (at this version) won’t do it for you.

1. Open a command prompt (run as administrator if you are using a 2008 Server for your DPM server) and type “diskpart”. 
2. Type “List Volume” at the prompt.
3. Right click and “select all” then enter to copy the output to the clipboard
4. Paste it in notepad so you can do a search and search for the Data Source
   1. You should see a line similar to this:

      Volume 534       DPM-Prolo  NTFS   Simple      2050 MB  Healthy
        C:\Program Files\Microsoft DPM\DPM\Volumes\Replica\SQL2.domain.com\ SqlServerWriter\PrologPilot\
      Volume 535       DPM-Prolo  NTFS   Simple      2050 MB  Healthy
        C:\Program Files\Microsoft DPM\DPM\Volumes\DiffArea\SQL2.domain.com\ SqlServerWriter\PrologPilot\
      Volume 536       DPM-Non VSS  NTFS   Simple      1540 MB  Healthy
        C:\Program Files\Microsoft DPM\DPM\Volumes\Replica\quick1.domain.com\Non VSS Datasource Writer\Computer\SystemState\SystemState

   1. The volume number  comes before what it is describing and there are 2 for each protected object.  A Replica volume and a DiffArea.  The replica volume is a copy of the data as it is on the protected member.  The DiffArea is where the recovery points are stored.  The “Non VSS Datasource Writer” is system state in the example.
5. At the DISKPART> prompt type “select volume” and the volume number i.e. : select volume 534
6. If you want to see the details about the disk, you can type detail volume and it gives an output similar to:
   

   DISKPART> detail volume

     Disk ###  Status      Size     Free     Dyn  Gpt
     ——–  ———-  ——-  ——-  —  —
   * Disk 2    Online      2560 GB   356 GB   *    *

   Read-only              : No
   Hidden                 : No
   No Default Drive Letter: Yes
   Shadow Copy            : No
   Dismounted             : No
   BitLocker Encrypted    : No

   Volume Capacity        : 1030 MB
   Volume Free Space      :  186 MB

7. In order to increase the space for the Replica volume you would type: EXTEND SIZE=1024 DISK=2.  This would extend the selected volume by 1 GB (1024 MB) on DISK 2. 
8. Now you have to go back in and tell DPM that you extended the volume.  (I believe it may figure it out on its own eventually, but I prefer to get the warning cleared up sooner rather than later, so I go update DPM.

Note:  Each time you use DISKPART, you are likely to see different numbers for the volumes.  I haven’t looked into what that is, but I do know that the system volume is always one of the last in the list.  For that reason I recommend that you always view detail volume after you select it, to make sure you are seeing the volume you intend to work with.