This post is more than 5 years old
61 Posts
0
2322
July 25th, 2012 13:00
VADP restore is not using the VADP proxy
Hello,
I did a quick search of the forums, but didnt seem to find anything along these lines. I have a new deployment of networker 7.6.3 for windows. it involves 2 sites (one datazone). the remote site has our NWserver a virtual storage node for VADP and a datadomain box.
Our home office has a physcial storage node, a virtual storage node (again for vadp backups) and annother data domain box.
I can backup and restore these with no problem at our datacenter, i am using NBD as my transport mode, 60-80mpbs backup/restore throughput.
When i backup at our home office, i get great through put 50-60mbps for our backup, and it IS going to the DDbox at our home office. the device its referencing is a remote device and i verified the config. rd=vadpnode:ddbox_space, at our home office and the disk volume is infact in our home office. the device access info is ddbox:/nwserver/ddbox_space
What is odd is when i attempt to RESTORE the image (these are test images btw, base windows installs) i get around 1mbps. I set the VADP storage node at the home office as the backup/restore node in the client settings, but i dont see ANY activity, network or processor on the VADP proxy. This leads me to belive its hopping the pipe we have between sites and hitting our networker server to do all of the work. I thought that i might have to innitiate the restore of the saveset from the vadp storage node, but when i bring it up, i have nothing from ANY of my VM backups listed there.
If anyone has an idea of anything to check i would apprecaite your input.
NetworkSupport-
61 Posts
0
July 31st, 2012 12:00
Ok,
I just had a tech jump in and take a look at my configuration. Although i did have a few instances of the vadp backup systems, they did infact have the same ID. The issue was that under Gloabal2 SYSTEM@(VADPSERVER) was not sufficient as far as permissions went. once he configured it as *@VADPSERVER the savesets apeared within the VADP networker user list. Also, if you are using a VADP proxy it is absolutely supposed to be launched from the VADP proxy (as long as its also a storage node). changing system to * allowed the networker user on the VADP system to see the save sets.
coganb
736 Posts
0
July 26th, 2012 04:00
Hi,
AFAIK, the 'recover storage node' attribute of the client that you are recovering should define which Storage Node is being used for the recover operation. I'm not sure why it's not working for you. Is there only one VM affected by this or all of them? You should check your name resolution aswell to be sure that the entry in that field is being correctly resolved.
-Bobby
NetworkSupport-
61 Posts
0
July 26th, 2012 05:00
As this is a new deployment and i have been concentrating on getting the backups functional, this was the first full vm restore i have done. The rest are actual systems and i dont care to delete their datastores if i cannot restore them in under 2 days
.
here is a screencap of the config for the test system im working with. the VADP storage node local to the home office is the VUSVADP02 as listed in the storage node and recover storage nodes.
coganb
736 Posts
0
July 26th, 2012 06:00
I had a look at the documentation and neither of the two conditions that override the 'recover storage node' field are met in this scenario (read hostname field for a jukebox, and a volume already being mounted on another storage node). If I were you, I'd test the non-VADP behaviour if you can to see if what you are seeing is specific to VADP. Also, you could try changing the 'recover storage node' field of the NetWorker server's client instance and the proxy's client instance just to see if this changes the behaviour. It might give you a better understanding of what's going on.
-Bobby
NetworkSupport-
61 Posts
0
July 26th, 2012 07:00
Good idea,
I did a redirected restore from the networker server. i had it restore a 3Gb iso image from one system and applied it to another. it flew by in about 25 seconds at 40mbps (ish).
just for fun, once i have an opportuinity to try the restore again, i will set the recovery storage node to the physical node at the home office and see if that gives me any changes.
NetworkSupport-
61 Posts
0
July 26th, 2012 08:00
Well changing the restore node to the physical node for VADP did nothing.
I want to ask a different question here. Under the manual i saw that it said "restoring to virtual center server". Well our virtual center server is across the WAN connection to our datacenter. the ESXI hosts in our dev environment are at our home office... shoudl i be attempting to restore this in a different manner? EG is there a way to push it directly onto the ESXI host or datastore?