Best practice for storing data locally and offsite.

Currently my data is backed up on the server which the Minecraft server is running off, however I would like to be able to store data both locally and then off site. What would be the best practice for doing this?

As it stands I think there may be two options, but I would welcome your input on deciding which is the preferred on or whether or not they are both the same.

1. Running two versions of the `docker-mc-backup` container. Both with restic but with one on a remote container, this does give the option of customizing the backup time. I may only back up remotely every 2 hours but keep a local backup every fifteen minutes. Then I can set the remote repository in my `docker-compose.yml`
2. Writing my own script to back up the restic repo to the cloud.

I am leaning towards option one but can you see any issue with running two versions of the container. If they both tried to backup at the same time could that lead to some weird behavior? I suppose I could customise them with initial delay, having the local start up three minutes after the server starts and the second starting up after seven with then irregular intervals?

Could the project implement some kind of lock file? Or since that it only has the files mounted as read only it might be okay. My only worry would be sending the `rcon` command twice.

Start with the docker-compose.yml setup and the two proposed docker-mc-backup container configurations. Investigate whether concurrent backups and duplicate rcon commands are safe, and whether a lock file is needed. Done means documenting the preferred local/offsite backup approach or defining an agreed implementation for coordination.

Written by the indexing model from the issue text.