2024-01-23, 10:17 PM
(This post was last modified: 2024-01-23, 10:24 PM by Efficient_Good_5784. Edited 2 times in total.)
Is there a specific purpose for running the secondary server? Do you intend to keep it as a backup, or do you intend to use it along with your main server?
Also, are both servers running the exact same hardware?
You could do what I'm doing. I have a two servers. On both, Jellyfin runs in a container with the media and Jellyfin config folders outside of the containers.
Daily, my main server copies the media and config folders onto the secondary server (using an rsync task). Since the Jellyfin config folder is relatively small, this can be transferred to the 2nd server within a minute.
Before the transfer, I have a script run to turn off the Jellyfin container on the 2nd server, then a second script run to turn it back on around 10 minutes later. I figured leaving around 10 minutes of time is more than enough time to allow for the config folder to be copied to the destination in its entirety on a 1Gbps network link.
So when my 2nd server starts Jellyfin up, that Jellyfin instance will have an exact copy of my main server. If I make changes on it, it will only hold for a day. The rsync task I use is set to delete anything that's not on the main server (basically an exact copy after each transfer). Each day, it will get updated with whatever is on my main Jellyfin server.
Also, since both my servers have different hardware, I edited one of the xml files for playback to modify which settings to use for transcoding, then made a script replace that exact xml file on the 2nd server so that after each daily rsync task, the 2nd server will still have its necessary playback settings. I also did something similar with some of the scheduled task files so that the 2nd server doesn't run any background tasks (since the main server does all that work).
Also, are both servers running the exact same hardware?
You could do what I'm doing. I have a two servers. On both, Jellyfin runs in a container with the media and Jellyfin config folders outside of the containers.
Daily, my main server copies the media and config folders onto the secondary server (using an rsync task). Since the Jellyfin config folder is relatively small, this can be transferred to the 2nd server within a minute.
Before the transfer, I have a script run to turn off the Jellyfin container on the 2nd server, then a second script run to turn it back on around 10 minutes later. I figured leaving around 10 minutes of time is more than enough time to allow for the config folder to be copied to the destination in its entirety on a 1Gbps network link.
So when my 2nd server starts Jellyfin up, that Jellyfin instance will have an exact copy of my main server. If I make changes on it, it will only hold for a day. The rsync task I use is set to delete anything that's not on the main server (basically an exact copy after each transfer). Each day, it will get updated with whatever is on my main Jellyfin server.
Also, since both my servers have different hardware, I edited one of the xml files for playback to modify which settings to use for transcoding, then made a script replace that exact xml file on the 2nd server so that after each daily rsync task, the 2nd server will still have its necessary playback settings. I also did something similar with some of the scheduled task files so that the 2nd server doesn't run any background tasks (since the main server does all that work).