When a Grid backup, aka snapshot, is restored, you are replacing the entire database on the GM. This means all data AND settings are reverted to what was in the backup. Once the GM restarts with the “old” settings and data, ALL members will get a new snapshot of the data and configuration and they will restart as well.

The restart happens because all information, specifically settings, can change along with the restored backup file. All changes that were made between when the backup was taken and when the restore is done are lost. This means all data (leases, DNS updates, discovery data, etc) as well as any modifications to member settings (adding members, removing members, changing IPs, configuring services, etc).

Generally, you should attempt to resolve the issue with the current database rather than do a restore. A restore should be your last line of defense to resolve an issue. Exceptions are when you have a lab and you want to restore data from the production Grid for testing purposes OR when you are testing upgrades in a lab or something similar. Production restores should only be done after you have opened a ticket and worked to resolve your issue with support.