Supports global file recovery and rapid data versioning across 80 nodesWhen we implemented CTERA Enterprise File Services Platform early on, and we've been on the platform for three years, we have three different cloud portals. We have an EU portal, we have an Americas portal, and we have an APAC portal. It would be nice if we could combine that into one portal just for that global single pane of glass look. We've talked with them about that and they say it's challenging just because of some of the structure, but that would be something nice if we could get that. I integrated with Varonis, and because CTERA Enterprise File Services Platform didn't have initially a working relationship with that vendor, it would have been nice had that pre-existed us saying we need this. But that wasn't totally CTERA's fault. There was a lot of challenge working with the vendor to build out that interface. A single pane of glass for CTERA Enterprise File Services Platform would be beneficial. Everything else works fairly well. We've never had a point where we couldn't get to something that caused us to have a serious outage, and that to me is the mark of a good software package. It's never really caused us serious issues. We have our issues, that's true, and every software package does. However, we've always been able to meet the needs of the business, and we drive hard on security, stability, and scalability. From the scalability standpoint, that's one of the most important things to us. We're on their capacity-based licensing, so if I need to ramp up another CTERA Enterprise File Services Platform NAS, if we have an M&A, I can easily and quickly spin up another NAS and start doing that data transition fairly quickly. The biggest maintenance issue with CTERA Enterprise File Services Platform is firmware upgrades. We've done a lot of transition from hardware solution to virtualized infrastructure in order to minimize that hardware lifecycle portion of it. We have to upgrade the firmware and sometimes that can be challenging in the nature of business of our size with 80 CTERA Enterprise File Services Platform nodes around the globe. The issue we've had with CTERA Enterprise File Services Platform happened recently in a firmware upgrade where there was a major database back-end upgrade and that took some time. For our smaller sites, it would be an hour or two, and I can build that into a fairly easy change window. But in our larger sites where we may have hundreds of terabytes of data, that database update process took maybe a day or a day and a half. That becomes more challenging, especially in a manufacturing environment where people are wanting to access configuration files. We had to pin the data locally because the data would be available on the local edge filer, but the cloud sync, while it was updating the database, the cloud files weren't available. That would be the other thing I'd like to see an improvement on: some way to do those database upgrades either in a more segmented fashion or in some type of offline environment. I understand the logistics behind that sounds easy, but I'm sure it's not.
