This post is more than 5 years old
25 Posts
0
4952
April 16th, 2014 09:00
Second EBR Not Backing Up VMs
I have a case open for this issue that I'm having, but I thought I'd give the forum a try to see if you all have seen it before. So here's my setup:
:8.1.1 Networker with Data Domain (5.4)
:vcenter server on primary site with EBR configured
:vcenter server on DR site with EBR configured
: DR site also has Data Domain and a storage node
:vmware protection policy at primary is working fine as it uses the 1st EBR and DD
Problem:
;my EBR at the DR site is not working with its own vmware protection policy. it has it's own volume/pool that was created at the second DD. not sure exactly what i'm missing. here's the error that i get:
2014-04-15 20:59:20 avnwcomm Error <0000>: Received error from NetWorker connection attempt:
Error Code -7: no matching devices for save of client `proxy-02.domain.local'; check storage nodes, devices or pools
2014-04-15 20:59:20 avnwcomm Error <0000>: Failed connection to NetWorker server networkerserver.domain.local
2014-04-15 20:59:20 avnwcomm Warning <15188>: failed to process message type 11 snapup
2014-04-15 20:59:20 avnwcomm Error <6677>: Error processing CTL message "
2014-04-15 20:59:20 VMBackups-VA-1397609949089 Warning <0000>: [ctl_spawn] Workorder "VMBackups-VA-1397609949089" non-zero exit status 'code 3: No such process'
Here's what I've done so far to troubleshoot:
-DNS and/or communication are not an issue; i can ping/nslookup to/from all of the devices including the EBR proxy
-storage nodes, devices pools seem to be fine
Thanks in advance


TheStorageProto
27 Posts
0
April 17th, 2014 07:00
The main error is this "no matching devices for save of client `proxy-02.domain.local'; check storage nodes, devices or pools"
What needs to be checked:
a. The pool selected in the Backup action should be valid pool and should have no "Groups" selected in pool properties
b. The Destination storage node selected in the Action should be valid and should have some devices from this pool
c. The device selected in the pool should be valid and should be a Data domain device
Hope this helps!
Dustin21
7 Posts
1
May 21st, 2014 11:00
What one of these fixed your issue? I'm having the same problem with a setup pretty much like yours. I tried putting in the destination storage node for the VBA Backup, but it still does not work. Same error: "no matching devices for save of client `********'; check storage nodes, devices or pools" My EBR which is at the same DC as Networker server works just fine. Thanks in advanced.
Update: I figured it out. I had my NW server as the storage node inside of the EBR client in NW. I just had to change to to the storage node and it works now.
Ram.P
16 Posts
0
July 11th, 2015 07:00
Hi ,
I have so many backups failing with this errors:
can any 1 suggests anything :
We are currently on NW Version 8.1.1.5 and DD OS 5.4.5.0, the VBA is currently 1.0.1.9
With below all Hotfixes already installed in VBA and Proxies.
Extracted Lines:
2015-07-11 13:09:06 avnwcomm Error <0000>: Error connecting to NetWorker server.
2015-07-11 13:09:06 avnwcomm Error <0000>: Connection to NetWorker server timed out.
2015-07-11 18:00:28 avnwcomm FATAL <5889>: Fatal signal 11 in pid 7055
2015-07-11 18:00:28 avnwcomm Error <5891>: handlefatal: exiting thread pid=7055, sig=11
2015-07-11 18:00:28 avnwcomm FATAL <5889>: Fatal signal 6 in pid 7055
2015-07-11 18:00:28 avnwcomm Error <5891>: handlefatal: exiting thread pid=7055, sig=6
TheStorageProto
27 Posts
0
July 15th, 2015 07:00
This indicates a timeout waiting for a response from NetWorker server, generally caused by underlying performance problem on the NetWorker server. I would suggest to start checking if you have enough devices on the required pool where the backups go. Additonally, check for problems like 'peer information' errors that can cause delays in communication. The NetWorker VMware integration guide has a lot of information on how to process these.
Lastly, you can change the default timeout by following this: https://support.emc.com/kb/199042
Hope this helps!