Skip to main content

Console Locations section getting list of old locations and now TAPE locations

Thread needs solution

I have two odd issues around the Location section in the ABA server console.

1) I've used Acronis for 9+ years and many windows clients have been upgraded from older versions that pointed to old network storage locations that have been offline for years. Those locations are showing up in the 12.5 console and there are literally almost about 100 of them. Is there any way to turn off discovery of these defunct locations? I only want locations in ABA console that I add.

2) I recently (?) started seeing about 130 TAPE icons showing up under Locations. It appears that almost half of my clients decided to register a tape location for some reason and I am not using tape anywhere. Any idea why this is happening?

I both cases I deleted all of these unwanted locations but I don't want to have to do that again.

thanks

Pete

0 Users found this helpful
frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 22
Comments: 3800

Hi Pete,

The locations from old clients are added to the list of locations in Acronis Backup 12.5, including "local" locations, and if your old agents were backing up to local drives then it might be the case that all locations (1 from each client) may appear in the list after the upgrade. Still in order to properly investigate such problems it makes sense to contact our support team for assistance. Definitely excessive tape locations appearance is not normal, but we haven't seen similar reports yet, so it needs to be investigated separately.

Thank you.

oh! yeah! here's a "similar report"

i've got 8 of them sitting inside Locations right now!

every agent on every server and every workstation creates it's own "tape"

i'm tired of deleting them!

and to add insult to injury, i've never used any tapes with Acronis

so you can't blame old agents and configs for that - it's an outright bug! :)