User`s guide

Please be aware that consolidation is just a method of deletion but not an alternative to deletion.

The resulting backup will not contain data that was present in the deleted backup and was

absent from the retained incremental or differential backup.

Backups resulting from consolidation always have maximum compression. This means that all

backups in an archive may acquire the maximum compression as a result of repeated cleanup

with consolidation.

Best practices

Maintain the balance between the storage device capacity, the restrictive parameters you set and

the cleanup frequency. The retention rules logic assumes that the storage device capacity is much

more than the average backup size and the maximum archive size does not come close to the

physical storage capacity, but leaves a reasonable reserve. Due to this, exceeding the archive size

that may occur between the cleanup task runs will not be critical for the business process. The rarer

the cleanup runs, the more space you need to store backups that outlive their lifetime.

The Vaults (p. 70) page provides you with information about free space available in each vault. Check

this page from time to time. If the free space (which in fact is the storage device free space)

approaches zero, you might need to toughen the restrictions for some or all archives residing in this

vault.

2.8 Backing up LVM volumes (Linux)

This section explains in brief how you would back up and recover volumes managed by Linux Logical

Volume Manager (LVM)—called logical volumes—using Acronis Backup & Recovery 10.

Acronis Backup & Recovery 10 Agent for Linux can access, back up and recover such volumes when

running in Linux with 2.6.x kernel or a Linux-based bootable media.

You can back up data of one or more logical volumes and recover it to a previously created logical

volume or a basic (MBR) disk or volume; likewise, it is also possible to recover the data of a basic

volume to a logical volume. In each case, the program stores and recovers volume contents only. The

type or other properties of the target volume will not change.

A system, recovered from a logical volume backup to a basic MBR disk, cannot boot because its kernel tries to

mount the root file system at the logical volume. To boot the system, change the loader configuration and

/etc/fstab so that LVM is not used and reactivate your boot loader as described in the Bootability

troubleshooting (p.

128) section.

When recovering a logical volume over a basic MBR volume, you can resize the resulting volume.

Before recovering logical volumes to a target machine with no corresponding logical volume

structure (for example, to recover to bare metal), you need to create the logical volumes and groups

in either of these ways:

 Before performing the first disk backup on a source machine, run the following command:

trueimagecmd --dumpraidinfo

This will save the machine's logical volume structure to the /etc/Acronis directory. Include the

volume with this directory to the list of volumes to back up.

Before the recovery, use the restoreraids.sh script in bootable media to create the structure.

 Alternatively, use the lvm utility to create the structure manually, and then perform the

recovery. You can perform this procedure either in Linux or in bootable media.