From owner-freebsd-hackers@FreeBSD.ORG Tue Aug 16 07:04:52 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 C642216A41F for ; Tue, 16 Aug 2005 07:04:52 +0000 (GMT) (envelope-from vd@datamax.bg) Received: from jengal.datamax.bg (jengal.datamax.bg [82.103.104.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 478E243D45 for ; Tue, 16 Aug 2005 07:04:52 +0000 (GMT) (envelope-from vd@datamax.bg) Received: from sinanica.bg.datamax (sinanica.bg.datamax [192.168.10.1]) by jengal.datamax.bg (Postfix) with QMQP id 4AA8587CD; Tue, 16 Aug 2005 10:04:51 +0300 (EEST) Received: (nullmailer pid 21356 invoked by uid 1004); Tue, 16 Aug 2005 07:04:48 -0000 Date: Tue, 16 Aug 2005 10:04:48 +0300 From: Vasil Dimov To: Patrick Dung Message-ID: <20050816070448.GA21272@sinanica.bg.datamax> References: <20050816064109.86120.qmail@web52104.mail.yahoo.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="IJpNTDwzlM2Ie8A6" Content-Disposition: inline In-Reply-To: <20050816064109.86120.qmail@web52104.mail.yahoo.com> X-OS: FreeBSD 5.4-STABLE User-Agent: Mutt/1.5.10i 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 Reply-To: vd@datamax.bg 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:04:52 -0000 --IJpNTDwzlM2Ie8A6 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Aug 15, 2005 at 11:41:09PM -0700, Patrick Dung wrote: > Hi >=20 > 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. >=20 > So, whats the alternatives to perform backup for this situation? > This is current idea: >=20 > Tar all the mysql directory and split into small files < 2GB. >=20 > Any suggestions? >=20 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... --IJpNTDwzlM2Ie8A6 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- iD8DBQFDAZAPFw6SP/bBpCARAucTAKCPEtdaH1L8b7MBhdCuev9zGQvq5ACfeA27 rDqf7uKT4gaH2zTmmtoC0Wo= =LZAz -----END PGP SIGNATURE----- --IJpNTDwzlM2Ie8A6--