As the architect for Imanis Data’s Vertica integration, I’ve helped a number of customers protect critical business data stored in Vertica. I’ve noticed that a number of Imanis Data’s capabilities are highly valued by Vertica customers whose experiences with scripting and other utilities have been disappointing. That’s especially true for the most common use case we see with Vertica backup and recovery. I’d like to point out what Imanis Data offers to simplify that use case.
1. Searchable catalog. Imanis Data includes FastFind, a metadata catalog with a visual search interface that enables intuitive and rapid recovery without your having to know the exact name or version number of the object you want to recover. Previously, script-dependent customers had to know the exact object name and version number and had to explicitly specify those attributes in a command-line interface—a procedure both error prone and time consuming.
2. Flexibility with restoring data. Imanis Data can restore your data to a different cluster size or topology. If, for example, you want to run some QA on your data before working with it, or if you are restoring data for your analytics or development team working on a different Vertica instance, you can easily do such tasks. Customers using scripts find that if their initial production environment has grown or shrunk, or they’ve added nodes since the initial Vertica backup, a restore does not work.
3. Support for different Vertica versions. Imanis Data can back up from a particular Vertica version and restore to a different version.This capability is particularly useful to a company that has upgraded in the interim between a backup and a restore. Customers not using Imanis Data must restore back to the Vertica version from which they backed up, even at the minor version number. For example, if they originally backed up 7.0.2-3 but then upgraded to 7.0.2-5, they cannot recover to the new version. Furthermore, when non-Imanis Data customers upgrade to the latest Vertica version (7.2.x), they must do another full backup of data in 7.2.x in order to begin recovery. Thus, they risk a data loss between the time they upgrade and the first time after upgrading they back up their data.
4. Agnostic to production cluster changes. Imanis Data remains transparent to changes to IP addresses or node names associated with the Vertica cluster. Typically, scripts or utilities must explicitly list such associations and so require human intervention if those environments change.
The preceding capabilities are specific to Vertica backup and recovery. I haven’t discussed how Imanis Data supports test data management, works with multiple data environments from a ‘single pane of glass,’ or optimizes storage infrastructure through a combination of content-aware deduplication, compression, and erasure coding. I encourage you to explore our solutions for Vertica backup and recovery and discover how clients around the world are using Imanis Data to enable “always on” data.