Sage Upgrade with Simultaneous Computer Move.

[Mike]

I know these questions get asked alot and If I was just moving from one computer to another I think I'd be fine, but I'm going to upgrade to 7 at the same time that I change computers so I have the following question.

Should I do an upgrade before the move and then perform the recording transfer function as described here in response number 6, or would I be safe to just install Version 7 directly onto the new computer and just follow the above procedure and replace the wiz with one I backed up before I started moving everything ?

[Spectrum]

Just install V7. If you have a V7 upgrade key, when for license key, put in your V6 key and it should ask for new V7 key afterward. If you have a new key that is valid for V6/7 just put it in. After you get Sage up and running and get tuners configured, copy in your old recording info and your old wiz.bin and you should (TM) be good to go

[Mike]

Thanks, I think I'll start on it in the morning.

[Tomahawk51]

From the perspective of bringing in old recordings, would Mike be better off doing the v7 upgrade on his system now, and then do an install on the new system?

The reason I wonder comes from the v7 feature that keeps metadata about recordings in the file (so that it's OK to just dump your recording files around rather than worry about drive mapping exactness, etc.).

FYI - I did the v6-v7 upgrade, server and OS rebuild, install v7, drop in wiz.bin approach and it worked well for me. Maybe these were redundant steps.

[Mike]

I don't guess I was aware of this feature in V7. Would I need to alter the method of moving I linked to above if I did the upgrade first?


TIA

[Fuzzy]

As long as you still have the original v6 wiz.bin, there's no need to go through the upgrade step on the old machine, just to get the metadata in the files. If sage recognizes the recording by referencing the AiringID in the filename to the data in the wiz.bin, it doens't need the metadata in the files themselves.

[Mike]

I did the upgrade yesterday using the procedure I linked to, and by just installing Version 7 directly on the new computer. I have a couple of minor issues, but I'm past all of the big stuff that could have gone wrong with all of the program data intact.

Thanks!

[Mike]

One thing I would add is that I did wind up redoing a bunch of configuration stuff & scanning and editing channels etc. that I wouldn't have done if I had either moved 6 and then upgraded or upgraded and then moved 7. I could have just copied the properties file in those cases.

[Fuzzy]

As infrequently as it is, I find it good when I do a move/upgrade like this to go ahead and start the settings from scratch. Gives me a new look at the channel lineup and such.

[Mike]

That is a good point. I hadn't looked at the channel line up since we went to all digital OTA and I did see some new things in the configuration menus. Kind of a preference thing one way or another.

[BobPhoenix]

Originally Posted by Fuzzy

As long as you still have the original v6 wiz.bin, there's no need to go through the upgrade step on the old machine, just to get the metadata in the files. If sage recognizes the recording by referencing the AiringID in the filename to the data in the wiz.bin, it doens't need the metadata in the files themselves.

Except when an EPG update updates the ID in the Wiz.bin for an existing recording. The file name doesn't get updated with the new number. I had to write a small java app to do that for approximately 320 recordings (out of several thousand - maybe 10,000+). At least I'm assuming it was an EPG update that did it. Those recordings were from 2007 so it could have been caused by an old Sage version. Or a combination of the two - old version with EPG update.

[Fuzzy]

and EPG update shouldn't have changed data fro 3 years ago. Odds are that data was just no longer in the wiz.bin anymore (I don't think it used to keep everything forever.. oddler versions I believe purged that data after the file was 'removed'.)

[Opus4]

The numbers that changed had nothing to do with the EPG data, but were Airing IDs (the number that is part of the filename), which could get changed once in a while prior to v7 -- this is mentioned somewhere in the FAQ topic for moving recordings, where it talks about dealing with that case. As far as I know, v7 should not be re-indexing those values any more & it can match on the embedded recording metadata anyway.

- Andy

[BobPhoenix]

Originally Posted by Fuzzy

and EPG update shouldn't have changed data fro 3 years ago. Odds are that data was just no longer in the wiz.bin anymore (I don't think it used to keep everything forever.. oddler versions I believe purged that data after the file was 'removed'.)

Originally Posted by Opus4

The numbers that changed had nothing to do with the EPG data, but were Airing IDs (the number that is part of the filename), which could get changed once in a while prior to v7 -- this is mentioned somewhere in the FAQ topic for moving recordings, where it talks about dealing with that case. As far as I know, v7 should not be re-indexing those values any more & it can match on the embedded recording metadata anyway.

- Andy

That is what I figured and why I updated to V7 first - so that data in wiz.bin that was still connected for these mismatched files would get written out to the files. The update to V7 didn't help however. When I moved them they ended up in imported videos with no data. I had to do the process outlined below. I though incorrectly that an EPG update from back in 2007 caused the airingIDs to change. But as you said Sage just reindexed the database - did not remember that - sorry. Do you think it could be either of the following as to not getting metadata on those files when I upgraded to V7 and then moved them?

1. Since it had an airingID in the file name already the metadata written to the file from the wiz.bin airingID was not displayed but is actually IN the file like it is suppose to be. But Sage wouldn't import it since the airingID of the file didn't match the airingID in the file metadata - assuming the airingID is even within the metadata written to the file anyway.
2. Since the airingID on the file didn't match the airingID in wiz.bin no data was written to the file by V7.0.23

But in any case I got the files moved. What I actually had to do to retain a connection was:

1. Get airingID from the wiz.bin entry.
2. Replace the file airingID with the retrieved airingID.
3. Add the new media file (with updated airingID) to the database.
4. Delete the original media file from the database.
5. Associate the new media file with the old airing.
6. Repeat from step 1 until all files processed

And FYI this is what I tried when updating this server my other servers updated and I was able to move files no problem. This one was my oldest. The wiz.bin started in 2004 but I no longer have any connections in wiz.bin prior to 2007.

1. Renaming a file with the correct airingID didn't appear to work in V6. It was just seen as an imported video after a library import scan - kind of expected this.
2. So I then tried to update to V7 thinking that the info would be written to the file. That didn't appear to have worked because moving them after the upgrade still put them in imported videos with the old mismatched airingID or the new airingID on the file. They were still connected at their original locations after the upgrade however.
3. The only thing that worked was the code I outlined above.
4. During all of the above I tried it on one file and had backups of wiz.bin that I restored between each test as well as renaming file back to original file name.

[Opus4]

The FAQ has instructions for fixing airing IDs - it ends up renaming the files to match the new airing ID. I think if that had been done, there would have been no problem.

There is a known issue in v7 where is you import the recording to a new v7 server (so that it is a different wiz.bin, essentially), if the airing ID matches an ID already in the database, you could get the wrong airing info for the recording. This will be handled in a future update.

It should have worked OK to just install v7 on top of the v6 installation & kept the correct EPG data for all recordings. As long as the file was moved & SageTV v7 used the same wiz.bin after that, it should have continued to work... as far as I know.

- Andy

[BobPhoenix]

Originally Posted by Opus4

It should have worked OK to just install v7 on top of the v6 installation & kept the correct EPG data for all recordings. As long as the file was moved & SageTV v7 used the same wiz.bin after that, it should have continued to work... as far as I know.

- Andy

That's what I hoped too. I should have turned in a support issue. Unfortunately I didn't have the time. Only took a day to write my fix and on a weekend. I would have been waiting until Monday for a support request so I just fixed them myself. Doubt it will come up now that I'm on V7 but I will report it if it happens again.