Size of database

[nydave69]

currently have >1000 shows mostly really old one's, some are just missing one or two episodes, some specials etc..
I need them to be active to locate missing items...

What I was thinking is to split the list into 2 running versions of Medusa, one for show that started airing before 2000 and the other after.

What are the issues in doing this?
Is it possible?
better way?

[p0psicles]

Yeah you could do that. Then one of the two instances you can set a high interval for backlog searches. And even disable daily search. As that's the highest CPU hog

[nydave69]

Only thing I can't figure out is how to change the WebUI to reflect which is which,
one being Medusa 1900 and the other Medusa 2000.

[p0psicles]

You could create different show labels doe each install

[nydave69]

Show labels?
Not sure how or where I would do that

[nydave69]

So I have decided to go ahead and split the database into two instances Medusa_1900 and Medusa_2000
So far I am on my second attempt and it looks good.. I'll detail what I did later once it has run for a while.

[nydave69]

All is good, very good actually wish I had done this a year+ ago.
Seem the split is running faster with less CPU resources. Used to be 80% to 90% almost all the time. Now it's down around 15%
I do not know why such a big change, also It was finding only one or two episodes a night, This morning I had a list of 80 to get.

I'm running this on Windows, The process runs in a command window..
How I did the split...
First I made sure all shows had the year attached and I didn't miss any.
I copied the Medusa folder to a storage drive. (7GB)
I had Medusa due a external backup just in case.
I then copied the Medusa folder to c:\Medusa_1900 and again to c:\Medusa_2000
all settings and data are duplicated to both folders
I started Medusa_1900 first and watched it load, no errors other than the usual ones.
At this point on the first try I didn't due a few things I should have.

1. In settings change the log file location, mine was c:\medusa\data\log and changed to c:\medusa_1900\data\log
   other wise the two will conflict when both are running.
2. Disable all notifications like Tratk etc.. otherwise when removing the shows in this instance it will send out all the notifications.
3. made sure no queues were running (wish there was an overall pause button)

For this instance I want to remove all the shows with years started in 2000+ leavening the 1900 shows in the database.
Only removing database records not the actual files..
I opened mass update

