Use a full checkpoint to restore the entire configuration repository back to the state it was in at the time the full checkpoint was made.
Privileges for managing repository checkpoints differ, depending on the administrative role of the user. Roles include monitor, operator, configurator, and administrator. If you are a user with either a monitor or an operator role, you can only view the repository checkpoint information. If you are a user with either a configurator or an administrator role, you have all configuration privileges for repository checkpoints.
Ensure that you have an adequate number of open file descriptors
available. The default number of open files setting is 2000, which is typically
sufficient for most applications. If the value set for this parameter is too
low, errors might occur when opening files or establishing connections. Because
this value limits the number of file descriptors that a server process might
open, a value that is too low prevents optimum performance. See Tuning operating systems for more information.
When you restore a checkpoint, save conflicts will occur if you have uncommitted changes in your workspace. The checkpoint gets restored, but the uncommitted changes are flagged as a save conflict should you attempt to save them. Also, if more than one user is working on configuration changes to the repository through the administrative console or otherwise, then other users with uncommitted changes will get save conflicts as well if one user performs a checkpoint restoration.