User Guide

Copyright © Acronis, Inc., 2000-2009 17
 BackupComments – The backup comments: in the GUI, the contents of the Archive comments
field of the backup plan under which the backup was created
 IsSectorBySectorBackup – Equals 1 if the backup is sector-by-sector (as opposed to a backup
performed by taking a disk snapshot); otherwise, equals 0
 IsLiveLinuxBackup – Equals 1 if the backup was created by Agent for Linux; otherwise, equals 0
 BackupOccupiedSpace – The size actually occupied by the backup
 BackupUniqueDataSize – The amount of backed up data that is not deduplicated or indexed at
the moment. After indexing of the backup is completed, this data includes disk blocks of a
nonstandard size (for disk backups) and small files (for file backups).
If deduplication is not performed on the backup (for example, when the vault is non-deduplicated
or when the archive is encrypted), the value in this column is the same as in the BackupDataSize
column.
 BackupDataSize – The amount of data that was backed up to the backup.
 BackupOriginalDataSize – The amount of data that can be recovered from the backup. For a full
backup, this amount is the same as in the BackupDataSize column. For an incremental or
differential backup, this amount may include data from the backups on which the given backup
depends. You will find an example in the section Original data size (p. 17).
 ArchiveID – The unique identifier of the archive
 VaultID – The unique identifier of the managed vault in which the archive is stored
 HostID – The unique identifier of the agent that ran the corresponding backup plan.
 ManagedEntityID – The unique identifier of the physical machine where the corresponding
backup plan ran.
 BackupID – The unique identifier of the backup
5.5.4 Original data size
The original data size of a backup shows the amount of data that can be recovered from that backup.
To illustrate this size, let us suppose the following:
 You have an archive consisting of two backups: the first backup is full and the second backup is
incremental.
 The amount of data that was backed up to the first and second backups is 100 GB and 10 GB,
respectively.
 The 10 GB in the second backup include 5 GB of data that changed since the first backup,
and 5 GB of new data.
In this case, the amount of data that you can recover from the first (full) backup is 100 GB.
The amount of data that you can recover from the second (incremental) backup is 105 GB; namely,
10 GB of the new and changed data that is stored in this backup, plus 95 GB of the unchanged data
that is stored in the full backup.
Thus, the original data sizes of the first and second backups are 100 GB and 105 GB, respectively.
The original data size of an archive is the sum of the original data sizes of its backups—in this
example, 205 GB. It shows the total size of the sets of data that can be recovered from the archive.
The original data size of a vault is the sum of the original data sizes of the archives stored in the vault.