Disaster recovery has often been used for one-time occasions when a set of data has been corrupted, infected with malware, or accidentally compromised during testing. What if you could consistently use disaster recovery on a regular basis to ensure your data is always secure and performing optimally 24/7? With ionir, you can.
Legacy technologies require you to complete a full recovery of your entire dataset to know whether or not the application can stop, leading to longer wait times. The problem here is that a full restore can take four hours (or more). So once your data is restored, it’s technically outdated by four hours or however long the time to restore takes.
ionir’s data teleport pushes the data directly to the target location alongside global deduplication to make sure:
Legacy technologies require you to do a backup and restore which takes a long time to complete. What’s worse is that you’re stuck at whatever recovery point you have — recovered data can even be a week old.
ionir sets up your data to do a full replication once a day enabling you to frequently test whenever you want, depending on those cycles.
By sending over change blocks once an hour, you can keep remote replications on the remote site, providing you with clones that go back months, all without having to keep the timeline alive.
With a very short window of replication, you can have a long string of recoverable points and gain the ability to test each one of them.
Create a site “B” where the replicated data will be stored.
Teleport 100% of the data to the remote site.
Create replicated recovery points at the remote site, only by sending change law blocks across both sites.
Update the changes that occurred in the last day or since the latest teleport occurred.
Test the data at any specified date and time without the need to recover and/or affect any other data.
