That doesn’t actually delete the DTTG2 data right away. It might, of course, be useful to delay the deletion.
If the current theory is correct, namely that the problem was lying dormant, having been caused by a problem in DTTG2 a while back, then it’s possible that once it has been rectified once, it no longer appears. But I guess the last word hasn’t yet been spoken on that.
I heard Eric’s sigh of relief from hundreds of kilometres away 
Now that the immediate problem is solved, I guess the team will be back with a clearer and happier head, looking at what is actually going on. I look forward to feedback on what the root actually was (assuming I’m competent to understand the explanation, that is). But we can have a little party in the meantime. (Well, we’re still in the middle of a pandemic, so we can’t - how about a cup of tea? Masked, gloved and alone.)