Export/import cycle of recording-backup.xml changes recording time

[vmq]

I am moving my NPVR installation to a new machine. In order to keep my recording database I exported it to recording-backup.xml, then search/replaced the <filename>J:\rec\...</filename> information with the new path and imported the xml file back into the new machine. The lower picture shows the old machine, recording from 7pm to 8pm.

Code:

2016-12-13 18:58:08.437    [DEBUG][8]    Asking NDigitalHost to start: J:\rec\NCIS\NCIS_20161213_19002000.ts
2016-12-13 18:58:15.015    [DEBUG][8]    Temp at 12/13/2016 6:58:25 PM
2016-12-13 18:58:15.015    [DEBUG][8]    Started recording (1807:1:J:\rec\NCIS\NCIS_20161213_19002000.ts)

After the import the time is shifted to 1pm to 2pm.

Looking at the xml:

Code:

<filename>J:\rec\NCIS\NCIS.S14E10.The Tie That Binds.ts</filename>
    <status>READY</status>
    <startTime>2016-12-14T00:58:15.0000000Z</startTime>
    <endTime>2016-12-14T02:02:00.0000000Z</endTime>

The time is saved in GMT (my timezone is CT) and the import gets it wrong twice. The imported time time now is 2016-12-13 at 12:58:15. It seems the timezone difference is subtracted twice.

Is there another way to move the db and change the paths?

Volker

P.S.: Old system Windows XP, new system Windows 10.

[vmq]

The time is saved in GMT (my timezone is CT) and the import gets it wrong twice. The imported time time now is 2016-12-13 at 12:58:15. It seems the timezone difference is subtracted twice.

I looked into the npvr.db3 database. The time is exported correctly, in UTC, but when importing the xml file the time gets imported as the corresponding local time, i.e. -6 hours. This leads to the observed time difference in NPVR.

Volker