The context: we have an APC SMART-UPS 2200 RM XL 3U backup battery with a serial port (NO USB). We also have an Apple Xserve dual G5 with both USB ports and a serial port. I have been trying to use the free APC PowerChute software to setup a script that would gracefully shut down our server and FileMaker databases in the event of a power failure. I have had a number of unhelpful popup message generated by PowerChute, including one that power was lost and the computer will shut down in about 2 hours. After calling tech support (which was fairly helpful), I started messing around with things. Here is my followup email…
~~~~~~~~~~~~~~~~~~~~~~~~
"Hi again,
After experimenting with the server setup last night, I have come to conclude that the PowerChute software is practically useless (or I am doing something seriously wrong).
The APC SMART-UPS device itself seems to be a star performer. After unplugging the power from the wall several times, it kept our Xserve, switches, phone system, T1 box and other devices running. We eventually plan on plugging several power-over-ethernet enabled IP cameras into our network that will rely on this battery as well, and I have no doubt it will work.
However, in the event of a prolonged power outage, the thing that most concerns me is our hosted FileMaker database. I do have a backup routine in place, but abruptly removing the power from the Xserve, which will obviously close all open applications and services, is not good for FileMaker files. They need to be properly closed in order to prevent corruption.
The APC PowerChute ReadMe file says the following:
"Shutdown : The OS shutdown performed by this application is an emergency shutdown. No applications are closed and no application data is saved. On restart some applications may report a warning. This is expected behavior."
This is also unacceptable behavior for a server running business critical services like ours.
As I scroll down to the "For Advanced Users" section of the ReadMe, I see a procedure that illustrates a way to gracefully shutdown the Xserve using a shell script. One thing that you must understand is that I am NOT a person who appreciates the command line. I very much dislike the fact that if I am to have even a remote chance at shutting down the server gracefully, I have to have UNIX experience (I don't, so I am left Googling for answers and stumbling through the Terminal).
Furthermore, I came across a disconcerting report that indicates that even if I setup everything correctly, the PowerChute software only launches this shell script "a split second before the battery power is cut off." Given that this report dates back to Febraury of 2003, I looked at the latest list of changes (current version being 1.3.4), and no mention of allowing for more time for the script to work is mentioned.
Furthermore, I noticed with great surprise that upgrading to PowerChute version 1.3.4 was a huge mistake, as Mac OS X Server 10.3.9 is no longer supported!!! This is something I should have double-checked before upgrading myself, but I had just taken your word for it.
Again, I am just kicking myself for not purchasing an APC with USB support, because if I had done so, Mac OS X would have "just worked".
Please tell me something good."
~~~~~~~~~~~~~~~~~~~~~~~~
It's been over a month and still no reply, so I decided to post it here for everyone to see. :(
APC Powerchute
for the uninterruptable power supplies (UPS)
Version: 1.3.4
My Unanswered Email to APC
Feedback Type: Review
Contributed by: mdlarson Friday, September 29 2006 @ 07:29 AM PDT
Product Platform: MacOSX
Used Product For: 6-12 months
Recommend Product: NO
Overall Rating:
Ease of Use:
Support:
Features:
Quality / Stability:
Price:
My Unanswered Email to APC - Kent Durvin
One solution would be to buy the cheapest UPS with USB, and then connect the USB to your server. Don't use it for power to the server, and set Energy Saver to shut down after a few minutes on UPS power. Don't have it shut down based on expected time left, because it will be different with this UPS.Reply to This
Wednesday, October 18 2006 @ 10:07 AM PDT