Unusual error editing backup definition using ATI 2014

This message describes an unusual error which occurred while editing backups definitions in ATI 2014. Editing appeared to corrupt the database.

Sorry about long post.
Unfortunately, the detailed evidence is lost because I have since done a clean re-install of the product, but just in case someone else notices here are the details:

Product is ATI 2014, 3 users, premium, installed as a upgrade. Install successful, schedule still in place and backups found/verified etc. A small issue noted on conversion – the product adds a " into one of my command strings which means it does not work. I've since found that this happens on settings import as well. So first backup failed, easy fix.

Then noted that the setting to 'shutdown the computer after backup' no longer works. This issue documented elsewhere and support advised me to use "shutdown –s" as a post command for now.
Edited the backup definition, tested the command and when the schedule ran overnight the issue started -

Next morning both backups had failed (I have two - an 'all partitions' disk incremental and an email incremental)
Both backup definitions appeared in the GUI as failed email backups. The change log showed that, as well as editing the command etc, the task name of the partitions backup had been set to the same name as the email one(!) The names were originally quite different and there is no way I would have done this deliberately. I'ts pretty natural to say "user error" of course, but I don't think so.

When I went to edit the backup to fix the issue the GUI showed the correct name for the partitions backup (ie the changed name did not show in the GUI); but the backup type was email and I could not change it back to disk. From this point all backup failed with various errors including one were I recreated the disk backup from scratch. I assumed that the backup definition database was now hopelessly corrupt and so I uninstalled, cleaned up and re-installed.

Backups appear to work correctly. Shutdown still does not work (obviously need to wait for a fix).
I'm not going to speculate on the issue, and see little point in a formal support call as the evidence is gone (pity!); so this is for info only, happy to answer questions and provide any info I can. Considering going back to 2012 for now.