Unless your servers themselves are redundant, you'd be better off with one large UPS with an external battery cage/frame. You can often find those for sale used, but you will almost always need to replace any batteries that come with them. Buy units that use commodity batteries - you can shop around for price among battery specialty shops - often there are substantial savings available. By having an external battery box, you can add battery strings in the future to increase backup time as needed. Having more than one string (if it's wired correctly) also means you can take one string off-line for testing but still have some backup. There are some bigger units that are rack-mountable if this is in a CoLoc, but I think they offer less bang/buck than other units I've seen.
The MTTF of the bigger UPS systems is typically longer than the individual smaller UPS units (not to mention the the effective MTTF of the smaller units is reduced if any one of them failing brings down your whole application), and the bigger ones usually have much better ways to do maintenance on them without taking your AC down (such as bypass switches, which could be available for smaller systems but would have to be wired for each one, which doesn't ever happen).
Next, if you buy a system that is fairly common, you should plan (by leaving space, etc.) to buy another one just like it some day. Then you can do a "Red/Blue" power setup, where all of your key gear has dual power supplies, with one plugged into each of the different UPS systems.
Eventually, batteries run out. And eventually, you will go down long enough that some VIP will recommend buying a generator. Generators are also best purchased used. I used to like the idea of natural gas powered generators - in a true emergency, it can be hard to get fuel deliveries for diesel generators. However, I found that in many areas the natural gas pressure depends on a functioning electrical power grid to keep the pump stations running - so I'd go with diesel power and make sure I had a contract in place that guaranteed fuel delivery even in case every generator owner in town was screaming for diesel.
I wouldn't mess with small gas powered generators - they aren't reliable enough to be worth it.
And finally, whatever you get, make sure you have a process in place that tests the functionality, and a way to make sure that if the tests fail that in is obvious and can get fixed. I can't tell you how many times I have seen backup systems fail, and as it turned out it had been failing weekly tests for a month previously, but the e-mail account that notification went to (or cell-phone number, or whatever) was no longer monitored. Embarrassing.
You are right. Conduit is key. There is no way you can realistically future-proof you're wiring.
You can, however, make paths so that when you decide you need cat"x", coax, speaker wire, fiber, or whatever, you can run it without getting out a saw, spackle, and a putty knife.
If you are on this site, you'd rather run cable than patch drywall, eh?
Correct me if I am wrong, but isn't the Jawbone a binaural (either ear, but not both) headset? It looks high-tech, and no doubt it is great for conversation, but mono doesn't make it for games.
I have a little over 20 years experience in telecom and network operations. This is how we do it:
1.) We don't do service contracts - they are way too pricey. Instead we defined common spares, hired people who knew how to troubleshoot, and did a good job of communicating who to get in touch with to fix and test each piece of gear.
2.) We are anal about using as many cookie-cutter solutions as possible. Keep them similarly configured, and you'll only need enough spares so that it is geographically feasible to get in a car and drive a part to the site in what you define as a reasonable time.
3.) Some stuff is so critical that just having common spares is not enough. Buying a second complete box to collect dust doesn't seem to work as well as you'd think it would. Someone always seems to be borrowing something from it, or you can't find it, or it didn't get the latest patch which is now critical, etc. Hot-standby, or even better, load-sharing, seems to work better. Make sure that in your N+1 configurations you are very good at know what N equals at peak times.
4.) We buy enough stuff from at least one local vendor so that if the worst happens, we can get in touch with someone who will open their warehouse on a Sunday, grab the part we need, and drive it over. That may mean you pay a little more for some of your equipment, but you still save money over service contracts.
5.) We practice changing stuff out, restoring backups, getting into our data center at 0200 when the security guard is off somewhere sleeping, etc. Our team actually comes up with tons of crazy scenarios. Then, because the team knows that we are respected and valued, those ideas get to management and planned for.
6.) We spend a ton of time documenting how well all this works, so that some new VP doesn't come along and say, "gee, look at all the personnel and CapEx in NetOps, lets outsource."
Slashdot Mirror
you mean the way we have this terrible problem with illegal importation to avoid heavy taxes on, say, cigarettes?
Unless your servers themselves are redundant, you'd be better off with one large UPS with an external battery cage/frame. You can often find those for sale used, but you will almost always need to replace any batteries that come with them. Buy units that use commodity batteries - you can shop around for price among battery specialty shops - often there are substantial savings available. By having an external battery box, you can add battery strings in the future to increase backup time as needed. Having more than one string (if it's wired correctly) also means you can take one string off-line for testing but still have some backup. There are some bigger units that are rack-mountable if this is in a CoLoc, but I think they offer less bang/buck than other units I've seen.
The MTTF of the bigger UPS systems is typically longer than the individual smaller UPS units (not to mention the the effective MTTF of the smaller units is reduced if any one of them failing brings down your whole application), and the bigger ones usually have much better ways to do maintenance on them without taking your AC down (such as bypass switches, which could be available for smaller systems but would have to be wired for each one, which doesn't ever happen).
Next, if you buy a system that is fairly common, you should plan (by leaving space, etc.) to buy another one just like it some day. Then you can do a "Red/Blue" power setup, where all of your key gear has dual power supplies, with one plugged into each of the different UPS systems.
Eventually, batteries run out. And eventually, you will go down long enough that some VIP will recommend buying a generator. Generators are also best purchased used. I used to like the idea of natural gas powered generators - in a true emergency, it can be hard to get fuel deliveries for diesel generators. However, I found that in many areas the natural gas pressure depends on a functioning electrical power grid to keep the pump stations running - so I'd go with diesel power and make sure I had a contract in place that guaranteed fuel delivery even in case every generator owner in town was screaming for diesel.
I wouldn't mess with small gas powered generators - they aren't reliable enough to be worth it.
And finally, whatever you get, make sure you have a process in place that tests the functionality, and a way to make sure that if the tests fail that in is obvious and can get fixed. I can't tell you how many times I have seen backup systems fail, and as it turned out it had been failing weekly tests for a month previously, but the e-mail account that notification went to (or cell-phone number, or whatever) was no longer monitored. Embarrassing.
You are right. Conduit is key. There is no way you can realistically future-proof you're wiring.
You can, however, make paths so that when you decide you need cat"x", coax, speaker wire, fiber, or whatever, you can run it without getting out a saw, spackle, and a putty knife.
If you are on this site, you'd rather run cable than patch drywall, eh?
~T
Correct me if I am wrong, but isn't the Jawbone a binaural (either ear, but not both) headset? It looks high-tech, and no doubt it is great for conversation, but mono doesn't make it for games.
~T
I have a little over 20 years experience in telecom and network operations. This is how we do it:
1.) We don't do service contracts - they are way too pricey. Instead we defined common spares, hired people who knew how to troubleshoot, and did a good job of communicating who to get in touch with to fix and test each piece of gear.
2.) We are anal about using as many cookie-cutter solutions as possible. Keep them similarly configured, and you'll only need enough spares so that it is geographically feasible to get in a car and drive a part to the site in what you define as a reasonable time.
3.) Some stuff is so critical that just having common spares is not enough. Buying a second complete box to collect dust doesn't seem to work as well as you'd think it would. Someone always seems to be borrowing something from it, or you can't find it, or it didn't get the latest patch which is now critical, etc. Hot-standby, or even better, load-sharing, seems to work better. Make sure that in your N+1 configurations you are very good at know what N equals at peak times.
4.) We buy enough stuff from at least one local vendor so that if the worst happens, we can get in touch with someone who will open their warehouse on a Sunday, grab the part we need, and drive it over. That may mean you pay a little more for some of your equipment, but you still save money over service contracts.
5.) We practice changing stuff out, restoring backups, getting into our data center at 0200 when the security guard is off somewhere sleeping, etc. Our team actually comes up with tons of crazy scenarios. Then, because the team knows that we are respected and valued, those ideas get to management and planned for.
6.) We spend a ton of time documenting how well all this works, so that some new VP doesn't come along and say, "gee, look at all the personnel and CapEx in NetOps, lets outsource."
~Thom