A few unpleasant surprises with r13400
Hello,
after updating to r13400 (from r11010) we have noticed a few little bit anoying things. Like for example:
1. Organization unit list is no longer in alphabetical order
Up until the update, organization list was alphabetical and thus easy to orient yourself in (I mean, if you are administrator for more than one unit, you have to open this list to switch from managing one to another one), but now the list is just completely random.
For most admins it won't be a problem, as they usually have only one or two units (sites) to manage, but our global administrators are managing ~40 units and then it's a little bit annoying to find the correct site shortcut
Is it possible for us to fix this issue by ourselves?
2. Locations' space usage stats are now nonsense
After the update, application server counts into "Occupied space" (for all the Locations we have) only the backups, that were literally created AFTER the update.
Any update that was created with previous version is not counted.
Example:Backups take 1.96TB of space in this specific Location (but it's the same for all other), but current Acronis release ignores them and counts only backups created after the update to "Ocuppied space".
This also means that Total ratio is now worthless information, as it's using Original data size and Occupied space for its calculation.
Same goes for Storage stats in the Dashboard.
Is this a known issue? Can we fix it somehow?
Thank you
Lukas

- Log in to post comments

Hello Brose,
thank you for your posting!
1. Organization unit list is no longer in alphabetical order
sounds like an issue in the product that needs to be reproduced in our environment. I've passed this to the product team.
2. Locations' space usage stats are now nonsense
This is a known issue (internal ID for ref ABR-230399), which is expected to be fixed in the next Update 5.
- Log in to post comments

Ekaterina wrote:1. Organization unit list is no longer in alphabetical order
sounds like an issue in the product that needs to be reproduced in our environment. I've passed this to the product team.
UPD: we're able to reproduce the issue and here the related ticket for fixing ABR-233386
- Log in to post comments

Hello Ekaterina,
thank you very much for your feedback.
Regarding third mentioned problem I've started a ticket and will have remote session with Acronis support today.
- Log in to post comments

Hello,
one more issue worth mentioning:
4. Archives belonging to devices that were offline during the server update and are still offline, now have archive with no name and with similar error message as mentioned in issue n.3
Immediately after the update I've noticed that quite a few archives are missing names now and at first I had no idea to which devices they belong to.
Fortunately it's still possible to see backups in these archives, so from their history I was able to find out to which devices they belong to and noticed that all of them are offline and were offline during the update process.
It seems that if specific Agent is unavailable during the server update, then it's impossible to browse/recover its backups until it's online again and its archive has no identification until then (still present on the server, but has no name shown in the console).
- Log in to post comments

Brose wrote:Hello,
one more issue worth mentioning:
4. Archives belonging to devices that were offline during the server update and are still offline, now have archive with no name and with similar error message as mentioned in issue n.3
Hello Brose,
did you open a ticket for this issue? If not yet, could you please report this to the support team and share the ticket ID with me? I'll leave a comment to speed up escalation to the RnD.
- Log in to post comments

Hello Ekaterina,
I'm sorry for late response. I've just created a ticket for this issue (04093430) and also included another issue there - users, that are members of 40 and more Units (we have separate Unit for each of our storage nodes) are unable to log in and get Internal Server Error.
This doesn't affect many of our users (only 2 of them) and it can be worked around if you cut down number of Units to 39, so it's not such a big deal, but I believe it should be fixed too and it wasn't happening with previously used version (11010)
- Log in to post comments