https://login.veeam.com/en/oauth?client_id=nXojRrypJ8&redirect_uri=https%3A%2F%2Fwww.veeam.com%2Fservices%2Fauthentication%2Fredirect_url&response_type=code&scope=profile&state=eyJmaW5hbFJlZGlyZWN0TG9jYXRpb24iOiJodHRwczovL3d3dy52ZWVhbS5jb20va2I0MDQ4IiwiaGFzaCI6IjcxZmVkYTc5LTRjOTUtNGYyZi04Yzc0LWFmMTJhMmJlZTQzMSJ9
1-800-691-1991 | 9am - 8pm ET
EN
 

Configuring Overland Tandberg RDX based storage as a backup repository

Challenge

To fulfill the 3-2-1 rule’s requirement for an offsite backup, a repository backed by an Overland Tandberg RDX removable storage media has been used. The action of swapping to a new medium causes Veeam Backup & Replication jobs failure due to inability to find the previous backup file(s).

Cause

By default, in case some of the previous backup files in the backup chain are missing, the job fails due to backup chain inconsistency.

Solution

To support RDX changeable media, additional configuration steps are required to let Veeam Backup & Replication know that rotated drives are used. Please enable the rotated drives option in the repository settings.

Please consider limitations incurred by the usage of backup repositories with rotated drives and considerations outlined in this KB article.

KB ID:
4048
Product:
Veeam Backup & Replication
Published:
2020-11-12
Last Modified:
2020-12-03
Please rate how helpful this article was to you:
5 out of 5 based on 1 ratings
Thank you for helping us improve!
An error occurred during voting. Please try again later.

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.
Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text

Knowledge base content request
By submitting, you agree that your personal data will be managed by Veeam in accordance with the Privacy Policy.

ty icon

Thank you!

We have received your request and our team will reach out to you shortly.

OK

error icon

Oops! Something went wrong.

Please go back try again later.