热门搜索:
weseek/mongodb-awesome-backup
自动构建
weseek
Backup scripts of MongoDB Databases to Amazon S3
下载次数: 0状态：自动构建维护者：weseek仓库类型：镜像最近更新：5 天前
!https://github.com/weseek/mongodb-awesome-backup/workflows/Test/badge.svg
What is mongodb-awesome-backup?
mongodb-awesome-backup is the collection of scripts which backup MongoDB databases to Amazon S3 or Google Cloud Storage. You can set a custom S3 endpoint to use S3 based services like DigitalOcean Spaces instead of Amazon S3.
Requirements
- Amazon IAM Access Key ID/Secret Access Key
- which must have the access lights of the target Amazon S3 bucket.
OR
- Google Cloud Interoperable storage access keys (see [***]
- GCP_SERVICE_ACCOUNT_KEY_JSON_PATH and GCP_PROJECT_ID are only required if using service account authentication.
- GCP_ACCESS_KEY_ID, GCP_SECRET_ACCESS_KEY, and GCP_PROJECT_ID are only required if using HMAC authentication.
- When using oauth authentication, a docker mount
-v ~:/maband is the can be added to save auth0 credentials to your home directory after mongodb-awesome-backup is run. On subsequent runs, the same~/.botofile will be used for authentication. - The name 'mab' was chosen as the Docker container mount point simply because it's an acronym for "
mongodb-awesome-backup"). The /mab mount point maps to the home directory of whatever user is used to run mongodb-awesome-backup, and is where the .boto file will be saved.
Usage
Note that either AWS_ or GCP_ vars are required not both.
bashdocker run --rm \ -e AWS_ACCESS_KEY_ID=<Your IAM Access Key ID> \ -e AWS_SECRET_ACCESS_KEY=<Your IAM Secret Access Key> \ [ -e GCP_SERVICE_ACCOUNT_KEY_JSON_PATH=<JSON file path to your GCP Service Account Key> \ ] [ -e GCP_ACCESS_KEY_ID=<Your GCP Access Key> \ ] [ -e GCP_SECRET_ACCESS_KEY=<Your GCP Secret> \ ] [ -e GCP_PROJECT_ID=<Your GCP Project ID> \ ] -e TARGET_BUCKET_URL=<Target Bucket URL ([s3://...|gs://...])> \ [ -e BACKUPFILE_PREFIX=<Prefix of Backup Filename (default: "backup") \ ] [ -e MONGODB_URI=<Target MongoDB URI> \ ] [ -e MONGODB_HOST=<Target MongoDB Host (default: "mongo")> \ ] [ -e MONGODB_DBNAME=<Target DB name> \ ] [ -e MONGODB_USERNAME=<DB login username> \ ] [ -e MONGODB_PASSWORD=<DB login password> \ ] [ -e MONGODB_AUTHDB=<Authentication DB name> \ ] [ -e AWSCLI_ENDPOINT_OPT=<S3 endpoint URL (ex. https://fra1.digitaloceanspaces.com)> \ ] [ -v ~:/mab \ ] weseek/mongodb-awesome-backup
and after running this, backup-YYYYMMdd.tar.bz2 will be placed on Target S3 Bucket.
How to backup in cron mode
Execute a docker container with CRONMODE=true.
bashdocker run --rm \ -e AWS_ACCESS_KEY_ID=<Your IAM Access Key ID> \ -e AWS_SECRET_ACCESS_KEY=<Your IAM Secret Access Key> \ [ -e GCP_SERVICE_ACCOUNT_KEY_JSON_PATH=<JSON file path to your GCP Service Account Key> \ ] [ -e GCP_ACCESS_KEY_ID=<Your GCP Access Key> \ ] [ -e GCP_SECRET_ACCESS_KEY=<Your GCP Secret> \ ] [ -e GCP_PROJECT_ID=<Your GCP Project ID> \ ] -e TARGET_BUCKET_URL=<Target Bucket URL ([s3://...|gs://...])> \ -e CRONMODE=true \ -e CRON_EXPRESSION=<Cron expression (ex. "CRON_EXPRESSION='0 4 * * *'" if you want to run at 4:00 every day)> \ [ -e BACKUPFILE_PREFIX=<Prefix of Backup Filename (default: "backup") \ ] [ -e MONGODB_URI=<Target MongoDB URI> \ ] [ -e MONGODB_HOST=<Target MongoDB Host (default: "mongo")> \ ] [ -e MONGODB_DBNAME=<Target DB name> \ ] [ -e MONGODB_USERNAME=<DB login username> \ ] [ -e MONGODB_PASSWORD=<DB login password> \ ] [ -e MONGODB_AUTHDB=<Authentication DB name> \ ] [ -e AWSCLI_ENDPOINT_OPT=<S3 endpoint URL (ex. https://fra1.digitaloceanspaces.com)> \ ] [ -v ~:/mab \ ] weseek/mongodb-awesome-backup
How to restore
You can use "restore" command to restore database from backup file.
bashdocker run --rm \ -e AWS_ACCESS_KEY_ID=<Your IAM Access Key ID> \ -e AWS_SECRET_ACCESS_KEY=<Your IAM Secret Access Key> \ [ -e GCP_SERVICE_ACCOUNT_KEY_JSON_PATH=<JSON file path to your GCP Service Account Key> \ ] [ -e GCP_ACCESS_KEY_ID=<Your GCP Access Key> \ ] [ -e GCP_SECRET_ACCESS_KEY=<Your GCP Secret> \ ] [ -e GCP_PROJECT_ID=<Your GCP Project ID> \ ] -e TARGET_BUCKET_URL=<Target Bucket URL ([s3://...|gs://...])> \ -e TARGET_FILE=<Target S3 or GS file name to restore> \ [ -e MONGODB_URI=<Target MongoDB URI> \ ] [ -e MONGODB_HOST=<Target MongoDB Host (default: "mongo")> \ ] [ -e MONGODB_DBNAME=<Target DB name> \ ] [ -e MONGODB_USERNAME=<DB login username> \ ] [ -e MONGODB_PASSWORD=<DB login password> \ ] [ -e MONGODB_AUTHDB=<Authentication DB name> \ ] [ -e MONGORESTORE_OPTS=<Options list of mongorestore> \ ] [ -e AWSCLI_ENDPOINT_OPT=<S3 endpoint URL (ex. https://fra1.digitaloceanspaces.com)> \ ] [ -v ~:/mab \ ] weseek/mongodb-awesome-backup restore
Environment variables
For backup, prune, list
Required
| Variable | Description | Default |
|---|---|---|
| AWS_ACCESS_KEY_ID | Your IAM Access Key ID | - |
| AWS_SECRET_ACCESS_KEY | Your IAM Secret Access Key | - |
| TARGET_BUCKET_URL | Target Bucket URL ([s3://...|gs://...]). URL is needed to be end with '/' | - |
Optional
| Variable | Description | Default |
|---|---|---|
| GCP_SERVICE_ACCOUNT_KEY_JSON_PATH | JSON file path to your GCP Service Account Key | - |
| GCP_ACCESS_KEY_ID | Your GCP Access Key | - |
| GCP_SECRET_ACCESS_KEY | Your GCP Secret | - |
| GCP_PROJECT_ID | Your GCP Project ID | - |
| BACKUPFILE_PREFIX | Prefix of Backup Filename | "backup" |
| MONGODB_URI | Target MongoDB URI (ex. mongodb://mongodb?replicaSet=rs0). If set, the other MONGODB_* variables will be ignored. | - |
| MONGODB_HOST | Target MongoDB Host | "mongo" |
| MONGODB_DBNAME | Target DB name | - |
| MONGODB_USERNAME | DB login username | - |
| MONGODB_PASSWORD | DB login password | - |
| MONGODB_AUTHDB | Authentication DB name | - |
| CRONMODE | If set "true", this container is executed in cron mode. In cron mode, the script will be executed with the specified arguments and at the time specified by CRON_EXPRESSION. | "false" |
| CRON_EXPRESSION | Cron expression (ex. "CRON_EXPRESSION=0 4 * * *" if you want to run at 4:00 every day) | - |
| AWSCLI_ENDPOINT_OPT | Set a custom S3 endpoint if you use a S3 based service like DigitalOcean Spaces. (ex. AWSCLI_ENDPOINT_OPT="[***]") If not set the Amazon S3 standard endpoint will be used. | - |
| AWSCLIOPT | Other options you want to pass to aws command | - |
| GCSCLIOPT | Other options you want to pass to gsutil command | - |
| HEALTHCHECKS_URL | URL that gets called after a successful backup (eg. [***] | - |
For restore
Required
| Variable | Description | Default |
|---|---|---|
| AWS_ACCESS_KEY_ID | Your IAM Access Key ID | - |
| AWS_SECRET_ACCESS_KEY | Your IAM Secret Access Key | - |
| TARGET_BUCKET_URL | Target Bucket URL ([s3://...|gs://...]). URL is needed to be end with '/' | - |
| TARGET_FILE | Target S3 or GS file name to restore | - |
Optional
| Variable | Description | Default |
|---|---|---|
| GCP_SERVICE_ACCOUNT_KEY_JSON_PATH | JSON file path to your GCP Service Account Key | - |
| GCP_ACCESS_KEY_ID | Your GCP Access Key | - |
| GCP_SECRET_ACCESS_KEY | Your GCP Secret | - |
| GCP_PROJECT_ID | Your GCP Project ID | - |
| MONGODB_URI | Target MongoDB URI (ex. mongodb://mongodb?replicaSet=rs0). If set, the other MONGODB_* variables will be ignored. | - |
| MONGODB_HOST | Target MongoDB Host | "mongo" |
| MONGODB_DBNAME | DB name to be restored from backup | - |
| MONGODB_USERNAME | DB login username | - |
| MONGODB_PASSWORD | DB login password | - |
| MONGODB_AUTHDB | Authentication DB name | - |
| MONGORESTORE_OPTS | Options list of mongorestore. (ex --drop) | - |
| AWSCLI_ENDPOINT_OPT | Set a custom S3 endpoint if you use a S3 based service like DigitalOcean Spaces. (ex. AWSCLI_ENDPOINT_OPT="[***]") If not set the Amazon S3 standard endpoint will be used. | - |
| AWSCLIOPT | Other options you want to pass to aws command | - |
| GCSCLIOPT | Other options you want to pass to gsutil command | - |
镜像拉取方式
您可以使用以下命令拉取该镜像。请将 <标签> 替换为具体的标签版本。如需查看所有可用标签版本，请访问 标签列表页面。
轩辕镜像加速拉取命令点我查看更多 mongodb-awesome-backup 镜像标签
docker pull docker.xuanyuan.run/weseek/mongodb-awesome-backup:<标签>
DockerHub 原生拉取命令
docker pull weseek/mongodb-awesome-backup:<标签>
更多 mongodb-awesome-backup 镜像推荐
mongodb/mongodb-atlas-local
mongodb
通过Docker创建、管理和自动化MongoDB Atlas Local资源
12 次收藏500万+ 次下载
11 天前更新
mongodb/mongodb-community-server
mongodb
官方MongoDB社区服务器是由MongoDB公司推出的免费开源文档数据库服务，专为开发者与技术社区打造，支持以JSON格式存储灵活的非结构化及半结构化数据，具备高可扩展性、易部署性和丰富的查询功能，广泛应用于Web开发、大数据分析、移动应用后端等场景，为用户提供高效的数据管理解决方案并促进社区协作与技术交流。
186 次收藏1000万+ 次下载
18 小时前更新
mongodb/mongodb-atlas-search
mongodb
Atlas Search提供无缝、可扩展的体验，用于构建基于相关性的应用功能。
4 次收藏100万+ 次下载
1 个月前更新
mongodb/mongodb-enterprise-server
mongodb
MongoDB官方企业高级服务器是面向企业级应用的高性能、可扩展文档数据库服务器，支持复杂查询、分布式部署与实时数据分析，提供企业级安全特性（如身份验证、数据加密）、完善的数据备份与恢复机制及专业监控工具，助力企业构建稳定高效的现代应用架构，满足大规模数据存储、处理与业务创新需求。
15 次收藏500万+ 次下载
18 小时前更新
mongodb/mongodb-mcp-server
mongodb
官方MongoDB MCP服务器镜像，用于部署和运行MongoDB MCP服务，提供官方支持的可靠运行环境。
3 次收藏10万+ 次下载
23 小时前更新
mongodb/mongodb-atlas-kubernetes-operator
mongodb
MongoDB Atlas Kubernetes Operator - 基于Kubernetes原生管理MongoDB Atlas基础设施
5 次收藏100万+ 次下载
1 天前更新
轩辕镜像配置手册
探索更多轩辕镜像的使用方法，找到最适合您系统的配置方式
Docker 配置
登录仓库拉取
通过 Docker 登录认证访问私有仓库
专属域名拉取
无需登录使用专属域名
K8s Containerd
Kubernetes 集群配置 Containerd
K3s
K3s 轻量级 Kubernetes 镜像加速
Dev Containers
VS Code Dev Containers 配置
Podman
Podman 容器引擎配置
Singularity/Apptainer
HPC 科学计算容器配置
其他仓库配置
ghcr、Quay、nvcr 等镜像仓库
Harbor 镜像源配置
Harbor Proxy Repository 对接专属域名
Portainer 镜像源配置
Portainer Registries 加速拉取
Nexus 镜像源配置
Nexus3 Docker Proxy 内网缓存
系统配置
需要其他帮助？请查看我们的 常见问题Docker 镜像访问常见问题解答 或 提交工单
镜像拉取常见问题
使用与功能问题
配置了专属域名后，docker search 为什么会报错？
docker search 限制
Docker Hub 上有的镜像，为什么在轩辕镜像网站搜不到？
站内搜不到镜像
机器不能直连外网时，怎么用 docker save / load 迁镜像？
离线 save/load
docker pull 拉插件报错（plugin v1+json）怎么办？
插件要用 plugin install
WSL 里 Docker 拉镜像特别慢，怎么排查和优化？
WSL 拉取慢
轩辕镜像安全吗？如何用 digest 校验镜像没被篡改？
安全与 digest
第一次用轩辕镜像拉 Docker 镜像，要怎么登录和配置？
新手拉取配置
轩辕镜像合规吗？轩辕镜像的合规是怎么做的？
镜像合规机制
错误码与失败问题
docker pull 提示 manifest unknown 怎么办？
manifest unknown
docker pull 提示 no matching manifest 怎么办？
no matching manifest（架构）
镜像已拉取完成，却提示 invalid tar header 或 failed to register layer 怎么办？
invalid tar header（解压）
Docker pull 时 HTTPS / TLS 证书验证失败怎么办？
TLS 证书失败
Docker pull 时 DNS 解析超时或连不上仓库怎么办？
DNS 超时
docker 无法连接轩辕镜像域名怎么办？
域名连通性排查
Docker 拉取出现 410 Gone 怎么办？
410 Gone 排查
出现 402 或「流量用尽」提示怎么办？
402 与流量用尽
Docker 拉取提示 UNAUTHORIZED（401）怎么办？
401 认证失败
遇到 429 Too Many Requests（请求太频繁）怎么办？
429 限流
docker login 提示 Cannot autolaunch D-Bus，还算登录成功吗？
D-Bus 凭证提示
为什么会出现「单层超过 20GB」或 413，无法加速拉取？
413 与超大单层
账号 / 计费 / 权限
用户好评
来自真实用户的反馈，见证轩辕镜像的优质服务
oldzhang
运维工程师
Linux服务器
5
"Docker访问体验非常流畅，大镜像也能快速完成下载。"