-> Most [actually all the ones we have worked with] co-locs advertise one's servers on a single network block and that has the standard problem of being blacklisted, route flapped and being DoSed against.
The blacklist problem at least is something that you'd face equally at most large tier 1s - and several large providers know enough not to block mail from us.
-> What about LAN problems at a co-loc? -> What about problems with the core routers at the location? -> Fiber cuts? Problems with major upstream providers?
redundancy is the name of the game. tier 1s usually dont go phut because of a single core router, and nor do they have upstreams .. they usually have peers.
the issue is that maintaining high availablity clusters across two network / geographically separate networks and processing tons of mail in real time gets tough. We can, at a pinch, switch large parts of our mail operations to our other clusters elsewhere though.
And these are in addition to the physical problems that can happen at site - like you have mentioned - power, fire, strikes, sabotage.
Which would take out operations at that site and leave our other sites up - so we could bring service back up at an alternate location for at least some time.
suresh
-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g. Take an Oracle 10g class now, and we'll give you the exam FREE. http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
_______________________________________________
linux-india-help mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/linux-india-help
