Parallels Plesk Panel Server backup repository
Server backup repository location.
As of Parallels Plesk Panel version 9.0, the structure and location of the server backup repository have both changed.
The root backup directory is now stored in the file /etc/psa/psa.conf, while it is still set by the variable DUMP_D as before:
Backups directory
DUMP_D /var/lib/psa/dumps
Server backups, backups of resellers, clients, domains, and daily MySQL dumps are now stored in this directory.
Logical Volume Backup
Metadata backups and archives are automatically created on every volume group and logical volume configuration change unless disabled in the lvm.conf file. By default, the metadata backup is stored in the /etc/lvm/backup file and the metadata archives are stored in the /etc/lvm/archive file.
How long the metadata archives stored in the /etc/lvm/archive file are kept and how many archive files are kept is determined by parameters you can set in the lvm.conf file. A daily system backup should include the contents of the /etc/lvm directory in the backup.
Note that a metadata backup does not back up the user and system data contained in the logical volumes. You can manually back up the metadata to the /etc/lvm/backup file with the vgcfgbackup command.
Create a partial backup cpanel
To back up a portion of your site:
*Select Backup from the first page.
*Select the portion of your site to back up by clicking Home Directory, MySQL Databases, or Email Forwarders & Filters.
*Click the appropriate link or button on the following page to store the required information to your computer or web server.
The type of the backup file will depend on what portion of your site you are saving to your computer. For a list of backups and their corresponding file types, see the table below.
————————–
Part of Site File Type |
————————–
Home Directory *.tar.gz
————————–
Email Forwarders *.net, *.com
————————–
Email Filters *.net, *.com
————————–
SQL Database *.sql
————————–
Account Backup and Restoration
When restoring backups from read-only media a working directory is created in a suitable, writable location. The location is determined by the same function used during account creation, based upon the HOMEDIR and HOMEMATCH values in /etc/wwwacct.conf. The backup is extracted into the working directory, then the restoration occurs. Afterwards, the working directory is cleared.
The cpmove file location is now output at the end of the packaging process. Prior versions dispalyed it earlier in the process, risking losing the location due to terminal scroll buffer constraints.
Backup using the dd command
`dd’: Convert and copy a file
`dd’ copies a file (from standard input to standard output, by default)with a changeable I/O block size, while optionally performing conversions on it. Synopses:
dd [OPERAND]…
dd OPTION
The only options are `–help’ and `–version’.
For instance, to make an exact clone of the /boot partition to a backup file, you could use:
# dd if=/dev/sda1 of=/srv/boot-linux.img
We can also use bzip2 to compresses files and then bunzip2 (or bzip2 -d) decompresses all specified files.
To clone one hard disk to another first use fdisk to recreate the appropriately-sized partitions, on the new disk and then use dd to do the actual cloning.
dd –help
Usage: dd [OPERAND]…
or: dd OPTION
Copy a file, converting and formatting according to the operands.
bs=BYTES force ibs=BYTES and obs=BYTES
cbs=BYTES convert BYTES bytes at a time
conv=CONVS convert the file as per the comma separated symbol list
count=BLOCKS copy only BLOCKS input blocks
ibs=BYTES read BYTES bytes at a time
if=FILE read from FILE instead of stdin
iflag=FLAGS read as per the comma separated symbol list
obs=BYTES write BYTES bytes at a time
of=FILE write to FILE instead of stdout
oflag=FLAGS write as per the comma separated symbol list
seek=BLOCKS skip BLOCKS obs-sized blocks at start of output
skip=BLOCKS skip BLOCKS ibs-sized blocks at start of input
status=noxfer suppress transfer statistics
