Restore on new windows installation

[Space]

The "[backup]" button only takes the existing backups and zips them?

Maybe it should create new backups and then zip them? Most likely someone is going to use this to save the backups after making some changes, and you would want the latest backups. If the "every 5 days" cleanup/backup hasn't run since the changes, then they won't be saving the latest backups which is not very intuitive...

[garyan2]

It does, I simplified. You hit the backup button, it runs -b, and then when that completes it zips the new files.

Sent from my SM-G965U using Tapatalk

[technodevotee]

For 1.6.7.2, there will be a log entry during the client run for "Successfully forced a Media Center database configuration backup. Exit code: 0". This is when the WMC backup is done. For the next release, the WMC backup will be wrapped in with the garbage cleanup run and will not be a separate log entry.

Are you saying that the backup won't run if you use the -nogc option like I do?

For some reason, I haven't been able to allow your software to run a garbage collection when RecordingBroker is running and had to create a batch file that stops RecordingBroker, runs the cleanup then starts RecordingBroker. I don't think it is anything to do with EPG123, just the fact that EPG123 automated the process when I used to run it manually when I felt it was needed.

I guess I could add a command to run a backup in there if needed.

[garyan2]

Correct. The forced WMC backup will not run if you use -nogc option for the client. For manually controlling the garbage collection and forcing the backup, just change the command to "mcupdate.exe -b -dbgc -updatetrigger"

Code: Select all

-b Backup
-dbgc Garbage collection
-updatetrigger Bypasses trying to download package updates from MS

This should probably be now referred to as the client maintenance.

[Space]

I removed the -updateTrigger from my stand-alone backup and garbage collection due to this thread, should I add it back?

It's my understanding that with the -updateTrigger option it will no longer try to download packages (which no longer exist) but it will also not initiate a reindex.

Isn't a reindex needed after a garbage collection (GC)? I assume the GC will delete some stuff that has been indexed, so reindexing seems appropriate.

[garyan2]

You are correct. I had forgotten about that. I'll attribute it to old age.

EDIT: I will note that when the client imports the mxf file, it will kick off the reindex then. I think it is fine to leave it out.

[technodevotee]

Turns out that my script doesn't work very well even when I enable the Scheduled Task that I created to run it periodically.

GC has been running for a couple of days now.....

When it kicked off mcupdate.exe -dbgc, it didn't wait for it to finish completely so Recording Broker was being restarted before the Garbage Collection was finished.

To get round that, I've created a (rather crude) vbs script that monitors the process list and shuts down the Recording Broker service when mcupdate is running, then starts it when it is no longer active.

This should allow me to run the EPG123 update with Garbage Collection enabled.

We'll see how it goes.

Update: GC eventually finished and the database shrank from 1.2GB to 252MB. I reckon it was worth the wait to have hopefully retained my history.

[garyan2]

Though you now have a vbs script, in the batch you should use "START /WAIT c:\windows\ehome\mcudpate.exe -dbgc" to block the batch file from proceeding until the dbgc has completed.

[technodevotee]

Yeah, I tried that but as I'm sure you aware, mcupdate restarts (with a new PID) quite a few times when the DB is heavily fragmented or contains a lot of outdated records and the batch file continues as soon as that happens.