From owner-freebsd-hackers@FreeBSD.ORG Tue Aug 16 08:58:04 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 1DAE616A41F for ; Tue, 16 Aug 2005 08:58:04 +0000 (GMT) (envelope-from dmitry.mityugov@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.200]) by mx1.FreeBSD.org (Postfix) with ESMTP id 991E543D49 for ; Tue, 16 Aug 2005 08:58:03 +0000 (GMT) (envelope-from dmitry.mityugov@gmail.com) Received: by wproxy.gmail.com with SMTP id 36so1181646wra for ; Tue, 16 Aug 2005 01:58:02 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=EsHDBxl41kw4ZdA/Bcpo73lfGhzmwHbOtkfMgjfBo483HnOBLjcmt46UBU7StOzvcvi1a4SctiVM3bzNoAHr/RvaixZcO9kbSK+GMXBeSiCnb+dGLg9vKcYrWhAxE9yjNXMBsL9E1o9G5UoUkBQqOn/x5XcMr0wQHdiIAagchaU= Received: by 10.54.43.51 with SMTP id q51mr148665wrq; Tue, 16 Aug 2005 01:58:02 -0700 (PDT) Received: by 10.54.56.33 with HTTP; Tue, 16 Aug 2005 01:58:02 -0700 (PDT) Message-ID: Date: Tue, 16 Aug 2005 12:58:02 +0400 From: Dmitry Mityugov To: Patrick Dung In-Reply-To: <20050816064109.86120.qmail@web52104.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <20050816064109.86120.qmail@web52104.mail.yahoo.com> 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 08:58:04 -0000 On 8/16/05, 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? Use mysqldump or mysqlhotcopy? --=20 Dmitry Mityugov, St. Petersburg, Russia I ignore all messages with confidentiality statements "We live less by imagination than despite it" - Rockwell Kent, "N by E"