If a user has already uploaded files to a single S3 region in Ente Photos (self-hosted), and later adds additional S3 regions in museum.yaml (for example one in Asia and one in Europe) with replications: true, will Museum automatically replicate all the previously uploaded files to these new regions?
Or does the user need to manually sync/replicate the existing data that was uploaded before the new regions were added?
#Will Museum auto-replicate previously uploaded files after adding new S3 regions?
1 messages · Page 1 of 1 (latest)
Ente's replication feature is disabled by default in self-hosted instances, with only the first bucket (b2-eu-cen) being used. Replication requires all 3 storage buckets to be configured.
To enable replication, set replication.enabled to true in the museum.yaml file after configuring all 3 storage buckets. See the example museum.yaml file at https://github.com/ente-io/ente/blob/main/server/configurations/local.yaml.
For more information, you can refer to the discussion on reliability at https://github.com/ente-io/ente/discussions/3167#discussioncomment-10585970 and the article on ensuring reliability at https://ente.io/reliability/.
-# If your issue is resolved, feel free to use the </solved:1410327008973557843> command to close this thread. If you'd like to ask me another question use </docsearch:1378409618417647708>
ente
Ente keeps 3 encrypted copies of your data across EU data centers—including an underground facility—to ensure durability and protect against data loss.
Could a human answer this?
Same question! Seems Self Hosting Ente in no way friendly....
Please keep in mind that support for Ente in general goes first. This channel is community run. And that the AI is based on the docs
Ohh thanks for tha information!
Unless you have multiple users with uploaded photos, why not start over and set everything up the way you would like and test its functionality before re- backing up all of your photos.
One thing that has worked well for me is to set up a secondary test instance of Ente on a non production test environment and experiment with changes to the setup until I reach my desired result. Then roll those changes out to my production server.
But did you set ENVIRONMENT=production in your production server?