Configure LEM appliance to run scheduled backups according to your requirements and preferences.
The Following are definitions and recommendations for the primary LEM backup options:
The procedure for scheduling these backups is the same for each.
It is not possible to merge backup data with live data at this time. Use these backups for data retention and disaster recovery only.
Schedule or run this backup to back up the normalized alert database on your LEM appliance. Since it backs up everything on the database, this backup file grows as your database grows. If you have a separate LEM appliance dedicated to this database, schedule or run this backup on the dedicated database appliance.
Recommended schedule: Run monthly
Schedule or run this backup to back up all of the settings on your LEM appliance. These settings include all user-defined groups, rules, and users. This backup does not back up any alert or log data.
Recommended schedule: Run weekly
Schedule or run this backup to back up the original syslog data on your LEM appliance. This backup is optional since archiveconfig backs up the corresponding alert data.
Recommended schedule: Run monthly, if used
Schedule or run logmarchiveconfig to back up data cores once they rotate. Data cores deleted from the database remain archived in the share folder.
Schedule: Runs automatically every 15 minutes (by manager)
File Name: TriGeoLogMArchive
Mirrors data cores contained on appliance. Archives data cores added to share. In this case, when data cores are deleted from database, so are the archived data cores on the share.
Schedule: Runs automatically every 15 minutes and once a day at midnight (by manager)
File Name: TriGeoLogMBackup
The procedure is the same for scheduling and running each of the LEM appliance backups.
To schedule or run a backup on your LEM appliance:
|1||daily||Perform daily full backup at 6:25AM|
|2||weekly||Perform weekly full backup Sunday at 6:47AM|
|3||monthly||Perform monthly full backup the first of the month at 6:52AM|
|4||never||Unschedule any configured backup|
|5||once||Run a one-time backup|
cmc::cmmprompt, enter the name of the backup you want to schedule or run. Choose from one of the files listed above.
yto confirm your selection.
\\server\share. If your LEM appliance cannot resolve hostnames, use the server's IP address instead.
n, new backup files overwrite any existing backup file with the same name. Otherwise, the script creates a new file for every backup, appending the date to the filename in
ywhen asked. We recommend that you only run archiveconfig and logbackupconfig during off-peak hours, as they can be very resource intensive.
Each time the backups run, your LEM manager displays an alert similar to the following in the default SolarWinds Alerts filter.
Alert Name: InternalInfo
EventInfo: ManagerMonitor Info: Backup Done with backup. InsertionIP: gman Manager: gman DetectionIP: 10.10.10.10 InsertionTime: 10:11:26 Mon Jan 30 2012 DetectionTime: 10:11:25 Mon Jan 30 2012 Severity: 2 ToolAlias: Manager Monitor InferenceRule: ProviderSID: ManagerMonitor Manager Backup Info ExtraneousInfo: DUMP: Date of this level 0 dump: Mon Jan 30 09:30:32 2012
To restore raw data on your LEM appliance:
cmc>prompt, enter ndepth to navigate to the nDepth menu.