Aller au contenu principal

Deleting backups fails if the location was renamed

Thread needs solution

Hello!

I recently renamed one of my storage nodes and edited the relevant plans to reference the new name. It appears however that I couldn't delete any of the backups that previously backed up to this location. These are all full backups. The error message of the deleting activity: 

Command has failed. Command=Applying retention rules; tenantID=00000000-0000-0000-0000-000000000000

Unknown location: 'Old Vault name'.

After detaching and reattaching the vault the issue seems to be resolved. Is this an intended behavior?

-- Peter

0 Users found this helpful
frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Contributions: 0
Commentaires: 2016

Hello Peter,

thank you for posting this question on Acronis forums!

The metadata of this renamed Storage Node contained its old name which could lead to this peculiarity. After you have detached/attached this vault, its metadata has been renewed.

Hello Maria!

Is there a way to avoid this, or this is the way to handle it? If it is, the same message, that notes that you'll need to edit your plans to the renamed location, could also note that you'll need to reattach the location. 

-- Peter

 

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Contributions: 250
Commentaires: 7092

Hello Peter,

discussed this issue with the RnD - wee need to reproduce the scenario in our labs. I'll get back to you once we have new information.

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Contributions: 250
Commentaires: 7092

Dear Peter,

we've reproduced the issue and created a task for fixing ABR-264327, thank you for bringing this to our attention!

Hello Ekaterina!

Has this fix been implemented yet? I'm still experiencing it in build 16428.

-- Peter

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Contributions: 250
Commentaires: 7092

Dear Peter,

checked the status of the task - it's still in progress..I'll clarify the ETA and if there is any workaround 

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Contributions: 250
Commentaires: 7092

Hello Péter,

do you know if the issue reproduces on Acronis Cyber Protect 15? The RnD suggests upgrading to 15, where this behavior should be corrected. 

Hello Ekaterina!

No idea, I originally planned to use 12.5 until spring/summer and upgrade then, before extended support ends in september. Might do it sooner if there are so many bugs fixed in 15.

-- Peter

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Contributions: 250
Commentaires: 7092

UPD: no, looks like the behavior is the same in the v15 - once renamed the vault needs to be re-attached