From derby-dev-return-93759-apmail-db-derby-dev-archive=db.apache.org@db.apache.org Mon Feb 27 17:54:21 2012 Return-Path: X-Original-To: apmail-db-derby-dev-archive@www.apache.org Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 4865D9CC7 for ; Mon, 27 Feb 2012 17:54:21 +0000 (UTC) Received: (qmail 48856 invoked by uid 500); 27 Feb 2012 17:54:21 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 48837 invoked by uid 500); 27 Feb 2012 17:54:21 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 48826 invoked by uid 99); 27 Feb 2012 17:54:21 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 27 Feb 2012 17:54:21 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [216.32.181.184] (HELO ch1outboundpool.messaging.microsoft.com) (216.32.181.184) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 27 Feb 2012 17:54:11 +0000 Received: from mail179-ch1-R.bigfish.com (10.43.68.250) by CH1EHSOBE017.bigfish.com (10.43.70.67) with Microsoft SMTP Server id 14.1.225.23; Mon, 27 Feb 2012 17:53:28 +0000 Received: from mail179-ch1 (localhost [127.0.0.1]) by mail179-ch1-R.bigfish.com (Postfix) with ESMTP id 958BB2E023F for ; Mon, 27 Feb 2012 17:53:28 +0000 (UTC) X-SpamScore: 0 X-BigFish: VPS0(zzc85fhzz1202hzz8275bh8275dhz2dh2a8h668h839h) X-Forefront-Antispam-Report: CIP:74.62.37.82;KIP:(null);UIP:(null);IPV:NLI;H:CPHUB1.canoga.com;RD:rrcs-74-62-37-82.west.biz.rr.com;EFVD:NLI Received: from mail179-ch1 (localhost.localdomain [127.0.0.1]) by mail179-ch1 (MessageSwitch) id 1330365207199049_12100; Mon, 27 Feb 2012 17:53:27 +0000 (UTC) Received: from CH1EHSMHS001.bigfish.com (snatpool1.int.messaging.microsoft.com [10.43.68.243]) by mail179-ch1.bigfish.com (Postfix) with ESMTP id 250343E004B for ; Mon, 27 Feb 2012 17:53:27 +0000 (UTC) Received: from CPHUB1.canoga.com (74.62.37.82) by CH1EHSMHS001.bigfish.com (10.43.70.1) with Microsoft SMTP Server (TLS) id 14.1.225.23; Mon, 27 Feb 2012 17:53:26 +0000 Received: from vserver1.canoga.com ([169.254.2.24]) by CPHUB1.canoga.com ([172.16.1.93]) with mapi; Mon, 27 Feb 2012 09:54:32 -0800 From: "Bergquist, Brett" To: "derby-dev@db.apache.org" Date: Mon, 27 Feb 2012 09:53:21 -0800 Subject: Is there any documentation on how the online database backup works? Thread-Topic: Is there any documentation on how the online database backup works? Thread-Index: Acz1eLGUd6dXd3aASzyNDiTr5kp4Ig== Message-ID: <97EB699F861AD841B5908C7CA9C9565602065A079934@VSERVER1.canoga.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US x-tm-as-product-ver: SMEX-8.0.0.1307-6.500.1024-18738.005 x-tm-as-result: No--39.759000-0.000000-31 x-tm-as-user-approved-sender: Yes x-tm-as-user-blocked-sender: No Content-Type: multipart/alternative; boundary="_000_97EB699F861AD841B5908C7CA9C9565602065A079934VSERVER1can_" MIME-Version: 1.0 X-OriginatorOrg: canoga.com X-Virus-Checked: Checked by ClamAV on apache.org --_000_97EB699F861AD841B5908C7CA9C9565602065A079934VSERVER1can_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable As expected, the using the online backup slows the insertion rate of rows i= nto some tables in my system in production. So I want to take a look at = how the online backup is done and see if there can be any room for improvem= ent. I can poke around and try to figure it out, but I was wondering if t= here is any architectural or design documents on this that might help. Thanks. Brett --_000_97EB699F861AD841B5908C7CA9C9565602065A079934VSERVER1can_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

As expected, the= using the online backup slows the insertion rate of rows into some tables = in my system in production.    So I want to take a look at h= ow the online backup is done and see if there can be any room for improveme= nt.   I can poke around and try to figure it out, but I was wonde= ring if there is any architectural or design documents on this that might h= elp.

 

Thanks.

 

Brett

= --_000_97EB699F861AD841B5908C7CA9C9565602065A079934VSERVER1can_--