-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
create a logfile which contains all added mail objects #148
Labels
Comments
jrse
added a commit
that referenced
this issue
May 24, 2018
jrse
added a commit
that referenced
this issue
May 24, 2018
jrse
added a commit
that referenced
this issue
May 25, 2018
Added unit tests to evaluate behavior. - write to new file - write to existing file - write multithreading (pthread) - parse line in >> operator and reconstruct RadosSaveLogEntry.
jrse
added a commit
that referenced
this issue
May 25, 2018
…ion,poolname,namespace,oid (operations: save,cp,mv). activate login in 90-plugin.conf: plugin { rados_save_log=logfile.log }
jrse
added a commit
that referenced
this issue
May 25, 2018
jrse
added a commit
that referenced
this issue
May 25, 2018
- new option -r allows the deletion of ALL objects in the given logfile! - added unit tests to eval logfile read and deletion.
jrse
added a commit
that referenced
this issue
May 28, 2018
done. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In case of a failed backup restore, it is helpful to have a list of objects to make a full rollback easier.
For that we could use a global log file which can be defined in 90-plugin.conf.
If the log file is set, the plugin should log all mail object creations to this file via append (thread safe).
The log file entry should contain at least the name-space, oid and pool name. e,g, separated by semicolon or space.
The text was updated successfully, but these errors were encountered: