2621844 - Backup ID provided for DT backint based backups is incorrect - SAP HANA DYNAMIC TIERING

When doing a full backup on SAP HANA Dynamic Tiering, there are four invocations of hdbbackint that relate to the full database backup like the following:

2018-02-23 08:36:02.000 backint started:
command: /usr/sap/SUP/SYS/global/hdb/opt/hdbbackint -f backup -p /usr/sap/SUP/SYS/global/hdb/opt/hdbconfig/initSUP.utl -i /var/tmp/hdbbackint_SUP.Sb4rPa -o /var/tmp/hdbbackint_SUP.cyp5In -u XXX -s XXXXX -c 5 -l COMPLETE
pid: 5673
input:
#SOFTWAREID "backint 1.04" "HANA HDB server 1.00.122.15.1516128271"
#PIPE "/usr/sap/SUP/SYS/global/hdb/backint/AFTER_UPDATE_databackup_0_1"

And among them there is an additional one:

2018-02-23 08:36:12.000 backint started:
command: /usr/sap/SUP/SYS/global/hdb/opt/hdbbackint -f backup -p /usr/sap/SUP/SYS/global/hdb/opt/hdbconfig/initSUP.utl -i /var/tmp/hdbbackint_SUP.92f3dT -o /var/tmp/hdbbackint_SUP.P8EnPb -u XXX -s XXXXX -c 1 -l COMPLETE
pid: 5775
input:
#SOFTWAREID "backint 1.04" "HANA HDB server 1.00.122.15.1516128271"
#PIPE "/usr/sap/SUP/SYS/global/hdb/backint/AFTER_UPDATE_databackup_1024_1_1519371361036"

It is supposed not to belong to the backup because argument for parameter -s is different from the other hdbbackint call (1519371372204).
but there are only 4 hdbbackint calls with '-s 1519371361036'.
When checking the backup catalog, the backup with id 1519371361036 consists of 5 objects including the
/usr/sap/SUP/SYS/global/hdb/backint/AFTER_UPDATE_databackup_1024_1_1519371361036.

command: /usr/sap/SSS/SYS/global/hdb/opt/hdbbackint -f backup -p /usr/sap/SSS/SYS/global/hdb/opt/hdbconfig/initSSS.utl -i /var/tmp/hdbbackint_SSS.92f3dT -o /var/tmp/hdbbackint_SSS.P8EnPb -u XXX -s XXXXX -c 1 -l COMPLETE

pid: 5775
input:
#SOFTWAREID "backint 1.04" "HANA HDB server 1.00.122.15.1516128271"
#PIPE "/usr/sap/SSS/SYS/global/hdb/backint/AFTER_UPDATE_databackup_1024_1_1519371361036"

Options '-s' is supposed to be the backup id (here 1519371372204). But in the backup catalog the file gets assigned to backup id 1519371361036.

> hdbsql -U my_key 'select BACKUP_ID,DESTINATION_PATH,DESTINATION_TYPE_NAME,EXTERNAL_BACKUP_ID from M_BACKUP_CATALOG_FILES where BACKUP_ID=1519371361036' | cat
BACKUP_ID,DESTINATION_PATH,DESTINATION_TYPE_NAME,EXTERNAL_BACKUP_ID
1519371361036,"/usr/sap/SSS/SYS/global/hdb/backint/AFTER_UPDATE_databackup_0_1","backint","SSS___A0JDZMHANU"
1519371361036,"/usr/sap/SSS/SYS/global/hdb/backint/AFTER_UPDATE_databackup_1_1","backint","SSS___A0JDZMHANU"
1519371361036,"/usr/sap/SSS/SYS/global/hdb/backint/AFTER_UPDATE_databackup_2_1","backint","SSS___A0JDZMHANU"
1519371361036,"/usr/sap/SSS/SYS/global/hdb/backint/AFTER_UPDATE_databackup_3_1","backint","SSS___A0JDZMHANU"
1519371361036,"/usr/sap/SSS/SYS/global/hdb/backint/AFTER_UPDATE_databackup_1024_1_1519371361036","backint","SSS___A0JDZMHIM3"

So the esserver is considered to be part of the backup. Which matches the hdbbackint command line argument '-c 5'.
That means the backup consists of 5 files.
But there are just 4 hdbbackints started for backup id 1519371361036.
It is missing one hdbbackint call for the esserver and the esserver backup should be started with arguments '-c 5' and '-s 1519371361036' too.