For shows I entered (20 to get only the shows from (2000) on.
I checked to make sure I had selected the correct shows
I did a select all for the shows, I then did a select all for remove (just want them out of the database) then click Trigger Actions

This can take a long time depending on the number of shows it needs to remove, let it run to complication,
When finished Check the shows list etc.. to make sure things turned out fine.
note that it's possible that shows were sent to the downloader while this process was taking place.
If everything checks out shutdown this instance and start the 2000 one.
Following the same procedure but removing the 1900 to 1999 shows.

One other thing is I use a label sent to the downloader MU to seperate shows from other things.
I changed it to MU19 and MU20

[nydave69]

One issue I have is after doing the above I could not get the latest version to update 14 commits behind..
So I did a backup of Medusa... Downloaded and installed python 3.10.... Downloaded 1.03 of Medusa and installed it into a new folder..
I stared Medusa using Python 3.8.10 and all went well.. I than restored the database back to Medusa...
But I'm back to the 14 commits behind and Version 1.03 is running.

Medusa Configuration

Medusa Info:	Branch: master Commit: Unknown Version: 1.0.3 Database: 44.19
Python Version:	3.8.10 (tags/v3.8.10:3d8993a, May 3 2021, 11:34:34) [MSC v.1928 32 bit (Intel)]
SSL Version:	OpenSSL 1.1.1k 25 Mar 2021
OS:	Windows-7-6.1.7601-SP1
Locale:	en_US.cp1252
Timezone:	Eastern Daylight Time

Medusa Configuration Medusa Info: Branch: [master](https://github.com/pymedusa/Medusa/tree/master) Commit: Unknown Version: [1.0.3](https://github.com/pymedusa/Medusa/releases/tag/v1.0.3) Database: 44.19 Python Version: 3.8.10 (tags/v3.8.10:3d8993a, May 3 2021, 11:34:34) [MSC v.1928 32 bit (Intel)] SSL Version: OpenSSL 1.1.1k 25 Mar 2021 OS: Windows-7-6.1.7601-SP1 Locale: en_US.cp1252 Timezone: Eastern Daylight Time

Now I see There is a newer version available (you're 39 commits behind) — Update Now

And when I try to update...
Update Medusa
Checking if medusa needs an update Yes
Waiting for Medusa to create a backup: Yes
Waiting for Medusa to update: No

So I tried a second time and now the message is There is a newer version available (1.0.4) — Update Now

Trying another update with the new message, clicking update in that new message.

the log for the three attempts;
`2022-07-05 12:16:27 INFO APIv2-Thread :: Moving files from C:\Medusa_1900\medusa-update\pymedusa-Medusa-848c295 to C:\Medusa_1900
2022-07-05 12:16:27 INFO APIv2-Thread :: Deleting file C:\Medusa_1900\medusa-update\medusa-update.tar
2022-07-05 12:15:51 INFO POSTPROCESSOR :: Post-processing completed.
2022-07-05 12:15:51 INFO POSTPROCESSOR :: Processing path: O:\utorrent\completedDownload\MU19
2022-07-05 12:15:48 INFO APIv2-Thread :: Extracting file C:\Medusa_1900\medusa-update\medusa-update.tar
2022-07-05 12:15:41 INFO APIv2-Thread :: Downloading update from 'http://github.com/pymedusa/Medusa/tarball/master'
2022-07-05 12:15:41 INFO APIv2-Thread :: Clearing update folder 'C:\Medusa_1900\medusa-update' before extracting
2022-07-05 12:15:41 INFO APIv2-Thread :: Clearing out update folder 'C:\Medusa_1900\medusa-update' before extracting
2022-07-05 12:15:41 INFO APIv2-Thread-2 :: Config backup successful
2022-07-05 12:12:50 INFO APIv2-Thread-2 :: Config backup in progress...
2022-07-05 12:11:23 INFO APIv2-Thread :: Moving files from C:\Medusa_1900\medusa-update\pymedusa-Medusa-848c295 to C:\Medusa_1900
2022-07-05 12:11:23 INFO APIv2-Thread :: Deleting file C:\Medusa_1900\medusa-update\medusa-update.tar
2022-07-05 12:10:47 INFO APIv2-Thread :: Extracting file C:\Medusa_1900\medusa-update\medusa-update.tar
2022-07-05 12:10:41 INFO APIv2-Thread :: Downloading update from 'http://github.com/pymedusa/Medusa/tarball/master'
2022-07-05 12:10:41 INFO APIv2-Thread :: Clearing update folder 'C:\Medusa_1900\medusa-update' before extracting
2022-07-05 12:10:41 INFO APIv2-Thread :: Clearing out update folder 'C:\Medusa_1900\medusa-update' before extracting
2022-07-05 12:10:41 INFO APIv2-Thread-1 :: Config backup successful
2022-07-05 12:08:08 INFO APIv2-Thread-1 :: Config backup in progress...
2022-07-05 12:05:50 INFO POSTPROCESSOR :: Post-processing completed.
2022-07-05 12:05:50 INFO POSTPROCESSOR :: Processing path: O:\utorrent\completedDownload\MU19
2022-07-05 12:00:50 INFO APIv2-Thread-1 :: Moving files from C:\Medusa_1900\medusa-update\pymedusa-Medusa-848c295 to C:\Medusa_1900
2022-07-05 12:00:50 INFO APIv2-Thread-1 :: Deleting file C:\Medusa_1900\medusa-update\medusa-update.tar
2022-07-05 12:00:03 INFO APIv2-Thread-1 :: Extracting file C:\Medusa_1900\medusa-update\medusa-update.tar
2022-07-05 11:59:57 INFO APIv2-Thread-1 :: Downloading update from 'http://github.com/pymedusa/Medusa/tarball/master'
2022-07-05 11:59:57 INFO APIv2-Thread-1 :: Clearing update folder 'C:\Medusa_1900\medusa-update' before extracting
2022-07-05 11:59:57 INFO APIv2-Thread-1 :: Clearing out update folder 'C:\Medusa_1900\medusa-update' before extracting
2022-07-05 11:59:57 INFO APIv2-Thread-2 :: Config backup successful
2022-07-05 11:56:39 INFO APIv2-Thread-2 :: Config backup in progress...
2022-07-05 11:55:50 INFO POSTPROCESSOR :: Post-processing completed.

`

[p0psicles]

You keep having issue with git.
Else manually install git on your system. So that you can run git commands at each location.

[nydave69]

Found the issue....

When I restored the database and config files for some reason unknown to me, the branch was reset to none of the two..
I changed it to master and did a branch checkout... saved the config... all is good again...