Windows to Linux - How to?

[stanger89]

So, I've kind of wanted to do this for a while, but I was never big on spending for the linux license, anyway the stars are aligning (V9/Linux development is active, I've got a "linux" server....) that I'm seriously considering finally switching.

Specifically I'm looking at moving SageTV from a Windows 7 VM to a Docker.

The focus of this thread is to collect info on how to migrate from a Windows install to a Linux one.

I don't run much for plugins, webserver and sjq are about it for server plugins, I access everything from extenders (maybe clients someday), and I also run comskip/SA.

The big issue/question for me is how do you handle moving the wiz.bin/recordings without losing any info? Windows and Linux look at paths entirely differently. Is it best to just record to a samba/unc path share?

[wayner]

I am in the process of moving from V7 Win7 to V90 on Win10 and I have migrated my recordings to new drives on the new PC. I would suggest making sure that you have .properties files created and then when you copy or move the files over to the new box the metadata from the .properties files can be read in to the new wiz.bin. This worked fine for me with the exception of some Fanart that didn't display properly which appears to be a bit of a or bug in Phoenix or Gemstone.

[bcjenkins]

Readers Digest version

You could look at some of my old posts. When I made that switch, I just moved the Wiz.bin file and the content to the right locations. If you ever set up actual clients, you recreate the paths using a junction link on Windows to mount the share using the same path structure.

[rerooks]

Stanger, how did your transition to Linux go? What was your big driver, the amount of Java memory available?

[stanger89]

I still haven't yet. Everything is working as is.

But for me the main driver is streamlining, currently I have Sage running on a Windows 7 VM on my unRAID (essentially linux) server. Seems like it would be much more streamlined to just run Sage on unRAID (via Docker).

[hugenbdd]

Originally Posted by stanger89

I still haven't yet. Everything is working as is.

But for me the main driver is streamlining, currently I have Sage running on a Windows 7 VM on my unRAID (essentially linux) server. Seems like it would be much more streamlined to just run Sage on unRAID (via Docker).

Would love to have Sage in a Docker for unRAID. Are you working on a docker or have you tested one?

[stanger89]

There's another user here who created a docker early on. I've played with it in a VM, it can actually be simplified a good bit now that there are installers for V9. It seemed to work, but I didn't spend much time with it.

I also haven't tackled issues like what to record to, if the unRAID pool is fast enough to be recorded to directly for example (I suppose an enormous cache drive would be one option).

[SomeWhatLost]

Originally Posted by stanger89

I also haven't tackled issues like what to record to, if the unRAID pool is fast enough to be recorded to directly for example (I suppose an enormous cache drive would be one option).

simple, just get one of those 16TB SSD's from Samsung for a cache drive and call it a day...
maybe replace the array+parity drives with them also?
problem solved...

I am sure they are repetitively cheap by now...

[stanger89]

This is probably going to take a while, but just wanted to post some thoughts.

I mentioned I have concerns about writing directly to the unRAID pool, so I did a little investigating about the practicality of using a "really large" cached drive and having Sage write to that.

I used a program SSD Ready* and measured my average writes over about a week. By that, Sage writes about 90GB/day of recordings. First thing, that's easily handled by "normal" SSD capacities.

Second, that seems to be well within the capabilities of SSDs without having to worry about write endurance. The 500GB 840 EVO that would probably find itself as my cache drive if/when I do this, should last 15 years at that rate:
http://www.anandtech.com/show/7173/s...odels-tested/3

So basically, it seems plausible to put a big SSD cache drive in unRAID and record to a cache enabled share. That should provide plenty of performance and I shouldn't need to worry about burning out the SSD.

Now, when my cash flow opens up and I can upgrade the SSD in my desktop I may take on this experiment.

*SSDReady seemed to work fine, but I got a out of memory error in Sage which I've never had before. Coincidence? Possibly.