[MDEV-15731] mariabackup: create method for backup tool to extract from mbstream Created: 2018-03-29  Updated: 2020-12-15

Status: Open
Project: MariaDB Server
Component/s: Backup
Fix Version/s: None

Type: Task Priority: Major
Reporter: Geoff Montee (Inactive) Assignee: Unassigned
Resolution: Unresolved Votes: 2
Labels: mariabackup

Issue Links:
Relates
relates to MDEV-15713 mariabackup: throw warning/error if -... Closed

 Description   

As I mentioned in MDEV-15713, some people seem to think that the --stream option can be used like:

mariabackup --backup --stream=xbstream --user=root > backup.xbstream
cat backup.xbstream | mariabackup --prepare --stream=xbstream

The proper method to use it seems to be more like this:

mariabackup --backup --stream=xbstream --user=root > backup.xbstream
mbstream -x < backup.xbstream
mariabackup --prepare --target-dir=./

Some users think that mariabackup should have a way to extract the files from the mbstream archive itself without making the user go through the extra step.

Is that feasible and/or desirable?



 Comments   
Comment by Vladislav Vaintroub [ 2018-05-28 ]

well, user does not make a lot of steps here, single trivial command, that can be combined with prepare into a single shell (or Windows batch) command as

mbstream -x path/to/backup && mariabackup --prepare --target-dir=.

making prepare reading from archive does not add benefits (all the archive needs to be extracted before prepare can start), but adds some questions as for how to handle prepare errors, and what should happen on cleanup in this case.

Comment by Geoff Montee (Inactive) [ 2018-05-29 ]

Hi wlad,

making prepare reading from archive does not add benefits

I know that it wouldn't really add any functional benefits. Based on my conversation with the user who requested this, the request is more about making the restore process more intuitive for users who are used to database platforms that support "single-step physical restore from a backup". I guess the reference to a "single step" would imply that the user would want this single step to include both the --prepare and --copy-back steps? I will ask for clarification on that.

but adds some questions as for how to handle prepare errors, and what should happen on cleanup in this case.

Yeah, I understand your concerns. I've passed on your concerns to the user that requested this.

Comment by Vladislav Vaintroub [ 2018-05-29 ]

the --prepare is something you would not find elsewhere. usually, you take a backup, and unpack it in the destination, and it works. so all the steps in between (prepare, copy-back) are not there for more intuitive databases.

Generated at Thu Feb 08 08:23:35 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.