With the ngax webUI, the first step when creating a new backup is to give it a name.
If the machine is registered into the Console webapp, a default email will be sent at the end of each run, showing that name of the backup in the Subject and in the Body of the email.
Later on, if you decide to edit the configuration of the backup, you can obviously modify the name of the backup.
However, subsequent automatic emails, sent by the Console after the runs of the backup, will continue to show the initial first name of the backup. So effectively, the change of the name of the backup is not taken into consideration in the mail report of the Console.
First backup triggered at 17:16.
Then backup edited and name of the backup changed.
Triggered the backup at 17: 22.
2nd report email doesn’t show the new name of the backup.
Yes. The logic for this is that the first backup made will record the name. This name will then be used on subsequent reports, even if you change the name locally.
The reason for this is that you can change the name in the console, and if you do, that name will stick. If we update the name based on what the machine reports, you could loose the custom name assigned in the portal.
One potential fix is to track if the name was automatically assigned or not, and only update if it is manually assigned. This adds some complexity in the UI where it needs a “reset” button to go back if you manually change it.
I have added this request to our internal issue tracker for the console and will report back here when we have a resolution.
