Pre-defined Reports: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 5: | Line 5: | ||
!Backup report name!!Description!!Information available | !Backup report name!!Description!!Information available | ||
|- | |- | ||
|backup-status-info||Status of backup runs||backup-set, backup-date, backup-level, backup-status, backup-comment | |backup-status-info||Status of backup runs||backup-set, backup-date, backup-level, backup-status, backup-type, backup-comment | ||
|- | |- | ||
|backup-method-info||Backup methods used||backup-set, raw-databases, raw-databases, logical-databases | |backup-method-info||Backup methods used||backup-set, raw-databases, raw-databases, logical-databases | ||
| Line 11: | Line 11: | ||
|backup-retention-info||How long are the backups retained?||backup-set, backup-date, backup-level, backup-size, retention-policy | |backup-retention-info||How long are the backups retained?||backup-set, backup-date, backup-level, backup-size, retention-policy | ||
|- | |- | ||
|backup-performance-info||Backup performance ||backup-set, backup-date, backup-level, backup-size, backup-size-compressed, backup-time,compress-encrypt-time | |backup-performance-info||Backup performance ||backup-set, backup-date, backup-level, backup-type, backup-size, backup-size-compressed, backup-time,compress-encrypt-time | ||
|- | |- | ||
|backup-app-performance-info||Impact of backups on application||backup-set, backup-date, backup-level, backup-size, backup-time, read-locks-time, flush-logs-time | |backup-app-performance-info||Impact of backups on application||backup-set, backup-date, backup-type, backup-level, backup-size, backup-time, read-locks-time, flush-logs-time | ||
|- | |- | ||
|restore-info||Information for doing full/incremental recovery of databases||backup-set, backup-date, backup-level, backup-directory, backup-status, backup-comment | |restore-info||Information for doing full/incremental recovery of databases||backup-set, backup-date, backup-level, backup-directory, backup-status, backup-comment | ||
Revision as of 00:02, 9 December 2008
The mysql-zrm-reporter utility generates predefined backup reports with --show option. The reports are listed below.
| Backup report name | Description | Information available |
|---|---|---|
| backup-status-info | Status of backup runs | backup-set, backup-date, backup-level, backup-status, backup-type, backup-comment |
| backup-method-info | Backup methods used | backup-set, raw-databases, raw-databases, logical-databases |
| backup-retention-info | How long are the backups retained? | backup-set, backup-date, backup-level, backup-size, retention-policy |
| backup-performance-info | Backup performance | backup-set, backup-date, backup-level, backup-type, backup-size, backup-size-compressed, backup-time,compress-encrypt-time |
| backup-app-performance-info | Impact of backups on application | backup-set, backup-date, backup-type, backup-level, backup-size, backup-time, read-locks-time, flush-logs-time |
| restore-info | Information for doing full/incremental recovery of databases | backup-set, backup-date, backup-level, backup-directory, backup-status, backup-comment |
| selective-restore-info | Information for doing selective recovery of databases | backup-set, backup-date, incremental |
| replication-info | Replication files backed up | backup-set, backup-date, replication, slave-load-files |
Specific backup runs can be selected from the predefined backup reports using --where option.
Example: A backup status report
# mysql-zrm-reporter --where backup-set=backupSet1 --show backup-status-info
backup_set backup_date backup_level backup_status comment
-------------------------------------------------------------------------------------------
backupSet1 20060909100021 0 Backup Before application upgrade
succeeded
backupSet1 20060909100123 0 Backup After application upgrade
succeeded
backupSet1 20060909100300 0 Backup Nightly
succeeded