Acronis Snap Deploy 4 - User Guide - Manual (Page 139)

139 Copyright © Acronis International GmbH, 2002-2012
/restore_bootable: <auto|on
|off>
Sets the rule of deployment for the master boot record (MBR) when
deploying a volume (when deploying a disk, MBR is always deployed):
 auto: Deploy the MBR only when deploying an active volume that
contains an operating system. Use this setting to ensure that the
operating system can boot.
 on: Deploy the MBR when deploying any active volume, no matter
whether the volume contains an operating system or not.
 off: Do not deploy the MBR. Use this setting, for example, to preserve
the Unix boot loader.
/type: <active|primary|logi
cal >
Sets the deployed volume to active, primary or logical, if possible (for
example, there cannot be more than four primary volumes on a disk).
Setting a volume to active always sets it to primary, but a volume that is set
to primary may remain non-active.
If the type is not specified, the software tries to keep the target volume
type. If the target volume is active, the deployed volume is set to active. If
the target volume is primary and there are other primary volumes on the
disk, one of them will be set to active, and the deployed volume becomes
primary. If no other primary volumes remain on the disk, the deployed
volume is set to active.
When deploying a volume to unallocated space, the software extracts the
volume type from the image. For a primary volume, the type will be set as
follows:
 If the target disk is the first according to BIOS and it has no other
primary volumes, the deployed volume will be set to active.
 If the target disk is the first according to BIOS and there are other
primary volumes on it, the deployed volume will be set to logical
 If the target disk is not the first according to BIOS, the deployed volume
will be set to logical.
/preserve_mbr When deploying a volume over an existing one, the target volume is
deleted from the disk along with its entry in the target disk’s master boot
record (MBR). Then, with the /preserve_mbr parameter, the deployed
volume’s entry will occupy the upper empty position in the target disk’s
MBR. Thus, the target disk’s MBR is preserved.
Without this parameter, the deployed volume’s entry will occupy the same
position as in the source disk MBR saved in the image. If the position is not
empty, the existing entry will be moved to another position.
/preserve_disk_layout
When deploying an MBR disk or volume with a convertible OS, and
the target drive is larger than 2 TB, the target drive is converted to
GPT by default. To disable this default behavior and preserve the
MBR disk layout on the deployed machine, use
/preserve_disk_layout parameter. This may be useful when
are deploying an image to a machine that does not support UEFI
architecture and thus cannot boot from a GPT volume.
This parameter is an equivalent for the deployment template option
Convert disk to GPT if target disk is larger than 2 TB (p. 86).