I'm going to restart PVA Agent / MN, what would be the impact?
[root@vz ~]# pvaagent restart Shutting pvaagentd: [ OK ] Starting pvaagentd: [ OK ] [root@pva ~]# pvamn restart Shutting pvamnd [ OK ] Starting pvamnd [ OK ]
PVA Agent restart will interrupt services provided by PVA, but won't affect Virtual Environment availability. Restart itself is very quick — usually it takes only 5 seconds, however the restart will interrupt tasks running via PVA.
PVA MN restart will interrupt any currently running tasks in PVA web interface. In addition, PVA MN controls all container backup/restore operations, even if they were launched directly on a hardware node via CLI, so such operation will get interrupted as well.
You can expect that:
- Backup tasks will be interrupted if any. Even if node serves only as a Backup Node.
- Offline Management (Power Panel, Plesk Power Panel) will be unavailable during PVA Agent restart. Active sessions in containers' Power Panels will be dropped.
- Any task initiated from PVA Management Node to the Slave node (where service is restarted) will be interrupted. For example such tasks as migration, backup, cloning, creation, etc.
- The node will become unavailable in PVA Management Node interface (grayed out) for a short period of time.
NOTE: Installing PVA MN / Agent updates implies service restart.