05-24-2018 08:32 PM
I have discovered something annoying after doing some test uploads to the cloud and reviewing my Amazon S3 billing...
$0.01 per 1,000 PUT, COPY, POST or LIST requests to Standard-Infrequent Access
3,659,107 Requests .................. $36.59
Huh? What is going on? Why so many of these requests? So I go poking around in the bucket to see what is in there....
Folder BEOST_00000008
etc
So, it appears Backup Exec is breaking up my data into millions of tiny files that are only 1 megabyte in size, and thereby jacking up my cloud storage costs with so many GET/POST commands.
Yet weirdly, although I can set a "Maximum file size" for data stored to a physical local drive, I can not find an equivelant file size setting for cloud storage, and the size is apparently forced to be 1 megabyte.
Why am I not permitted to have control over this? If I could just increase the cloud file size to 10 megabytes, my Amazon billing for GET/POST would drop to 1/10th of the charges so far.
,
I am aware that choosing a larger cloud storage file size will increase costs for restore downloads of small data requests, but restores will happen extremely rarely, so it is a cost that can be largely ignored as part of day-to-day operations.
05-25-2018 12:01 AM
Do you stil have verify enabled as verify counts as a read operation so may incur costs
05-25-2018 02:59 AM
Verify is disabled on all my cloud backup jobs.