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
It would very useful to below or similar feature to track restore task
medusa restore status - checks status of the current restore, provide estimate of time to completion and files download and restores per node
medusa restore stop/pause/restart
medusa restore verify - verifies restore data against a source cluster and/or aganist files stored in s3/gcs
┆Issue is synchronized with this Jira Story by Unito
┆Issue Number: MED-16
The text was updated successfully, but these errors were encountered:
I understand where you're coming from. It's really hard (if not impossible) to monitor the restore process. Sadly, thanks to how Medusa is designed, this is not easy to add. We could somehow wire it to BackupMan, or add it to the gRPC service mode. Other option would be to expose this via monitoring.
So yes, it'd be very nice to have, but we need to see if we can squeeze this in alongside other obligations of ours.
I understand where you're coming from. It's really hard (if not impossible) to monitor the restore process. Sadly, thanks to how Medusa is designed, this is not easy to add. We could somehow wire it to BackupMan, or add it to the gRPC service mode. Other option would be to expose this via monitoring.
So yes, it'd be very nice to have, but we need to see if we can squeeze this in alongside other obligations of ours.
Can some please provide me manual instruction to update cassdc , remove RESTORE_KEY
Project board link
It would very useful to below or similar feature to track restore task
medusa restore status - checks status of the current restore, provide estimate of time to completion and files download and restores per node
medusa restore stop/pause/restart
medusa restore verify - verifies restore data against a source cluster and/or aganist files stored in s3/gcs
┆Issue is synchronized with this Jira Story by Unito
┆Issue Number: MED-16
The text was updated successfully, but these errors were encountered: