Host-based backup of VMware vSphere VMs.
Post Reply
guest52
Novice
Posts: 8
Liked: never
Joined: Sep 11, 2013 9:15 am
Full Name: Vyacheslav
Contact:

Did not get to configure SureJob

Post by guest52 »

Hi!
I have:
a cluster of ESXi 5.1 (hosts are in a subnet 10.81.17.xxx, Veeam server and repository are in a subnet 10.81.10.xxx).
Veeam Backup Server
Veeam Backup Repository (Windows 2008r2, named "vbr-01")
When I do a Sure Backup job, I get the error: "Fail Error: Unable to mount vPower NFS volume (vbr-01.xxx.domain.local:/VeeamBackup_vbr-01.xxx.domain.local). vbr-01.xxx.domain.local: An error occurred during host configuration.
10.xx.xx.xxx: An error occurred during host configuration."

When I created a repository, I did settings that:
Image
Image

Folders on Veeam Backup Repository:
Image

Services on Veeam Baskup Repository:
Image

SureBackup job Statistics:
Image


What am I doing wrong?
nefes
Veeam Software
Posts: 643
Liked: 162 times
Joined: Dec 10, 2012 8:44 am
Full Name: Nikita Efes
Contact:

Re: Did not get to configure SureJob

Post by nefes »

Your problem is related to mounting NFS datastore to the selected ESX(i) host.
Please review this KB article, it provides steps to troubleshoot such problems: http://www.veeam.com/kb1055
guest52
Novice
Posts: 8
Liked: never
Joined: Sep 11, 2013 9:15 am
Full Name: Vyacheslav
Contact:

Re: Did not get to configure SureJob

Post by guest52 »

nefes wrote:Your problem is related to mounting NFS datastore to the selected ESX(i) host.
Please review this KB article, it provides steps to troubleshoot such problems: http://www.veeam.com/kb1055
I saw this KB. I have completed checks in accordance with this KB.
All ports in network is the open.

Explanations:
VBRS-01 -- Veeam BaR Server.
VBR-01 -- Veeam BaR Repository.

I create a virtual lab, application group and surebackup job. After this, in ESXi-host inventory I see a new datastore (from VBRS-01 -- Veeam BaR Server).

Datastores after creating Virtual Lab:
Image

I run the Surebackup Job for the first time and get the error, which can be seen in the work of 13:33:34 (pls, see a report screenshot). Network settings set manually (using the DHCP I have the same problem). I start work without changing any of the settings for the second time, and I get an error that can be seen in the work of 14:31:21. Why Veeam is trying to connect a NFS that is VBR-01 (Veeam BaR Repository)? Why errors are different?

Errors:
Image
nefes
Veeam Software
Posts: 643
Liked: 162 times
Joined: Dec 10, 2012 8:44 am
Full Name: Nikita Efes
Contact:

Re: Did not get to configure SureJob

Post by nefes »

First error from your log at 13:34 tells that Veeam B&R server could not ping Proxy Appliance VM.
According to the fact that second time you have not seen that error, I would say that some temporary network issues occured.
Second time your job failed with the same NFS problem.
Let me try to explain NFS mechanism in little more details.
Every Backup Repository server have its own NFS server, which can be chosen in Backup Repository wizard.
When you begin SureBackup Job which use some backups, Veeam need to mount NFS Share directly to ESX where that VMs would be started.
In your case backups resides on VBR-01 and it is set up to use itself as NFS server. So VeeamBackup_..._VBR-01 should be mounted to the host, not VeeamBackup_..._VBRS-01 like it shown on your screenshot.
foggy
Veeam Software
Posts: 21069
Liked: 2115 times
Joined: Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson
Contact:

Re: Did not get to configure SureJob

Post by foggy »

Yep, you've specified VBR-01 server to serve as vPower NFS server while creating the repository on it (according to the screenshot in you original post). vPower NFS datastore that you see already mounted to the host is a different datastore, configured on your default backup repository (which is installed as a part of Veeam B&R installation on the backup server itself, VBRS-01).

