Operation Manual

Indexing

An activity (p. 236) performed by a storage node (p. 246) after a backup (p. 236) has been saved to a

deduplicating vault (p. 240).

During indexing, the storage node performs the following operations:

 Moves data blocks from the backup to a special file within the vault. This file is called the

deduplication data store.

 In the backup, replaces the moved blocks with their fingerprints ("hashes")

 Saves the hashes and the links that are necessary to "assemble" the deduplicated data, to the

deduplication database.

Indexing can be thought of as "deduplication at target", as opposed to "deduplication at source"

which is performed by the agent (p. 236) during the backup operation (p. 236). A user can suspend

and resume indexing.

Local backup plan

A backup plan (p. 237) created on a managed machine (p. 244) using direct management (p. 240).

Local task

A task (p. 247) created on a managed machine (p. 244) using direct management (p. 240).

Logical volume

This term has two meanings, depending on the context.

 A volume, information about which is stored in the extended partition table. (In contrast to a

primary volume, information about which is stored in the Master Boot Record.)

 A volume created using Logical Volume Manager (LVM) for Linux kernel. LVM gives an

administrator the flexibility to redistribute large storage space on demand, add new and take out

old physical disks without interrupting user service. Acronis Backup Agent (p. 236) for Linux can

access, back up and recover logical volumes when running in Linux with 2.6.x kernel or a

Linux-based bootable media (p. 237).

Machine

A physical or virtual computer uniquely identified by an operating system installation. Machines with

multiple operating systems (multi-boot systems) are considered as multiple machines.

Managed machine

A machine (p. 244), either physical or virtual, where at least one Acronis Backup Agent (p. 236) is

installed.