Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.
Original topic: BR能否支持恢复时指定恢复到哪个数据库
Can BR support specifying which database to restore to when restoring data? Most data recovery scenarios are not full coverage (accidental deletion or misoperation, exceeding GC time). If it can be restored to a specified database, and then quickly recovered by comparing the restored data with the online data, this will greatly improve the efficiency of RTO and be very convenient!
Yes, this kind of scenario is quite common. It is now recommended to recover in another cluster, but it is actually quite difficult to execute because we don’t have that environment.
Just take a look at the new features of 6.5 LTS, they are even better than you imagined.
However, it still only supports the same database name 
This scenario is too common. Has the official responded?
I saw version 6.5 as soon as it came out, and it supports incremental backups, but it doesn’t solve my problem.
It seems that it is not supported at the moment.
Currently, the functionality cannot meet your needs. If you want this feature to have a chance to go online, you can provide your product requirements according to the format below:
Requirement Feedback
Please clearly and accurately describe the problem scenario, required behavior, and background information to help the product team follow up on the requirement in a timely manner.
[Problem Scenario Involved in the Requirement]
[Expected Requirement Behavior]
[Alternative Solutions for the Requirement]
[Background Information]
For example, which users will benefit from it, and some usage scenarios. Any API design, models, or diagrams will be more helpful.
Can this meet your needs? What exactly are you looking for?
It has already been mentioned.
Simply put, the two parameters --source-db and --database in myloader represent the source database and the target database, respectively.
Understood, it’s similar to routing functionality, which is currently not available. You can only achieve this through intermediate steps, such as restoring to one database and then renaming it, or restoring to a new database and then using dumpling and lightning for routing. This feature does seem to be very necessary.
Yes, everyone can make suggestions and ask my cousin to bring them up to the product manager.
|
username: Running
|
username: 
|
username: 
|
username: 
|
username: 
|
username: