• 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.

Plesk 8.3 to Plesk 8.3

B

barjolu

Guest
Hi,

I have a problem with a virtual server running Plesk 8.3. Therefore I'll need to move all client accounts and domains to a newly fresh installed server. Both source and destination will be running plesk 8.3 on a virtual win2003 server.

I'm also running PBAS 3.3.

What's the best way to do this? Would it be best to do a backup on the source plesk node, then shut it down.
On the destination server I then set the same IP and hostname as the source server and do a restore.

How will PBAS react on this? As for now both source and destination server is registered in PBAS as win1 and win2.

So, the real question is, what is the best procedure to move all accounts from a registred PBAS plesk node to a new server which also will be registered in PBAS?
 
Back
Top