Article ID: 118832, created on Nov 24, 2013, last review on Jun 17, 2016

  • Applies to:
  • Virtuozzo 6.0
  • Virtuozzo containers for Linux
  • Virtuozzo containers for Windows
  • Virtuozzo hypervisor
  • Virtual Automation

Symptoms

I am using vzabackup and vzarestore utilities for backing up containers and/or virtual machines. I need to change backup settings on a PVC/PSBM/PCS node using PVA API. How can I do it?

Cause

If you are not using PVA Management Node, it is possible to configure PVA Agent on a node directly using PVA API. PVA API packets are sent by /opt/pva/agent/bin/vzlcon utility or /opt/pva/agent/bin/sendRequestViaTCP.pl script, more details are available in the article below:

  • 111220 How to send XML API request to PVA

Resolution

  1. First, check the current backup settings on a node:

    Example of a packet that would show you the current configuration.

    <packet version="4.0.0">
    <target>backupm</target>
    <data>
    <backupm>
    <get_config/>
    </backupm>
    </data>
    </packet>
    
  2. According to your needs, you can configure backups to be stored locally or on a remote server, as well as configure these parameters:

    • backup_server - Backup server connection information (whether the same node or remote server should be used)

    • chain_length - Maximum number of incremental backups in any given backup sequence. When this number is exceeded, a new backup sequence must be started by creating a new full backup.

    • chain_days - Maximum number of days an incremental backup sequence may continue uninterrupted. When this number is exceeded, a new sequence must be started beginning with a new full backup.

    • keep_max - The maximum number of backup archives (chains with full and incremental archives) for a virtual environment that should be kept on the backup server. When this number is exceeded, the oldest backup files are automatically removed after creating a successful new ful backup.

    • compression - The default compression level.

    • type - Default backup type.

    Full list of configurable parameters and values can be found in PVA XML API reference guide

    Example of a packet that would set local node to store backups:

    <packet version="4.0.0">
    <target>backupm</target>
    <data>
    <backupm>
    <set_config>
    <backupm_config>
    <backup_server>
    <protocol>agent</protocol>
    <login>
    <realm>00000000-0000-0000-0000-000000000000</realm>
    </login>
    <address>local</address>
    </backup_server>
    <chain_length>0</chain_length>
    <chain_days>0</chain_days>
    <keep_max>0</keep_max>
    <compression>1</compression>
    <type>0</type>
    </backupm_config>
    </set_config>
    </backupm>
    </data>
    </packet>
    

    Example of a packet that would set a remote node with IP address $IP_ADDRESS to be the backup node:

    <packet version="4.0.0">
    <target>backupm</target>
    <data>
    <backupm>
    <set_config>
    <backupm_config>
    <backup_server>
    <protocol>SSL</protocol>
    <port>4434</port>
    <password>$BASE64ENCODEDPASSWORD</password>
    <login>
    <name>$BASE64ENCODEDUSERNAME</name>
    <realm>00000000-0000-0000-0000-000000000000</realm>
    </login>
    <address>$IP_ADDRESS</address>
    </backup_server>
    <chain_length>0</chain_length>
    <chain_days>0</chain_days>
    <keep_max>0</keep_max>
    <compression>1</compression>
    <type>0</type>
    </backupm_config>
    </set_config>
    </backupm>
    </data>
    </packet>
    

    Do not forget to change the IP, Username and Password and preferable settings in the packets above.

For more information you can refer to the PVA XML API reference guide

Search Words

backup conf

backup location

PVA API

u676

change backup node

vzabackup -commandline syntax to get more fullbackups

backup settings

a26b38f94253cdfbf1028d72cf3a498b 2897d76d56d2010f4e3a28f864d69223 319940068c5fa20655215d590b7be29b d02f9caf3e11b191a38179103495106f 0dd5b9380c7d4884d77587f3eb0fa8ef e8e50b42231236b82df27684e7ec0beb 965b49118115a610e93635d21c5694a8 c62e8726973f80975db0531f1ed5c6a2

Email subscription for changes to this article
Save as PDF