Issue Migration Manager

[dicker]

Server operating system version

Ubuntu 22.04.4 LTS

Plesk version and microupdate number

Plesk Obsidian Version 18.0.63 Update #4

Hello,
I would like to use the migration manager to move some customers to another virtual server.
I only have access to the source server via SSH key and to the target server only via root and password.
Unfortunately I get an error message
Failed to check SSH connection to the source server 'source' (IP source server): Unable to connect to 'IP source server' by SSH: Bad authentication type; allowed types: ['publickey'].
Ensure that the server is up and there are no firewall rules that may block SSH connections to the server,
then restart migration.

I entered the IP of the source server and then the data from the target server, i.e. root and the password.

 

[alapshin]

Hello @dicker
On the screen Tools & Settings > Migration & Transfer Manager > Start a new migration should be entered credentials of source server.

Here described how to connect to source server via SSH key Authentication by SSH (Linux). Please note that RSA key pair without a passphrase should be used.

 

[dicker]

For me it says SSH key (on target server) *
Do I have to move the SSH key from the source server to the target server?
I can't find the SSH key on the source server.
I don't have /root/.ssh/id_rsa.

 

[dicker]

root@vmd148914:~# ssh-copy-id root@quellserver IP
/usr/bin/ssh-copy-id: INFO: Source of key(s) to be installed: "/root/.ssh/id_rsa.pub"
/usr/bin/ssh-copy-id: INFO: attempting to log in with the new key(s), to filter out any that are already installed
/usr/bin/ssh-copy-id: INFO: 1 key(s) remain to be installed -- if you are prompted now it is to install the new keys
root@Quellserver IP: Permission denied (publickey).

 

[alapshin]

I suppose the best way in your case is manually copy public key to the source server.
1. Connect to the target server and execute
# ssh-keygen -t rsa (do not enter any passphrase)
2. On the target server execute # cat /root/.ssh/id_rsa.pub and copy the output
3. Connect to the source server and paste output of the previous step to the very end of /root/.ssh/authorized_keys file. Do not overwrite, just add at the very end.
4. Login to Plesk UI of target server and select "SSH keys" in Tools & Settings > Migration & Transfer Manager > Start a new migration screen and specify IP address of source sever.

 

[dicker]

That worked very well. Thank you very much
I have another question about the right backup strategy.
So far I have only done 1 full backup and an incremental backup every day. If I now have a server crash and have to restore the backup to another server, I will see backup size 2.58 GB (this addition) + 2.27 TB (previous additions) + 683 GB (first backup) = 2.94 TB.
The problem is that in every case it first loads the entire 2.94 TB onto the new server and that doesn't fit on the new server at all. Even if I only want to restore one customer via backup, the server loads the 2.94 TB.
The data on the defective server is only 1.2 TB in total.
The backup seems to be getting bigger every day because of the daily incremental backups. You should actually be able to limit the number of backups to be kept. Unfortunately I can't find such an option. Full backups cannot be limited either. If I have set a maximum of 2 full backups, the server still makes further full backups. The correct thing to do would actually be to overwrite the older full backup and only keep 2 at a time.
Otherwise, the largest external backup storage will be full at some point.
What can I set so that the backup doesn't become excessively large?

 

[alapshin]

> What can I set so that the backup doesn't become excessively large?
This can be adjusted by backup schedule. For example, If go to Tools & Settings > Backup Manager > Schedule and select only Daily with the following settings:

that means total number of backups will be not more than seven:
- 1 full backup
- 6 incrementals.
After seven days (At the start of new week) Plesk will create 1 new full backup and remove previous full backup and all increments. Each next day it will create new increment until new week started.