Preskočiť na hlavný obsah
Odhlásiť sa

Vitajte v spoločnosti Dell!

Moje konto
  • Zadávajte objednávky rýchlo a jednoducho
  • Pozrite si svoje objednávky a sledujte priebeh doručenia
  • Vytvorte si zoznam svojich produktov a majte ho vždy poruke
  • Spravujte svoje lokality Dell EMC, produkty a kontaktné informácie na úrovni produktov pomocou Správy informácií o spoločnosti.
Prihlásiť sa Vytvoriť konto Prihlásenie na stránky Premier Prihlásenie do partnerského programu
Kontaktujte nás

Číslo článku: 000197385

NVP vProxy: How To Upgrade the NVP vProxy Appliance using nsrvproxy_mgmt

Zhrnutie: This KB provides a general overview of how to upgrade the NVP vProxy appliance from the NetWorker 19.x (or later) NetWorker server.

Je možné, že tento článok bol preložený automaticky. Ak máte nejaké pripomienky ku kvalite prekladu, pošlite nám ich prostredníctvom formulára naspodku stránky.

Obsah článku

Pokyny

The NetWorker NVP vProxy appliance can be upgraded directly from the NetWorker server operating system. The process no longer involves deleting and re-creating the vProxy VM manually from within VMware. This process still occurs; however, is automated by using the nsrvproxy_mgmt command on the NetWorker server. This uses a local repository to redeploy one or multiple vProxies. 

The process for manually replacing or upgrading a vProxy appliance is detailed in: 

NVP-vProxy: How-To Manually Upgrade / Redeploy vProxy

Limitations

  • Concurrent vProxy redeployment is not supported using CLI; However, you can sequentially redeploy multiple vProxies using a script.
  • vProxy redeployment is not supported for vProxies that are directly deployed in the ESXi bypassing the vCenter. If the vProxy is deployed on the ESXi bypassing the vCenter, then you must manually redeploy the vProxy.
  • The root and admin password length of the vProxy should be in between 8–20 characters only. Before redeployment, you must change the root and admin password and update the vProxy resource in NetWorker with the updated vProxy admin password.
  • Deploying new vProxies using CLI is not supported.
  • During vProxy redeployment, the manual settings that were performed on the previous vProxy are not retained.

Process

1. Download the vProxy OVA you want to deploy from: https://www.dell.com/support/home/product-support/product/networker/driver
2. On the NetWorker server, create the following directory:
Linux: /nsr/vproxy_ova/ovas
Windows: C:\Program Files\EMC NetWorker\nsr\vproxy\vproxy_ova\ovas\
NOTE: This is the repository location that is used to redeploy the vProxy appliance. In Windows, you must manually create the ovas folder. On Linux, you must manually create the vproxy_ova/ovas directory.
3. Place the extracted OVA file in the ovas directory.
4. Open an administrative or root command prompt on the NetWorker server.
5. For a single vProxy deployment, open a command prompt on the NetWorker Server, and then run the
nsrvproxy_mgmt command in the following format: 
nsrvproxy_mgmt redeploy -h vProxy-host-name -z vProxy-root-password [-x] [-
f] [-u comments] [-t timeout in minutes] [-D debug-level]
Where:
● -t specifies the maximum timeout value for any active vProxy session to get over and then start the redeployment.   The default timeout value is ten minutes.
● -x can be used when the vProxy admin password is same as that of root of existing vProxy.
● -z is used when specifying the vProxy root password of existing vProxy.
● -h vProxy-host-name is the vProxy name that was used for registration and exists in the RAP resource.
● -f is used to disable the confirmation prompt.
● -D is used to set the debug level. By default, the debug level is 0.
● -u is used to display the comments.
 
NOTE: The vProxy hostname value must be specified as it is configured in the NMC. Meaning, if vProxy is registered with short-name, user the short name for the -h value; otherwise, if vProxy was registered using the FQDN, specify the FQDN for the -h value.
6. If redeploying multiple vProxies, sequential redeployment can be accomplished by creating a .bat (Windows) or .sh (Linux) script on the NetWorker server. The script can then be run from an administrative or root command prompt.

Windows .bat script would contain something like: 
nsrvproxy_mgmt redeploy -h blrv027b075 -z Welcome@123 -f
nsrvproxy_mgmt redeploy -h blrv027b076 -x -f
nsrvproxy_mgmt redeploy -h blrv027b077 -z P@ssw0rd123 -f
A Linux .sh script would contain something like: 
#!/bin/bash
nsrvproxy_mgmt redeploy -h blrv027b075 -z Welcome@123 -f
nsrvproxy_mgmt redeploy -h blrv027b076 -x -f
nsrvproxy_mgmt redeploy -h blrv027b077 -z P@ssw0rd123 -f


 

Ďalšie informácie

Logs:

Troubleshooting Logs Table
Log File Location on NetWorker Server Description
<job-uuid>.log 
  • Linux: /nsr/logs/adhoc/nsrvproxy_mgmt/
  • Windows: C:\Program Files\EMC NetWorker\nsr\logs\adhoc\nsrvproxy_mgmt\
 vProxy management job log file is created.
During the redeployment of the associated
vProxy.
vproxy_upgrade_sessio
n_<vProxyidentifier>_<
jobuuid>
  • Linux: /nsr/logs/adhoc/nsrvproxy_mgmt/
  • Windows: C:\Program Files\EMC NetWorker\nsr\logs\adhoc\nsrvproxy_mgmt\
 Associated nsrvisd log file is created during redeployment of the vProxy.
nsrvisd-daemon.log
  • Linux: /opt/nsr/vproxy/logs/nsrvisd/
  • Windows: C:\Program Files\EMC NetWorker\nsr\vproxy\logs\nsrvisd\
 Associated nsrvisd detailed log file is created.
ProxySessions-<uuid> .log
  • Linux: /nsr/logs/adhoc/nsrvproxy_mgmt/
  • Windows: C:\Program Files\EMC NetWorker\nsr\logs\adhoc\nsrvproxy_mgmt\
 Associated ProxySessions log file is created during redeployment of the vProxy.
Nsrvisd logs
  • Linux: /opt/nsr/vproxy/logs/nsrvisd
  • Windows: C:\Program Files\EMC NetWorker\nsr\vproxy\logs\nsrvisd\
 Associated inventory sessions log file is created.

Vlastnosti článku

Dotknutý produkt

NetWorker

Produkt

NetWorker Family, NetWorker Series, VMware

Dátum posledného zverejnenia

13 júl 2023

Verzia

9

Typ článku

How To

Späť na začiatok