By default, all backups are created in a backup repository located on the Panel-managed server: in %plesk_dir%\Backup\ folder, where %plesk_dir% is environment variable specifying directory where Panel is installed (if installed to default locations, it is "C:\Program Files\Parallels\Plesk\")
The repository is structured as follows, starting with the content of repository root folder (we omit auxiliary files and folders which are irrelevant for backing up and restoring Panel data using pleskbackup and pleskrestore utilities).
|
|
Metadata files of full and server-level backups, one per backup, describe configuration and content. |
||||||||||
|
|
Archives with content related to server configuration and Panel settings. |
||||||||||
|
|
|
Directory containing the following backup data:
Organization of the directory is the same as that of |
|||||||||
|
|
|
Directory containing the following backup data:
Organization of the directory is the same as that of |
|||||||||
|
|
|
Directory containing data related to all sites hosted under a subscription. |
|||||||||
|
|
|
Directory containing data related to all sites hosted under a subscription. |
|||||||||
|
|
|
Directory containing the following backup data:
|
|||||||||
|
|
|
Directories containing backup data of particular resellers, one reseller per directory, and the objects owned by them. The reseller ID stands for the reseller username. |
|||||||||
|
|
|
Metadata files of the reseller backups, one file per backup, describe configuration and content of the reseller and the objects they own. |
|||||||||
|
|
|
Archives with the content. |
|||||||||
|
|
|
Directory containing the following backup data:
Organization of the directory is the same as that of |
|||||||||
|
|
|
Directory containing the following backup data:
|
|||||||||
|
|
|
Directories containing backup data of particular customers, one customer per directory, and the objects owned by them. |
|||||||||
|
|
|
Metadata files of the customer backups, one file per backup, describe configuration and content of the customer account and the objects it owns. |
|||||||||
|
|
|
Archives with the customer content. |
|||||||||
|
|
|
Directory containing the following backup data:
|
|||||||||
|
|
|
Directory containing data related to all sites hosted under a subscription. |
|||||||||
|
|
|
Metadata files of the domain backups, one file per backup, describe configuration and content of the backed up webspace. |
|||||||||
|
|
<content> |
ZIP archives containing data related to the hosted websites and mail accounts. |
|||||||||
Files of each backup are placed in the repository folders according to the described structure.
If a partial backup is created, its files will be places according to the place the backup objects have in the hierarchy. For example, if backing up domain example.com owned by reseller JaneDoe, its files will be located in the <repository root directory>\resellers\JaneDoe\domains\example.com\ folder. If backing up reseller JohnDoe who owns the subscription joe.info and has one customer Client1 who owns the subscription sample.org, the backup files will be located in the following folders:
Previous page
Next page
Locate page
<repository root directory>\resellers\JohnDoe\<repository root directory>\resellers\JohnDoe\domains\joe.info\<repository root directory>\resellers\JohnDoe\clients\Client1\<repository root directory>\resellers\JohnDoe\clients\Client1\domains\sample.org\To distinguish files belonging to different backups of the same object, specific prefix and suffix are added to the file names:
backup is added by default, and, if you like, you can change it to your own on a per-backup basis<yymmddhhmm>. For example, files of backup created on 6 April 2011, 8:58 PM will have suffix 1104062058.Panel is capable of exporting backup as a single .zip file. Each archive has the same structure as the repository, the only difference is that there is only one <info>.xml file on each level.
In case a partial backup is exported, the resulting file structure is reduced from the top so that the highest level corresponds to the level of the highest backup object. For example, if a backup of a single customer (called, for example, SandyLee) is exported, the resulting file will have the following structure:
zip {
<sandy lee info>.xml.zipdomains\subscription1\...subscription_N\...}