Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Received-SPF: pass (nike.apache.org: local policy)
Date: Thu, 01 Nov 2007 20:29:57 +0100
From: Dyre.Tjeldvoll@Sun.COM
Subject: Re: Derby Backup
In-reply-to: <46ACD0E6.8000800@m3tech.com.br>
Sender: Dyre.Tjeldvoll@Sun.COM
To: derby-dev@db.apache.org
Message-id: <x1o3odedu5l6.fsf@sun.com>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
References: <46ACD0E6.8000800@m3tech.com.br>
User-Agent: Gnus/5.110004 (No Gnus v0.4) Emacs/22.1 (usg-unix-v)

Francisco Trindade <francisco@m3tech.com.br> writes:

> Hi,
>
> Im building a system using Apache Derby, and I couldnt find a way to
> backup the existing data from the database.
> The only procedure I've found in the documentation is to create a
> online/offline backup, that copies the existent database to a
> different location.
> The problem with this approach is that the backup file becomes very
> large (15 - 30 MB) in my case, and that's because Im zipping the
> database after copying it.
>
> I was wondering if it doesn't exist a way to create a backup only of
> the existent data, and not the whole database, like a dump.
>
> Does anyone have a suggestion?

I could not see that anyone else had answered your
question. Appologies if I missed it. 

Not sure I understand the distinction between "existent data" and the
whole database. Are you expecting the backup to be smaller than your
database? I don't think there is any automatic compression of the
backup image so unless you compress the backup yourself it will be the
same size as the database. I don't think Derby supports incremental
backups, so each new backup will have roughly the same size. The size
of each backup image may be reduced if you compress your tables 
before making the backup, (see the manual).

-- 
dt