Some think I have been extremely (and overly) critical of the Hopper for the nightly reboots. I would argue that I set higher standards. I'm paying for a service and the devices aren't available a significant portion of the time. If my systems only had uptimes of 95.x% they wouldn't be my systems any longer; I'd be unemployed. Even standalone systems should be able to maintain 99% uptime. Clearly that isn't the case with hopper.
During the hopper reboot, no recordings can kick off and any attached joeys are unavailable. Yes, it's done in the middle of the night but I've missed recordings because the nightly reboot doesn't complete quickly enough. If you have 2 hoppers, your still SOL, as they both reboot at about the same time.
I have managed various flavors of Unix systems for 25 years. In those 25 years I haven't had any systems that required daily or even weekly reboots. I have encountered poorly written applications which required restarts on a scheduled basis due to memory leaks. But that didn't require a reboot of the OS to clean up, after all it's Unix of some form. I currently manage ~150 nodes with ~250 unique OS instances and in the vicinity of 350 TB of user data in a directly customer facing application.
Hopper is in a directly customer facing application.
Vivek:
If you have any background in IT and specifically in service delivery you should be appalled by this. At this point I want an explanation -- why must these be rebooted nightly and why does a system check that you obviously think should take 10 minutes (or you wouldn't put it up there) taking 60+ minutes. Since the hopper is a purpose built computer running some flavor of a *nix OS on a MIPS processor I expect it to behave like one.
Your product is in a directly customer facing role, and you need to treat it as though it is. Currently from my perspective you are not.