Bug #39356 Backup progress table details aren't updated properly
Submitted: 10 Sep 2008 2:16 Modified: 13 May 2009 21:55
Reporter: Hema Sridharan Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Server: Documentation Severity:S3 (Non-critical)
Version:mysql-6.0-backup OS:Linux
Assigned to: Assigned Account CPU Architecture:Any

[10 Sep 2008 2:16] Hema Sridharan 
Description:
1) Create database, tables and load with lots of data. 
2) Perform data backup (ensure that backup operation takes few mins to
complete).
3) Check the backup_progress table from another thread for the
start_time and stop_time. 
4) The time is always shown as '0000-00-00 00:00:00' for backup notes of
'starting', 'running', 'validity point' and 'complete'.
5) Also the total bytes and progress are always indicated '0' for all
phases of backup operation. 

The WL#4296 mentions that,
"The backup progress log provides the following information"
* percent done i.e. 'the size of the object in bytes' / 
  'the number of bytes processed'

But this is not the actual response from backup_progress table.

How to repeat:
connection con1;
mysql> backup database try to 'tryp.bak';
+-----------+
| backup_id |
+-----------+
| 258       |
+-----------+
1 row in set (3.47 mins)

connection con2;
mysql> select * from mysql.backup_progress\G;
*************************** 1. row ***************************
  backup_id: 258
     object: backup kernel
 start_time: 0000-00-00 00:00:00
  stop_time: 0000-00-00 00:00:00
total_bytes: 0
   progress: 0
  error_num: 0
      notes: starting
*************************** 2. row ***************************
  backup_id: 258
     object: backup kernel
 start_time: 0000-00-00 00:00:00
  stop_time: 0000-00-00 00:00:00
total_bytes: 0
   progress: 0
  error_num: 0
      notes: running
*************************** 3. row ***************************
  backup_id: 258
     object: backup kernel
 start_time: 0000-00-00 00:00:00
  stop_time: 0000-00-00 00:00:00
total_bytes: 0
   progress: 0
  error_num: 0
      notes: validity point
*************************** 4. row ***************************
  backup_id: 258
     object: backup kernel
 start_time: 2008-09-09 16:39:36
  stop_time: 0000-00-00 00:00:00
total_bytes: 0
   progress: 0
  error_num: 0
      notes: vp time
*************************** 5. row ***************************
  backup_id: 258
     object: backup kernel
 start_time: 0000-00-00 00:00:00
  stop_time: 0000-00-00 00:00:00
total_bytes: 0
   progress: 0
  error_num: 0
      notes: running
*************************** 6. row ***************************
  backup_id: 258
     object: backup kernel
 start_time: 0000-00-00 00:00:00
  stop_time: 0000-00-00 00:00:00
total_bytes: 0
   progress: 0
  error_num: 0
      notes: complete

From the above table, we can notice that start_time, stop_time are always '0000-00-00 00:00:00' and also total_bytes, progress are indicated as '0', though backup operation took 3mins to complete.
[3 Mar 2009 20:21] Chuck Bell 
This is not a bug. The state of the backup_progress log content was left for a later design and worklog. 

This is the known state of the backup logs:

* The start_time and stop_time in the backup_progress log are not used for all states and have a default value of '0000-00-00 00:00:00'.
* The couting columns (total_bytes and progress) are not used and default to 0.
* All columns in the logs are required to have default values.

See the 'Future Work' section of the HLD in WL#4296 for more details.

Note: BUG#42693 may modify the content of the backup_progress log.

A worklog for revising the backup_progress reporting has been created. See WL#4815.
[13 May 2009 21:55] Chuck Bell 
Duplicate of BUG#39528.