I went through this decision process recently for a different use case, read this thread, and decided to use Nearline. I back up ~100 GiB daily but prune only a couple times a year. After months of use 99.9% of the costs for me are byte storage and multi-region replication, meaning restic didn’t add any significant overhead with Class A and B operations. If any others want to repeat how I double-checked costs, it was straightforward to export billing data to BigQuery, wait a day for it to backfill, then run a BigQuery query like:
SELECT
project.id project,
sku.description sku,
usage_start_time,
SUM(cost) cost,
STRING_AGG(DISTINCT currency) currency,
SUM(usage.amount) usage,
STRING_AGG(DISTINCT usage.unit) usage_unit,
FROM `<table_name_created_by_billing_export>`
GROUP BY 1, 2, 3
ORDER BY 1, 2, 3