Archive format
From ISPWiki
The archive name created with pbackup should meet the following requirements:
"plan id"_"plan name"-"creation date"."archiver extension"
where:
- "plan id" - the "Id" column in the Backup plans management (ISPmanager) module. Must contain figures only;
- "plan name" - the "Plan name" in the Backup plans management (ISPmanager) module. The "-_/., " symbols are not allowed;
- "creation date" - date (YYYY-MM-DD);
- "archiver extension" - depends on the archiver: tar, tar.gz, tar.bz2, zip.
Following is the backup that was created on January 22, 2010 via the zip-archiver based on the id=1 plan named usertest:
1_usertest-2010-01-22.zip
The prefix "admin-" and "full" are added to the backups that the root created for a user:
admin-1_full-2010-01-22.zip
The backup that was created with the updated version of pbackup contains several essential files:
1) PBKP_CONTENT is the xml-file that describes logical content of the archive (i.e. the items that are backed up in the archive), as well as the object parameters necessary for their recovery. This file is always located in the archive. PBKP_CONTENT format.;
2) PBKP_XML_LISTING is the xml-file, that describes the hierarchy of the files in the archive. The "auxiliary files" are not included into this hierarchy. The file may not be present, if no files were backed up in the archive. PBKP_XML_LISTING and *.dir files format.
* Auxiliary files: PBKP_CONTENT, PBKP_XML_LISTING, PBKP_PATH and all the files that are described in the "filename" tag of the PBKP_CONTENT file.
For the archive that was created with tar and the like, all axillary files are located in the archive root. Following is the example of the tar -ztf command:
var/ var/log/ var/log/wpa_supplicant.log-20100110 var/log/audit/ var/log/audit/audit.log var/log/cron var/log/ppp/ var/log/maillog var/log/dmesg.old var/log/httpd/ var/log/proftpd/ var/log/secure var/log/dmesg var/log/lastlog var/log/vnetlib var/log/ntpstats/ var/log/messages PBKP_CONTENT PBKP_XML_LISTING pbkp_encm.sql pbkp_mdbm.sql pbkp_mdb1m.sql pbkp_mysqlm.sql pbkp_testdbm.sql pbkp_email@test.com
For the archive that was created with ZIP, location of the the axillary files will depend on the temporary folder that was used while creating the archive. The archive root contains the PBKP_PATH with the archive root-relative path to the folder, where axillary files are located. Following is the example of the unzip -l command output (tmp/pbkp_3575/value in PBKP_PATH):
var/ var/log/ var/log/wpa_supplicant.log-20100110 var/log/audit/ var/log/audit/audit.log var/log/cron var/log/ppp/ var/log/maillog var/log/dmesg.old var/log/httpd/ var/log/proftpd/ var/log/secure var/log/dmesg var/log/lastlog var/log/vnetlib var/log/ntpstats/ var/log/messages PBKP_PATH tmp/pbkp_3575/PBKP_CONTENT tmp/pbkp_3575/PBKP_XML_LISTING tmp/pbkp_3575/pbkp_encm.sql tmp/pbkp_3575/pbkp_mdbm.sql tmp/pbkp_3575/pbkp_mdb1m.sql tmp/pbkp_3575/pbkp_mysqlm.sql tmp/pbkp_3575/pbkp_testdbm.sql tmp/pbkp_3575/pbkp_email@test.com