Have you tried to mount that vPower NFS datastore manually, as described in the mentioned KB article? Anyway, you can contact technical support with this (as it is advised to do with all technical issues) and get assistance in your native language (I'm also removing the "Russian" part of your post, since these forums are for English-speaking users). Thanks.
guest52
Novice
Posts: 8
Liked: never
Joined: Sep 11, 2013 9:15 am
Full Name: Vyacheslav
Contact:

Re: Did not get to configure SureJob

Post by guest52 »

nefes wrote: In your case backups resides on VBR-01 and it is set up to use itself as NFS server. So VeeamBackup_..._VBR-01 should be mounted to the host, not VeeamBackup_..._VBRS-01 like it shown on your screenshot.
Thanks!
But SureBackUp Job start only when I chose "Use this server" (VBRS) in vPower NFS settings.....

Network errors has been resolved after changing Network Settings in vLab.
foggy
Veeam Software
Posts: 21069
Liked: 2115 times
Joined: Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson
Contact:

Re: Did not get to configure SureJob

Post by foggy »

guest52 wrote:But SureBackUp Job start only when I chose "Use this server" (VBRS) in vPower NFS settings.....
Not sure I understand what do you mean here. Do you have vPowerNFS server configured on your repository server (VBR-01)? Have you tried to mount that vPower NFS datastore manually?
guest52
Novice
Posts: 8
Liked: never
Joined: Sep 11, 2013 9:15 am
Full Name: Vyacheslav
Contact:

Re: Did not get to configure SureJob

Post by guest52 »

foggy wrote: Not sure I understand what do you mean here. Do you have vPowerNFS server configured on your repository server (VBR-01)? Have you tried to mount that vPower NFS datastore manually?
Sorry for the late answer.

No, that vPower NFS Datastore not mount manually... BUT: this configuration works after I recreate Veeam BackUp repository and move Veeam BackUp repository in the same network as ESXi-hosts and Veeam BaR Server.

But in another sites I still get this error... "Unable to mount vPower NFS volume (VeeamBackupRepository.domain.local:/VeeamBackup_VeeamBackupRepository.domain.local). VeeamBackupRepository.domain.local: An error occurred during host configuration.
VeeamBackupRepository's IP: An error occurred during host configuration"

...and this vPower NFS share don't connect manually. ESXi-hosts and Veeam servers are in the same network.

All ports in network is open. No firewall.
Veeam vPower NFS Service is started.

Netstat's outputs:

netstat -a:

Code: Select all

Active Connections

  Proto  Local Address          Foreign Address        State
  TCP    0.0.0.0:111            VeeamBackupRepository:0        LISTENING
  TCP    0.0.0.0:135            VeeamBackupRepository:0        LISTENING
  TCP    0.0.0.0:445            VeeamBackupRepository:0        LISTENING
  TCP    0.0.0.0:1058           VeeamBackupRepository:0        LISTENING
  TCP    0.0.0.0:2049           VeeamBackupRepository:0        LISTENING
  TCP    0.0.0.0:2701           VeeamBackupRepository:0        LISTENING
  TCP    0.0.0.0:3389           VeeamBackupRepository:0        LISTENING
  TCP    0.0.0.0:6160           VeeamBackupRepository:0        LISTENING
  TCP    0.0.0.0:6161           VeeamBackupRepository:0        LISTENING
  TCP    0.0.0.0:6162           VeeamBackupRepository:0        LISTENING
  TCP    0.0.0.0:47001          VeeamBackupRepository:0        LISTENING
  TCP    0.0.0.0:49152          VeeamBackupRepository:0        LISTENING
  TCP    0.0.0.0:49153          VeeamBackupRepository:0        LISTENING
  TCP    0.0.0.0:49154          VeeamBackupRepository:0        LISTENING
  TCP    0.0.0.0:49155          VeeamBackupRepository:0        LISTENING
  TCP    0.0.0.0:49174          VeeamBackupRepository:0        LISTENING
  TCP    0.0.0.0:49180          VeeamBackupRepository:0        LISTENING
  TCP    10.47.157.19:139       VeeamBackupRepository:0        LISTENING
  TCP    10.47.157.19:445       guest52:58745        ESTABLISHED
  TCP    10.47.157.19:3389      guest5258744        ESTABLISHED
  TCP    10.47.157.19:6160      Veeam_BaR_Server:60365   ESTABLISHED
  TCP    10.47.157.19:6161      Veeam_BaR_Server:60366   ESTABLISHED
  TCP    10.47.157.19:50133     Server_SCCM-01:10123    ESTABLISHED
  TCP    10.47.157.19:51647     10.81.98.127:1688      SYN_SENT
  TCP    127.0.0.1:1550         VeeamBackupRepository:0        LISTENING
  TCP    127.0.0.1:1551         VeeamBackupRepository:0        LISTENING
  TCP    127.0.0.1:30523        VeeamBackupRepository:0        LISTENING
  TCP    127.0.0.1:51627        VeeamBackupRepository:0        LISTENING
  TCP    127.0.0.1:62501        VeeamBackupRepository:0        LISTENING
  TCP    [::]:135               VeeamBackupRepository:0        LISTENING
  TCP    [::]:445               VeeamBackupRepository:0        LISTENING
  TCP    [::]:2701              VeeamBackupRepository:0        LISTENING
  TCP    [::]:3389              VeeamBackupRepository:0        LISTENING
  TCP    [::]:6160              VeeamBackupRepository:0        LISTENING
  TCP    [::]:6161              VeeamBackupRepository:0        LISTENING
  TCP    [::]:6162              VeeamBackupRepository:0        LISTENING
  TCP    [::]:47001             VeeamBackupRepository:0        LISTENING
  TCP    [::]:49152             VeeamBackupRepository:0        LISTENING
  TCP    [::]:49153             VeeamBackupRepository:0        LISTENING
  TCP    [::]:49154             VeeamBackupRepository:0        LISTENING
  TCP    [::]:49155             VeeamBackupRepository:0        LISTENING
  TCP    [::]:49174             VeeamBackupRepository:0        LISTENING
  TCP    [::]:49180             VeeamBackupRepository:0        LISTENING
  UDP    0.0.0.0:111            *:*                    
  UDP    0.0.0.0:123            *:*                    
  UDP    0.0.0.0:500            *:*                    
  UDP    0.0.0.0:1058           *:*                    
  UDP    0.0.0.0:2049           *:*                    
  UDP    0.0.0.0:4500           *:*                    
  UDP    0.0.0.0:5355           *:*                    
  UDP    0.0.0.0:15000          *:*                    
  UDP    10.47.157.19:137       *:*                    
  UDP    10.47.157.19:138       *:*                    
  UDP    127.0.0.1:51763        *:*                    
  UDP    127.0.0.1:62113        *:*                    
  UDP    127.0.0.1:62115        *:*                    
  UDP    127.0.0.1:62759        *:*                    
  UDP    [::]:123               *:*                    
  UDP    [::]:500               *:*                    
  UDP    [::]:4500              *:*                    
netstat -b:

Code: Select all

Active Connections

  Proto  Local Address          Foreign Address        State
  TCP    10.47.157.19:445       guest52:58745        ESTABLISHED
 Can not obtain ownership information
  TCP    10.47.157.19:3389      guest52:58744        ESTABLISHED
  TermService
 [svchost.exe]
  TCP    10.47.157.19:6160      Veeam_BaR_Server:60365   ESTABLISHED
 [VeeamDeploymentSvc.exe]
  TCP    10.47.157.19:6161      Veeam_BaR_Server:60366   ESTABLISHED
 [VeeamNFSSvc.exe]
  TCP    10.47.157.19:50133     Server_SCCM-01:10123    ESTABLISHED
 [CcmExec.exe]
netstat -n:

Code: Select all

Active Connections

  Proto  Local Address          Foreign Address        State
  TCP    10.47.157.19:445       10.81.10.209:58745     ESTABLISHED
  TCP    10.47.157.19:3389      10.81.10.209:58744     ESTABLISHED
  TCP    10.47.157.19:6160      10.47.157.18:60365     ESTABLISHED
  TCP    10.47.157.19:6161      10.47.157.18:60366     ESTABLISHED
  TCP    10.47.157.19:50133     10.81.10.146:10123     ESTABLISHED
Network settings of vLab's:
Image
foggy
Veeam Software
Posts: 21069
Liked: 2115 times
Joined: Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson
Contact:

Re: Did not get to configure SureJob

Post by foggy »

Vyacheslav, I encourage you to contact support for assistance, since troubleshooting such technical issues via forum posts is very inefficient. Our support folks will be able to set up a webex with you to review your configuration.
Post Reply

Who is online

Users browsing this forum: Google [Bot] and 78 guests