Skip to main content

I was really surprised the that JDS does not have auto failover. I was considering setting up a few of them in my environment and but now I'm not sure if I should use JDS or just setup an HTTP/S server as that has failover functionality. I don't expect it to go down, but in such a large environment as mine, I'd like the reliability of failover.

My other thought is if JDS is a web tool (apache), should I talk to my web team about some type of load balancer/failover from that angle and see what they suggest.

What are other people doing? Using JDS and just dealing if the server goes down? Or using other distribution methods?

Were still using HTTP from an AFP share on our Mac servers.

We need failover, load balancing & scheduling of replication.. Which is why we've not made the move.

Why exactly are my thoughts, I think it may appeal to some but personally I'm with Ben on that. When dealing globally failover, load balancing and scheduled replication is a must

We're running vanilla JDS', but are working on setting them up with AnyCast IP Addresses, so if one goes down the client will redirect to a nearby JDS. We also have an Amazon CloudFront-based CDS, so if I know a region is going to loose it's JDS I can redirect clients to the CDS for a time. Not perfect, but it works.

@kilodelta what a great idea :)

For me, the big plus for JDS is its replication and throttling capabilities as well as its stupid simple setup on OS X and Linux.

In my old environment, I had 12 global sites with WAN links back to our central office. My network folks jumped all over me when I'd copy something like an Adobe Creative Suite package across the WAN to my AFP/SMB distribution points. There's goes the bandwidth!

While it would have certainly taken a while, I could have used the throttling capabilities of JDS to distribute my packages across our WAN in a friendlier manner.

A JDS distirbution point is not for everyone. I still recommend a regular AFP or SMB file share for most customers I support. But it certainly has its place in a dispersed network.

Terms & ConditionsCookie settingsAccessibility statement