Sysload Management Server database restore

book

Article ID: 210160

calendar_today

Updated On:

Products

CA Automic Sysload

Issue/Introduction

A human error provokes the removal of many Monitored Objects from the Sysload Management Server database, as a result, end-users can no longer create charts / reports or extract data from these Monitored Objects anymore.

Can Sysload Management Server database be restored to a date before the issue and if so, how should this be done?

Cause

Human error provoked the removal of different objects from Sysload Management Server Database.

Environment

Release : 6.1

Component : SYSLOAD

Subcomponent: Sysload Management Server

Resolution

The Sysload Management Server can either user an internal database SQLITE or an external database MS SQL Server.

Because of that, the steps 2 and 3 will be different depending on that.

The Sysload Management Server Database restore procedure would be:

1. Stop Sysload Management Server

2. Backup current Sysload Management Server Database

3. Restore the Sysload Management Server Database from a previous backup before the issue

4. Start Sysload Management Server Database

 

 

 

Additional Information

For SQLite, the default configuration generates a backup of the Sysload Management Server database daily in the folder daily_backup:

https://techdocs.broadcom.com/us/en/ca-enterprise-software/intelligent-automation/sysload/5_80/Management_Server_12/Management_Server_Configuration.html

 

For MS SQL Server, it is up to the DB Administrators to configure a Backup for the Database.