Reasons that could trigger automated system checkpoints are highlighted below:
- License expiration of a feature
- Disabling a feature with the no feature command
- Removing an instance of a Layer 3 protocol
The system-generated checkpoint name convention has the format system-fm-feature. To help illustrate this automated feature we attempted to disable the VRRP feature on our Nexus 5000 therefore triggering the system to create a checkpoint. First we confirm the VRRP feature is enabled by issuing the show feature | include vrrp command then disable it and then verify it has been disabled:

Notice that the system now shows a second checkpoint system-fm-vrrp which did not previously exist. This second checkpoint was created automatically by the Nexus as soon as we disabled the vrrp feature.
Reference:
https://www.firewall.cx/cisco-technical-knowledgebase/cisco-data-center/1202-cisco-nexus- checkpoint-rollback-feature.html