[Bugs] [Bug 1207028] [Backup]: User must be warned while running the 'glusterfind pre' command twice without running the post command

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1207028



--- Comment #3 from Aravinda VK <avishwan at redhat.com> ---
(In reply to Sweta Anandpara from comment #2)
> >> Pre command always gets the latest information when we run more than once
> 
> Does it not compare the time stamp in the status file (in $SESSION_DIR), and
> compare the mtime/ctime of files wrt to *that* timestamp? 
> 
> In the case where the customer has run pre command, supplied the outfile to
> the backup tool and forgotten to run the post command - the next pre command
> is going to get the list of files wrt to the time stamp present in the
> status file. And this will result in an outfile which will have one *big*
> list of files - which includes all the changed-files already backed up from
> the previously run pre command as well.

pre and post commands will be configured as hook script in backup utilities, so
will get executed automatically.

If post command is failed or not run, that means some failure in consuming the
file generated from pre command. So when we run next time it should pick those
changes again since it is not completed last time.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.