Restorepoint RP 5.6 20250409 Release
Hello, We are pleased to announce the release of Restorepoint RP 5.6 20250409 on April 9, 2025. This release contained the following: The ability for administrators to define a global alert for backup sizes. This allows the administrator to configure a defined size for backups which, if exceeded, sends an email alert to the appliance owner. Various updates to increase the security of the Restorepoint appliances. Thank you, Release ManagementRestorepoint 5.6 03262025 Release
Hello - We are pleased to announce an important update to our Restorepoint appliances. This afternoon, the team pushed out the Restorepoint 5.6 03262025 release to all appliances. This release provides significant enhancements to Domains, allowing you to limit user access based on domain assignment. Domain support has been added to the release as follows: You can now add a Domain ID to device commands, command schedules, reports, report schedules, and device policies. NOTE--If a command is assigned to a command schedule, you cannot delete the command. Likewise, if a report is assigned to a report schedule, you cannot delete the report. You can now add multiple Domain IDs to Commands and Reports. When creating or editing a credential, agent, command, or policy, devices shown in the list are filtered based on the domain to which they belong. If a device command, command schedule, report, report schedule, or device policy is in the global domain, any global domain user with the correct permissions can view or edit it. Users assigned to the global domain with the appropriate permission within the global domain can create or change any element that belongs to more than one domain. Caveats: You cannot delete a label, command, policy, agent, or credential that is assigned to a device. You cannot change the domain of a label, command, policy, agent, or credential when it is assigned to a device which shares that domain. You cannot change the domain of a report when it is assigned to a report schedule which shares that domain. If a user does not have access to the same domain as a report, report schedule, command, command schedule, or policy, the form appears disabled. Additionally, important changes were included for permissions: The following permissions were added to allow for interactions with schedules, such as pausing or postponing schedules, on the Schedules page: View All Schedules Modify All Schedules The following permissions replace View Schedule and Modify Schedule: View Backup Schedule Modify Backup Schedule The following permissions were updated for Schedule groups to allow you to assign one or more domains to a report schedule: View Device Report Schedule Modify Device Report Schedule The following permissions were added to control who can view or change Device Control commands: View Device Command Modify Device Command The Command Device permission is enforced only when controlling or sending a command to a device. The following permissions replace View Rules, Modify Rules, and Apply Rules: View Device Policy Modify Device Policy Apply Device Policy Renamed the Old Report permissions to Legacy Permissions to clarify the permissions interact with the Legacy Reports that reside in the old user interface. You can now filter Device Control > Schedule so command schedules are filtered based on the command's device type. Updated Report Schedules (Reports > Schedules) and Reports (Report > Reports) to be filtered by domain. Thank you, Release ManagementRestorepoint 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 Management
