Hot backup implementation
This drafting is obsoleted.
Please check
http://
#######
##### <Way1> has been selected #####
#######
#############
Difficulty (size) to implement
Way1 : big
Way2-A : small
Way2-B : medium
Need crash recovery
Way1 : No
Way2-A : Yes
Way2-B : No (but recreates logfiles if no logfiles)
-------
Hot backuped file: We can startup InnoDB directly from the files (datafiles, logfiles).
The normal crash recovery processing at the startup may be acceptable.
(If the recovery always succeeds.)
-
We may have several way to implementation.
<Way1> As external executable
- Its usage will be similar to InnoDBHotBackup.
- The executable will be created with XtraDB.
copying all transaction log records from the last checkpoint at the start,
during copying datafiles.
applying the logs to the datafiles and generate proper logfiles.
<Way2> As internal XtraDB
- will be implemented as like UDF. (We should patch only to InnoDB part)
<Way2-A> "START BACKUP" ~ "END BACKUP"
the datafiles and logfiles.
Of course, we need crash recovery when startup from the files.
If the log records reach to the (near of ?) limit during the period,
the safety of the copying logfiles.
<Way2-B> "SNAPSHOT"
The command creates or overwrites all datafiles (and logfiles ?) snapshot
to another directory.
We can startup from the copied datafiles without logfiles. (maybe)
- special copying process.
- applying transaction log to the copied files and closing correctly
- finish.
the necessity of the logfiles.
Blueprint information
- Status:
- Complete
- Approver:
- Vadim Tkachenko
- Priority:
- Medium
- Drafter:
- Yasufumi Kinoshita
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Drafting
- Series goal:
- None
- Implementation:
- Implemented
- Milestone target:
- None
- Started by
- Yasufumi Kinoshita
- Completed by
- Yasufumi Kinoshita