I need to update my NetBox, and not sure which route to take.

I use NetBox to manage all my infrastructure data. It’s primarily an IPAM for me, but I also track racks and ports and some wiring. I store serial numbers and console urls and whatnot there too. It’s an important (to me) tool that runs on a docker host with daily backups.

I need to upgrade. I have seen shots of the new version, and boy does it look cool. Talked with another lemming about it yesterday and decided to figure out my pathway.

The choice.
Do I in-place upgrade (their way), or do I deploy a new one and migrate the data to it?

The challenge.
See … this is embarrassing. I’m a professional virtualization guy, that’s how I pay my bills. But I’m barely proficient with docker. So yes, I run NetBox on a docker system that I configured from scratch, but I lack real confidence in what I’m doing in that environment.

NetBox-docker Upgrade
https://github.com/netbox-community/netbox-docker/wiki/Updating

I am afraid that if I follow the directions for an in-place upgrade, I’m risking my data. Docker is just not my thing, and I feel I might screw it up.

NetBox Migrate Data
https://github.com/netbox-community/netbox/discussions/14104

But lift-and-shift some data to a new (upgraded) system?
I do that sort of thing quite a bit. I’m pretty darn comfortable with deploying migrated data to a pre-prod, testing it, and then cutting over.
That sounds like a normal day at work.

Just to note … NetBox is capable of much more than I use it for. Its designed to expose and update its data via API for other apps to use and modify. I only access it via the GUI to track my infra. I say this bit just because that simplifies questions about the upgrade, in that there are no external links to consider. It’s a stand-alone system, talks to nothing else.

So … yet another long-ass post about my lab.
I’d welcome any input, however tangentially related. Thanks!

  • punkibas@lemmy.zipEnglish
    2·
    2 months ago

    If you have backups there’s really no wrong way of doing it. I guess it could be a perfect time to test one of those backups by restoring it somewhere else and doing the upgrade.

    Docker is not that hard, and this is a great opportunity to learn the couple of things you’ll constantly use when deploying or updating netbox or any app later on.

    I have netbox deployed too, I’ll do the upgrade on my system to see how it goes. If you have any specific questions just ask and I’ll try to help you as best I can.

    You can start by going to the netbox directory, doing a docker compose down and copying that whole directory somewhere else. Then, wherever you copy that you can always just cd into it and restore netbox with a docker compose up -d

    • dbtngOPEnglish
      2·
      2 months ago

      Hey thanks.
      Ok, that’s one vote for an in-place upgrade, along with explicit directions on how to clone and test.
      Um … well done!

      I was poking about my NetBox to find version info, and it sent me to this page for upgrade info.
      https://netboxlabs.com/docs/netbox/installation/upgrading/

      It’s got a complete matrix. I’ve got an 4.14, so I’m not making a full version jump.
      They say the lift-and-shift upgrade is for full version jumps.

      So, you’re right. I should just figure out docker and utilize it effectively. I’ll read through this page.

      • punkibas@lemmy.zipEnglish
        2·
        2 months ago

        Those instructions are for the non docker release, how are you doing your backups? If you’re sure you have everything properly backed up and it’s not a full version jump you’ll only have to cd into the netbox directory and execute this:

        Docker compose pull && docker compose up -d
        • dbtngOPEnglish
          2·
          2 months ago

          Got it. Yes, I have much to read in general, and in particular I should pay attention to the first link I posted from the NetBox-docker github.

          My backups are of the docker host, which is a Linux Mint virtual machine on Proxmox. I believe I do have file-level restore options, but I wanted a restore I’d probly just stand up a copy of the host, grab what i need, and nuke the copy.

          I’m the weekend guy, this is mid-work-week for me right now. And I’ve got CCNA studying I should be after. I’ll probably pickup my NetBox docker-style clone/upgrade/test early next week.

          Thanks again, friend. That was all really solid and direct feedback. Quite helpful.