#1 Global Leader in Data Resilience

Backup to NFS repository may hang

KB ID: 3131
Product: Veeam Backup & Replication
Version: 10
Published: 2020-03-23
Last Modified: 2020-08-13
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.

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 the backup job starts, some task may hang if all of the following conditions are met:
  • The backup repository type is the NFS repository.
  • A Linux server is selected as a gateway server explicitly or it was selected by the automatic selection from options.
  • NFS v3 is used to access the NFS repository.
In this case, the target agent log shows the "There was no finalized server sessions during the last 60 minutes." message, for example:
[29.10.2019 14:03:20.405] <140689077683968> stg| Opening storage [/mnt/Veeam/{d19c5d30-90a5-4d77-a9a0-3f59727a49c6}/<Job name>/<Backup file name>.vib] for read/write access.
[29.10.2019 14:03:20.406] <140689077683968> stg|   Opening storage file [HostFS:///mnt/Veeam/{d19c5d30-90a5-4d77-a9a0-3f59727a49c6}/<Job name>/<Backup file name>.vib.vib].
[29.10.2019 14:03:20.406] <140689077683968> stg|     Applying exclusive lock on file [/mnt/Veeam/{d19c5d30-90a5-4d77-a9a0-3f59727a49c6}/<Job name>/<Backup file name>.vib.vib].
[29.10.2019 14:23:20.405] <140689069291264> cli| WARN|MTA invoke thread : timed out for backup events. Wait cycle will be resumed for '336' hours.
[29.10.2019 15:03:07.707] <140689469306624> srv|   There was no finalized server sessions during the last 60 minutes.
[29.10.2019 16:03:07.715] <140689469306624> srv|   There was no finalized server sessions during the last 60 minutes.

Cause

Access to nlockmanager is not configured on the NFS server.

Solution

Make sure that all required ports are configured properly:
 
TCP and UDP port 2049 for NFS.
TCP and UDP port 111 (rpcbind/sunrpc).
TCP and UDP port specified with MOUNTD_PORT
TCP and UDP port specified with STATD_PORT
TCP port specified with LOCKD_TCPPORT
UDP port specified with LOCKD_UDPPORT

 
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
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please, try again later.