-m backup |
Takes a backup of the specified data. |
-m restore |
Restores the data from the specified backup file. 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:
|
-m info |
Displays the information for the specified backup file. |
-a |
Takes a backup of the Advisor data. By default, this parameter is disabled in the script, because the data is available from other sources. To enable this parameter, edit the script manually and change FLAG_A_DISABLED = "disabled" to FLAG_A_DISABLED = "enabled". |
-e |
Takes a backup of all the online event data. If the backup is performed on the Sentinel server, the current online partition is not backed up unless you shut down the server. |
-c |
Takes a backup of the configuration data. |
-dN |
Takes a backup of the event data for the specified number of days. By default, just specifying the -e option backs up all the online event data. Based on the current settings specified in the SDM, event data partitions can be kept online for up to last 90 days. Backing up all 90 days of event data with every backup might not be essential.
NOTE:If you specify only -d, no event data will be backed up.You must specify this parameter along with the -e parameter. For example:
backup_util.sh -m backup -e -d5 -f <install_directory>/data/<events_5days_backup.tar.gz>
|
-s |
Shuts down the Sentinel server. You must use this command if you want to backup the current online partitions in the database and/or to backup the dynamic runtime data because the server must be shutdown before taking a backup of these data. After the backup is complete, the server restarts automatically. |
-f |
Enables you to specify the location and name of the backup file. If this option is not used, then the backup file gets a random name based on the current date. |
-l |
Includes the log files in the backup. |