Bug #56393 MEB backup logs are not affected by time zones.

• Submitted: 31 Aug 2010 4:24
• Modified: 10 Nov 2010 9:35
• Reporter: Hema Sridharan
• Status: Closed
• Category: MySQL Enterprise Backup
• Severity: S3 (Non-critical)
• Version: MEB3.5
• OS: Linux
• CPU Architecture: Any

[31 Aug 2010 4:24] Hema Sridharan

Description:
In the MySQL server, the default time zone is GMT. Change this time zone to some other zone(I changed to local time)

Now execute innobackup.
Check the history logs for start time and stop time of backup, it shows the GMT time and not the local time. The time shown in logs should have the time zone that is set by user.

How to repeat:
SELECT now();
now()
2010-08-31 07:16:14
SET TIME_ZONE='-5:00';
SHOW VARIABLES LIKE '%zone%';
Variable_name   Value
system_time_zone        GMT
time_zone       -05:00
SELECT now() INTO @start_backup;
#
# Run innobackup 

--echo # Run innobackup with compression.
--exec $INNOBACKUP --port=$MASTER_MYPORT --user=root --no-timestamp $SERVER_CNF $BACKUP_TARGET_DIR1 > $BACKUP_LOG 2>&1
--echo ...
# If not success, mysqltest would exit after exec.
--echo # Success
--echo

# Success

SELECT now() INTO @stop_backup;
SELECT @start_backup;
@start_backup
2010-08-30 23:16:14
SELECT @stop_backup;
@stop_backup
2010-08-30 23:16:22

SELECT start_time, end_time FROM mysql.backup_history;
start_time      end_time
2010-08-31 07:16:15     2010-08-31 07:16:22

From the above example, we can notice that backup_history logs are independent of time zones.

[10 Nov 2010 9:35] Satya B

From decision meeting notes.

MOM-BACKUP-100907-1 Backup

3. For BUG#56353 we will always follow :"Store timezone in UTC display
   Local time."
   - Close bug with above comment
   A new bug to be created for display messages to be in local
   timezone.