Empty Folder(s) in Datastore after Replication job runs

KB ID: 1793
Product: Veeam Backup & Replication
Version: 6.x, 7.x
Published: 2013-07-19
Last Modified: 2020-08-13
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.

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.

Challenge

When a replication job is ran, an empty folder is created in one of the datastores listed as the <Replica’s VM name>_#. 

Cause

The cause of this behavior is Veeam getting pointed to write to one datastore, while the replica VM itself is on a different datastore. When the job is pointed to a different location than the replication job is setup to process to, a folder gets created to hold the data on that datastore because it does not see anything there. Once it goes to write the data and work with the replica, it finds the correct location via the reference ID of the replica VM.

Solution

The solution to this is to verify the datastore location in VMware, and then edit the replication job to match this. After doing this, you can delete the empty folders, though it is highly advised to check each folder individually before deletion to verify they are in fact all empty. 

More information

In the situation where the VM has been moved to a different standalone host (this does not apply when replicating to a cluster or vCenter) than it was specified, it is very likely that the replication will fail the first time, and when it is then mapped to the replication job via the Low Bandwidth Seeding options the job will be successful. The folders will then be created like in the above description, but files that are copied over via the NFC Connection Stream will be in those folders (The VMX, VMFX, NVRAM).
 
In this situation, make the above change to the replication job, but prior to deleting the folders, let the job run successfully once and make sure the original folder has it’s VMX, NVRAM, and VMFX files updated.  
Click here to send feedback regarding this KB, or suggest content for a new KB.
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 reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please try again later.

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 reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
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
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please try again later.