# Rollback help on Rancher Cluster

**URL:** <https://forums.suse.com/t/rollback-help-on-rancher-cluster/12387>\
**Category:** General\
**Created:** [November 15, 2018, 8:05am UTC](https://forums.suse.com/t/rollback-help-on-rancher-cluster/12387 "2018-11-15T08:05:04Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![vinhlamn](https://avatars.discourse-cdn.com/v4/letter/v/839c29/32.png) [@vinhlamn](https://forums.suse.com/u/vinhlamn)\
**Post date:** [November 15, 2018, 8:05am UTC](https://forums.suse.com/t/rollback-help-on-rancher-cluster/12387/1 "2018-11-15T08:05:04Z")

</div>

Hi fellow members,

I’m testing out a restore procedure ([https://rancher.com/docs/rancher/v2.x/en/backups/restorations/ha-restoration/](https://rancher.com/docs/rancher/v2.x/en/backups/restorations/ha-restoration/)) on my Rancher Cluster B , which uses a database file that was exported from Rancher Cluster A.

After restoring the cluster I’m able to see my kubernetes cluster that was on Cluster A, however it says " This cluster is currently **Unavailable** ; areas that interact directly with it will not be available until the API is ready."

I can see all the pods running by checking kubectl get pods --all-namespaces

Is there additional steps required to bring the cluster up?

Please note the kubernetes cluster is still attached to Rancher Cluster A

Cheers