Aller au contenu principal

Volume Number to Deploy Image on to

Thread needs solution

Just looking some confirmation that the "volume #" as displayed in diskpart is the correct number to enter into the volume field, when creating the task for a single volume deployment.

Fichier attaché Taille
diskpart.png 13.54 Ko
0 Users found this helpful

So ive just confirmed that Diskpart "Volume ###" is not correct number to use (it just ploughed through the wrong volume). Can somebody in Acronis please confirm whether I should user the "Partition ###" in Diskpart, or some other reliable method to determine the target volume on the disk.

Best Regards

 

 

Fichier attaché Taille
358920-129235.png 22.95 Ko

Hello, Richard

I'm sorry for the delayed response.

 

1. For example, we have a machine with 6 volumes (see  Source_machine.png).

2. Then we create a master image of the machine.

3. After that, we need to deploy only one volume, e.g. D:.

4. We select the created master image while creating a deployment template and see the disk layout (see Master_image_selected.PNG).  

5. The next step is to select the volume D: to deploy (see Select_D.PNG)

6. We go through the Wizard till the template settings. Then we must specify "Replace volume = 3" (Replace_volume_3.PNG), because the volume D: is the third volume, according to the disk layout (Master_image_selected.PNG).

7. Save the template and perform deployment.

 

 

Best regards.

Fichier attaché Taille
360778-129577.png 61.85 Ko
360778-129580.png 122.59 Ko
360778-129583.png 95.19 Ko
360778-129586.png 122.42 Ko

Ok, ill follow your guidlines. thanks. i maust have misread or mistyped something.

 

Cheers,

Rich

I have worked out the problem and does highlight a potential risk.

The volumes according to diskpart span across multiple disks. So my C drive is listed as volume 4. If i select this as my target in ASD the will smash through my D drive. This is because a newer PHYS drive was inserted into disk 0 (dont ask, i have no idea either). which i guess means your volume # pertains to the volume number as the image sees it for one disk.

i guess if i simply ignore the volume number that windows sees (on diskpart) and target the volume as the image sees it i will be fine.

Fichier attaché Taille
361442-129649.png 39.12 Ko

Richard,

Since you're having recovery issues, you should have a valid support case with technical support at no cost.  I would reach out to them to see if they can assist.

As I read the ocumenation, dynamic disks are not supported with Snap Deploy though..

https://kb.acronis.com/content/47391

"Imaging and deployment of dynamic disks/volumes is not supported."