db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kim Haase (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (DERBY-6399) clarify backup section in Derby Server and Administration Guide regarding connecting to the backed up db
Date Wed, 06 Nov 2013 22:36:19 GMT

     [ https://issues.apache.org/jira/browse/DERBY-6399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Kim Haase resolved DERBY-6399.
------------------------------

          Resolution: Fixed
       Fix Version/s: 10.11.0.0
                      10.10.1.3
    Issue & fix info:   (was: Patch Available)

Committed patch DERBY-6399-3.diff to documentation trunk at revision 1539484. 
Merged to 10.10 doc branch at revision 1539486.

> clarify backup section in Derby Server and Administration Guide regarding connecting
to the backed up db
> --------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-6399
>                 URL: https://issues.apache.org/jira/browse/DERBY-6399
>             Project: Derby
>          Issue Type: Improvement
>          Components: Documentation
>    Affects Versions: 10.10.1.1
>            Reporter: Myrna van Lunteren
>            Assignee: Kim Haase
>            Priority: Minor
>             Fix For: 10.10.1.3, 10.11.0.0
>
>         Attachments: DERBY-6399-2.diff, DERBY-6399-2.zip, DERBY-6399-3.diff, DERBY-6399-3.zip,
DERBY-6399.diff, DERBY-6399.stat, DERBY-6399.zip
>
>
> The Derby Server and Administration Guide could clarify better that a backup created
using the SYSCS_UTIL.SYSCS_BACKUP_DATABASE is effectively a copy (with the caveats regarding
non-logged data).
> But when using the SYSCS_UTIL.SYSCS_BACKUP_DATABASE_AND_ENABLE_LOG_ARCHIVE_MODE the resulting
backed up directory is *not* a full copy of the database, and connecting to it directly could
be missing data, and possibly invalidate the backup. 
> Also, it might be helpful to add an example to the rollforwardrecovery page that is more
of a scenario, whereby first the old, perhaps corrupted database, gets renamed, and then a
new one is created in its place, but based on the backup and using the logDevice text, maybe
something like:
> Should a problem have developed with a database, the best approach is to shutdown the
original database, rename the original database directory, use the rollForwardRecovery with
the logDevice attribute, for instance in a linux shell, if the database wombat was previously
backed up to directory /backups:
> mv /databases/wombat /databases/brokenwombat
> cd /databases
> then do the following in ij:  
> connect 'jdbc:derby:wombat;rollForwardRecoveryFrom=/backups/wombat;logDevice=/databases/brokenwombat';



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message