User guide

GFS (Grandfather-Father-Son)

A popular backup scheme (p. 239) aimed to maintain the optimal balance between a backup archive

(p. 238) size and the number of recovery points (p. 248) available from the archive. GFS enables

recovering with daily resolution for the last several days, weekly resolution for the last several weeks

and monthly resolution for any time in the past.

For more information please refer to GFS backup scheme.

Image

The same as Disk backup (p. 243).

Incremental backup

A backup (p. 238) that stores changes to the data against the latest backup. You need access to other

backups from the same archive (p. 238) to recover data from an incremental backup.

Indexing

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

deduplicating vault (p. 242).

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. 238) during the backup operation (p. 238). A user can suspend

and resume indexing.

Local backup plan

A backup plan (p. 239) created on a managed machine (p. 247) using direct management (p. 242).

Local task

A task (p. 249) created on a managed machine (p. 247) using direct management (p. 242).

Logical volume

This term has two meanings, depending on the context.