Automatic renaming of dtSparse to sparseimage and unintended consequences

[anon6914418]

As I understood earlier this issue only affects backups of encrypted databases that are written by TM to a network volume, not to local volumes:

Encrypted database empty after restore from TimeMachine? - Resolved

As far as we know it happens only in case of Time Machine backing up to network volumes and that’s the only way we could also reproduce it.