From owner-freebsd-isp@FreeBSD.ORG Tue Jul 12 22:06:40 2005 Return-Path: X-Original-To: freebsd-isp@freebsd.org 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 3340C16A41C for ; Tue, 12 Jul 2005 22:06:40 +0000 (GMT) (envelope-from dmp@bitfreak.org) Received: from mail.bitfreak.org (mail.bitfreak.org [65.75.198.146]) by mx1.FreeBSD.org (Postfix) with ESMTP id E6DF243D49 for ; Tue, 12 Jul 2005 22:06:39 +0000 (GMT) (envelope-from dmp@bitfreak.org) Received: from SMILEY (mail.bitfreak.org [65.75.198.146]) by mail.bitfreak.org (Postfix) with ESMTP id 6AEED19F52; Tue, 12 Jul 2005 15:08:52 -0700 (PDT) From: "Darren Pilgrim" To: "'RC'" , Date: Tue, 12 Jul 2005 15:06:37 -0700 Message-ID: <001801c5872d$fa107db0$642a15ac@SMILEY> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2527 In-Reply-To: <20050712214555.42683.qmail@web53902.mail.yahoo.com> Importance: Normal Cc: Subject: RE: fastest way to duplicate production server? X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Jul 2005 22:06:40 -0000 From: RC >=20 > We have a production FreeBSD 4.10 server running old versions=20 > of Apache/MySQL/PHP from ports. We'd like to upgrade=20 > Apache/MySQL/PHP to the latest versions. Before upgrading=20 > we'd like to test on a test box. >=20 > What's the fastest way of duplicating the existing=20 > Apache/MySQL/PHP (including user databases)? (The production=20 > server cannot go down for more than a few seconds.) Make per-filesystem back-ups of everything excluding those files opened read-write by whatever services you're running (ignore log files). Use nice to run the backup at a priority low enough to not usurp resources from the production services. Stop whatever services are running. Use fstat to make sure the excluded files are closed. Make a backup of the files excluded from the first backup run (again, ignore logs). Restart whatever services you stopped. If you can get away with it, flip the volumes read-only before doing the backup, it can make things just a little bit faster.