"recovering" recording DB entries

[fbachofner]

I disconnected my server for some cleaning today. On reboot I had to reconfigure BIOS (it turns out in addition to a lot of dust in the machine the RTC battery is dead).

I messed up and changed a setting for one of my banks of SATA controllers. [Wouldn't ya know it, the ones for drives related to my TV recordings.]

Reboot worked fine. Ten minutes later I decide to perform some file exploring . . . my "T:" drive is not there. Aha! I realize I made a small mistake in BIOS.

Long story short, in those ten minutes GBPVR apparently deleted entries regarding about 200 recordings from the DB since it could not "see" them while the recordings drive was invisible to the system.

The recordings are, however, ALL still listed in the "PROGRAMME" table in the gbpvr.db3 database. What can I do to make them reappear in recordings in the GBPVR interface? [The recordings are nicely grouped at the beginning of the PROGRAMME table, followed by what appears to be the EPG for upcoming shows.]

The actual recording files are, of course, still on the drive too.

My problem seems less severe than other similar posts. I'm guessing I just need to refer to the PK of the relevant entries in another table, which I could probably do in a batch with some SQL wizardry. Unfortunately, I don't understand the GBPVR.db3 format particularly well.

Any and all help is appreciated! I have new recordings scheduled for June 10 . . . at which point I guess my situation might become more complicated. [I do, of course have a backup of the .db3 file in its current state.]

Thanks in advance.


Felix

[martint123]

You should have two files in the gbpvr program directory called "recording-dump.xml" and "recording-dump.bak" these are exports of recordings made when the EPG update is done (and the .bak from the time before)
These can be imported with teh config utility to restore things. Make sure your drive letter is back to what it was before you import things or it will housekeep them away again.
There is an option in config.xml to stop this housekeeping function if required.

[fbachofner]

Hi Martint123:

You should have two files in the gbpvr program directory called "recording-dump.xml" and "recording-dump.bak" ... <snip> ...
These can be imported with teh config utility to restore things.

Thank you *SO* much! This worked like a charm. If you had answered a day later I might have been out of luck (unless I could undelete an earlier "recording-dump.bak" -- but as you know, undeletes are not a sure thing.

There is an option in config.xml to stop this housekeeping function if required.

That's great! I've been looking for an option named something like "delete missing recordings from DB," but there seems to be no similar option.

Do you happen to know what <AutoCompactDatabaseAfterEPGUpdate> does? As a description I would just guess that gbpvr.db3 gets SQLite "vacuumed" if this option is set to true, but perhaps this is the setting for which I am looking.

Sub, can you comment on this issue if no one else knows? Thanks.


Felix

[Jaggy]

I think this is the one you are looking for I have mine set to false at the moment but it would be nice to be able to change it from within config & not have to edit the config.xml all the time...oh well wishful thinking I guess

<AutoRemoveMissingRecordings>false</AutoRemoveMissingRecordings>

[sub]

Yes, its called <AutoRemoveMissingRecordings>

[LewE]

Thank you *SO* much! This worked like a charm. If you had answered a day later I might have been out of luck (unless I could undelete an earlier "recording-dump.bak" -- but as you know, undeletes are not a sure thing.Felix

I found myself in a similar situation a while back and addressed it with the following added to my PostUpdateEPG.bat. You can make it go back as many days as you want. It has saved me several times where I had to go back more than one generation of saves. In Windows Explorer you can easily see which day each backup is from.

[COLOR="Blue"]cd "\Program Files\devnz\gbpvr"
if exist recording-dump.6 del recording-dump.6
if exist recording-dump.5 ren recording-dump.5 recording-dump.6
if exist recording-dump.4 ren recording-dump.4 recording-dump.5
if exist recording-dump.3 ren recording-dump.3 recording-dump.4
if exist recording-dump.2 ren recording-dump.2 recording-dump.3
if exist recording-dump.1 ren recording-dump.1 recording-dump.2
if exist recording-dump.xml copy recording-dump.xml recording-dump.1[/COLOR]