Sudden DB size increase following v3.4.0 update

Hello, The size of my backup (.sql file) increased from about 60 MB to over 100 MB following some updates yesterday.
Another curious thing is that when comparing all of the db tables, there are no size differences present that could account for the “huge” increase. The 60 MB .sql file is virtually identical to the 100 MB .sql file…

Here are the two log entries #1 is before the update and #2 is after the update:

#1:
[INFO] BackWPup 3.3.7; A project of Inpsyde GmbH
[INFO] WordPress 4.7.5 on https://themakeuplight.com/
[INFO] Log Level: Normal
[INFO] BackWPup job: onetime man
[INFO] Logfile is: backwpup_log_aa1cf4_2017-06-12_16-11-30.html
[INFO] Backup file is: backwpup_aa1cf4_2017-06-12_16-11-30.tar.gz
[12-Jun-2017 16:11:31] 1. Try to backup database …
[12-Jun-2017 16:11:31] Connected to database the1324702504175 on the1324702504175.db.11739663.hostedresource.com
[12-Jun-2017 16:11:41] Added database dump “the1324702504175.sql” with 59.72 MB to backup file list
[12-Jun-2017 16:11:41] Database backup done!
[12-Jun-2017 16:11:44] 1. Trying to generate a manifest file …
[12-Jun-2017 16:11:44] Added manifest.json file with 7.43 KB to backup file list.
[12-Jun-2017 16:11:44] 1. Trying to create backup archive …
[12-Jun-2017 16:11:44] Compressing files as TarGz. Please be patient, this may take a moment.
[12-Jun-2017 16:11:48] Backup archive created.
[12-Jun-2017 16:11:48] Archive size is 4.74 MB.
[12-Jun-2017 16:11:48] 3 Files with 59.73 MB in Archive.
[12-Jun-2017 16:11:51] One backup file deleted
[12-Jun-2017 16:11:51] One old log deleted
[12-Jun-2017 16:11:51] Job done in 21 seconds.

#2:
[INFO] BackWPup 3.4.0; A project of Inpsyde GmbH
[INFO] WordPress 4.7.5 on https://themakeuplight.com/
[INFO] Log Level: Normal
[INFO] BackWPup job: daily db auto
[INFO] Logfile is: backwpup_log_aa1cf4_2017-06-12_21-00-58.html
[INFO] Backup file is: backwpup_aa1cf402_2017-06-12_21-00-58.tar.gz
[12-Jun-2017 21:00:58] 1. Try to backup database …
[12-Jun-2017 21:00:58] Connected to database the1324702504175 on the1324702504175.db.11739663.hostedresource.com
[12-Jun-2017 21:01:10] Added database dump “backwpup_aa1cf402_the1324702504175.sql” with 102.50 MB to backup file list
[12-Jun-2017 21:01:10] Database backup done!
[12-Jun-2017 21:01:12] 1. Trying to generate a manifest file …
[12-Jun-2017 21:01:12] Added manifest.json file with 7.46 KB to backup file list.
[12-Jun-2017 21:01:12] 1. Trying to create backup archive …
[12-Jun-2017 21:01:12] Compressing files as TarGz. Please be patient, this may take a moment.
[12-Jun-2017 21:01:18] Backup archive created.
[12-Jun-2017 21:01:18] Archive size is 5.75 MB.
[12-Jun-2017 21:01:18] 3 Files with 102.51 MB in Archive.
[12-Jun-2017 21:01:19] One old log deleted
[12-Jun-2017 21:01:19] Job done in 21 seconds.

(The second was the overnight scheduled backup. Another manual backup later showed the same increase)

Could BackWPup have caused such an increase, and why doesn’t the increased file size show “where” the increase in data is when looking at the database tables?

Thank you for your time and answer.