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
Lets say a PMM server has a custom retention window of 180 days and a backup is taken.
Pick your disaster but you want/need to restore the data to a new PMM server (fresh docker image).
When you copy the backup artifact to the new server and run the took in restore mode, any clickhouse data older than the default 30 days will be dropped.
the workaround for now is to run the restore a second time but this is a pain given 180 days retention can mean large backup artifacts.
One potential fix is to change the order of restoration so that grafana is first updated so that QAN and Clickhouse are made aware of the increased retention window and then start the clickhouse restore. Another possiblity is to cherry pick out the setting for retention and restore that first...not sure which is better or if there's a 3rd option.
The text was updated successfully, but these errors were encountered:
Lets say a PMM server has a custom retention window of 180 days and a backup is taken.
Pick your disaster but you want/need to restore the data to a new PMM server (fresh docker image).
When you copy the backup artifact to the new server and run the took in restore mode, any clickhouse data older than the default 30 days will be dropped.
the workaround for now is to run the restore a second time but this is a pain given 180 days retention can mean large backup artifacts.
One potential fix is to change the order of restoration so that grafana is first updated so that QAN and Clickhouse are made aware of the increased retention window and then start the clickhouse restore. Another possiblity is to cherry pick out the setting for retention and restore that first...not sure which is better or if there's a 3rd option.
The text was updated successfully, but these errors were encountered: