Skip to main content
  • EN

Hi,

I’m using a GFS tape job to store my backup jobs. It contains 12 monthly and 5 yearly jobs. If I want to show all restore points, I only see until may 2025. All restore points before are not showed. When I’m searching my emails, I’m able to find the tape which contains the not shown backups. On the tape I will find the monthly backup, I’m searching for.

I few months ago, I do not know how many, I changed the name of the tape job. He seems to work.

What can I do? When I catalog the tape an error appears. “Error: Violation fo primary key constraint…...”

I opened a ticket, but it still works slowly. “Case-Nr.07791336 Restore Points werden nicht angezeigt”

Can anyone help?

Kind regards 

Gunter

Hi ​@Gunter Brandmaier,

Best is to go with support - what you already did.

Which tapes are you using? LTO8? LTO9?

Did you make sure that - depending on your design - all required tapes are inserted, online and not damaged?

Did you run a library rescan and inventory?

 

Please keep us posted as soon as you receive an update from support.

 

Best

Lukas

Hi, thanx for answering.

I’m using LTO8. All tapes are inserted. When the tapes are outside the library, their restore points should still be available in the database for selection and should appear when searching for them.

rescan or inventory aren’t done yet. Because i will wait for support.

The error, when doing catalog, seems to show, that the backup is still there. But it isn’t appearing when clicking on point…

best Gunter

  

Hi ​@Gunter Brandmaier 

What can I do? When I catalog the tape an error appears. “Error: Violation fo primary key constraint…...”

Wait for Support on this one. That error is bubbling up from the SQL Engine (MSSQL / PGSQL) and it’s as you theorize I suppose, likely there is a duplicate unique value trying to be inserted where it shouldn’t be. 

Support will review the situation and advise on next best steps. If you urgently need the backups on tape and they are the _only_ copy you have of these backups, inform Veeam Support in the case of this situation and they will change the focus of the case temporarily to try to assist with getting the backups off of the tape.

Note: You may find suggestions online that advise removing / readding tape infrastructure items to work around this. I strongly recommend do not follow these instructions, as they will almost certainly exacerbate the situation and delay resolution. The issue is in the database most likely.

Source: Me, 7 years in Veeam Support

Hi,

I’m in work with support. Unfortunately should I test the tape drives with TapeDiagCollector.ps1 and IBM ITDT. So it takes a while until we go working with the database. :(

Hi,

I’m in work with support. Unfortunately should I test the tape drives with TapeDiagCollector.ps1 and IBM ITDT. So it takes a while until we go working with the database. :(

 

 

Wait for Veeam Support.

 

 

 

Understood. I have reached out to my colleagues in support to offer guidance, hopefully you should hear from them soon.

Comment


Terms & Conditions