Xporte crashes Jira-Backups and Jira Upgrade process

Hello,

on monday i decided to upgrade my jira from 7.0 to 7.05 and on the restart, jira crashed with

ERROR [c.a.jira.upgrade.UpgradeLauncher] An Error occurred during UpgradeLauncher servlet context initialisation - javax/xml/bind/DatatypeConverter.

after some back and forth with the guys from Atlassian, we discovered that all my backups, beginning Oct. 27th were corrupt.

eventually Atlassian found the issue in one of "your" tables:

I saw that the instance was running into an issue handling Binary data. I then dumped out the Data base schema and started looking for Binary data, Looking through your database, I noticed this table:
mysql> desc AO_3C6513_XPORTER_SECURITY;
-----------------------------------------------------------+

Field

Type

Null

Key

Default

Extra

-----------------------------------------------------------+

ALGORITHM_KEY	varchar(255)	NO		NULL
CHARSET_VALUE	varchar(255)	YES		NULL
CIPHERTRANS_VALUE	varchar(255)	YES		NULL
ID	int(11)	NO	PRI	NULL	auto_increment
KEYSIZE_VALUE	int(11)	YES		NULL
PASSWORD_VALUE	varchar(255)	YES		NULL
PRIVATE_VALUE	blob	NO		NULL
PUBLIC_VALUE	blob	NO		NULL
USERNAME_VALUE	varchar(255)	YES		NULL

-----------------------------------------------------------+
It contains two BLOB columns that JIRA is struggling to handle.

after trying to file a bug for that at Atlassian, they replied to me with:

In regards to the bug that Matt mentioned, Atlassian does not fully support the BLOB data type in AO data, as mentioned here.
BLOBs and Active Object plugins
Currently, Atlassian's Active Object framework does not support binary large objects (BLOBs). Plugins that work with BLOBs fail. Until there is full support, do not write AO plugins that manipulate BLOBs.
The Xporter plugin, however, has two columns using BLOB data type. Thus, this is something you need to raise up to the plugin vendor, as this is third party plugin and out of our Support Scope. You may reach out to the vendor here.

so, here i am, filing a bug for xporter.

i was able to start my instance after removing the plugin and renaming the table. but this can only be a tempory measure.

i am unable to use the xporter plugin until it is fixed.

please also tell me, whats stored in that table as i proly will be unable to ever access the data from within jira again (it crashs during startup).

thank you!