In some cases, you need to regularly create a full backup. For example, your corporate backup policy may require that you create a full backup on weekend and run incremental backup on work days. To let you conform to these requirements, Veeam Agent for Oracle Solaris lets you create active full backups.
When Veeam Agent for Oracle Solaris performs active full backup, it produces a full backup file and adds this file to the backup chain.
The active full backup resets the backup chain. All incremental backup files use the latest active full backup file as a new starting point. A previously used full backup file and its subsequent incremental backup files remain on the disk. After the last incremental backup file created prior to the active full backup becomes outdated, Veeam Agent for Oracle Solaris automatically deletes the previous backup chain. To learn more, see Retention Policy for Active Full Backups.
You can create active full backups manually or schedule a backup job to create active full backups periodically. To learn more, see Creating Active Full Backups and Configuring Active Full Backup Schedule.
You can schedule a backup job to create active full backups periodically.
Active full backup schedule depends on the regular backup schedule. When you configure active full backup schedule, Veeam Agent does not create a record in the crontab configuration file as in case of the regular schedule. Instead, Veeam Agent creates a record in the configuration database. The record instructs the product to create active full backup during the first backup job session (started either automatically upon schedule or manually) that will run on the specified day.
For example, you configure a backup job with the following settings:
- The backup job starts upon schedule at 15:00 daily.
- The backup job creates active full backups weekly, on Friday.
If the backup job session started automatically at 15:00 is the first session that runs on Friday, Veeam Agent will create an active full backup during this session. During subsequent job sessions that run on Friday, Veeam Agent will create incremental backups.
If the first backup job session that runs on Friday is a session that you start manually (for example, at 13:00), Veeam Agent will create an active full backup during this backup job session. During subsequent job sessions that run on Friday (including the scheduled job session that starts at 15:00), Veeam Agent will create incremental backups.
Note that if the job is not scheduled to run on Friday, Veeam Agent will not create an active full backup on this day.
To be able to restore data from a Veeam Agent backup, you need to have a full backup file and a chain of subsequent incremental backup files on the disk. If you delete a full backup file, the whole chain of incremental backup files will become useless. In a similar manner, if you delete any incremental backup file before the point to which you want to roll back, you won’t be able to restore data (since later incremental backup files depend on earlier incremental backup files).
For this reason, if you create an active full backup, in some days there will be more restore points on the disk than specified by retention policy settings. Veeam Agent for Oracle Solaris will remove the full backup chain only after the last incremental backup file in the chain becomes outdated.
For example, the retention policy is set to 3 restore points. A full backup file is created on Sunday, incremental backup files are created on Monday and Tuesday, and an active full backup is created on Wednesday. Although the backup chain now contains 4 restore points, Veeam Agent for Oracle Solaris will not delete the previous backup chain. Veeam Agent for Oracle Solaris will wait for the next 2 incremental backup files to be created, and only then will delete the whole previous chain, which will happen on Friday. As a result, although the retention policy is set to 3 restore points, the actual number of backup files on the disk will be greater for some time.
Veeam Agent for Oracle Solaris treats the active full backup in the same way as a regular full backup. If some restore point becomes obsolete, Veeam Agent for Oracle Solaris will re-build the full backup file to include in it data of the incremental backup file that follows the full backup file. After that, Veeam Agent for Oracle Solaris will remove the earliest incremental backup file from the chain as redundant.