How Do I Find the Best Local Colo for Me?
-
@Jason That is a good point. I do use Amazon S3 and Glacier and am looking into Veeam Cloudconnect.
-
Are you looking for a hot site or cold site?
-
@anonymous Warm(?) I would kill two birds and have an ADDC there, as well as some minor things, depending on latency and also replicate backups from VMs, both ways.
-
Why look local? There are reasons for doing this but often people jump to local without really thinking through the business reasoning.
We've colo'd for a long time and only ever used semi-local. We use Toronto and are based in NY. We get better speeds, prices and services in Toronto than we can get in most, if not all of, NY. It's worth not just not being local but being in another country, the difference is so big! And we even have to pay customs to have servers there too!!
LA might easily have good offerings for you, but I would evaluate carefully if "local" adds value, loses value (like for DR) or is irrelevant. Typically it is irrelevant and should just be ignored as a factor. If you are doing things that involve you physically going to the colo facility, you aren't doing it right
-
Yeah as Scott and Jason have said, a local colo is generally bad practice.
Look to store the DR in a separate state or country, (or both) so if something goes belly up in one location, you have the other as a backup.
-
I'm in the same area as @wrx7m
2 questions:
- What if you want the local co-lo as a "hot" site
- For those that have co-lo in other geographical area's, do you own the gear or lease from the colo provider
-
@scottalanmiller said:
Why look local? There are reasons for doing this but often people jump to local without really thinking through the business reasoning.
We've colo'd for a long time and only ever used semi-local. We use Toronto and are based in NY. We get better speeds, prices and services in Toronto than we can get in most, if not all of, NY. It's worth not just not being local but being in another country, the difference is so big! And we even have to pay customs to have servers there too!!
LA might easily have good offerings for you, but I would evaluate carefully if "local" adds value, loses value (like for DR) or is irrelevant. Typically it is irrelevant and should just be ignored as a factor. If you are doing things that involve you physically going to the colo facility, you aren't doing it right
To be clear, Toronto is only 2.5 hours away, so yeah it's in another country, etc., but it's not that far away in reality.
-
@art_of_shred said:
To be clear, Toronto is only 2.5 hours away, so yeah it's in another country, etc., but it's not that far away in reality.
Until you get to customs..... HAHA
-
@art_of_shred said:
To be clear, Toronto is only 2.5 hours away, so yeah it's in another country, etc., but it's not that far away in reality.
For us on the West coast, Toronto is in another galaxy..
-
@FATeknollogee said:
@art_of_shred said:
To be clear, Toronto is only 2.5 hours away, so yeah it's in another country, etc., but it's not that far away in reality.
For us on the West coast, Toronto is in another galaxy..
The point wasn't for you to use Toronto, but to consider other options.
-
@Dashrender said:
The point wasn't for you to use Toronto, but to consider other options.
I realize that, hence my use of the "smiley"
-
@FATeknollogee said:
I'm in the same area as @wrx7m
2 questions:
- What if you want the local co-lo as a "hot" site
- For those that have co-lo in other geographical area's, do you own the gear or lease from the colo provider
Check out Colocation America, I've not used them but they have a lot of offerings.
-
If they have a datacenter in the location you choose, QTS has been amazing for us. Highly recommended, top quality company, great facilities and service.
-
@FATeknollogee said:
- For those that have co-lo in other geographical area's, do you own the gear or lease from the colo provider
We own everything. I think the Palo Alto's might have been a Lease to own program though (through palo alto, not the Colo).
-
@FATeknollogee said:
I'm in the same area as @wrx7m
2 questions:
- What if you want the local co-lo as a "hot" site
- For those that have co-lo in other geographical area's, do you own the gear or lease from the colo provider
- In the case of NTG, we own our own gear and just rent space at the DC. Very rarely do you have a case when you actually need to put hands on the physical equipment.
-
@art_of_shred said:
@FATeknollogee said:
I'm in the same area as @wrx7m
2 questions:
- What if you want the local co-lo as a "hot" site
- For those that have co-lo in other geographical area's, do you own the gear or lease from the colo provider
- In the case of NTG, we own our own gear and just rent space at the DC. Very rarely do you have a case when you actually need to put hands on the physical equipment.
We have out of band management plus dial modems on routers (protected) to console in if needed.
-
@FATeknollogee said:
- For those that have co-lo in other geographical area's, do you own the gear or lease from the colo provider
We don't normally call it colo if you lease the gear. Rackspace does that kind of thing, rarely makes sense. When going colo, 90% of the time at least you want to own all of the gear. If you aren't going to own the gear, then you almost certainly should be looking at cloud computing instead.
-
@Jason said:
@art_of_shred said:
@FATeknollogee said:
I'm in the same area as @wrx7m
2 questions:
- What if you want the local co-lo as a "hot" site
- For those that have co-lo in other geographical area's, do you own the gear or lease from the colo provider
- In the case of NTG, we own our own gear and just rent space at the DC. Very rarely do you have a case when you actually need to put hands on the physical equipment.
We have out of band management plus dial modems on routers (protected) to console in if needed.
Same here. ILO, DRAC, IPMI, etc.
-
@FATeknollogee said:
- What if you want the local co-lo as a "hot" site
Then you don't want it around the world as latency comes into play, but normally you would at least want it in another city if not state. For you, Fremont might make sense, or Vegas, for example. Far, but not crazy far.
-
If you are doing colo for your primary workload (live production) then you typically want it close-ish to you. Close enough to get latency as low as reasonable. But local isn't important at all unless you are talking Wall St. trading systems. You could be a few states away. If you are American, this normally means "your side of the Mississippi" with places like Texas, Chicago, Iowi and Missouri being good enough for either coast, which is why they are popular datacenter locations.
