We're turning on Redis Import for Compose Redis deployments. Some may say that, by its use as an in-memory data store, Redis doesn't seem like a database that needs an import tool, but we've been finding Compose users who want to bring their Redis data to our platform. They don't just cache data in their Redis, they use it as an active reference store for applications which can be rapidly updated and, thanks to the Redis pubsub options, update clients quickly too.
At Compose, we understand how, with Redis as an essential cog in your operations, you'd want to minimise downtime when migrating. So, for our first offering, we've created a static import tool which will import your data from a remote Redis installation into your Compose Redis deployment. You'll find the controls in the Compose Redis console under Settings.
Before you import a remote database, be aware that this import is going to make your Compose deployment identical to the remote database and it starts that process by clearing out your current Redis data in your deployment. The import process does not merge the content of the two Redis databases involved. If you have any data of value in your Compose Redis database then we recommend you create a new Redis deployment and import into that.
What you need to import a remote Redis database is a Redis URL for it, and to have that means the remote Redis needs to be accessible on the internet. If you're Redis is behind a firewall, you'll need to make the appropriate arrangements to make it accessible to your Compose Redis deployment. Your Redis URL includes the hostname and port that the database resides on and the password for the database.
Once you've assembled your redis URL and put it into the field, it's time to press Import.
As the import involves clearing your Compose Redis deployment, we ask you to confirm that this is what you want to do. Click Import again if it is. The import will begin.
A message will appear to signal the start of the import and the console will move to the Jobs screen. Here, you'll see the Redis RemoteDB, Redis Import and Run jobs will run. The firs one prepares for the import, the next does the actual import and the last wraps up and scales up the deployment if needed. It should look like this when done
The scaling only occurs if your imported data is larger than the currently deployed size of your Compose Redis. Do check after importing on the Overview page for the new storage usage to avoid a surprise.
This is the first import option we've added to Redis and it is just part of a development process that is bringing simpler, more reliable ways of moving your data to Compose and our production ready, high availability deployments.