jczornik / glacier_backup Goto Github PK

Is your feature request related to a problem? Please describe.
Creating big archives takes a long time - reduce time spent on encrypting archives.

Describe the solution you'd like
To work around this problem, we should split the archive before encrypting it.

Is your feature request related to a problem? Please describe.
We are unable to send archives larger than 4GB to Glacier. As specified here: https://docs.aws.amazon.com/amazonglacier/latest/dev/uploading-an-archive.html - for uploading a larger archive, we should use multi-part upload. It is recommended for archives larger than 100MB

Describe the solution you'd like
Check archive size and use the proper upload method.

Is your feature request related to a problem? Please describe.
The manifest file is only stored on disk, and we rely on the end user not to remove it. The better way is to store content in the local database.

Describe the solution you'd like
Store manifest files in db and on the local filesystem.

Add a missing description of the DB configuration to the README file.

Is your feature request related to a problem? Please describe.
When creating a backup for a directory that is actively used, we may get errors for tar like:

• file-removed
• file-changed

Describe the solution you'd like
The backup should be successful if the content of the directory has changed.

Describe alternatives you've considered
A user may specify which warnings to ignore.

Add information about running jobs to SQLite db. It will allow us to roll back failed jobs in case the job is not finished and the program crushes.

Describe the bug
When uploading big archives, we are trying to send more than 1000 parts.