From derby-dev-return-11619-apmail-db-derby-dev-archive=db.apache.org@db.apache.org Fri Dec 16 10:04:10 2005 Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 15801 invoked from network); 16 Dec 2005 10:04:10 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 16 Dec 2005 10:04:10 -0000 Received: (qmail 16002 invoked by uid 500); 16 Dec 2005 10:04:09 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 15774 invoked by uid 500); 16 Dec 2005 10:04:08 -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 15765 invoked by uid 99); 16 Dec 2005 10:04:08 -0000 X-ASF-Spam-Status: No, hits=1.3 required=10.0 tests=SPF_FAIL X-Spam-Check-By: apache.org Received: from [192.87.106.226] (HELO ajax.apache.org) (192.87.106.226) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 16 Dec 2005 02:04:08 -0800 Received: from ajax.apache.org (ajax.apache.org [127.0.0.1]) by ajax.apache.org (Postfix) with ESMTP id EF66D183 for ; Fri, 16 Dec 2005 11:03:46 +0100 (CET) Message-ID: <2145347395.1134727426978.JavaMail.jira@ajax.apache.org> Date: Fri, 16 Dec 2005 11:03:46 +0100 (CET) From: "Suresh Thalamati (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Updated: (DERBY-239) Need a online backup feature that does not block update operations when online backup is in progress. In-Reply-To: <131892714.1114538125243.JavaMail.jira@ajax.apache.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N [ http://issues.apache.org/jira/browse/DERBY-239?page=all ] Suresh Thalamati updated DERBY-239: ----------------------------------- Attachment: onlinebackup_6.diff This patch adds code to support online backup when jar operations are running parallel to the backup. Jar files are not logged, but the system catalogs updates are logged when a jar file is added/replaced. If the jar file operations are allowed during the backup, system catalog (sys.sysfiles) table in the backup database can have a reference to a jar file that does not exist in the backup database. And also backup can contain partial written jar files. To make a consistent online backup, this patch: 1) Makes Backup operation wait/fail for all the jar operations activity in progress to complete. 2) Blocks jar file operations when a backup is in progress. This patch also adds a new test to test the online backup with jar operations. TESTS : derbyall test suite passed on Windows XP/JDK142 It would be great if some can review and commit this patch. svn stat: M java\engine\org\apache\derby\impl\store\raw\xact\Xact.java M java\engine\org\apache\derby\impl\store\raw\xact\XactFactory.java M java\engine\org\apache\derby\impl\store\raw\data\BaseDataFileFactory.java M java\engine\org\apache\derby\impl\store\raw\data\RFResource.java M java\engine\org\apache\derby\iapi\store\raw\xact\RawTransaction.java A java\testing\org\apache\derbyTesting\functionTests\tests\store\obtest_customer.jar M java\testing\org\apache\derbyTesting\functionTests\tests\store\copyfiles.ant A java\testing\org\apache\derbyTesting\functionTests\tests\store\OnlineBackupTest3.java A java\testing\org\apache\derbyTesting\functionTests\tests\store\OnlineBackupTest3_app.properties A java\testing\org\apache\derbyTesting\functionTests\master\OnlineBackupTest3.out M java\testing\org\apache\derbyTesting\functionTests\suites\storemore.runall > Need a online backup feature that does not block update operations when online backup is in progress. > -------------------------------------------------------------------------------------------------------- > > Key: DERBY-239 > URL: http://issues.apache.org/jira/browse/DERBY-239 > Project: Derby > Type: New Feature > Components: Store > Versions: 10.1.1.0 > Reporter: Suresh Thalamati > Assignee: Suresh Thalamati > Attachments: onlinebackup.html, onlinebackup1.html, onlinebackup_1.diff, onlinebackup_2.diff, onlinebackup_3.diff, onlinebackup_4.diff, onlinebackup_5.diff, onlinebackup_6.diff > > Currently Derby allows users to perfoms online backups using SYSCS_UTIL.SYSCS_BACKUP_DATABASE() procedure, but while the backup is in progress, update operations are temporarily blocked, but read operations can still proceed. > Blocking update operations can be real issue specifically in client server environments, because user requests will be blocked for a long time if a > backup is in the progress on the server. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira