• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

[HOWTO]Linux Migration agent not work

E

ErenA

New Pleskian
Dear Friends ,

I have a two server ,
Source server Centos 5.x and running on Plesk 10.4 Version
And
Destination server windows server 2003 R2 , and running on Windows for Plesk 10.4

and twice installed migration manager.
but .

I cant start on linux server (source) smb-to-plesk-migration.sh file cannot run.
I tried smb-to-plesk-migration.sh run to ,

Get an error :
[root@plesk20 ~]# ./smb-to-plesk-migration.sh --work-dir=/usr/local/psa/admin/
Usage: ./smb-to-plesk-migration.sh
--backup-ct --ip=<ip> | --ct-id=<ctid> [ --backup-name=<name of backup> ] [ --work-dir=<path to working directory> ] [ --destination-dir=<path to destination directory>] - Create full server backup of the Panel on specified container and put into specified directory

--backup-local [ --backup-name=<name of backup> ] [ --work-dir=<path to working directory> ] [ --destination-dir=<path to destination directory> ] - Create full server backup of local Panel installation and put into specified directory

--restore-ct --ip=<ip> | --ct-id=<ctid> --backup-name=<name of backup> [ --work-dir=<path to working directory> ] - Restore specified backup into specified container

--restore-local --backup-name=<name of backup> - Restore specified backup into local Panel installation
Options:
--backup-name=<filename> Optional for backup. Name of the backup file to be created. By default: full-server-backup-<current date>
Required for restore. Name of the backup file to be restored.
--work-dir=<path> Optional. Path to directory where to put temporary files. By default: /var/cache
--ip=<ip> Required for working with vz containers. IP of VZ container on this VZ node
--ct-id=<ctid> Container ID
--destination-dir=<path> Path to directory where to put dump file

I understand but , i give to behind working directory.
for example : ./smb-to-plesk-migration.sh --work-dir=/usr/local/psa/admin/

I need help immediately.

Waiting .
Regards.
C.
 
You must log in or register to reply here.

Similar threads

B
Issue Backup creation to remote FTP storage fails due to local disk space check
Replies
1
Views
3K
Bitpalast
Bitpalast
T
Resolved FTPS remote backups fail after upgrade to Plesk 18.0.80 due to TLS session not being resumed on the FTP data connection (pmm-ras regression)
2
Replies
21
Views
36K
Sebahat.hadzhi
Sebahat.hadzhi
W
Resolved Filling up disk space in /var/lib/psa/dumps
Replies
3
Views
1K
WilliamGm
W
T
Issue Additional IPs Not Working After Migrating Plesk CT to Proxmox v8 (OVH)
Replies
9
Views
5K
Raul A.
R
S
Resolved Non-static method ProtectedDirectoryManipulator::updateProtDirectory() cannot be called statically
Replies
7
Views
6K
Sebahat.hadzhi
Sebahat.hadzhi
Back
Top