What exactly happen when BACKUP_FROM_SNAPSHOT=true? about docker-volume-backup HOT 6 CLOSED

BACKUP_FROM_SNAPSHOT is supposed to be used in the following situation:

1. you cannot stop your containers while taking the backup (this should always be the preferred option)
2. you are backing up a highly volatile file system that will change while writing the tar archive, see #32

In your particular case it looks as if a file in the backup target gets deleted while / right before you are trying to copy it. This is probably an upstream issue in package copy (https://github.com/otiai10/copy), maybe we should open an issue there or see if it has been reported before.

In the meantime, is stopping the containers during backup a workable option for you? You could also try running the backup without stopping containers and without using the snapshot option, but I would assume this fails as well, exposing the behavior described in #32

from docker-volume-backup.

Thank you for your answer.

I create backup of prometheus container. Backup time - 40 minutes. If i stop prometheus for this time it will be not good.
From other side i can send to prometheus container some command like that
curl -XPOST -u $prom_user:$prom_pass http://prometheus/api/v1/admin/tsdb/snapshot
to create snapshot

But how can i send this curl request from your docker_backup solution before start backuping?

Also i have many containers such as svn, postgres in which always write any dynamical data and this container can't stop on during backup process and i can't use BACKUP_FROM_SNAPSHOT because is just not working as need :(

from docker-volume-backup.

But how can i send this curl request from your docker_backup solution before start backuping?

Right now you can't, see #45

Also i have many containers such as svn, postgres in which always write any dynamical data and this container can't stop on during backup process and i can't use BACKUP_FROM_SNAPSHOT because is just not working as need :(

I'm not sure what is happening exactly, but maybe a good start would be creating an issue in the upstream repository about this https://github.com/otiai10/copy

from docker-volume-backup.

I created an upstream issue here otiai10/copy#72

from docker-volume-backup.

Not fixing the underlying issue, but running pre/post commands for preparing backups is now supported as of v2.13.0

from docker-volume-backup.

An upstream fix is now included in v2.26.1

from docker-volume-backup.