Hi,
I am wondering if you can calculate the needed cache-size for proper S3.
Is there also a way to first write into cache and sync to s3 afterwards?
Also just pushing (similar to sync job) into S3 by using local storage would be nice, i think this can be done by creating a syncjob using the pbs itself as a target?
Right now, if S3 is slow, backup is slow. And if S3 is unavail, backup just stops/fails. (PBS is close, S3 is far. not ideally but ja)
Also: From my investigation the cache is using100GB, or maybe 10% of backup-storage used?
This is already a nice feature and running pretty stable! My home-connection is just garbage but PBS does not bother and all backups are intact =)
I am wondering if you can calculate the needed cache-size for proper S3.
Is there also a way to first write into cache and sync to s3 afterwards?
Also just pushing (similar to sync job) into S3 by using local storage would be nice, i think this can be done by creating a syncjob using the pbs itself as a target?
Right now, if S3 is slow, backup is slow. And if S3 is unavail, backup just stops/fails. (PBS is close, S3 is far. not ideally but ja)
Also: From my investigation the cache is using100GB, or maybe 10% of backup-storage used?
This is already a nice feature and running pretty stable! My home-connection is just garbage but PBS does not bother and all backups are intact =)