From owner-freebsd-hackers@FreeBSD.ORG Tue Aug 16 07:16:50 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 390FE16A41F for ; Tue, 16 Aug 2005 07:16:50 +0000 (GMT) (envelope-from patrick_dkt@yahoo.com.hk) Received: from web52108.mail.yahoo.com (web52108.mail.yahoo.com [206.190.48.111]) by mx1.FreeBSD.org (Postfix) with SMTP id 7609E43D48 for ; Tue, 16 Aug 2005 07:16:49 +0000 (GMT) (envelope-from patrick_dkt@yahoo.com.hk) Received: (qmail 44021 invoked by uid 60001); 16 Aug 2005 07:16:48 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com.hk; h=Message-ID:Received:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=v4SLn8pYvDAqKroVgMhDF5ZLjXfTkQRx2lnctNvoyqSTycVFGmSWzGL8a+XpDIEQexazCvv2VZSfPJF5jvskozD08bhPoO7MWBmKOqW0q0bVV26alM1akZjipiqwbIBqktZPQ76TPT/trLk6LsBsWwdenxVMUmExHtg5j8ZQmO0= ; Message-ID: <20050816071648.44019.qmail@web52108.mail.yahoo.com> Received: from [202.134.67.19] by web52108.mail.yahoo.com via HTTP; Tue, 16 Aug 2005 00:16:48 PDT Date: Tue, 16 Aug 2005 00:16:48 -0700 (PDT) From: Patrick Dung To: vd@datamax.bg In-Reply-To: <20050816070448.GA21272@sinanica.bg.datamax> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Cc: freebsd hackers Subject: Re: Backup problem for backup MySQL (a table > 2GB) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Aug 2005 07:16:50 -0000 The main problem is money. Buying a new product needs money. The old backup product (commercial) is scalable and is working fine with various OS. However it is outdated and is not supported anymore (unless we have a service agreement with the vendor of the backup product.) It consumes lots of space to do tar+gzip and split. I am thinking if I could copy all mysql files to another server (by ftp/ssh) periodically. Regards Patrick --- Vasil Dimov wrote: > On Mon, Aug 15, 2005 at 11:41:09PM -0700, Patrick Dung wrote: > > Hi > > > > We are using an old backup product which can only backup files < > 2GB. > > Now we have a mysql file > 2GB. The backup product refuse to backup > > that file. > > > > So, whats the alternatives to perform backup for this situation? > > This is current idea: > > > > Tar all the mysql directory and split into small files < 2GB. > > > > Any suggestions? > > > > I guess this is not applicable, but what about using other "backup > product" that supports larger files? > > Otherwise tar(1) + gzip(1) (eventually) + split(1) seems reasonable > solution... > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com