volume-backup - GitLite

KO | EN

gitlite — search

#javascript #hacktoberfest #ai #llm #deep-learning #linux #docker #macos #cli #vue #awesome-list #pytorch #security #ios

volume-backup

(★ 913)

docker volume backup & restore utility

파일 탐색기

최종 버전 다운로드 (.zip)

- - publish-image.yml
- FUNDING.yml
Dockerfile
LICENSE
README.md
volume-backup.sh

# 설치 가이드

1. 코드 내려받기

git clone https://github.com/loomchild/volume-backup

깃허브에서 프로젝트 코드 전체를 내 컴퓨터로 내려받습니다.

cd volume-backup

방금 내려받은 프로젝트 폴더 안으로 이동합니다.

2. Docker

쉬움 추천

사전 준비물

Git GitHub에서 프로젝트 코드를 내려받으려면 필요합니다.
Docker Desktop 컨테이너를 빌드하고 실행하려면 필요합니다. 설치 후 실행해서 백그라운드에 켜두세요.

docker pull loomchild/volume-backup

이 명령어를 터미널에 그대로 입력해 실행하세요.

docker pull ghcr.io/loomchild/volume-backup

이 명령어를 터미널에 그대로 입력해 실행하세요.

docker ps -a --filter volume=[volume-name]

이 명령어를 터미널에 그대로 입력해 실행하세요.

docker run -v [volume-name]:/volume --rm --log-driver none loomchild/volume-backup backup -e [excluded-glob] > [archive-path]

빌드된 이미지를 실제 컨테이너로 실행합니다.

docker run -v [volume-name]:/volume --rm --log-driver none loomchild/volume-backup backup -c pigz > [archive-path]

빌드된 이미지를 실제 컨테이너로 실행합니다.

✅ 터미널에 docker compose ps 를 입력해 컨테이너들이 Up 상태인지 확인하세요. README에 포트 번호가 적혀있다면 브라우저에서 http://localhost:포트번호 로 접속해보세요.

이 레포의 README에 적힌 실제 명령어를 그대로 가져왔습니다.

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

# volume-backup

An utility to backup and restore [Docker volumes](https://docs.docker.com/storage/volumes/). For more info, read my article on [Medium](https://medium.com/@jareklipski/backup-restore-docker-named-volumes-350397b8e362).

It works just as well with [Podman](https://podman.io/) volumes, just prefix each command with `podman` instead of `docker`.

> [!WARNING]
> Make sure no container is using the volume before backup or restore, otherwise your data might be damaged. See [Miscellaneous](#miscellaneous) for instructions.

> [!TIP]
> When using docker-compose, make sure to backup and restore volume labels. See [Miscellaneous](#miscellaneous) for more information.

> [!TIP]
> I am doing my best to keep this utility backwards-compatible. However, if you are using it in production environment and you want to be sure that it doesn't break with the future updates, request a specific image digest, e.g.: `docker run -v [volume-name]:/volume --rm --log-driver none loomchild/volume-backup@sha256:d598345843d8eb20e4b0da331d538eb9158b70bcaff56f7ba09f5ce1b6498019 backup > [archive-path]`. You can find the last digest on Docker Hub or GHCR. Note that old unused images might get deleted.

## Backup

Syntax:

docker run -v [volume-name]:/volume --rm --log-driver none loomchild/volume-backup backup > [archive-path]

For example:

docker run -v some_volume:/volume --rm --log-driver none loomchild/volume-backup backup > some_archive.tar.bz2

will archive volume named `some_volume` to `some_archive.tar.bz2` archive file.

> [!NOTE]
> The `--log-driver none` option is necessary to avoid storing an entire backup in a temporary stdout JSON file. More info in [Docker logging documentation](https://docs.docker.com/config/containers/logging/configure/) and in [this issue](https://github.com/loomchild/volume-backup/issues/39).

> [!NOTE]
> This method should not be used under PowerShell on Windows as no usable backup will be generated.

### Backup to a file (deprecated)

Syntax:

docker run -v [volume-name]:/volume -v [output-dir]:/backup --rm loomchild/volume-backup backup [archive-name]

For example:

docker run -v some_volume:/volume -v /tmp:/backup --rm loomchild/volume-backup backup some_archive

will archive volume named `some_volume` to `/tmp/some_archive.tar.bz2` archive file.

## Restore

Syntax:

docker run -i -v [volume-name]:/volume --rm loomchild/volume-backup restore < [archive-path]

For example:

docker run -i -v some_volume:/volume --rm loomchild/volume-backup restore < some_archive.tar.bz2

will clean and restore volume named `some_volume` from `some_archive.tar.bz2` archive file.

> [!NOTE]
> Don't forget the `-i` switch for interactive operation.

> [!NOTE]
> Backup will fail if the source volume is empty. Restore will fail if the target volume is not empty. You can use the `-f` flag to override this.

### Restore from a file (deprecated)

Syntax:

docker run -v [volume-name]:/volume -v [output-dir]:/backup --rm loomchild/volume-backup restore [archive-name]

For example:

docker run -v some_volume:/volume -v /tmp:/backup --rm loomchild/volume-backup restore some_archive

will clean and restore volume named `some_volume` from `/tmp/some_archive.tar.bz2` archive file.

## Miscellaneous

1. Upgrade / update volume-backup
    ```
    docker pull loomchild/volume-backup
    ```

1. volume-backup is also available from GitHub Container Registry (ghcr.io), to avoid DockerHub usage limits:
    ```
    docker pull ghcr.io/loomchild/volume-backup
    ```
    Then write `ghcr.io/loomchild/volume-backup` instead of just `loomchild/volume-backup` when running the utility.

1. Find all containers using a volume (to stop them before backing-up)
    ```
    docker ps -a --filter volume=[volume-name]
    ```

1. Exclude some files from the backup and send the archive to stdout
    ```
    docker run -v [volume-name]:/volume --rm --log-driver none loomchild/volume-backup backup -e [excluded-glob] > [archive-path]
    ```

1. Use different compression algorithm for better performance
    ```
    docker run -v [volume-name]:/volume --rm --log-driver none loomchild/volume-backup backup -c pigz > [archive-path]
    ```

1. Show simple progress indicator using verbose `-v` flag (works both for backup and restore)
    ```
    docker run -v [volume-name]:/volume --rm --log-driver none loomchild/volume-backup backup -v > [archive-path]
    ```

1. Pass additional arguments to the Tar utility using `-x` option
    ```
    docker run -v [volume-name]:/volume --rm --log-driver none loomchild/volume-backup backup -x --verbose > [archive-path]
    ```

1. Directly migrate the volume to a new host
    ```
    docker run -v [volume-name]:/volume --rm --log-driver none loomchild/volume-backup backup | ssh [receiver] docker run -i -v [volume-name]:/volume --rm loomchild/volume-backup restore
    ```
    In case there are no traffic limitations between the hosts you can trade CPU time for bandwidth by turning off compression via `-c none` option.

1. Volume labels are not backed-up or restored automatically, but they might be required for your application to work (e.g. when using `docker-compose`). If you need to preserve them, create a label backup file as follows: `docker inspect [volume-name] -f "{{json .Labels}}" > labels.json`. When restoring your data, target volume needs to be created manually with labels before launching the restore script: `docker volume create --label "label1" --label "label2" [volume-name]`.