Synchronizes the database watched status between two Plex servers. This includes watched times, and works for all users on the system without the need for tokens. Modified from original to include locations for Plexguide installation.
To use the script, you will need to be able to access the databases of both Plex servers from one place. This can be done with programs like sshfs
. For instance, you could run the script like this:
wget https://github.com/timekills/plex-db-sync-plexguide/blob/master/plex-db-sync-plexguide
apt install sshfs sqlite3
mkdir -p /mnt/sshfs
sshfs -o allow_other,nonempty [email protected]:"/opt/appdata/plex/database/Library/Application Support/Plex Media Server/Plug-in Support/Databases" /mnt/sshfs
chmod +x plex-db-sync-plexguide
./plex-db-sync-plexguide \
--plex-db-1 "/mnt/sshfs/com.plexapp.plugins.library.db" \
--plex-start-1 "ssh -o StrictHostKeyChecking=no -i root@TLD docker start plex" \
--plex-stop-1 "ssh -o StrictHostKeyChecking=no -i root@TLD docker stop plex" \
--plex-db-2 "/opt/appdata/plex/database/Library/Application Support/Plex Media Server/Plug-in Support/Databases/com.plexapp.plugins.library.db" \
--plex-start-2 "docker start plex" --plex-stop-2 "docker stop plex"
The script stops and starts Plex Media Server for a very short period of time to make updates. Due to buffering and reconnections, this does not impact clients when playing, except perhaps on the first run when a very large number of records are being updated.
The following example is for docker-compose. It assumes you are running one Plex server locally, and another remotely and that you are using the Plexguide.com install.
version: '4'
services:
plex-db-sync:
image: timekills/plex-db-sync-plexguide
container_name: plex-db-sync-plexguide
volumes:
- /etc/localtime:/etc/localtime:ro
- ./plex-db-sync/sshkey:/sshkey
- /opt/appdata/plex/database/Library/Application Support/Plex Media Server/Plug-in Support/Databases/:/mnt/DB2
cap_add:
- SYS_ADMIN
devices:
- /dev/fuse
security_opt:
- apparmor:unconfined
environment:
- CRON=0 4 * * *
- S1_SSH_KEY=~/.ssh/id_rsa
- S1_SSH_USER=root
- S1_SSH_HOST=hostname
- S1_SSH_PORT=22
- S1_DB_PATH==/config/Library/Application Support/Plex Media Server/Plug-in Support/Databases
- S1_START=ssh -oStrictHostKeyChecking=no -i /sshkey root@hostname 'cd /; docker start plex'
- S1_STOP=ssh -oStrictHostKeyChecking=no -i /sshkey root@hostname 'cd /; docker stop plex'
- S2_DB_PATH=/config/Library/Application Support/Plex Media Server/Plug-in Support/Databases/
- S2_START=cd /; docker start plex
- S2_STOP=cd /; docker stop plex
restart: always
Command Line | Docker Variable | Description |
---|---|---|
--backup <true/false> |
BACKUP |
Create a backup of the DB before running any SQL. |
--debug <true/false> |
DEBUG |
Print debug output. |
--dry-run <true/false> |
DRYRUN |
Don't apply changes to the DB. |
--plex-db-(1/2) |
S(1/2)_DB_PATH |
Location of the server's DB. Pre-set above for Plexguide Docker, so shouldn't need to use this variable. |
--plex-start-(1/2) |
S(1/2)_START |
The command to start the Plex server. Pre-set for Plexguide Docker, so shouldn't need to use this variable. |
--plex-stop-(1/2) |
S(1/2)_STOP |
The command to stop the Plex server. Pre-set above for Plexguide Docker, so shouldn't need to use this variable. |
n/a | CRON |
A string that defines when the script should run in crond (Default is 4AM). |
n/a | INITIALRUN |
Run at start prior to starting cron. |
n/a | S(1/2)_SSH_KEY |
The SSH identity file. Assumes you've already created and shared the SSH files between the servers and they're stored in the default path. If so, then leave the as above. |
n/a | S(1/2)_SSH_USER |
The SSH user. You'll have to change this. |
n/a | S(1/2)_SSH_HOST |
The SSH host. You'll have to change this. |
n/a | S(1/2)_SSH_PORT |
The SSH port. |
n/a | S1_DB_PATH |
Path to the database file on the server you're SSH'ing into and copying the database to (the host's /opt/appdata/plex/database directory is already mounted to /config inside the Plex Docker container.) |
n/a | S2_DB_PATH |
Path to the database file on the server you're running the command from and copying the database from. |