1/13/2024 0 Comments S3 data backupS3 target with the format s3://bucketname/path. Otherwise only basic messages are printed. BACKUP_DEBUG: If set to true, print copious shell script messages to the container log. If you use this option, all other scheduling options, like BACKUP_FREQ and BACKUP_BEGIN and BACKUP_CRON, become obsolete. as part of an orchestration solution like Cattle or Docker Swarm or kubernetes cron jobs) and don't want the container to do the scheduling internally. Useful if you use an external scheduler (e.g. RUN_ONCE: Run the backup once and exit if RUN_ONCE is set.BACKUP_CRON: Set the BACKUP schedule using standard crontab syntax, a single line.+0 (immediate), +10 (in 10 minutes), or +90 in an hour and a half how many minutes after starting the container, e.g. BACKUP_BEGIN: What time to do the first BACKUP.Defaults to 1440 minutes, or once per day. BACKUP_FREQ: How often to do a BACKUP, in minutes. The above will run a backup every 60 minutes, beginning at the next 2330 local time. v /local/file/path:/home/backupuser/data ultrasites/data-backup-s3 Everything is controlled by environment variables passed to the container.ĭocker run -d -restart=always -e BACKUP_FREQ=60 -e BACKUP_BEGIN=2330 -e S3_TARGET=s3://. To run a backup, launch data-backup-s3 image as a container with the correct parameters.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |