[ http://issues.apache.org/jira/browse/DERBY-916?page=comments#action_12365136 ]
Suresh Thalamati commented on DERBY-916: ---------------------------------------- Hi Eric, Thanks for volunteering to document the online backup feature. You are right, Server Admin Guide and Reference Guide has to be updated with the above information. In addition to what you already mentioned, I think following information also should be added: Server Guide : 1) in Section : Using the backup procedure to perform an online backup (SYSCS_UTIL.SYSCS_BACKUP_DATABASE ..topic) SYSCS_UTIL.SYSCS_BACKUP_DATABASE procedures will throw error, if there are any unlogged operations already executed in the same transaction as backup procedure. If there are any unlogged operations in progress in other transactions in the system when backup starts, this procedures will block until those transactions are completed before performing the backup. Derby automatically converts unlogged operations to logged mode if they are started when the backup is in progress except operations that are used to maintain application jar files in the database. Procedures to install, replace, and remove jar files in a database are blocked when the backup is in progress. If you don't want backup to block for unlogged operation in other transactions to complete, use SYSCS_UTIL.SYSCS_BACKUP_DATABASE_NOWAIT procedure. This procedure will return error immediately if there are any transactions in progress with unlogged operations at the start of the backup instead of waiting for those transactions to complete. 2) Same information as above should be added to Rollforward Recovery Section also. (SYSCS_UTIL.SYSCS_BACKUP_DATABASE_AND_ENABLE_LOG_ARCHIVE_MODE topic). Info is same as above(1) , except procedure names will be SYSCS_UTIL.SYSCS_BACKUP_DATABASE_AND_ENABLE_LOG_ARCHIVE_MODE and SYSCS_UTIL.SYSCS_BACKUP_DATABASE_AND_ENABLE_LOG_ARCHIVE_MODE_NOWAIT 3) Any mention of update operations not possible should be removed except when it is mentioned in the context of using SYSCS_UTIL.SYSCS_FREEZE_DATABASE procedure. 4) In the freeze procedure section following sentence should be changed. Current sentence: "For example, because the UNIX tar command uses operating system file-copying routines, and Derby uses the IBM Application Developer Kit file-copying routines, the tar command might provide faster backups than the SYSCS_UTIL.SYSCS_BACKUP_DATABASE procedure. " replace it with something like: "For example, because the UNIX tar command uses operating system file-copying routines, and SYSCS_UTIL.SYSCS_BACKUP_DATABASE procedure uses java I/O calls with additional internal synchronization to allow updates during the backup, the tar command might provide faster backups than the SYSCS_UTIL.SYSCS_BACKUP_DATABASE procedure. " Reference Guide: 1) Following two new procedures needs to be added to the Reference Guide: --SYSC_UTIL.SYSCS_ONLINE_BACKUP_DATABASE_NOWAIT and --SYSC_UTIL.SYSCS_BACKUP_DATABASE_AND_ENABLE_LOG_ARCHIVE_MODE_NOWAIT 2) While scanning throws the docs, I also noticed Following two procedures are missing in 10.0 and 10.1 docs in the reference manual , I think they need to be added too. SYSCS_UTIL.SYSCS_BACKUP_DATABASE_AND_ENABLE_LOG_ARCHIVE_MODE (IN BACKUPDIR VARCHAR(32672), IN SMALLINT DELETE_ARCHIVED_LOG_FILES) SYSCS_UTIL.SYSCS_DISABLE_LOG_ARCHIVE_MODE(IN SMALLINT DELETE_ARCHIVED_LOG_FILES) Thanks -suresht > documentation to address Derby-239: online backup > ------------------------------------------------- > > Key: DERBY-916 > URL: http://issues.apache.org/jira/browse/DERBY-916 > Project: Derby > Type: Sub-task > Components: Documentation > Versions: 10.0.2.0 > Reporter: Eric Radzinski > Assignee: Eric Radzinski > -- 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
