google cloud platform - Storage pricing during migration from Standard type to Archive type - Stack Overflow

admin管理员组

文章数量:1289880

At the moment I have a bucket with 25.7 TiB (26,317 GiB) of data and 117 millions (approximately) of objects. It is small logs and activity files accumulated for years. Bucket's location is US multi-region and storage type is Standard. I want to optimize cost of this bucket because I'm not using these files in any way, but they must be kept. I'm planning to change storage type to Archive and change location to a single US region.

If I understand correctly:

• if I want to change only storage type, I can either change storage type of existing bucket or create new bucket with appropriate type and move all items into it
• if I want to change both storage type and location, the only I can is to create new bucket with appropriate location and type

Based on this I did pricing calculations:

• change storage type of existing bucket to Archive using Lifecycle manager: 117000000 ÷ 1000 × 0.1 [class A operations] ~ $12,000
• create new bucket in a single US region with Archive storage type and move all items into it using "TRANSFER DATA" button: (117000000 ÷ 1000 × 0.01) [storage.objects.list on the source table] + (117000000 ÷ 1000 × 0.005) [storage.objects.copy on the destination table] + (26317 * 0.02) [inner data transfer] ~ $2,300
• remove entire bucket: free
• keep current bucket as is: 26317 × 0.026 [GB price] ~ $700 [per month]
• store items in the new bucket in a single US location and Archive storage type: 26317 * 0.0012 [GB price] ~ $32 [per month]
• download current bucket using "gsutil cp": (117000000 ÷ 1000 × 0.01) [storage.objects.list] + (1000 × 0.12 + 9000 × 0.11 + 16317 × 0.08) [data transfer to US] ~ $3,600

Mostly I wonder on the first two calculations. Why difference of total costs is so big? These two actions achieve same purpose - they changing storage type. The second one is even better because I'm changing location to a single region. Because of such big difference I'm thinking that all my calculations are wrong. It is not really clear what operations of what class are involved when I'm using Lifecycle manager, TRANSFER DATA button, gsutil cp.

I'm asking this:

1. please verify or correct above calculations
2. perhaps there is any other way to optimize pricing of the source bucket? I just want to store all the items, there is no plans to interact with them in any way

Thanks!

At the moment I have a bucket with 25.7 TiB (26,317 GiB) of data and 117 millions (approximately) of objects. It is small logs and activity files accumulated for years. Bucket's location is US multi-region and storage type is Standard. I want to optimize cost of this bucket because I'm not using these files in any way, but they must be kept. I'm planning to change storage type to Archive and change location to a single US region.

If I understand correctly:

• if I want to change only storage type, I can either change storage type of existing bucket or create new bucket with appropriate type and move all items into it
• if I want to change both storage type and location, the only I can is to create new bucket with appropriate location and type

Based on this I did pricing calculations:

• change storage type of existing bucket to Archive using Lifecycle manager: 117000000 ÷ 1000 × 0.1 [class A operations] ~ $12,000
• create new bucket in a single US region with Archive storage type and move all items into it using "TRANSFER DATA" button: (117000000 ÷ 1000 × 0.01) [storage.objects.list on the source table] + (117000000 ÷ 1000 × 0.005) [storage.objects.copy on the destination table] + (26317 * 0.02) [inner data transfer] ~ $2,300
• remove entire bucket: free
• keep current bucket as is: 26317 × 0.026 [GB price] ~ $700 [per month]
• store items in the new bucket in a single US location and Archive storage type: 26317 * 0.0012 [GB price] ~ $32 [per month]
• download current bucket using "gsutil cp": (117000000 ÷ 1000 × 0.01) [storage.objects.list] + (1000 × 0.12 + 9000 × 0.11 + 16317 × 0.08) [data transfer to US] ~ $3,600

Mostly I wonder on the first two calculations. Why difference of total costs is so big? These two actions achieve same purpose - they changing storage type. The second one is even better because I'm changing location to a single region. Because of such big difference I'm thinking that all my calculations are wrong. It is not really clear what operations of what class are involved when I'm using Lifecycle manager, TRANSFER DATA button, gsutil cp.

I'm asking this:

1. please verify or correct above calculations
2. perhaps there is any other way to optimize pricing of the source bucket? I just want to store all the items, there is no plans to interact with them in any way

Thanks!

• google-cloud-platform
• google-cloud-storage
• google-cloud-billing

Share Improve this question Follow asked Feb 20 at 15:31 AmaimersionAmaimersion 1,0151818 silver badges3131 bronze badges 2

• 1 You use 0.1 for class A operations in the first one, and 0.01 in the others, which probably explains the price difference. Also note that the move in storage class is free if you use autoclass on the bucket, however this will come with a delay in change of class: cloud.google/storage/docs/autoclass#transitions which probably results in higher costs than instantly moving it to archive for your amount of data. Also storage.objects.copy is class A, you priced it as class B. And I think you missed the class B .get on download. – somethingsomething Commented Feb 20 at 15:53
• @somethingsomething I'm using this for reference - cloud.google/storage/pricing 0.1 because it targets Archive storage type, 0.01 because it targets Standard storage type. Move to Archive storage type by Autoclass also charged as class A operation, it is not free. storage.objects.copy priced at the rate of single region, while operations that target the old bucket are priced at the rate of multi region. I don't think I missed .get on download, .get is needed to retrieve file metadata, which is not the case. I think network data transfer only is enough to download file knowing URL. – Amaimersion Commented Feb 20 at 19:00

Add a comment  | 

1 Answer 1

Sorted by: Reset to default 0

Based on Autoclass pricing “There is no operation charge when Autoclass transitions an object to a colder storage class.”. In terms of your sample calculation and which is the most cost-effective solution, it would be best to consult a Google Cloud sales specialist for clarification. They can offer detailed insights based on your use-case to optimize the cost of your transition.

本文标签： google cloud platformStorage pricing during migration from Standard type to Archive typeStack Overflow