Skip to main content

Tape replication is completely broken

Thread needs solution

Whichever operation I try  with tape replication it gets broken.

Firstly I could not do a tape rescan of  multiple tapes containing concatenated backups as the rescan would not continue on the next tape.

Then I decided to make a replication to only 1 tape, but any repeated attempt on multiple tape rescan would result in the error of the single tape replication operation as half added archives to the index (during a failed replication) would screw up replication to this single tape also. 

Then after deleting all the backups from the index and trying a single tape rescan would work but then on subsequent replication to the tape I would get:

Internal error: The backup with GUID 'E8AC4BE6-5280-4E78-8B3C-4148B009396F' already exists in the current backup chain and has ID '1322BE76-96BE-46AB-ACFF-180B8246C788'

What does this mean? I rescanned the tape and it won't add new backup as the old backup has the same name. I don't understand.

You better pray than nothing goes wrong with local index as  any attempt at rescan would either fail immediately or it will fail on the next backup.

The only solution is to start with empty tape and hope you never have to rescan it again. This isn't how reality works.

There is always unpredictable situation where you need to rescan the tape. Acronis please fix this!!!

0 Users found this helpful
frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 0
Comments: 2016

Hello Toni,

thank you for posting a new thread on Acronis forums!

I recommend that you set replication to a new archive. You will need to create a new tape pool for this.

Internal error: The backup with GUID 'E8AC4BE6-5280-4E78-8B3C-4148B009396F' already exists in the current backup chain and has ID '1322BE76-96BE-46AB-ACFF-180B8246C788'

This issue should be investigated and reproduced in details by Acronis engineers. Please open a case with Acronis Support Team and describe this issue + add forum links.