Hello,
I noticed that when backing up to S3, SBP has to read the destination volume up at S3 before deciding what has changed from the source.
I don't use S3 for collaboration and only have SBP backing up subfolders of a bucket from one server. So I feel that SBP doesn't have to waste the time (and billable transfer bytes) to read the S3 volume every time before uploading. Depending on the volume up at S3, the initial read/compare can take a long time before any uploading changed files takes place.
This brings up several questions:
- Is there a way that SBP has it's own DB where it does not have to read what is up at S3 first? Obviously this isn't favored if you have other sources changing the S3 files without SBP knowing it, but it my case, I don't.
- Is there a toggle I have missed to prevent this big initial "read" portion of the backup?
Thanks in advance.
I noticed that when backing up to S3, SBP has to read the destination volume up at S3 before deciding what has changed from the source.
I don't use S3 for collaboration and only have SBP backing up subfolders of a bucket from one server. So I feel that SBP doesn't have to waste the time (and billable transfer bytes) to read the S3 volume every time before uploading. Depending on the volume up at S3, the initial read/compare can take a long time before any uploading changed files takes place.
This brings up several questions:
- Is there a way that SBP has it's own DB where it does not have to read what is up at S3 first? Obviously this isn't favored if you have other sources changing the S3 files without SBP knowing it, but it my case, I don't.
- Is there a toggle I have missed to prevent this big initial "read" portion of the backup?
Thanks in advance.