We have two primary use cases. One would be to use it in reaction to a cyber-terror event, particularly ransomware, because Zerto has point-in-time backup. If we find an area that needs to be restored, as long as we figure it out within 24 hours, which is approximately the amount of time we have replicated, we can go back to a point in time. Let's say the files got encrypted at 9:30 AM. We can say restore our 9:29 AM copy of what the data looked like at that point. We have not needed to use that, thankfully, because we've been educating our users very well.
The other case that we would use it for is because we're in a hurricane area. Our particular office is actually in an evacuation area, typically, meaning that we're close enough to the coast that should a hurricane event come through, they generally force us out of the area. What we would do if we needed it, and thankfully we haven't yet, would be to shut down our primary on-prem services to make them a little bit more resistant to water damage. Obviously, if they're not running, they're a little bit less likely to get zapped if there is some water damage. Then we can bring up the copies that we have at our data center and run remotely from that if. It doesn't have a full copy of our entire environment, but it does have a copy of our ERP system, as far as sales are concerned. We wouldn't be able to ship anything, but we could look at orders and help our customers. We could even take orders if we needed to, although we wouldn't be able to process them.
Zerto is a replication solution. It copies our setup which is on-prem to our data center, which is also somewhat local, about 15 miles away. It doesn't really do anything in the cloud other than move data across it. We're not replicating to any cloud-based services like Amazon or Azure. Essentially, we're using it at two on-premises locations: Our primary location, which is what is being replicated, and the replicated copy is being stored at another on-premises location, nearby.