Radar42 for Higher Education

Welcome to Radar42 

You are here because you are a University or College and you have an on-premise CrashPlan installation that your internal IT department maintains and you have at least one of the following challenges: 

  1. You have to generate and supply timely usage reports to the various department heads of the constituents of your user base. 
  2. You have a large user base split across multiple CrashPlan Servers and you wish you had a "single pane of glass" to get a picture of the overall health of the systems and the collective user base. 
  3. You have a significant number of end users that are depending upon the system to continue working in "background" mode and you wish to maintain their ability to effectively restore their backups at a moment's notice.
If one of these problems applies to you then please take a moment to read the following and see exactly how Radar42 addresses all of the above challenges (and more).

When we talk backups not everyone stops to connect the dots that the only reason a backup actually exists is to facilitate a complete and accurate restoration of the data that has been chosen to be backed up. In a timely fashion no less. It does not matter that terabytes of data reside on the backup server if yesterday's finalized thesis can not be restored after a laptop gets bathed in scotch and cola during the requisite thesis completion celebration. 

Backups should remain invisible, be completely automatic, and since you have chosen to implement a CrashPlan based service for the most part they are. You're on CrashPlan precisely because you've done your homework! That invisible, background automation is at the very core of the promise of Code 42's CrashPlan platform. Completely automated operations with little or nothing for you, the IT staff or your users to worry about.  

And CrashPlan almost delivers just that. 

Extensive research over the past decade has shown that all backup engines, not just CrashPlan, are plagued by some very specific usage patterns that trick the server, it's admins and it's user base into thinking most things are still humming along nicely, yet the ability to actually restore a backup has nonetheless been compromised. 

Some of these conditions are, of course, related to human factors and some are just side effects of the interplay of complex technology and systems. 

Here are the known patterns we have already identified: 

  1. No Recent Check In
  2. No Active Destinations 
  3. Destination Stalled
  4. Pattern of Low Completion
  5. Zero Files Selected 
  6. Archive Growth Flat-lining 
  7. Significant shift in data being backed up 
  8. Reduced Data-set from Source  
We have also documented precisely what do to in each case to facilitate an easy path to restore-ability recovery. (If you wish to see our cliff notes then just ask and we'll be happy to share them with you.) 

Pop Quiz! 

Can you tell what state each of your users is presently in at this very moment? 

Radar42 can! 

On a typical server we audit we find the following rough averages: 

  • No Recent Check In
    • 20 to 30 %
  • No Active Destinations
    • 2 - 5% 
  • Destination Stalled
    • >1%
  • Pattern of Low Completion
    • 20 to 40%
  • Zero Files Selected
    • 3 to 5% 
  • Archive Growth Flat-lining
    • 3 to 5% 
  • Significant shift in data being backed up
    •  >1%
  • Reduced Data-set from Source 
    • 4 to 5%
  • All Clear 
    • Typically about 60 to 70%
That begs the question what would your server(s) show if they were audited today? 

You might be surprised!

We believe in what we do so much that you are welcome to find out the exact answer to that question right now -- on our dime no less! (no credit card or long term commitment required) 

To take us up on that offer please go to this link: Radar42 Free Trial and authorize our servers to access https://www.crashplan.com/apidocviewer/the API that is already built into each CrashPlan server for precisely this reason.

If you would like continued access to our reports and our single pane of glass dashboard overview then of course you are welcome to stay for as long as you like. Here is the pricing model we currently use: Radar42 Pricing although you are welcome to discuss with us any extenuating circumstances that require specific deployments, e.g.: data must reside in a certain country or region for example or even an on-site appliance.

How does Radar42 work?


We take a reading via your CrashPlan server's API and we record the data on an hourly basis. As we've got extensive experience with this dataset we've developed proprietary ways to compress those readings keeping our long term operating costs down. Savings we can, and do, pass along to you.

With that collection of data we then analyse it for the above patterns and record the current status of each and every device. Those readings can be viewed in the portal right down to the individual device or as aggregates at each level: 

  • Users 
  • Orgs
  • Servers

Remember those Monthly Reports we spoke of earlier?

Since we already have all this data archived, then as each month end (or other definable period) comes long, we simply roll up that data, based on our highly configurable price plans, to slice and dice it's presentation any which way you so choose. 

Interested in Average Selected Bytes? No problem. Concerned about Highest Archive Size? Easy. How many files selected? Percentage backed up? 

Just about any metric can be rolled into a custom pricing plan for an instant, accurate, personalized reporting process triggered at the time of your choosing each month (or alternate defined period). 
Have questions? 

Please feel free to contact us and let us know what questions or concerns you have using our Contact Us page

Radar42 get started today with your  Radar42 Free Trial and start sleeping better tomorrow night!