Help cleaning up database

[Jakesty]

Hello.  I have a problem where the system is very slow to respond.  Especially in the Web App.  One problem I know of is that the database has a lot of references to files which are no longer there.  They have been removed/deleted elsewhere and the DB doesn't know about them.  Is there a way to clean up what's in there to what I have?  If not really a good solution, can I just stop services and delete the DB as a last ditch effort?

thanks, Jake

[sub]

What page is slow in the web app?

One problem I know of is that the database has a lot of references to files which are no longer there. They have been removed/deleted elsewhere and the DB doesn't know about them.

By default NextPVR will automatically remove items from the disk if they'd been deleted on disk. Do you still have these set this set in your config.xml:

<AutoRemoveMissingRecordings>true</AutoRemoveMissingRecordings>

If not really a good solution, can I just stop services and delete the DB as a last ditch effort?

You can do that. Its the nuclear approach though. You'll have no recordings, or channels, and have to setup your devices again.

[Jakesty]

The slowness is when opening the ALL RECORDINGS screen. So maybe changing the autoremove to TRUE will help with this. Using the phone app is also very hit or miss. Most often the GUIDE won't fully populate, maybe I have too many channels? I've tried to minimize the numbers.
I'll also point out, I'm still on 4.x, so I understand you won't be able to fix this. But it's the only system so far that will record to my QNAP Nas drive. 5.x and 6.x won't find the drive path. I've used server name and IP addresses trying to map it or just path to the drive. 4.x had the feature to BROWSE for a network path, I don't see that in the newer releases.

thanks as always for your help Sub.
Jake

[mvallevand]

V5+ will use the same shares on you NAS just run the service as the user and enter the path manually. If that is still a problem run the service with the slower Delayed Start option used in earlier versions.

Using <CheckForRenamedRecordings>false</CheckForRenamedRecordings> will speed up the recording load as it will be a database only run which should be very fast.

Martin

[sub]

Most often the GUIDE won't fully populate, maybe I have too many channels?

How many channels do you have?

I'll also point out, I'm still on 4.x, so I understand you won't be able to fix this. But it's the only system so far that will record to my QNAP Nas drive.

Oh right - yeah, nothing is going to be fixed in v4.

5.x and 6.x won't find the drive path. I've used server name and IP addresses trying to map it or just path to the drive.

There is no reason v5 shouldn't be able to work just as well with your network shares, other than maybe timing issues (as Martin referred to above), where maybe NextPVR is trying to use your NAS before the network is up.

4.x had the feature to BROWSE for a network path, I don't see that in the newer releases.

Correct, there is not network browse feature in newer releases, because there wasn't a way to do this in a platform independent way (ie compatible with Linux/Mac/etc, but you can easily type \\server\share as a recording path if you're on Windows and want to use a share.

[artmetz]

The slowness is when opening the ALL RECORDINGS screen.  So maybe changing the autoremove to TRUE will help with this.  Using the phone app is also very hit or miss.  Most often the GUIDE won't fully populate, maybe I have too many channels?  I've tried to minimize the numbers.
I'll also point out, I'm still on 4.x, so I understand you won't be able to fix this.  But it's the only system so far that will record to my QNAP Nas drive.  5.x and 6.x won't find the drive path.  I've used server name and IP addresses trying to map it or just path to the drive.  4.x had the feature to BROWSE for a network path, I don't see that in the newer releases.

Jake,
I also have a QNAP Nas with several network directories mapped to it in NPVR (Latest). When the Nas is offline, my All Recordings screen is extremely slow in the windows app. Fortunately, this normally isn't a problem for me. You might check to see if all directories in your config.xml still exist and are accessible.
Art

[Jakesty]

Just a follow up, thanks for all the help. I'm running NextPVR, now 6.x, on a Hyper-V VM, with a shared path to my QNAP array. I used the local user on the service to get the network drives connected. I'm not sure if the two config.xml updates made enough of a difference, hopefully they did. But converting to 6.x and I added more CPUs to the VM, the devices and channels are substantially better.

One last question, Is is ok to move the npvr.db3 file over to the new 6.x? I really just want to have the scheduled recordings, nothing else matters as the new system is working.

Thank you, Jake

[mvallevand]

Do you mean the scheduled recording table or the recurring rules table? Recurring rules can only be copied if the channels are the same number which is unlikely or you scheduled them for all channels.

You can capy the v4 npvr.db3 and see how it works, it really depends on your tuner types.

Martin

[Jakesty]

My tuners are all the same, I'm really just interested in the recurring shows so that when they come up again I know they'll record. I guess one problem might be that the defaults might not be the same, but I can edit them.