MySQL Bugs: #81788: MEB Backups (silently) not scheduled when home directory has space

Bug #81788	MEB Backups (silently) not scheduled when home directory has space
Submitted:	9 Jun 2016 13:48	Modified:	4 Feb 2020 20:48
Reporter:	Andrii Nikitin	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench: Administration	Severity:	S3 (Non-critical)
Version:	6.3.6	OS:	Windows
Assigned to:		CPU Architecture:	Any

Description:
Backups are silently not scheduled if Home Directory has space.

E.g. with Backup Home Directory "D:\meb backup" - wb.log indicates error 'There is no file extension', which is not recognized as error  :

14:11:39 [INF][wb_admin_meb_syshelpers.py:update_backup_scheduling:44]: Execute cscript /nologo "D:\meb backup\mysqlwbmeb.vbs" UPDATE_SCHEDULING DELETE c520a28f-2e3a-11e6-9388-448500332006 backup 1 0 as root
14:11:43 [INF][wb_admin_meb_syshelpers.py:update_backup_scheduling:49]: Profile Rescheduling finished: Input Error: There is no file extension in "D:\meb".

(notice the path is truncated on the space in last message).

How to repeat:
1. Configure "Backup Home Directory" to have space, e.g. "D:\meb backup\"
2. Schedule backup and observe error in log mentioned in Description.
3. Backup appears as scheduled in WB, but no actual entry gets created in Windows Task Scheduler
4. At scheduled time nothing occurs.

Suggested fix:
1. Fix it
2. Make sure that WB correctly behaves if error occured during scheduling
3. Make sure that WB never displays scheling in 'correct' state if no entry exists in Task Scheduler

Posted by developer:
 
Fixed as of the upcoming MySQL Workbench 8.0.21 release, and here's the proposed changelog entry from the documentation team:

No errors or warnings were reported when scheduling a backup with MySQL
Enterprise Backup, although the backup did not execute as scheduled.

Thank you for the bug report.