Before migrating to Redis Cloud, you should evaluate the migration and consider the best option. We will describe three scenarios.
If you can tolerate a flush of all your Redis data, there’s no need to migrate the data at all. You can point your application to a new Redis Cloud database by configuring your client libraries and start working with a fresh, empty database. This can be a valid option if you use Redis as a cache and can restart without data. However, slow performance may impact your service while data is rehydrated, especially if Redis is used as a cache.
Pros:
Cons:
If you use Redis for more than caching, such as session storage, you can't afford data loss or performance issues from a full data flush. For this, a durable persistence option is available. Next, consider if you can handle downtime, which might only last a few minutes, depending on the time needed to export and import your Redis data. If the downtime is acceptable, we recommend offline data migration. It's straightforward but will cause downtime during the data transfer from the source database to Redis Cloud.
Pros:
Cons:
Live data migration can be done without downtime or data loss, but it is more complex and requires careful consideration. This method uses an external tool called RIOT, which was developed by Redis experts. The documentation provides guidance, and expert support is available if needed.
Pros:
Cons:
Once you determine which migration strategy to use, click on one of the links below to learn how to migrate your data.
