On 6/7/23 10:21, Samantha Falconer wrote:
We're running Bacula v13.0.1. Some of our backups are to S3 which then go to Glacier after a set period of time. When doing
restores from S3, the necessary file is downloaded automatically from S3 but, if it involves Glacier, it appears that no
attempt is made to retrieve the file. Bacula just sits waiting for the part file, so we have to actually manually initiate
the retrieval from Glacier and then Bacula continues once the part file has appeared in S3.
https://www.bacula.org/13.0.x-manuals/en/main/Storage_Daemon_Configuratio.html
<https://www.bacula.org/13.0.x-manuals/en/main/Storage_Daemon_Configuratio.html> seems to indicate that Bacula works with AWS
Glacier as it states:
Transfer Priority = <High | Medium | Low>
When restoring directly a part from Glacier, this directive indicates the
rehydration priority level. Values can be High,
Medium or Low. Default is High. Those values match respectively Expeditive,
Standard and Bulk transfers tiers within S3.
We configured Transfer Priority = "Low" so we expected it to use the Bulk transfer tier - see
https://docs.aws.amazon.com/amazonglacier/latest/dev/downloading-an-archive-two-steps.html
<https://docs.aws.amazon.com/amazonglacier/latest/dev/downloading-an-archive-two-steps.html>. Is Bacula capable of
initiating the Glacier restore? Or is that config (Transfer Priority) not what we thought?
Hello Samantha, As far as I know, only the S3 plugin has been ported from the Enterprise edition to the Community edition.In the Enterprise edition, there is an additional 'Glacier' plugin which automatically handles these transfers from Glacier back to the S3 bucket.
I have a strong feeling this is the issue you are experiencing here. Best regards, Bill -- Bill Arlofski w...@protonmail.com
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
