Importing Backup Files from Redis
Scenario
Migrate backup data between different DCS Redis instances in the same region. The source instance type must be master/standby, read/write splitting, or cluster.
Simply back up your Redis data, create a migration task on the DCS console, and then import the source backup data to a DCS Redis instance.
Prerequisites
A target DCS Redis instance has been created in the same region as the source Redis. The source instance has data written and has been backed up.
Step 2: Prepare the Target DCS Redis Instance
- If a DCS Redis instance is not available, create one first. For details, see Buying a DCS Redis Instance.
- If you already have a DCS Redis instance, you do not need to create one again, but you need to clear the instance data before the migration. For details, see Clearing DCS Instance Data.
If the instance data is not cleared before the migration and the source and target instances contain the same key, the key in the target instance will be overwritten by the key in the source instance after the migration.
Step 3: Create a Migration Task
- Log in to the DCS console.
- In the navigation pane, choose Data Migration. The migration task list is displayed.
- Click Create Backup Import Task.
- Enter the task name and description.
- For source Redis, set Data Source to Redis.
- For Source Redis Instance, select the instance prepared in Step 1: Obtain the Source Instance Name.
- Select the backup task whose data is to be migrated.
- For Target Redis Instance, select the DCS Redis instance prepared in Step 2: Prepare the Target DCS Redis Instance.
- If the target Redis instance has a password, enter the password and click Test Connection to check whether the password is correct. If the instance is not password-protected, click Test Connection directly.
- Click Next.
- Confirm the migration task details and click Submit.
Go back to the data migration task list. After the migration is successful, the task status changes to Successful.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.