
The platform offers centralized alerting and a structured approach to monitoring backup activity across environments, which can be useful for organizations looking to standardize their backup oversight. Review collected by and hosted on G2.com.
We spent several months attempting to deploy Backup Radar in our environment and integrate it into our Comet backup workflow, and ultimately were not able to get it into a place where it was operationally usable.
The primary challenge for us was the Comet integration. The data being pulled into Backup Radar did not provide the level of detail or accuracy needed for us to confidently monitor backup success and failure states. This created gaps in visibility that made it difficult to rely on the platform for day-to-day operations. In our case, pass/fail reporting and actionable alerting were not at the level we needed for an MSP environment managing multiple endpoints.
During our onboarding and follow-up interactions, we were told that some of these limitations were due to constraints within Comet’s API. However, after further testing and ultimately building our own internal tooling, we were able to confirm that the API is capable of providing the required data. This led us to conclude that the limitation was in how the integration was implemented rather than an external constraint, which created confusion and reduced our confidence in the platform.
We also found that getting to a usable state required more manual effort and workflow adjustments than expected. Instead of simplifying backup monitoring, it introduced additional overhead, and we were not able to establish a streamlined, reliable process for our team.
From a business perspective, the biggest issue was that after a good-faith effort to deploy and test different approaches, we did not have a clear path to adopting the product in a production environment. Without that, it became difficult to justify the ongoing cost.
Overall, the platform may work in environments with simpler backup requirements or different tooling, but in our case it did not align with our workflow or provide the level of visibility we needed. Review collected by and hosted on G2.com.



