Reducing operational cost for backup copy to Google Cloud

[ryand22]

I have an issue when backing up primary backup file from local storage to Google Cloud and the storage class using Nearline storage, it requires very high costs when writing and deleting data because it is calculated per file in Google Cloud storage (CMIIW).
The question is whether the Veeam backup file structure that is copied from local storage to Google Cloud (with VBK & VIB format) can be converted to be less like the file format in local storage? because what I currently see is that the file structure that is copied to Google Cloud storage becomes many small files, not like in local storage.

Thanks for your kind of answer.

Best regards,
Ryan

[tyler.jurgens]

You can adjust the block size in your backup job to push larger blocks to your S3 compatible storage. There is no way to have it generate files in the old format though with a backup/backup copy job.