2024-01-28, 08:40 PM
(This post was last modified: 2024-01-28, 08:43 PM by Host-in-the-Shell. Edited 2 times in total.)
Well, my experience is not with Ubuntu, but with Debian instead, so make of that what you will. I've been running a WordPress site (That I've now converted to ClassicPress) since around September 2010. In all that time I only reinstalled once, mainly because I was changing the server hardware from an old 32bit laptop to a newer 64bit laptop, and I didn't understand the process of converting my installation into another architecture, although I'm sure that was also possible if I had taken the time to figure it out, but I was fairly new and inexperienced with hosting at the time. That was around 2012, so since then I've upgraded between versions without much issue until this very day.
My advice: before you do anything to your system, you should backup everything that you can't afford to lose. And by the way, having a backup solution should not be something that you do only before a potentially breaking change, but a regular countermeasure that you deploy on any machine(s) which contain critical data; get on it yesterday if you haven't. Now, I won't lecture you about what backup software to use and how, but I will recommend that for extra important data you consider a 3-2-1 backup rule if losing any of it is devastating for your particular use case.
Whatever backup solution you employ, I would also highly recommend frequently making and storing restorable full disk images of the disk where you installed your OS. For that I use clonezilla, although this approach leads to service interruptions; however, for personal, self-hosted affairs, some downtime for general cleanup and maintenance should be acceptable. The main advantage of this approach is that it serves as the big eraser of mistakes that backups can be, while also allowing you to transfer said installations between disks and even machines. Currently I use rsync to automate a daily and weekly backup through cron jobs, and pair it with making a full image of my disk with clonezilla whenever I have to power off or reboot the server. Since I rsync to a different disk than the one that contains the OS, I can safely restore a couple weeks old image and then sync my files back as needed with the daily or weekly backup in case I need to.
Now, my jellyfin server is much younger, starting out as a laptop in 2021 and currently being hosted on a previous gaming PC I used. That's also running Debian and I successfully upgraded it from Debian 11 to 12 and it went just fine. My Jellyfin installation remained intact and functional. Again, that was my experience with Debian instead of Ubuntu, so I can't tell you how Ubuntu handles version upgrades and if it's better to reinstall. Ultimately, whether to reinstall or upgrade will depend on what you prefer. Installing from scratch will be more involved in having to set up many things again, but will give you a fresh start. Upgrading will be likely more streamlined provided nothing goes wrong, but you will need to handle any potential conflicts, merge config files changes as is convenient and deal with obsolete/loose files and packages (at least on Debian).
My advice: before you do anything to your system, you should backup everything that you can't afford to lose. And by the way, having a backup solution should not be something that you do only before a potentially breaking change, but a regular countermeasure that you deploy on any machine(s) which contain critical data; get on it yesterday if you haven't. Now, I won't lecture you about what backup software to use and how, but I will recommend that for extra important data you consider a 3-2-1 backup rule if losing any of it is devastating for your particular use case.
Whatever backup solution you employ, I would also highly recommend frequently making and storing restorable full disk images of the disk where you installed your OS. For that I use clonezilla, although this approach leads to service interruptions; however, for personal, self-hosted affairs, some downtime for general cleanup and maintenance should be acceptable. The main advantage of this approach is that it serves as the big eraser of mistakes that backups can be, while also allowing you to transfer said installations between disks and even machines. Currently I use rsync to automate a daily and weekly backup through cron jobs, and pair it with making a full image of my disk with clonezilla whenever I have to power off or reboot the server. Since I rsync to a different disk than the one that contains the OS, I can safely restore a couple weeks old image and then sync my files back as needed with the daily or weekly backup in case I need to.
Now, my jellyfin server is much younger, starting out as a laptop in 2021 and currently being hosted on a previous gaming PC I used. That's also running Debian and I successfully upgraded it from Debian 11 to 12 and it went just fine. My Jellyfin installation remained intact and functional. Again, that was my experience with Debian instead of Ubuntu, so I can't tell you how Ubuntu handles version upgrades and if it's better to reinstall. Ultimately, whether to reinstall or upgrade will depend on what you prefer. Installing from scratch will be more involved in having to set up many things again, but will give you a fresh start. Upgrading will be likely more streamlined provided nothing goes wrong, but you will need to handle any potential conflicts, merge config files changes as is convenient and deal with obsolete/loose files and packages (at least on Debian).
Server specs => OS: Debian 12 | GPU: Arc A380 | CPU: Ryzen 5 5600X | 64GB RAM | 56TB
