WHY DB RESTORE
With DB Restore there is no need for agent installation.
You do not have to set up any servers or software manually. All of that is done by us and our automation. The two simple steps that our users need to take are:
adding the source location and the restore type (run either on-demand or with a fixed schedule),
launching a new CloudFormation template that will take care of server and software setup, configuration, and restore.
We require minimal access permissions.
Our SaaS model allows us to only ask for minimal permissions to start the migration. These minimal requirements are helping us to verify if a backup file exists when a source is added and to start/stop the target instance to make sure our users are not overspending.
Your native code never runs on private instances.
We use minimal Linux OS and 99% of our tools and scripts are open source.
Your private data is never copied to DB Restore servers.
We run the restore processes on users’ cloud and servers. We do not have access to backing up files on the ‘Target’ instance. This is only possible if our users give us permission by opening firewall ports.
After successful restores, we show our users overall statistics about table names, indexes, the number of rows, but we never do that for the data inside the tables. We don’t even have queries that may accidentally send such data.