Progressive Full Backups - how to configure
Progressive Full Backups represent a significant evolution in our backup/retention policies and procedures
available for both Hosted and Self Hosted customers
The way this works is as follows
- original full backup taken over the network
- incremental backups are then taken forever over the network
- when retention is reached, our system will take a new Virtual Full (performed directly on the storage device), by combining the original full, with the next incremental, to create a new full
- each day afterwards, the full from the beginning of the retention will be combined with the next incremental to create a new Full, and the original Full will be dropped
Since we have 1 full per retention period, we do not require fulls at the middle and end of the retention period. Total disk space savings on storage is approx 60%, and can be even more in various scenarios
Additionally, since we compile a new full + incremental each time to generate a new full, the full never ages to a point where recompiling for restores because extensively prolonged because of software overhead associated with recompiling all that data.
The ONLY exception to such a setup is scenarios with very long retention periods. In such cases, the "Virtual Full" option should be selected, which will create regular full (virtual) backups throughout the retention period
To activate Progressive Fulls - enter the wizard for a server and navigate to the "pool" section and simply select "Progressive" (currently flagged as "expiremental"). This is safe to use now and in the very near future will be the default option set under this section
Once configured and set (and/or cycled through if you switch an existing server with "Virtual" or "Classic" Full over to new Progressive Full), your restore points will look similar to the below. Notice the single Full at the oldest retention point, with all other restore points being Incremental
PLEASE NOTE - You can switch any server/vm from Classic Full or Virtual Full to Progressive at anytime. However, when switching existing servers, it will take a full retention period to cycle out the previous Full mechanism with the new Progressive Full method
Related Articles
Progressive Full Backups - How to Configure
Progressive Full Backups represent a significant evolution in our backup/retention policies and procedures available for both Hosted and Self Hosted customers The way this works is as follows - original full backup taken over the network - ...DCE/Self Hosted Installs - New Linux BMR and Progressive Full Backups launched - EOL Legacy BMR March 31st 2016
Bacula4 is pleased to announce 2 new Key Features for our DCE/Self Hosted customers. New Linux ReaR BMR PLEASE NOTE - Legacy BMR will be EOL March 31st 2016 and will be completely removed from your installs Action Required - Please enter the wizard ...Enable PST backups for Exchange
To enable PST Dumps / Backups on exchange: In the wizard while adding the server select the option for PST backups. On the exchange server itself create a directory in the main drive , call it anything relevant (ie baculapst) Share that folder with ...Enable PST backups for Exchange
To enable PST Dumps / Backups on exchange: In the wizard while adding the server select the option for PST backups. On the exchange server itself create a directory in the main drive , call it anything relevant (ie baculapst) Share that folder with ...Configure eMail Notifications
1) in your admin interface > config > SMTP. enter in your SMTP configuration and test to ensure all is working 2) within the end user account, under settings, configure the email notifications you desire