Enrollment in non‑cluster Environment : (Agent‑less Linux/Windows PNs) Enroll protected nodes

(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:
•
•
•
•
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.
To enroll an agent‑less PN:
1.
Enable ssh on the ESXi/ESX server.
2.
3.
4.
Click the PROTECTION CONFIG tab.
5.
The Add Protected Nodes via Host dialog appears.
6.
The onQ Portal queries the virtual machines hosted by the ESXi/ESX server, then displays the inventory.
7.
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.
•
Windows proxy address. The static IP address that you reserved for the Windows PN proxy.
•
Linux proxy address. The static IP address that you reserved for the Linux PN proxy.
•
Proxy subnet mask. The PN proxy’s subnet mask.
•
Proxy gateway. The PN proxy’s gateway.
•
Proxy VM Data store. The directory in which the vm’s files are stored.
•
Proxy VM Network. Your network configuration can include a vCenter-level Distributed Virtual Switches (DVS) or an ESXi host-level virtual switch. When you enroll an ESXi host, all available networks that are visible to that host are listed and available for selection.
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.
8.
9.
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.
To re‑enroll a proxy PN:
Use this procedure to re-enroll (aka reinstall) the Linux PN proxy or the Windows PN proxy or both. Perform this procedure on each ESX/ESXi host enrolled with the onQ.
1.
2.
Click the PROTECTION CONFIG tab.
3.
The Add Protected Nodes via Host dialog appears. The PN check boxes for enrolled PNs are greyed out.
4.
5.
In the Proxy VM Network field, reattach the virtual network adapter.
6.
Select Re-install Windows proxy or Re-install Linux proxy, depending on the operating system of the proxy you’re trying to reinstall, then ENROLL.
7.

v3.8 SP1
v3.8 SP1