Dynamic group, Dynamic volume, Encrypted archive – Acronis Backup for Windows Server Essentials - User Guide User Manual
Page 437: Encrypted vault
437
Copyright © Acronis International GmbH, 2002-2014
LDM Metadata
partition
1 MB
Dynamic disks organized on MBR (Disk 1) and GPT (Disk 2) disks.
For more information about dynamic disks please refer to the following Microsoft knowledge base
articles:
Disk Management (Windows XP Professional Resource Kit)
http://technet.microsoft.com/en-us/library/bb457110.aspx
816307 Best practices for using dynamic disks on Windows Server 2003-based computers
http://support.microsoft.com/kb/816307
Dynamic group
A group of machines (p. 439) which is populated automatically by the management server (p. 439)
according to membership criteria specified by the administrator. Acronis Backup offers the following
membership criteria:
Operating system
Active Directory organizational unit
IP address range
Listed in txt/csv file.
A machine remains in a dynamic group as long as the machine meets the group's criteria. However,
the administrator can specify exclusions and not include certain machines in the dynamic group even
if they meet the criteria.
Dynamic volume
Any volume located on dynamic disks (p. 436), or more precisely, on a disk group (p. 436). Dynamic
volumes can span multiple disks. Dynamic volumes are usually configured depending on the desired
goal:
to increase the volume size (a spanned volume)
to reduce the access time (a striped volume)
to achieve fault tolerance by introducing redundancy (mirrored and RAID-5 volumes.)
E
Encrypted archive
A backup archive (p. 431) encrypted according to the Advanced Encryption Standard (AES). When the
encryption option and a password for the archive are set in the backup options (p. 431), each backup
belonging to the archive is encrypted by the agent (p. 431) before saving the backup to its
destination.
Encrypted vault
A managed vault (p. 439) to which anything written is encrypted and anything read is decrypted
transparently by the storage node (p. 441), using a vault-specific encryption key stored on the node.