Restorepoint
Restorepoint is a Disaster Recovery and Secure Configuration Management appliance for network devices such as routers, switches, proxies, and firewalls. Restorepoint can automatically retrieve your network device configurations, detect changes and compliance violations, and report these automatically to network administrators. In this Powerhour session we will share with you how to add devices into Restorepoint, why having backups collected is useful in an autonomic IT environment, and how to leverage the SL1 platform in support of key workflows. Additionally, we will present the benefits of Governance, Risk and Compliance (GRC). Within the ScienceLogic Network Change and Configuration Management (NCCM) platform you will be backup over 100 different types of network equipment including firewalls to a central repository. Once the backup is collected then you can track change over time for auditing purposes as well as day to day operational needs to manage effective change control. Integration to the monitoring and automation platform adds layers of value which we will discuss during our session. When your organization is tasked with managing GRC then Restorepoint will apply your rules to assist in real time awareness of compliance. When configuration drift occurs then an alert will be sent to the SL1 platform for execution of automations in support of your defined workflow. For instance if you need to collect the difference of the last two configurations to compare an unplanned change while opening an incident into your IT Service Management (ITSM) product that can be completed so your operations team only need to receive the enhanced information set and begin resolutions steps. Often the best step is to revert the change and of course that’s supported from SL1 to allow for reduction in your Mean Time to Repair (MTTR). At the end of the June PowerHour you will have learned how to add devices into Restorepoint, why having backups collected is valuable and how to leverage the SL1 platform in support of key workflows. Additionally, we will present the benefits of Governance, Risk and Compliance (GRC). While blending into the overall SL1 platforms workflow operational needsAccess to SL1 and RP AMI's to automate AWS Provisioning
We're in the process of developing pipelines to provision and configure all our resources in AWS on a per client basis. Among these resources are the SL1 collector and RP agent. Right now in order to request the AMI for SL1 we need to fill out the form at https://support.sciencelogic.com/s/request-amazon-ami after authenticating via the webpage. Because of the login flow this has proven difficult to pass through the right information to authenticate and access the AMI request form where we can pass the form data to request the AMI on our AWS account. I understand this is probably not a common case, but has anyone come across a way to accomplish anything similar? The best I've been able to do so far is use Selenium to manage a browser logging in and navigating to the form page, but it doesn't lend itself well to the pipelines. For RestorePoint it seems like we still need to submit a case and request the AMI from support. Is there any plans to add this to the same request form for the SL1 AMI's? For now we're alright sticking to the manual effort of requesting AMI's, but it would be nice to be able to click a button and be done with provisioning :).
Configuration Recovery - SL RestorePoint
Hello all, I just had this question posed to our team regarding config recovery. "Do you have any way of retrieving the configs for switches that have been deleted from SLRP please?" Is there a way to retrieve a backup of RestorePoint (and maybe restore to a temp location) from a specific point in time? If anyone has any advice or previous experience with this SL RestorePoint scenario, your input would be greatly appreciated!
This week's updates to the Doc sites at docs.sciencelogic.com
8/29/25 Doc Updates to the release notes site at https://docs.sciencelogic.com/release_notes_html/ Added release notes forRestorepoint 5.6 MR 20250827, which addresses issues with the command scheduler for multi-device command schedules, addresses the Device Details scrolling issues; updated the default Regex buffer size to 5%; and migrated the Configure Changes report into the current user interface.Restorepoint 5.6 20250521 Release
Hello - We are pleased to announce that a new release has been pushed to Restorepoint appliances today. This release includes fixes to customer-reported issues, as well as additional updates to the Global Search functionality and the View Configuration page: Addressed an issue that prevented device reports from generating if you applied a filter. (Case: 00511414) Addressed an issue that prevented archive restoration when a new appliance shared the same serial number. (Case: 00512806) Updated the user interface for the Global Search page (Devices > Global Search) to include the RegEx search option and enhance usability. Updated the Global Search page (Devices > Global Search) with an [Export] button that allows you to export your RegEx search results to a .csv file. Modified the Global Search API to include the configuration lines that matched a given RegEx search. Updated the View Configuration pane (Global Search or Devices > Edit Device > Configurations > Configuration) to highlight the results of the newly added RegEx search. It was also updated to display line numbers and the backup name above the displayed configuration contents, and to improve the Wrap checkbox styling. Thank you, Release ManagementWelcome to the Restorepoint Discussion Forum
We would like to welcome you to this forum where you can participate in open collaboration and meaningful discussion about all things Restorepoint. The purpose of this area is to foster collaboration about network configuration backup, recovery, compliance, and change management topics and for you to find solutions. As a community of IT professionals, we're always eager to learn new things and improve our skills. In this forum you can find people with similar ideas and challenges who can help you learn and be inspired. We hope you look forward to participating in these discussions and contributing to the community. Cheers to fostering connections, sharing insights, and driving the future of AIOps together. The ScienceLogic Community TeamRestorepoint 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.
