[ https://forge.continuent.org/jira/browse/SEQUOIA-851?page=all ]
Robert Hodges resolved SEQUOIA-851:
-----------------------------------
Resolution: Fixed
This has been implemented in the 2.10.3 codeline and passed a variety of tests
which included implementing backup scripts that use the required protocol.
> Create script-based backuper that can interface with arbitrary backup
> mechanisms
> --------------------------------------------------------------------------------
>
> Key: SEQUOIA-851
> URL: https://forge.continuent.org/jira/browse/SEQUOIA-851
> Project: Sequoia
> Type: New Feature
> Components: Backup System
> Versions: Sequoia 2.10
> Environment: All
> Reporter: Robert Hodges
> Assignee: Robert Hodges
> Priority: Critical
> Fix For: Sequoia 2.10.3
>
>
> Create a script-based Backuper implementation that invokes a standard wrapper
> script to perform Backuper operations. This will permit Sequoia to use
> arbitrary backup management mechanisms and provide a last resort if there are
> problems with other Backupers. Integration is an exercise for the reader,
> but this will at least make it possible.
> The script semantics are summarized below. Some details may be added during
> the implementation.
> NAME
> backupmgr
> SYNTAX
> backupmgr --op {backup | restore | delete | test}
> --host hostname --port port --database dbname --login dblogin
> --password dbpass --dumpname name --dumppath dirpath --flags options
> --tables tables-to-backup
> DESCRIPTION
> Perform backup, restore, and log deletion operations. The operations
> are defined using the --op argument, which is always supplied.
> backup - Perform a backup
> restore - Restore a backup
> delete - Delete a backup
> test - Return immediately (used to check that script is available)
> The backupmgr script must encapsulate fully all operations, including
> if necessary dropping and recreating databases or other administrative
> functions associated with supported operations.
> RETURN CODE
> Scripts must return 0 if successful. Any other value is considered
> to indicate backup failure. In addition, the script is considered to
> have failed if it writes to stderr. Stderr from underlying processes
> must therefore be suppressed or redirected if it does not represent
> an error.
> This backuper will need to parse URLs in a generic way to get database name,
> host, and port. In addition to implementing a ScriptBackuper class it is my
> plan to extract the Url parsing currently embedded MySQLBackuper and
> AbstractPostgreSqlBackuper into a separate utility class. This will replace
> the embedded classes currently used in those classes.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://forge.continuent.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia
