# Syncing Data to GCP Storage

**URL:** <https://discuss.dvc.org/t/syncing-data-to-gcp-storage/1237>\
**Category:** Blog Comments\
**Created:** [July 6, 2022, 2:29pm UTC](https://discuss.dvc.org/t/syncing-data-to-gcp-storage/1237 "2022-07-06T14:29:04Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![milecia](https://avatars.discourse-cdn.com/v4/letter/m/dec6dc/32.png) [@milecia](https://discuss.dvc.org/u/milecia)\
**Post date:** [July 6, 2022, 2:29pm UTC](https://discuss.dvc.org/t/syncing-data-to-gcp-storage/1237/1 "2022-07-06T14:29:04Z")

</div>

Feel free to leave comments and ask questions about @milecia’s post on syncing data to GCP Storage with DVC!

[https://dvc.org/blog/using-gcp-remotes-in-dvc](https://dvc.org/blog/using-gcp-remotes-in-dvc)

---

<div class="post-metadata">

**Author:** ![TJC](https://avatars.discourse-cdn.com/v4/letter/t/54ee81/32.png) [@TJC](https://discuss.dvc.org/u/TJC)\
**Post date:** [October 22, 2024, 3:58pm UTC](https://discuss.dvc.org/t/syncing-data-to-gcp-storage/1237/2 "2024-10-22T15:58:04Z")

</div>

What do you think about defining a retention period for the GCS bucket? This way, no one can accidentally delete files in the remote storage. Would DVC still work then? After all, files in the bucket can no longer be modified either, right?

---

<div class="post-metadata">

**Author:** ![shcheklein](https://yyz1.discourse-cdn.com/flex035/user_avatar/discuss.dvc.org/shcheklein/32/173_2.png) [@shcheklein](https://discuss.dvc.org/u/shcheklein)\
**Post date:** [October 22, 2024, 4:28pm UTC](https://discuss.dvc.org/t/syncing-data-to-gcp-storage/1237/3 "2024-10-22T16:28:15Z")

</div>

Yes, and it’s a good practice to my mind - making DVC storage essentially immutable, append only. Yes, DVC will be working in this configuration.
