Planning New WHS2011 Sage Server Build - Please comment

[BobPhoenix]

Originally Posted by Skirge01

I had read similar articles, but never tried the separate VM appliance route. However, going through the comments on the one you linked to, there's a MUCH easier way if running 5.1. If you're running 5.0U1 (like I am), then this method is supposed to work.

The appliance was easy for me. I installed the appliance and made a few changes to the VM settings (reduced memory allocated and maybe something else don't remember) and then fired it up and connected with a browser and made a couple of configuration changes to the PowerPanel web app. I'm about to try your methods since the CyberPower UPS's I bought are a little weak for one of my ESXi servers (not using all green drives so uses more power when drives start).

Yes I'm running 5.0 ESXi.

[Skirge01]

Originally Posted by BobPhoenix

The appliance was easy for me. I installed the appliance and made a few changes to the VM settings (reduced memory allocated and maybe something else don't remember) and then fired it up and connected with a browser and made a couple of configuration changes to the PowerPanel web app. I'm about to try your methods since the CyberPower UPS's I bought are a little weak for one of my ESXi servers (not using all green drives so uses more power when drives start).

Yes I'm running 5.0 ESXi.

Definitely not "my" methods. I just found them through your links. Let us know how it goes, since it sounds quite easy to set up.

[BobPhoenix]

Originally Posted by Skirge01

Definitely not "my" methods. I just found them through your links. Let us know how it goes, since it sounds quite easy to set up.

I found a better way (at least for me) by using the CyberPower client appliance. I install it on one ESXi server and it connects up to the agent appliance on another ESXi server. Normally when I loose power on one box I loose it on all of them so with separate UPSs I still only really need one connection to a UPS as long as it is the one with the shortest run time. At least that is the theory. I've yet to test it out as I just installed both and I don't have a window where both SageTV VMs are not recording and I'm awake and home. Will pull the cord on the CyberPower UPS this weekend and see if both ESXi boxes shut down successfully.

[WellThen]

Thanks to the patient guidance from BobPhoenix and Skirge01, my 3TB drives are now connected to my new M1015 controller, and fully visible in my Sage Server VM! You guys are the best!

Now working on getting the USB 3.0 PCI controller I added passed through to the VM, so I can connect the HD-PVR.

[BobPhoenix]

Originally Posted by WellThen

Now working on getting the USB 3.0 PCI controller I added passed through to the VM, so I can connect the HD-PVR.

A possible warning on that. My USB 3.0 card works perfectly with my HD-PVRs but I have to cycle the HD-PVRs after the VM comes up because they are unrecognized USB devices when I first boot the VM. So I have to cycle the SageTV service as well after they are recognized. When I passed through a 2.0 USB card I didn't have that problem.

FYI: The CyberPower client works like I expected it too. But it would be better if the multiple boxes were on one UPS for this. So I'm still thinking about trying the APC methods out.

[Skirge01]

Glad to hear it! My pleasure.

Agreed. 3.0 support is still preliminary in ESXi, so don't be surprised if you have issues. If you find any problems, revert to a USB 2.0 NEC card for now.

[BobPhoenix]

Originally Posted by Skirge01

Glad to hear it! My pleasure.

Agreed. 3.0 support is still preliminary in ESXi, so don't be surprised if you have issues. If you find any problems, revert to a USB 2.0 NEC card for now.

The only problem I have with my NEC USB 2.0 cards are that to use them correctly (all ports available) I had to pass through 3 devices. This then limited me to only 3 other devices one of which was my recording drive controller. With my USB 3.0 controller it passes through as ONE device so I can use more PCI/PCIe devices with a single VM.

[WellThen]

Uh, oh. Hit a wall. Trying to set up Sage on one my new VMs running Windows 7. I get to the point where it wants to know my zip code to download EPG information, and I get:

"There was an error connecting to the SageTV Server. Please be sure your internet connection is established and that you have entered the correct zip/postal code."

I did a search on this error, and found reference to ensuring that the firewall rules are set up, but I see the rules for the Sage executables. I also tried turning off the firewall, and I still get the same error.

Since this is under ESXi (5.0), I have to allow for the possibility that there is some problem getting to the internet. However, I am able to browse from that Windows 7 VM in IE, and ping 8.8.8.8 from the command line, so I would think I'm connecting OK.

I am using the Realtek 8168 Gigabit NIC that is built into my motherboard for all networking under ESXi. Could that be a problem? I seem to remember something about Realtek being a potential issue with ESXi, but again, if I can browse from within the VMs, can the really be the issue?

[WellThen]

Well, the good news is that after about an hour, I tried again and it downloaded the EPG channel guide. So, I was able to complete the setup.

However, it could not find any channels with signal. It appears that this is because for some reason, my passthrough drives had dissappeared - Windows no longer saw them. Rebooted ESXi, and they were back.

[BobPhoenix]

Originally Posted by WellThen

Well, the good news is that after about an hour, I tried again and it downloaded the EPG channel guide. So, I was able to complete the setup.

Yes the servers were down/not connecting for me yesterday as well.

However, it could not find any channels with signal. It appears that this is because for some reason, my passthrough drives had dissappeared - Windows no longer saw them. Rebooted ESXi, and they were back.

Haven't seen that one. I did have a problem with a controller dropping out of pass through so nothing showing for drives in the VM. Reboot fixed it as well for me. Might have been the same thing.