Hi Team, 

In the etcd backup restoration process, 

IN RHOCP 4.12, 4.13 Checking step `Restoring to a previous cluster state` point `4.g` on below doc [1]: 
IN RHOCP 4.14 Checking step `Restoring to a previous cluster state` point `4.k` on below doc [2] :  

[1]https://docs.openshift.com/container-platform/4.12/backup_and_restore/control_plane_backup_and_restore/disaster_recovery/scenario-2-restoring-cluster-state.html#:~:text=If%20the%20/etc/kubernetes/manifests/keepalived.yaml%20file%20exists%2C%20follow%20these%20steps%3A

[2] https://docs.openshift.com/container-platform/4.14/backup_and_restore/control_plane_backup_and_restore/disaster_recovery/scenario-2-restoring-cluster-state.html#dr-scenario-2-restoring-cluster-state_dr-restoring-cluster-state:~:text=If%20the%20/etc/kubernetes/manifests/keepalived.yaml%20file%20exists%2C%20follow%20these%20steps%3A

Need to add a disclaimer in point `4.g` and `4.k` basis RHOCP aforementioned versions ideally this step works when we are deleting the node. When we are not deleting the node this step needs to be skipped.  
    

    4.12, 4.13, 4.14

    Following the step `Restoring to a previous cluster state` point 4.g and 4.k basis RHOCP aforementioned versions  in case node is not removed.

    1.
    2.
    3.
    

 MCP gets degraded and multiple operator got degraded because of keep-alived configuration check.

 Restoration should processed successfully without any issue.