This guide will help you migrate your data from a regional Upstash Redis database to a global database. If your database is Upstash Regional, we strongly recommend you to migrate to Upstash Redis Global. Our Regional Redis databases are legacy and deprecated.Documentation Index
Fetch the complete documentation index at: https://upstash.com/docs/llms.txt
Use this file to discover all available pages before exploring further.
Why Migrate?
- New infrastructure, more modern and more secure
- Upstash Global is SOC-2 (included with Prod pack) and HIPAA (included with Enterprise) compatible
- Enhanced feature set: New features are only made available on Upstash Global
- Ability to add/remove read regions on the go
- Better performance as per our benchmarks
Prerequisites
Before starting the migration, make sure you have:- An existing regional Upstash Redis database (source)
- A new global Upstash Redis database (destination)
- Access to both databases’ credentials (connection strings, passwords)
Migration Process
You can migrate your data without leaving Upstash Console:-
Create a backup of your regional database:
- Go to your regional database details page
- Navigate to the
Backupstab - Click the
Backupbutton - Provide a unique name for your backup
- Wait for the backup process to complete
During a backup operation, certain administrative operations will be temporarily unavailable: Backup operations, database config changes, plan and region setup, transferring database. Regular Redis commands (GET, SET, etc.) are not blocked and continue to work normally. -
Restore the backup to your global database:
- Go to your new global database’s details page
- Navigate to the
Backupstab - Click
Restore... - Select your regional database as the source
- Select the backup you created
- Click
Start Restore
Verification
After migration, verify your data:- Compare key counts in both databases
- Sample test some keys to ensure data integrity
Post-Migration Steps
- Update your application configuration to use the new Global database URL
- Test your application thoroughly with the new database
- Monitor performance and consistency across regions
- Keep the regional database as backup for a few days
- Once verified, you can safely delete the regional database