You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I do not understand your question. What is a 'multivol_snapshot'? What does it mean 'to face a multishot_snapshot'?
Why do you rename the volumes, because you run them on the same machine? If you run them on the same machine, why do you rename the volumes but point them to the same folder?
It means that when I download a duplicity-full.20220706T0000Z.vol1.difftar I have 2 folders:
multivol_snapshot
snapshot
Files in snapshot can be red in my Macos finder but not thoses on multivol_snapshot.
What I have now understand is that I should not try to restore files manually by downloading archive. I should only use volumerize command to do so.
Yes I run the containers in the same machine. I guess I should not point them to the same folder. But I've understood that source is a temp folder. So this is not a big deal is it?
Hi,
I'm facing a problem to understand
multivol_snapshot
of dupliciy.Trying to restore manually a db from tar.gz files, I cannot untar them because they are on multivol_snapshot.
I have 2 docker-compose using volumerize: one for preprod (rc) and one for production:
First, my volumes were named the same but since I've read that they must not be shared, I've changed the one for preprod to
volumerizerccache
But now on the preprod, when I run
docker exec RcBackup backup
I'm also facing a multivol_snapshot.I cannot understand why.
Any help? 🙏 🙏
Thank you!
The text was updated successfully, but these errors were encountered: