52 Copyright © Acronis International GmbH, 2002-2016
To delete a virtual machine that is running from a backup
1. On the All machines tab, select a machine that is running from a backup.
2. Click Delete.
The machine is removed from the web interface. It is also removed from the vSphere or Hyper-V
inventory and datastore (storage). All changes that occurred to the data while the machine was
running are lost.
2.12.1.3 Finalizing the machine
While a virtual machine is running from a backup, the virtual disks' content is taken directly from that
backup. Therefore, the machine will become inaccessible or even corrupted if the connection is lost
to the backup location or to the backup agent.
For an ESXi machine, you have the option to make this machine permanent, i.e. recover all of its
virtual disks, along with the changes that occurred while the machine was running, to the datastore
that stores these changes. This process is named finalization.
Finalization is performed without downtime. The virtual machine will not be powered off during
finalization.
To finalize a machine that is running from a backup
1. On the All machines tab, select a machine that is running from a backup.
2. Click Finalize.
3. [Optional] Specify a new name for the machine.
4. [Optional] Change the disk provisioning mode. The default setting is Thin.
5. Click Finalize.
The machine name changes immediately. The recovery progress is shown on the Activities tab. Once
the recovery is completed, the machine icon changes to that of a regular virtual machine.
2.12.2 Application-aware backup
When you back up an ESXi virtual machine running Microsoft SQL Server, Microsoft Exchange Server,
or Active Directory Domain Services, enable Application backup for additional protection of these
applications' data.
Why use application-aware backup?
By using application-aware backup, you ensure that:
1. The applications are backed up in a consistent state and thus will be available immediately after
the machine is recovered.
2. You can recover the SQL and Exchange databases without recovering the entire machine. Thus,
you do not need to install Agent for SQL or Agent for Exchange in the guest system and create an
additional backup plan to protect the applications.
3. The SQL and Exchange transaction logs are truncated after each successful backup. SQL log
truncation can be disabled in the backup plan options.
4. If a domain contains more than one domain controller, and you recover one of them, a
nonauthoritative restore is performed and a USN rollback will not occur after the recovery.
