Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Backup to Google Shared Drive does not follow maximum Backup Count #7444

Open
2 tasks done
iwdinw2 opened this issue May 7, 2024 · 1 comment
Open
2 tasks done

Backup to Google Shared Drive does not follow maximum Backup Count #7444

iwdinw2 opened this issue May 7, 2024 · 1 comment
Labels
support Community support

Comments

@iwdinw2
Copy link

iwdinw2 commented May 7, 2024

Important notices

Before you add a new report, we ask you kindly to acknowledge the following:

Describe the bug

Opensense Version: OPNsense 24.1.5_3-amd64

Setting up a backup up to Google Drive you can configure a "Backup Count".
The "Backup Count" should be the maximum count of backup files in the configured drive folder.
When an new file gets uploaded to the backup folder and the maximum count ist reached, the oldest file should be deleted.
This does work with a personal Google Drive Folder.
This does not work with a Google Shared Drive Folder.

To Reproduce

  1. Set up a Google Shared Drive
  2. Create a Folder within the Google Shared Drive
  3. Follow the manual to set up the backup using Google Drive
    https://docs.opnsense.org/manual/how-tos/cloud_backup.html
  4. Use the Google Drive Folder ID from the folder creted in 2.
  5. Enter a number in "Backup Count"
  6. Execute backups or wait for backups until the number of backup files is greater than the number in "Backup Count".
  7. Realize that old backup files do not get deleted.

Expected behavior

The number of backup files should not be greater than the number in "Backup Count".
Old backup files should get deleted.

Describe alternatives you considered

Since the introduction of the possibility to backup to Google Shared Drives I waited several versions for someone to solve the issue.

Workaround: You can create a Google Apps Script that takes care of the backup count from the target side.

Relevant log files

Additional context

Environment

Software version used and hardware type if relevant, e.g.:

OPNsense 24.1.5_3-amd64
Intel(R) Celeron(R) J6413 @ 1.80GHz (4 cores, 4 threads)
Network Intel® i226-V

@AdSchellevis
Copy link
Member

could be access grants on Google's end, trying my setup with 2 works, but I do need to execute twice to see the proper number of items in the gui (removal does not drop them from the list instantly)

foreach ($configfiles as $filename => $file) {

@AdSchellevis AdSchellevis added the support Community support label May 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
support Community support
Development

No branches or pull requests

2 participants