(Agent‑less Linux/Windows PNs) Enroll protected nodes

onQ supports both agent‑based and agent‑less PNs. To protect agent‑less PNs, you indirectly enroll PNs by enrolling the ESX/ESXi server itself. onQ’s VMware Real Agentless protection provides the following benefits:

•	No PN CPU utilization.

•	Easier deployment in a VMware environment.

•	No need to test or revalidate servers due to the introduction of new software.

•	No need to worry about voiding vendor contracts or support due to installing agent‑based software.

However, before you deploy agent‑less PNs, consider the tradeoffs outlined in Agent‑less PN Enrollment Limitations.

VMware‑hosted nodes, whether Windows or Linux, do not require that an agent (onQ Service) be installed on the PN. Instead, two PN proxies will be automatically installed on the ESX/ESXi server (aka Proxy Host) when you enroll that ESX/ESXi server: one Linux PN proxy (LPY_<onQhostname>_<ESXhostname>) and one Windows PN proxy (WPY_<onQhostname>_<ESXhostname>) for each onQ. All PNs on a given ESX/ESXi server and having the same operating system (Linux or Windows) will share a common PN proxy.

Using these proxies, the onQ’s backup utility works with VMware Snapshot to back up the PNs to the HA Appliance.

Note:  If you need to rename the onQ host name, you will need to perform the steps outlined in Modify Appliance’s network settings.

To enroll an agent‑less PN:

1.	Reserve two static IP address, one for the Windows PN proxy and one for the Linux PN proxy.

2.	Log on to the HA Appliance’s onQ Portal.

3.	Click the PROTECTION CONFIG tab.

4.	Click the double‑plus button (++).

The Add Protected Nodes via Host dialog appears.

5.	Provide the credentials and either the hostname or the IP address for the ESXi/ESX host, then GET LIST.

The onQ Portal queries the virtual machines hosted by the ESXi/ESX server, then displays the inventory.

6.	Install the PN proxies and enroll the PNs.

a.	In the virtual machine list, select the check boxes (or ALL button) for the PNs that you want to enroll. If you do not see a virtual machine does not appear in the list, it’s likely that the virtual machine does not have VMware Tools installed.

b.	Provide the following information to install the proxies:

•	Windows proxy address. The state IP address that you reserved for the Windows PN proxy.

•	Linux proxy address. The state IP address that you reserved for the Linux PN proxy.

•	Proxy subnet mask.

•	Proxy gateway.

•	Proxy VM Data store.

In the following example, three Windows PN are being enrolled, so only one static IP address (for the Windows PN proxy WPY_<onQhostname>_<ESXhostname>) is needed:

c.	Click the ENROLL button, then OKAY.

The PNs that you selected appear in the Protected Nodes list; however, they are unverified as evidenced by the status in the PROTECTED NODES page > Protection Disabled column.

7.	From the ESXi/ESX host, power on the PN proxies.

8.	Activate (aka verify) the PNs so that onQ can protect them.

a.	Go to PROTECTION CONFIG tab, select the PN, then click the MODIFY button.

b.	Specify values for the node parameters, then SAVE. The act of saving a PN’s configuration instructs onQ to activate that PN’s configuration.

The onQ Portal groups the PNs by ESXi server. If you do not want these PNs in such a group, clear the default Group Name field to remove the PNs from this group and place them in the shared pool.

v3.8 HF1