Skip to main content

Dashboard not showing Storage/Locations Data

Thread needs solution

Hello,

we have started deploying Acronis v12.5 and noticed, that not all data are being collected by the Monitoring service - at least it looks like that's the case here.

We have (at the moment) one management server and a few storage node servers with managed locations on them. Everything works so far, backups are being created etc., but Dashboard is not showing all the data we would like to see.

Storage widget shows 0 Bytes for "Backups" (for all our Storage nodes) even though, there are actually 100s of GBs of Acronis v12.5 backups (they are shown as "other files").

Example: (those 319,7GB of "other files" are in fact Acronis backups)

storage01.PNG

 

Similar problem with Storage usage stats - 0 Bytes all the time (even when backup jobs are running), Locations summary shows only Current free space, other stats are just " - " .
All storage or locations related stats shows no data.

 

Alerts, activities, status etc. reports are OK.

 

What could be the problem here? Are the reports not shown (updated), because all the locations are deduplicated?
Shouldn't be a firewall issue as I see no dropped communication between application server and storage nodes in the network firewall log.

Could this be permissions issue? Acronis Monitoring Service is run under account with admin permissions and the same user is also administrator on all the storage node servers (and has full access to the folder where acronis backups are stored).

Any hint, please? :)

 

Thank you,

Lukas

0 Users found this helpful
frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 250
Comments: 7092

Hello Lukas,

Thank you for raising this topic! I've looked through our internal sources and found some documented issues that show symptoms similar to those you described in this topic. As far as I understand they all have a common root cause that is expected to be fixed in the upcoming Update 4, but to make sure you've encountered one of the known issues, I'd still recommend submitting a support ticket, so that our engineers can take a look at your setup - there are cases where symptoms look similar, but the root cause is different. Please share the results of the investigation with the forum community. 

 

Hello Ekaterina,

thank you for your answer :) . I will submit a ticket and when I get some useful asnwers, I will share them here.

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 250
Comments: 7092

Great, thank you! Let me know if any assistance is needed

Support confirmed that this problem is known and will be fixed by Update 4 sometime in Q2 2019, so we will have to wait (not a big deal).

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 250
Comments: 7092

Brose wrote:

Support confirmed that this problem is known and will be fixed by Update 4 sometime in Q2 2019, so we will have to wait (not a big deal).

 Thank you for feeding back!