The [DATE] variable

If you specify the [DATE] variable in the archive name, the file name of each backup will include that backup’s creation date.

When using this variable, the first backup of a new day will be a full backup. Before creating the next full backup, the software deletes all backups taken earlier that day. Backups taken before that day are kept. This means you can store multiple full backups with or without incremental ones, but no more than one full backup per day. You can sort the backups by date, copy, move, delete the backups manually or by using a script.

The date format is m.d.yyyy. For example, it is 1.31.2011 for January 31, 2011. (Note absence of leading zeros.)

You can place this variable anywhere in the archive name. You can use both lowercase and uppercase letters in this variable.

  Examples  

Example 1. Suppose that you perform incremental backups twice a day (at midnight and noon) for two days, starting on January 31, 2011. If the archive name is MyArchive-[DATE]-, here is the list of backup files after day two:

MyArchive-1.31.2011-.tib (full, created on January 31 at midnight)
MyArchive-1.31.2011-2.tib (incremental, created on January 31 at noon)
MyArchive-2.1.2011-.tib (full, created on February 1 at midnight)
MyArchive-2.1.2011-2.tib (incremental, created on February 1 at noon)

Example 2. Suppose that you perform full backups, with the same schedule and archive name as in the previous example. Then, the list of backup files after day two is the following:

MyArchive-1.31.2011-.tib (full, created on January 31 at noon)
MyArchive-2.1.2011-.tib (full, created on February 1 at noon)

This is because the full backups created at midnight were replaced by new full backups of the same day.

The [DATE] variable