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=eyJmaW5hbFJlZGlyZWN0TG9jYXRpb24iOiJodHRwczovL3d3dy52ZWVhbS5jb20va2IxMDc2IiwiaGFzaCI6IjM5ZWJmM2M0LTQxYzItNDczNi1iMDlkLTJjMzRhMDUwNTFkOCJ9
1-800-691-1991 | 9am - 8pm ET
EN

How to disable VBK rename with Reversed Incremental

Challenge

The VBK file when using Reversed Incremental changes after every job run.

Solution

Note: This function only works with Backup Jobs using Reversed Incremental.
 
Perform the following steps to alter Veeam to prevent the VBK from being renamed.
1.       Open Registry Editor to HKLM\Software\Veeam\Veeam Backup and Replication
2.       Create a DWORD named DisableVBKRename
3.       Set Value = 1
4.       Restart the Veeam Backup Server
 
Fig. 1

User-added image



This will cause the current VBK for the job to always be named after the job without a timestamp.
 
Fig. 2

User-added image

 

More information

This feature will only work for new jobs or jobs you do "Delete from disk"/"Remove from backups" to remove the historical data from the VeeamBackup DB.
 
If a new active full is created for any reason, the old VBK’s name will be appended with a timestamp and the new active full VBK will be named after the job without a timestamp (see Fig. 2).

 

KB ID:
1076
Product:
Veeam Backup & Replication
Version:
5.x, 6.x, 7.x, 8.x, 9.x
Published:
2011-07-19
Last Modified:
2020-08-13
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.
Your report was sent to the responsible team. Our representative will contact you by email you provided.
We're working on it please try again later