Skip to main content
Question

Oracle RMAN Job Copy issue

  • January 25, 2025
  • 3 comments
  • 112 views
R

Good morning. I usually perform backup jobs using the Oracle RMAN plugin for a primary repository.

When creating a copy job of this backup job for a second repository, I receive several errors saying "File does not exist. File: [XXXX.vab].

Where is Veeam looking for these files that no longer exist in the primary repository?

We have an immutability configuration of 30 days in our primary repository. Since this is our first contact with Veeam, we were mistakenly deleting Oracle RMAN backup files older than 30 days directly in the repository file system. However, we were instructed by Veeam support to just rescan the repository so that possible invalid files in the Veeam database catalog could be resynchronized, but this did not solve the problem.

I have an open case about this but still no response. Has anyone had this problem and solved it?

Chris.Childerhose

3 comments

Chris.Childerhose
Forum|alt.badge.img+21
  • Chris.Childerhose
  • Veeam Legend, Veeam Vanguard
  • January 25, 2025

My guess would be Veeam is looking for all files in the backup chain and that is the missing file.  By deleting things manually which you never do it has corrupted the chain to Veeam.  I suggest staying with the support ticket to get this resolved.

Chris Childerhose - VMCA2024 | VMCE2023 | VMCE-SP2024 | Veeam Vanguard 8* | Veeam Legend 5* | VUG Canada Leader | vExpert 6* | Toronto VMUG Leader | VCAP-DCV/VCP-DCV | Object First Ace | Cisco Champion | Twitter: @cchilderhose | Blog Site – https://just-virtualization.tech
coolsport00
Forum|alt.badge.img+21
  • coolsport00
  • Veeam Legend
  • January 25, 2025

Agree with Chris here. Depending on your backup retention, you may need files which go beyond 30 days to be able to restore. For example, having a Full file and subsequent incremental files all are needed for performing a restore for a given timeframe. So, if you delete any manually outside of your backup solution, you indeed can not only run into restore issues, but backup (or copy) Job errors/issues as well...as noted by your error. 

Keep us posted what Support says.

Best.

Shane Williford - Veeam VMCA/VMCE | Veeam Legend | VUG Leader | VCP-DCV | Twitter: @coolsport00
dloseke
Forum|alt.badge.img+8
  • dloseke
  • Veeam Vanguard
  • February 3, 2025

Generally speaking, if you have manually deleted backup files and invalidated the chain, you’re going to need to take a new full backup and start a new chain and eventually you’ll be able to remove the backup data prior to the new chain being created.  With that said, I question the reasoning behind removing restore points outside of Veeam rather than letting the retention policies do their jobs.

Derek M. Loseke, Senior Systems Engineer | Veeam Vanguard 2025 | Veeam Legend 2022-2024 | VMSP/VMTSP | VCP6-DCV | VSP/VTSP | CCNA | https://technotesanddadjokes.com | @dloseke
Terms & ConditionsAccessibility statement