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

Using Rsync to Copy Backup Files Offsite

KB ID: 1193
Product: Veeam Backup & Replication
Version: 5.x
Published: 2011-10-06
Last Modified: 2020-08-13

Challenge

When using Rsync as a post job activity to copy backup files to an offsite location one of the problems that is encountered is that after the second backup is using reverse incremental, Rsync copies all the data from the vbk file one more time, and not just the changes from the last backup.

Cause

The cause of this behavior is every time the VBR job runs, it updates the file name of the vbk file. This causes Rsync to see it as 2 different files and sends all the data.

Solution

Start the registry editor on the server which has Veeam Backup & Replication 5.0.1 or later installed, then:

1. Browse to HKEY_LOCAL_MACHINE\SOFTWARE\VeeaM\Veeam Backup and Replication
2. Create DWORD = DisableVBKRename
3. Set Value = 1
4. Restart Veeam Backup Server 

Perform a new full backup and then the filename of the VBK will  not change anymore. This will resolve the issue.

KB ID: 1193
Product: Veeam Backup & Replication
Version: 5.x
Published: 2011-10-06
Last Modified: 2020-08-13

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.