Friday, March 01, 2013 5:16 PM
I'm about to move a large (>1TB) amount of data to some manually created replicas on a secondary DPM server. I mount each volume with the "mountvol" command, but are getting alerts saying "there is not enough space on DPM-vol_xxxxx-xxxxxx-xxxxxx". It's obvious that it's the disk space of the system drive C: it's all about, but the replica path is actually a shortcut to the "real" storage - which has several TB free space left.
Is there a way to solve this?
- Moved by Mike JacquetMicrosoft Employee, Moderator Friday, March 01, 2013 11:44 PM
Friday, March 01, 2013 11:43 PMModerator
Please provide step by step details of the procedure you are following when you get the error and the "exact error" you get.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.
Sunday, March 03, 2013 2:49 PM
Forget about this. I noticed that I managed to mount the recovery point volume instead, which happened to be exactly as large as the system drive (!). When changing to the replica volume, copying the .vhd files works just fine :)
- Marked As Answer by Amir J Sunday, March 03, 2013 2:49 PM