#1 Global Leader in Data Resilience
#1 Global Leader in Data Resilience
BACK TO KB LIST

How to Disable the Renaming of Reversed Incremental VBK File

KB ID: 1076
Product: Veeam Backup & Replication | 5.0 | 6.1 | 6.5 | 7.0 | 8.0 | 9.0 | 9.5 | 10 | 11 | 12 | 12.1 | 12.2
Published: 2011-07-19
Last Modified: 2024-10-15
mailbox
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

error icon

Oops! Something went wrong.

Please, try again later.

Article Applicability

This article is related to the automatic renaming of the VBK file, which occurs only when using Reverse Incremental backup mode.

Note: Reverse Incremental as a backup mode will begin being deprecated starting in version 13 of Veeam Backup & Replication.
For more information, review Veeam R&D Forums: [V13] Deprecated and discontinued features for our 2025 release

Purpose

This article documents how to disable the automatic renaming of the VBK file when using Reverse Incremental.

Solution

To disable automatically renaming the VBK file associated with a Backup Job using Reverse Incremental, create the following registry value on the Veeam Backup Server.

Key Location: HKLM\Software\Veeam\Veeam Backup and Replication
Value Name: DisableVBKRename
Value Type: DWORD (32-Bit) Value
Value Data: 1

Note: No reboot is needed. This registry value will affect jobs immediately and become effective when a job next creates a new Active Full.

PowerShell command to create this registry value:

New-ItemProperty -Path 'HKLM:\SOFTWARE\Veeam\Veeam Backup and Replication\' -Name 'DisableVBKRename' -Value "1" -PropertyType DWORD -Force
Screenshot of the impact of this setting:
Note how the VBK file's name no longer contains a datestamp that needs updating each time the job runs.
example

More Information

If a new Active Full is created for any reason, the old VBK’s name will be appended with a timestamp.
To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please, try again later.

You have selected too large block!

Please try select less.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case
By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Start using Veeam:
Download the product
&
Activate the license key
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please, try again later.