This article describes how to limit the number of backups allowed for creation through Parallels Power Panel (VZPP) and how to deny the creation of any backups.
Three use-cases are presented:
- Apply to several Hardware Nodes registered in PVA Management Node
- Apply to one stand-alone Node with PVA Agent
- Apply to several containers on a stand-alone Node with PVA Agent
Apply to several Hardware Nodes registered in PVA Management Node
Starting from PVA 4.6.3, it is possible to manage Parallels Power Panel Policies from a centralized location, and either set the allowed number of backups, or prohibit backups explicitly on both the Hardware Node level and on the container or VM level: Administrator's Guide
Apply to one stand-alone Node with PVA Agent
On a stand-alone Hardware Node with PVA Agent installed, it is only possible to disable backups through VZPP on the Hardware Node level:
Find the index-vzpp.xsl file:
- On PVCfW:
C:\Program Files (x86)\Parallels\Parallels Virtual Automation\Power Panel\xsl\screens\vz\ves\backups\index-vzpp.xsl
- On PVCfL or PSBM:
- On PVCfW:
Comment out the
"show backups"section as follows:
<!-- Show backups --> <xsl:otherwise> <xsl:variable name="browse-rtf"> <!-- commented out due to /en/114629 <xsl:call-template name="backups:browse-single-ve"> <xsl:with-param name="backups-limit" select="$backups-limit"/> <xsl:with-param name="filter-ve-eid" select="$ve-eid"/> </xsl:call-template> --> </xsl:variable>
Restart PVA Power Panel:
net stop pvapp && net start pvapp
On PVCfL or PSBM:
index-vzpp.xsl file will be overwritten after the next PVA update installation, and it will be necessary to apply the changes again. Therefore, we recommend using the following method provided for all containers on the Node.
Apply to several containers on a stand-alone Node with PVA Agent
It is possible to either limit the number of backups or prohibit backup creation from VZPP for one or several containers or VMs by sending XML API packets:
Set the backup limit via VZPP:
<packet version="4.5.0"> <target>policysl</target> <data> <policysl> <set_effective_policy> <policy> <object_id>PLACE HERE THE ACTUAL EID OF A CONTAINER</object_id> <rules> <policy_rule> <id>vzpp.limit_backups_count</id> <value>PUT BASE64-ENCODED NUMBER OF BACKUPS ALLOWED FOR CREATION</value> </policy_rule> </rules> </policy> </set_effective_policy> </policysl> </data> </packet>
NOTE: VZPP backups limit is ignored when backup is initiated from PVA MN or manually (via
prlctl backup). As a result, it is possible that container will have more existing backups than VZPP backups limit allows and VZPP user won't be able to create any new backup.
Prohibit backup creation via VZPP:
<packet version="4.5.0"> <target>policysl</target> <data> <policysl> <set_effective_policy> <policy> <object_id>PLACE HERE THE ACTUAL EID OF A CONTAINER</object_id> <rules> <policy_rule> <id>vzpp.deny_backups</id> <value>MQ==</value> </policy_rule> </rules> </policy> </set_effective_policy> </policysl> </data> </packet>
NOTE: Do not forget to place the actual EID of the container or virtual machine you want to set limits for into the provided request, and the actual number of allowed backups, encoded with base64.
NOTE: Packets must not contain any newline characters and should be terminated by the "^@" symbol.
For more information, refer to these articles:
111220 How to send an XML API request to PVA
113619 How to find the EID for a container
115252 Prohibit backup and application templates in Power Panel for hardware node with PVA Agent