it's 2023 and as well all know, object storage is a very good repository. Cheap, flexible, huge capacity, reliable, almost bulletproof immutability, etc. So why not use it for agents? I have already done a test for a small PoC, but some questions are still unanswered to me:
- If a backup job runs that doesn't fit into the local cache (for instance the full backup), the object storage is immutable and you're not having the best bandwidth to it (like when using a public object storage of cloud providers), you might be in an endless loop where the backup job can't complete in time, say the user shuts down the device and the backup job is aborted - the same happened the next time the device is started. Because the repo is immutable, every block will stay there until the period has expired and will only then be deleted or even later. Correct or is there an advanced feature that would be aware of that fact?
- in addition to the last point, I assume there is no cache on the vbr-side that would temporarily store the backup so that the client can finish its job while the upload is still taking place?
What I could imagine is doing the initial backup to a local repo and move it then to the object storage, but not sure if that was ideal for the further backup flow...
Thanks in advance!