1-800-691-1991 | 9am - 8pm ET
EN

Path to NFS datastore has been changed after upgrade to Veeam Backup & Replication U4

KB ID: 2881
Product: Veeam Backup & Replication
Version: 9.5.4.x
Published: 2019-01-31
Last Modified: 2021-11-12
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's 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.

Challenge

After upgrading to Veeam Backup & Replication U4, Veeam vPower NFS datastore location might be changed.

Cause

The NFS datastore path having changed is a known issue in the Veeam Backup & Replication U4. Starting with Update 4, the disk with the largest capacity is selected by default to be used as the NFS datastore location.

Solution

Review each Repository's Mount Server settings and adjust the "Instant recovery write cache folder" as needed.

More Information

If the IRCache path specified is invalid, it may cause the upgrade error documented in KB4166
"Error 1327. Invalid Drive: [a-z]:\"
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 Policy.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Thank you for your interest in Veeam products!
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.