© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Somehow MLOG_FILE_CREATE2 is still in the redo log, and the only reason for it could be that a remote tablespace was either CREATEed or ALTERed while the backup was being taken.
Speaking of partial backups, XtraBackup does not filter the REDO log (though it could), so it still tries to apply all log records, no matter what tablespace they modify. It just ignores those that do not exist. However, "create tablespace" records are always applied.