From owner-freebsd-isp@FreeBSD.ORG Sat Dec 27 05:56:48 2003 Return-Path: Delivered-To: freebsd-isp@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 47C4616A4CE for ; Sat, 27 Dec 2003 05:56:48 -0800 (PST) Received: from netlx010.civ.utwente.nl (netlx010.civ.utwente.nl [130.89.1.92]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7BAEC43D1D for ; Sat, 27 Dec 2003 05:56:46 -0800 (PST) (envelope-from eric@monkey-online.net) Received: from EricV.monkey-online.net (ericv.adsl.utwente.nl [130.89.226.252])hBRDtuS04366 for ; Sat, 27 Dec 2003 14:55:56 +0100 Message-Id: <5.2.1.1.0.20031227145502.04cb1c80@mail.monkey-online.net> X-Sender: eric@mail.monkey-online.net (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 5.2.1 Date: Sat, 27 Dec 2003 14:55:51 +0100 To: freebsd-isp@freebsd.org From: Eric Veraart Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-UTwente-MailScanner-Information: Scanned by MailScanner. Contact helpdesk@ITBE.utwente.nl for more information. X-UTwente-MailScanner: Found to be clean Subject: PSA 1.13 Linux -> PSA 6 FreeBSD X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Dec 2003 13:56:48 -0000 A client of mine is running Plesk 1.13 (actually Slash, but it's the same thing) on TurboLinux (Linux version 2.2.14-3). I've set up a new server running FreeBSD and Plesk 6. I noticed that all the account information (including passwords) are in the DB of Plesk 1.13. I don't have to copy all the website content etc but just the accounts, passwords, domains etc. I was wondering about the best strategy. Uptil now I figured the best way was: - Install a temporary server with Linux - copy psa 1.13 and passwd/group files to it, - update to psa 5.0 - update to psa 6 - use the backup util and place the backup on the FreeBSD server The worst way of copying is filling in the new server by hand. I was wondering, if all the information I need is in the database. Isn't it possible to just place the db on the new server, and let PSA 5 update the database and create all the sysusers? I have already found MySQL commands in the etc dir of PSA 6, to update the 1.13 db to psa 2 -> 5 -> 6 which worked flawlessly. The problem however is that the sysusers won't be created. I'm not so into the way PSA handles the database info for creating system files. I already informed about the costs for SW-Soft of doing the transfer, but they couldn't tell how long it would take and thus how much it would cost, so that's not an option.