Backup plans that operate with the same archive should back up the same data items (say, both
plans back up volume C.)
2. Applying multiple retention rules to an archive makes the archive content in some way
unpredictable. Since each of the rules will be applied to the entire archive, the backups belonging
to one backup plan can be easily deleted along with the backups belonging to the other. You
should especially not expect the classic behavior of the GFS and Tower of Hanoi backup schemes.
Normally, each complex backup plan should back up to its own archive.
6.2.8
Simplified naming of backup files
If you select the Name backup files using the archive name... check box:
The file name of the first (full) backup in the archive will consist of the archive name; for
example: MyData.tib. The file names of subsequent (incremental or differential) backups will
have an index; for example: MyData2.tib, MyData3.tib, and so on.
This simple naming scheme enables you to create a portable image of a machine on a detachable
media or move the backups to a different location by using a script.
Before creating a new full backup, the software will delete the entire archive and start a new
one.
This behavior is useful when you rotate USB hard drives and want each drive to keep a single full
backup (p. 111) or all backups created during a week (p. 112). But you might end up with no
backups if a full backup to your only drive fails.
This behavior can be suppressed by adding the [Date] variable (p. 113) to the archive name.
If you do not select the Name backup files using the archive name... check box:
Each backup will have a unique file name with the exact time stamp and the backup type; for
example: MyData_2010_03_26_17_01_38_960D.tib. This standard file naming allows for a wider
range of backup destinations and backup schemes.
Restrictions
When using simplified file naming, the following functionality is not available:
Setting up full, incremental and differential backups within a single backup plan. You need to
create separate backup plans for each type of backup
Backup to a managed vault, tape, Acronis Secure Zone or Acronis Online Backup Storage
Setting up retention rules
Setting up regular conversion of backups to a virtual machine
Tip.The FAT16, FAT32, and NTFS file systems do not allow the following characters in the file name:
backslash (\), slash (/), colon (:), asterisk (*), question mark (?), quotation mark ("), less than sign (<), greater
than sign (>), and pipe (|).
6.2.8.1
Usage examples
This section provides examples of how you can use simplified file naming.
Example 1. Daily backup replacing the old one
Consider the following scenario:
You want to perform a daily full backup of your machine.
110
Copyright © Acronis, Inc., 2000-2010
Need help?
Do you have a question about the BACKUP AND RECOVERY 10 SERVER FOR LINUX - UPDATE 3 and is the answer not in the manual?