• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Migration plesk 11.5 server to new server

TristanA

Basic Pleskian
Hello,

I have two servers, an older server and the other more recent.
Both servers are running plesk 11.5 .

Partitions from the old server :
Code:
# df- kh
Filesystem Size Used Avail Use % Mounted on
/ dev/mapper/vg_srv651-lv_root
***********************50G 4.2G 43G 9% /
tmpfs 3.9G 0 3.9G 0% / dev / shm
/ dev/sda1 485M 95M 366M 21% / boot
/ dev / mapper / vg_lv_home
**********************860G 254G 562G 32% / home

Partitions from the new server :
Code:
# df- kh
Filesystem Size Used Avail Use % Mounted on
rootfs 20G 17G 2.3G 13% /
/ dev / root 20G 17G 2.3G 13% /
devtmpfs 16G 256K 16G 1% / dev
/ dev/md3 1.8T 82G 1.7T 5% / var
tmpfs 16G 0 16G 0% / dev / shm
/ dev / root 20G 17G 2.3G 13% / var / named / chroot / etc / named
/ dev/md3 1.8T 82G 1.7T 5% / var / named / chroot / var / named
/ dev / root 20G 17G 2.3G 13% / var/named/chroot/etc/named.rfc1912.zones
/ dev / root 20G 17G 2.3G 13% / var / named / chroot / etc / rndc.key
/ dev / root 20G 17G 2.3G 13% / var/named/chroot/usr/lib64/bind
/ dev / root 20G 17G 2.3G 13% / var / named / chroot / etc / named.iscdlv.key
/ dev / root 20G 17G 2.3G 13% / var / named / chroot / etc / named.root.key
/ dev / root 20G 17G 2.3G 13% / var / named / chroot / etc / named
/ dev / root 20G 17G 2.3G 13% / var/named/chroot/usr/lib64/bind


When I execute the migration program I get an error :
Insufficient disk space on the destination server to store temporary files for transfer . Available : 16568 MB . Required: 104113 MB .

Can you tell me which folder plesk use for migration?
I would like to make a symbolic link to the folder / var / newsfolder /

Thank you for your help.

Good day.
 
Last edited:
You can pretty much ignore the "Insufficient disk space" warning when using rsync (which is default anyway). In the old days Plesk would create tarballs for each subscription, and then copy those tarballs. Nowaways Plesk uses rsync, which doesn't need all the additional storage to create the tarballs.
 
Back
Top