You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After noticing my GCP CloudStorage costs starting to increase, I found that the pi-hole is being backed up ~2/daily. While it was unnoticeable at first with the image being so small to start (~5mb), but as the pi-hole persisted and was logging, so did it's size. From Oct 31 to May 6 the size of the pi-hole image had reached >186mb. It also appears that there is no retention policy outlined in the ansible script (nor by default in GCP?). These balloned to nearly 40gb in ~6mos, and potentially would continuing growing indefinitely.
Digging into the GCP playbook; there is a section named Pihole to backup timer with a [Timer] OnUnitActiveSec=12h
This value is "ok" (I changed it to 48hrs, though arguably 24hrs is more appropriate).
I believe adding a retention "policy" to the ansible script would be appropriate.
I have began testing an added field to the pihole-to-backup.yml file:
- name: Delete old backups (keep last 30 days)
shell: |
gsutil ls gs://YOUR-BUCKET-NAME/pihole | sort -r | tail -n +31 | while read file; do
gsutil rm "$file"
done
The text was updated successfully, but these errors were encountered:
After noticing my GCP CloudStorage costs starting to increase, I found that the pi-hole is being backed up ~2/daily. While it was unnoticeable at first with the image being so small to start (~5mb), but as the pi-hole persisted and was logging, so did it's size. From Oct 31 to May 6 the size of the pi-hole image had reached >186mb. It also appears that there is no retention policy outlined in the ansible script (nor by default in GCP?). These balloned to nearly 40gb in ~6mos, and potentially would continuing growing indefinitely.
Digging into the GCP playbook; there is a section named Pihole to backup timer with a [Timer] OnUnitActiveSec=12h
This value is "ok" (I changed it to 48hrs, though arguably 24hrs is more appropriate).
I believe adding a retention "policy" to the ansible script would be appropriate.
I have began testing an added field to the pihole-to-backup.yml file:
The text was updated successfully, but these errors were encountered: