C.1 Parameters for the Backup and Restore Utility Script

The following table lists the various command line parameters that you can use with the backup_util.sh script:

Table C-1 Backup and Restore Script Parameters



-m backup

Takes a backup of the specified data.

-m restore

Restores the specified data. The restore mode of the script is interactive and allows you to specify the data to be restored from the backup file.

The restore parameter can be used in the following scenarios:

  • System Failure: In the event of a system failure, you must first reinstall Sentinel Log Manager and then use the backup_util.sh script with the restore parameter to restore the most recent data that you had backed up.

  • Data Loss: In the event of data loss, use the backup_util.sh script with the restore parameter to restore the most recent data that you had backed up.

    You must restart the Sentinel Log Manager server after you restore any data because the script might make several modifications to the database.

NOTE:The restore parameter is not backward compatible for local storage and networked storage data. Therefore, the local storage data and networked storage data can be restored only on the same or a later version of Sentinel Log Manager, and cannot be restored on an older version of Sentinel Log Manager.

-m info

Displays the information for the specified backup file.

-m simple_event_backup

Specifies to back up events located in a specified directory.

-m simple_event_restore

Specifies to restore events into a specified directory.


Takes a backup of the configuration data.


Takes a backup of the local storage event data. If the backup is performed on the Sentinel Log Manager server, the current local storage partition is not backed up unless you shut down the Sentinel Log Manager server.


Takes a backup of the event data for the specified number of days. The -dN option specifies to include the local storage event data from up to N days ago in the backup. Based on the current data retention policy settings, many days of events might be stored on the system. Backing up all of the event data might not always be necessary and might not be desirable. This option allows the specification of how many days to go back when backing up the event data. Example: -d7 includes only the event data from the last week in the backup.

NOTE:If you specify only -d, event data will not be backed up. You must specify this parameter along with the -e parameter. For example:

backup_util.sh -m backup -e -d5 -f /var/opt/novell/sentinel_log_mgr/data/<events_5days_backup.tar.gz>


Enables you to specify the location and name of the backup file.


Includes the log files in the backup. By default, the log files are not backed up unless you specify this option.


Includes the runtime data in the backup. Runtime data can only be backed up if the Sentinel Log Manager server is shut down because the data is dynamic. This means that this flag can only be used in combination with the -s option (described below). If -s is not specified, this flag will be ignored.


Shuts down the Sentinel Log Manager server before performing the backup. Shutting down the server is necessary to backup certain dynamic data such as the Runtime data and the current local storage partitions. By default, the server is not shut down before performing the backup. If this option is used, the server restarts automatically after the backup is complete.


Specifies to include the raw event data in the backup.


Only available with the simple_event_backup and simple_event_restore options. Specifies the location of the event data directory like where the event data is collected during a simple_event_backup and where the event data is placed during a simple_event_restore.