{"id":10452,"date":"2021-07-13T16:55:21","date_gmt":"2021-07-13T06:55:21","guid":{"rendered":"https:\/\/nsrd.info\/blog\/?p=10452"},"modified":"2021-07-13T16:55:24","modified_gmt":"2021-07-13T06:55:24","slug":"networker-basics-proxy-redeployment-using-nwui","status":"publish","type":"post","link":"https:\/\/nsrd.info\/blog\/2021\/07\/13\/networker-basics-proxy-redeployment-using-nwui\/","title":{"rendered":"NetWorker Basics \u2013 Proxy Redeployment using NWUI"},"content":{"rendered":"\n

NetWorker 19.3 introduced the option to redeploy VMware image-based backup proxies via the NWUI interface. Previously that functionality had been command-line driven — or you could delete a proxy, deploy it manually in vCenter, and register it in NMC.<\/p>\n\n\n\n

The main reason you redeploy<\/em> a proxy is in the event of a NetWorker upgrade. Sure, proxies are easy to deploy and, being stateless, can be deleted whenever you need, but having automation wrapped around proxy upgrades is certainly handy.<\/p>\n\n\n\n

So below, I’ve captured the end-to-end sequence of proxy redeployment.<\/p>\n\n\n\n

\"\"<\/a>
Starting Proxy Redeployment in NWUI<\/em><\/strong><\/figcaption><\/figure>\n\n\n\n

The process starts in the NWUI by going to Protection >> VMware Proxies<\/strong>. You’ll note there are two panels available: Proxies, and Tasks. We start in the Proxies area, select the proxy to be redeployed and click the ‘Redeploy’ button:<\/p>\n\n\n\n

\"\"<\/a>
Proxy Selected for Redeployment<\/em><\/strong><\/figcaption><\/figure>\n\n\n\n

When you initiate the redeployment, you’ll note that you can view your existing proxy version and adjust some settings relating to the deployment. You’re also told where the new proxy OVA file needs to reside on the NetWorker server. For a Linux NetWorker server, that’s \/nsr\/vproxy_ova\/ovas<\/strong>. At the time I did the redeployment, I didn’t grab a screen-shot of that area, but here’s one I grabbed afterwards:<\/p>\n\n\n\n

\"\"<\/a>
Storing the new vProxy OVA in the correct path for NetWorker<\/em><\/strong><\/figcaption><\/figure>\n\n\n\n

When you’re ready to redeploy the proxy in the wizard, you’ll get a confirmation prompt:<\/p>\n\n\n\n

\"\"<\/a>
Proxy redeployment confirmation<\/em><\/strong><\/figcaption><\/figure>\n\n\n\n

Once you’ve confirmed, the proxy redeployment process kicks off. You can watch that in the Tasks panel, which I’ll get to in a moment, but first I wanted to show how the redeployment starts showing up in the Server Messages area of the NWUI’s Monitoring panel. You can see the initial message below that NetWorker has disabled the proxy to avoid it being selected for backup\/recovery operations until the redeployment is complete:<\/p>\n\n\n\n

\"\"<\/a>
NetWorker Server Messages showing Redeployment in Progress<\/em><\/strong><\/figcaption><\/figure>\n\n\n\n

Likewise, jumping briefly to the vCenter UI shows the deployment in progress:<\/p>\n\n\n\n

\"\"<\/a>
Proxy Redeployment in Progress as Seen from the vCenter Console<\/em><\/strong> <\/figcaption><\/figure>\n\n\n\n

Back to the NWUI, and in the Protection >> VMware Proxies >> Tasks<\/strong> panel, I can see NetWorker keeping me updated on the progress:<\/p>\n\n\n\n

\"\"<\/a>
Proxy Redeployment Task Progress<\/em><\/strong><\/figcaption><\/figure>\n\n\n\n

And once the redeployment finishes, the task view is updated thusly:<\/p>\n\n\n\n

\"\"<\/a>
Proxy Redeployment Complete<\/em><\/strong><\/figcaption><\/figure>\n\n\n\n

The proxy appears as normal in the Proxies panel after the task has completed:<\/p>\n\n\n\n

\"\"<\/a>
Back to normal<\/em><\/strong><\/figcaption><\/figure>\n\n\n\n

And once the deployment was finished, it was time to run a backup:<\/p>\n\n\n\n

\"\"<\/a>
Post-Redeployment Backup using Proxy<\/strong><\/em><\/figcaption><\/figure>\n\n\n\n

And there you go — the redeployment of a proxy following a NetWorker upgrade within the NWUI.<\/p>\n","protected":false},"excerpt":{"rendered":"

NetWorker 19.3 introduced the option to redeploy VMware image-based backup proxies via the NWUI interface. Previously that functionality had been…<\/p>\n","protected":false},"author":1,"featured_media":7113,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_feature_clip_id":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2},"jetpack_post_was_ever_published":false},"categories":[16,1357],"tags":[1620,1164,1053,1359],"class_list":["post-10452","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-networker","category-vproxy","tag-deployment","tag-proxy","tag-upgrade","tag-vproxy"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t