[Help]: Backup volumes before upgrade? (and upgrade procedure in general)

[jhgarrison]

Controller Version

v5.13

Describe Your Issue or Question

When planning an upgrade from v5.13 to v5.15.8.2, I've taken a backup of the controller configuration and data. IIRC, an upgrade could update the database schema, making it impossible to revert to the current version in case of problems.

Should I also make a backup copy of the omada-data and omada-logs volumes, after stopping the container?

More generally, should the steps to perform an upgrade be:

1. Take a backup in the controller and save outside the container
2. Stop the container
3. Backup the volumes
4. docker run the new image
5. Test, make sure everything's working
6. Remove the old container

And the procedure for reverting in case of problems:

1. Stop and remove the "new" container
2. Restore the volume files
3. Start the "old" container

And of course, in case of total disaster:

1. Stop the running container (if there is one)
2. Remove the volumes
3. Start a new container with the desired image
4. Restore the saved configuration.

Sorry if this is a very basic question, I'm still quite new with Docker and don't use it except for this image.

Expected Behavior

n/a

Steps to Reproduce

n/a

How You're Launching the Container

As shown in the readme.md

Container Logs

n/a

MongoDB Logs

No response

Additional Context

No response

[mbentley]

You've got the process down quite well. I don't have any significant changes to what you said, just some reminders, really:

For stopping the container, just make sure you've either specified a stop timeout when starting the container or manually specify one at stop time to allow enough time to gracefully shut down the app and MongoDB. See this section of the readme for more info on that.

For your steps, you don't really need to keep the previous container around; you can remove the old container before starting the new one as there is nothing unique stored inside the previous container. As long as you have the image from the previous version, you can roll back quickly. Plus if you're like me, I like the name of the container to remain the same and you'd have to rename the container but that's all just an unnecessary step, in my opinion.

[jhgarrison]

Thanks, I'm finally getting comfortable with Docker :-)

I can report a successful upgrade from 5.13 to 5.15.8.2, without encountering any issues. Specifically I did not see the problem described in KNOWN_ISSUES.md for the 5.15 upgrade.

Startup took about 4 minutes (Intel Celeron N5095 @ 2.00GHz w/8GB RAM) which I assume was the database upgrade.

No errors were logged in server.log.

Thanks again for the help, and a big THANK YOU for creating and maintaining this image!