db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jørgen Løland (JIRA) <j...@apache.org>
Subject [jira] Commented: (DERBY-2969) Admin Guide: Document that online backup is non-blocking
Date Fri, 08 Feb 2008 07:31:08 GMT

    [ https://issues.apache.org/jira/browse/DERBY-2969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12566941#action_12566941
] 

Jørgen Løland commented on DERBY-2969:
--------------------------------------

Hi Kim,

These changes makes it much more clear that the backup functionality does not block transactions.
I have no comments to cadminhubbkup01.html, but I wonder if the following would make it even
clearer that transactions are not blocked during any part of the backup process. 

The SYSCS_UTIL.SYSCS_BACKUP_DATABASE procedure puts the database into a state in which it
can be safely copied. The procedure then copies the entire original database directory (including
data files, online transaction log files, and jar files) to the specified backup directory.
Files that are not within the original database directory (for example, derby.properties)
are not copied. With the exception of a few cases mentioned in Unlogged Operations, the procedure
does not block concurrent transactions at any time.

> Admin Guide: Document that online backup is non-blocking
> --------------------------------------------------------
>
>                 Key: DERBY-2969
>                 URL: https://issues.apache.org/jira/browse/DERBY-2969
>             Project: Derby
>          Issue Type: Improvement
>          Components: Documentation
>    Affects Versions: 10.2.2.0, 10.3.1.4, 10.4.0.0
>            Reporter: Jørgen Løland
>            Assignee: Kim Haase
>            Priority: Minor
>         Attachments: cadminhubbkup01.html, cadminhubbkup63476.html, DERBY-2969.diff
>
>
> The Admin Guide does not mention that the online backup functionality is non-blocking.
The information that a backup can be made without blocking transactions may be of great interest
to administrators.
> Furthermore, this sentence implies that online backup is performed by *blocking* updates:
> "The SYSCS_UTIL.SYSCS_BACKUP_DATABASE() procedure puts the database into a state in which
it can be safely copied, then copies the entire original database directory (including data
files, online transaction log files, and jar files) to the specified backup directory.
> Admin guide, online backup:
> http://db.apache.org/derby/docs/dev/adminguide/cadminhubbkup63476.html

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message