CAPÍTULO II. EL SISTEMA ELÉCTRICO
2.3. UN PASO MÁS PARA LAS FUENTES DE GENERACIÓN
Rather than converting a TIB file to a virtual disk file, which requires additional operations to bring the virtual disk into use, Acronis Backup performs the conversion by recovery of a disk backup to a fully configured and operational new virtual machine. You have the ability to adapt the virtual machine configuration to your needs when configuring the recovery operation.
With Acronis Backup Agent for Windows or Agent for Linux, you can create a new virtual machine in a local or network folder. You can start the machine using the respective virtualization software or prepare the machine files for further usage. The following table summarizes the available virtual machine formats and the actions you can take to add the machine to a virtualization server.
VM format Further action and tool to use Target virtualization
platform
VMware Workstation Export using VMware Workstation; or
Convert to OVF using VMware OVF tool > Deploy OVF template using vSphere Client
ESX(i)
Microsoft Virtual PC* Add the VHD file to a Hyper-V machine Hyper-V
Citrix XenServer OVA Import using Citrix XenCenter XenServer
Kernel-based Virtual Machine (Raw format)
Move the virtual machine files to a machine running Linux and run the virtual machine by using Virtual Machine Manager
- Red Hat Enterprise
Virtualization (RHEV) (Raw format)
Import using RHEV Manager RHEV
*Microsoft Virtual PC does not support disks that are larger than 127 GB. Acronis enables you to create a Virtual PC machine with larger disks so that you can attach the disks to a Microsoft Hyper-V virtual machine. With Acronis Backup Agent for Hyper-V or Agent for VMware, you can create a new virtual machine directly on the respective virtualization server.
6.2.3.1
Steps to perform
To perform a recovery to a new virtual machine
1. Connect the console to the management server, to a machine where an agent is installed, or to a machine booted from a bootable media.
2. Click Recover to open the Recover data (p. 100) page.
3. Click Select data (p. 101). Use the Data view tab or the Archive view tab to select the disks or volumes to convert.
4. In Recover to, select New virtual machine.
5. Click Browse. In the VM/VS Selection (p. 137) window, select the resulting virtual machine type or the virtualization server where to create the machine.
6. [Optional] In Storage, you can view or select the storage where the virtual machine will be created.
7. [Optional] In Virtual machine settings (p. 138), you can change the name of the virtual machine, the disk provisioning mode, the allocated memory, and other settings.
Machines of the same type and with the same name cannot be created in the same folder. If you get an error message caused by identical names, change either the VM name or the path.
8. The destination disk for each of the source disks or source volumes and the MBRs will be selected automatically. If required, you can change the destination disks.
On a Microsoft Virtual PC, be sure to recover the disk or volume where the operating system's loader resides to the Hard disk 1. Otherwise, the operating system will not boot. This cannot be fixed by changing the boot device order in BIOS, because a Virtual PC ignores these settings.
9. In When to recover, specify when to start the recovery task.
10. [Optional] In Task, review Recovery options and change the settings from the default ones, if need be. You can specify in Recovery options > VM power management whether to start the new virtual machine automatically after the recovery is completed. This option is available only when the new machine is created on a virtualization server.
11. Click OK. If the recovery task is scheduled for the future, specify the credentials under which the task will run.
In the Backup plans and tasks view, you can examine the state and progress of the recovery task.
6.2.3.2
Virtual machine type / virtualization server selection
Select the resulting virtual machine type or the virtualization server where the machine will be created.
The available options depend on the agent(s) installed on the machine the console is connected to. If the console is connected to the management server, you can choose any registered machine that is able to perform the required operation.
To select the virtualization server where the new virtual machine will be created
1. Choose the Create a new virtual machine on the server option.2. In the left part of the window, select the virtualization server. Use the right part of the window to review details on the selected server.
[Only if the console is connected to the management server] If multiple agents manage the selected ESX(i) host, you can choose the agent that will perform recovery. If no agent manages the ESX(i) and automatic deployment is turned on, Agent for VMware (Virtual Appliance) will be
deployed immediately after you click OK. Recovery will be performed by that agent. It will take a license.
3. Click OK to return to the Recover data page.
To select the virtual machine type
1. Choose the Save the virtual machine as a set of files option.
2. In the left part of the window, select the virtual machine type. Use the right part of the window to review details on the selected virtual machine type.
[Only if the console is connected to the management server] You can select the machine that will perform recovery. This can be any registered machine where Agent for Windows or Agent for Linux is installed.
3. Click OK to return to the Recover data page.
6.2.3.3
Virtual machine settings
The following virtual machine settings can be configured.
Disks
Initial setting: the number and size of the source machine's disks.
The number of disks is generally equal to that of the source machine. It might be different if the software has to add more disks to accommodate the source machine volumes because of limitations set by the virtualization product. You can add virtual disks to the machine configuration or, in some cases, delete the proposed disks.
When adding a new virtual disk, along with interface and capacity, you can specify its format.
Thin format. The disk occupies as much storage space as the data it stores. This saves the storagespace. To enable thin format, select the Thin provisioning (for ESX), or Dynamically expanding disk (for Hyper-V) check box.
Thick format. The disk occupies all the provisioned storage space. This improves the virtual machine performance. To use thick format, clear the Thin provisioning (for ESX), or Dynamically expanding disk (for Hyper-V) check box.The default setting is thick format if a physical machine was backed up. When recovering from a virtual machine backup, the software tries to reproduce the format of the original machine's disks. If this is not possible, thick format is used.
Implementation of Xen machines is based on Microsoft Virtual PC and inherits its limitations: up to 3 IDE disks and 1 processor. SCSI disks are not supported.
Memory
Initial setting: if not contained in the backup, it is the default setting of the virtualization server. This is the amount of memory allocated to the new virtual machine. The memory adjustment range depends on the host hardware, the host operating system and the virtualization product settings. For example, virtual machines may be allowed to use no more than 30% of memory.
Name
Enter the name for the new virtual machine. If the backup was created by Agent for VMware or Agent for Hyper-V, the software takes the name from the virtual machine configuration contained in the backup.
Processors
Initial setting: if not contained in the backup or if the backed-up setting is not supported by the virtualization server, it is the default server's setting.
This is the number of processors of the new virtual machine. In most cases, it is set to one. The result of assignment of more than one processor to the machine is not guaranteed. The number of virtual processors may be limited by the host CPU configuration, the virtualization product and the guest operating system. Multiple virtual processors are generally available on multi-processor hosts. A multicore host CPU or hyperthreading may enable multiple virtual processors on a single-processor host.