Describe the issue: In a non-orderly failback scenario (after following Failover after a non-orderly shutdown) when user performs steps "Fail back to the primary storage cluster", it makes previous snapshot schedule at image level obsolete as image resync operation changes rbd image id. So we need to ask users to re-add snapshot schedules at image level if they were added previously. Describe the task you were trying to accomplish: Perform non-orderly failover and failback Suggestions for improvement: MEntioned above Chapter/Section Number and Title: From current 5.x doc - 6.6.7.1. Product Version: 6.x Environment Details: NA Any other versions of this document that also needs this update: 5.x