You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
kbcli cluster backup mysql -n mysql --name testbackup --method xtrabackup
kbcli cluster list-backups -n mysql
>
NAME NAMESPACE SOURCE-CLUSTER METHOD STATUS TOTAL-SIZE DURATION CREATE-TIME COMPLETION-TIME EXPIRATION
testbackup mysql mysql xtrabackup Completed 38777361 18s Feb 13,2025 17:37 UTC+0800 Feb 13,2025 17:37 UTC+0800
Restore cluster
kbcli cluster restore myrestore --backup mybackup
restore status
> kbcli cluster list-ops
NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME
myrestore default Restore myrestore Creating -/- Feb 14,2025 11:26 UTC+0800
> kbcli cluster describe-ops myrestore
Spec:
Name: myrestore NameSpace: default Cluster: myrestore Type: Restore
Command: <none>
Status:
Start Time: Feb 14,2025 11:26 UTC+0800
Duration: 4h27m
Status: Creating
Progress: -/-
Conditions:
LAST-TRANSITION-TIME TYPE REASON STATUS MESSAGE
Feb 14,2025 11:26 UTC+0800 WaitForProgressing WaitForProgressing True waitforthe controller to process the OpsRequest: myrestorein Cluster: myrestore
Feb 14,2025 11:26 UTC+0800 Validated ValidateOpsRequestPassed True OpsRequest: myrestore is validated
Feb 14,2025 11:26 UTC+0800 Backup RestoreStarted True Start to restore the Cluster: myrestore
Warning Events: <none>
The text was updated successfully, but these errors were encountered:
Describe the bug
Error recovering cluster to another cluster in a different namespace . The recovery was stuck in the Creating status.
To Reproduce
Steps to reproduce the behavior:
kbcli cluster backup mysql -n mysql --name testbackup --method xtrabackup kbcli cluster list-backups -n mysql > NAME NAMESPACE SOURCE-CLUSTER METHOD STATUS TOTAL-SIZE DURATION CREATE-TIME COMPLETION-TIME EXPIRATION testbackup mysql mysql xtrabackup Completed 38777361 18s Feb 13,2025 17:37 UTC+0800 Feb 13,2025 17:37 UTC+0800
The text was updated successfully, but these errors were encountered: