Limitations and Good Pratices

Veeam Backup to Tape – Known Issue

Overview

This document describes a known issue that may occur when integrating with Veeam Backup & Replication when using “Backup to Tape” jobs with specific retention policies.

Issue Description

When using Veeam “Backup to Tape” jobs with an overwrite retention policy (where new backups overwrite previous data on the same tape), the system may encounter an issue with historical sessions.

Problem Details

• Root Cause: When the retention policy is set to overwrite previous data on the tape, older backup sessions may still contain information about previously copied objects.
• Result: This can lead to inconsistencies between the actual data available on tape and what is reported in the database.
• Impact: The Fenix DFA integration may display incorrect information about which objects were backed up in specific sessions.

Recommended Solution

To mitigate this issue, consider one of the following approaches:

1. Use Append Retention Policy: Configure your “Backup to Tape” jobs to use an append retention policy instead of overwrite, which adds new backups after existing data.
2. Adjust Database Queries: When integrating with Fenix DFA, ensure the database queries filter out superseded backup sessions.
3. Regular Catalog Synchronization: Perform regular catalog synchronization in Veeam to ensure the database accurately reflects the current tape contents.

Technical Details

When a tape is overwritten, the Veeam database may retain references to objects from previous backup sessions, even though these objects are no longer physically available on the tape. This can cause:

- Discrepancies between reported vs. available backup files
- Inaccurate restore point information
- Misleading backup coverage reporting

Additional Information

If you encounter this issue, please check your Veeam database logs for entries related to tape media overwrite operations and verify the retention policy settings for all “Backup to Tape” jobs.