Restorepoint 5.6 20250312 RPM Agent Release
Hello – We are pleased to announce the release of the Restorepoint 5.6 20250312 RPM Agent. The following issues are addressed in this release: Updated the storage protocols for back connection user passwords to ensure that the agent's back connection user password is encrypted and that only the encrypted variant is stored in the configuration file. Relocated the FullTranscript global setting to the Notifications & Monitoring tab on the Edit Devices page as a new checkbox. When you enable the FullTranscript checkbox, transcripts will not be truncated for that device. NOTE: ScienceLogic recommends only enabling the FullTranscript setting on an as needed basis as keeping it enabled may cause performance issues. Addressed an issue that prevented global administrators from seeing command outputs on domain devices. (Case: 00495158) Thank you, Release ManagementRestorepoint 5.6 20250305 Release
Hello, We're pleased to announce the release of Restorepoint 5.6 20250305. This release is a hotfix that contains the following update: Addresses an issue that prevented Restorepoint appliance backups restoration from restoring included device backup files correctly. Thank you, Release ManagementRestorepoint 20250226 Release
Hello, We are pleased to announce the Restorepoint 20250226 release, which includes the following update: Restorepoint user passwords are now stored as their salted and hashed variants* in the database. Restorepoint no longer stores the passwords in plain text. * Salting a password indicates that a random string of characters has been added to the password, and then the password is hashed, turning the salted password into unreadable ciphertext of fixed length. Thank you, Release ManagementRemediation with Restorepoint (Part I)
The Basics It’s important to understand that remediation options are part of the compliance rule definition, not the policy. That means a single policy can contain rules with different remediation options. To see the remediation options, go to Compliance --> Device Policies, open up a policy, and bring up the rule editor by either creating a new rule or selecting an existing one. You will see the “Remediation” drop-down menu: 1 - Remediation Type "Manual" The first and simplest remediation type is “Manual”. This is simply a text string providing instructions to an operator who is responding to a compliance alert. For example, a simple rule that checks for the existence of a default “public” SNMP community on a Cisco IOS device could have these very simple instructions: When a device is in violation of this rule, the remediation text will be included in the alert that gets generated. Here, in an email alert: 2 - Remediation Type "Automatic" The second remediation type, “Automatic”, lets you specify a series of commands to execute on the device. For example, to enable auto-remediation of our example “No Public SNMP Community” rule, you could run the “no snmp-server community public” IOS command: When a device is in violation of this rule, the specified commands are automatically executed on the device, bringing it back into compliance. 3 - Remediation Type "Command" The final remediation type, “Command”, is similar to “Automatic” except that, instead of entering the commands to run on the device, you can specify a previously saved Device Control script to run. In our example: Here, the "Remove Public SNMP Community" script has previously been saved and contains the same commands we used in the "automatic" example: Since device controls can be created as Lua scripts instead of simple lists of commands, using the “command” remediation type allows for more complex actions. Summary The goal of this article was to introduce the different Remediation options in Restorepoint. Remember: You don't have to add remediation steps to every rule in a policy -- and the ones you do add don't have to be of the same type. Even if you are not ready to enable automatic reconfiguration of devices in your environment, don’t be afraid to add a “manual” Remediation action to your compliance rules. Coming soon, I’ll post a follow-up article about using variables and Lua scripting to improve on the simple remediations we used today.Restorepoint 20241121 Release Notification
We are please to announce that Restorepoint 20241121 has been released with the following updates: Addressed issues in which: the Device Control Action Names were displaying as "Unknown", existing command outputs did not display for users in the Test Rule modal, the "Select All" options on the Device table did not operate when the "Disabled=True" filter was applied, users received an error message when clicking the Test Connection button on any device, restoring appliance backups required additional checks to ensure both their integrity and handling of legacy database dump formats were intact from CentOs 6.8-based appliances to an OL8-based one. Updated the Restorepoint API to enforce specificheaders. Updated the appliance backup process so that users now receive verification messages in conjunction with additional checks of the archive and backups within the archive. Update the API call logs to include user information, such as User ID, Username, and User address.Restorepoint Automation PowerPack v104 is Released
Hello, We are pleased to announce that Restorepoint Automation PowerPack version 104 has been released. This PowerPack contains supporting changes to enhance compatibility with Restorepoint SyncPack version 2.3.0. Restorepoint Automation PowerPack version 104 is supported for SL1 v12.1 or higher, and for PowerFlow version 2.6.0 and higher, and works with the Datacenter Advanced Enrichment Actions PowerPack. Thank you, Release ManagementRestorepoint 20241106 Release notification
We are pleased to announce the Restorepoint 20241106 has been released with the following updates: Users can now disable bulk processes on multiple devices with different protocols. The API is updated so calls on the /logs and /settings endpoints are now logged and syslogged for every API call that comes in. Users are redirected to the correct user security page when they need to update missing details on their account or logging in the first time via an email activation link.Restorepoint 20241023 Release notification
We are pleased to announce the Restorepoint 20241023 has been released with the following updates: Backups that failed when opening directories will now complete successfully and be accessible. A "Selected Only" checkbox was added to the Device Select table to allow only the selected devices to display instead of a full list. Writing appliance archives for FTP, SFTP, CIFS, and SCP storage servers now operates correctly and the archives retained are the newest archives. Device transcripts for backups via agents are no longer being cut short so users can now see any errors from backups that may occur.
