Skip to main content

Old Tape Backups Keep Re-Appearing

Thread needs solution

I am using build 11010.

I back up to network storage and tape. I find that cleanup of old backups works on the network storage, but no matter what I do, old backups to tape keep re-appearing. It seems to be an issue primarily with backup plans which no longer exist.

If I put the tape in and run an inventory, old backups appear. I have tried fast erasing the tape, moving it to the free tapes pool and refreshing the recovery points for each device, and that seems to update the database so the old backups don't appear, but they reappear any time I inventory the tape drive.

How do I permanently get rid of these old backups? The tape has been overwritten multiple times.

I also find that if I go to Tape Management and select "Show Backups" for the online tape, I can see backups to the device that appears, but if I click on any other devices with backups on the tape, I see a message no backups". I saw another report of this and understood it should be fixed in this build. Any news on that?

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

Hi! 

If you have already performed full inventory of tapes and re-scanning, it's worth raising a support ticket, so that our engineers can conduct more in-depth troubleshooting (Looks like the tape management database contains incorrect values from old tapes. I'd suspect the complete re-installation of the software will solve this issue, but if re-installation is not an option, better to continue investigation with the support team)

> I also find that if I go to Tape Management and select "Show Backups" for the online tape, I can see backups to the device that appears, but if I click on any other devices with backups on the tape, I see a message no backups". I saw another report of this and understood it should be fixed in this build. Any news on that?

This issue is expected to be fixed in the next update (internal ID for ref ABR-176119)

Thank you,

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 250
Comments: 7092

Please share the outcome with the community