co-location trap???

Dev Shed Forums Sponsor:

February 19th, 2002, 08:22 AM

pentium5

Contributing User

Join Date: Dec 2001

Location: entlegen

Posts: 442

Time spent in forums: < 1 sec
Reputation Power: 12

co-location trap???

what should we look into very careful in co-location?
no experience with co-location.

thanks!

__________________
regards,

wish to use AT 89c51 single chip computer to do remote sensing and send the data back from woods to office via nokie 3330 and internet. HOW?
first I must revise C program thro' example, what's next?

February 19th, 2002, 08:40 AM

slackdaddy

Linux Pimpin'

Join Date: Jan 2002

Location: Kansas City

Posts: 15

Time spent in forums: < 1 sec
Reputation Power: 0

We went with AT&T for a co location solution. We used Foundry server Irons switches for transparent failover (Radware also makes a product). We have a frame connection from our local data center to AT&Ts and we user rsync to update the remote machines. We also looked @ sungard and sprint but AT&T had the better deal. I think you should first identify what your CO LO requirements are ( i.e geographical diversity, transparent failover) then decide on who best fits your needs.

Viewing: Dev Shed Forums > Operating Systems > Linux Help > co-location trap???

« Previous Thread | Next Thread »

Developer Shed Advertisers and Affiliates

Thread Tools	Search this Thread
Email this Page	Search this Thread: Advanced Search
Display Modes	Rate This Thread
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode	Rate This Thread:

Posting Rules
You may not post new threads You may not post replies You may not post attachments You may not edit your posts vB code is On Smilies are On [IMG] code is On HTML code is Off

View Your Warnings | New Posts | Latest News | Latest Threads | Shoutbox

Forum Jump