Rolling back to a restore point
Use the prpcServiceUtils tool to roll back your system to a restore point. For example, if you created a restore point before doing a major system update, and the system update causes a serious problem, you can roll back to the restore point so that your system behaves as it did before the update.
You must have a running Pega Platform instance to use
You can specify which rule and data instances are returned to the previous state:
- System: Roll back every rule and data instance with a history record. This is the default setting.
- User: Roll back rule and data instances modified by a specific user.If any rule was changed by more than one user, you will see an error message and must use the system rollback.
- Application: Roll back rule and data instances in a specific application.
Follow these steps to roll back to a restore point:
Configure the common properties of the
prpcServiceUtils.propertiesfile. The pega.response.type must be JSON.
Property name Value
The URL for the REST service, specified in the following format:
The operator name on the target system with access to REST services.
The password of the specified operator.
The host name of the REST proxy server. Do not use localhost as the host name.
The port for the REST proxy server.
The operator name on the REST proxy server with import and export access.
The password of the REST proxy operator.
The domain of the REST proxy server.
The workstation ID for the REST proxy server.
The REST response type, either
json. The default value is
json. Rollback, restore point, and update access group operations support only
Enter the full path to the temporary directory. Leave this blank to use the default temporary directory. For more information about temporary directories, see Temporary files and temporary files directories .
Configure the scope for the rollback:
rollback.action=UserRollback rollback.userName= MyUserID
By default, the rollback process runs in asynchronous mode. In asynchronous mode, the system queues the job and returns a job ID for each operation. You can later use this job ID to check the status of the rollback operation.
As a best practice, leave the downloadLogToFile parameter with the default value of true to write the log to a file.
Save and close the
Run the prpcServiceUtils.bat or prpcServiceUtils.sh script with the rollback option, for example:
Optional: Pass one or more arguments.
prpcServiceUtils script argument Value
The full path to the
serviceConnection.propertiesfile that includes information for multiple targets.
The thread pool size. Default is 5.
How long the system waits for a response before failing with a time-out error. Default is 300 seconds.
The path to the job IDs file that is generated by the asynchronous operation.
The full path to the properties file, to override the default prpcServiceUtils.properties.