Backup progress about backupwordpress HOT 12 CLOSED

We can with zip archive and pclzip. Not with zip command.

from backupwordpress.

Looks like getting progress info from zip should be possible too, see popen and passthrough

from backupwordpress.

We can with zip archive and pclzip.

To track progress here we should add another key to the backup status array that is stored as a JSON string in the .backup_running file.

Then During the ZipArchive and PclZip loops we can simply periodically write the number of files added to the backup status, we should probably do it every 100 files or so and see what effect that has on performance.

We could similarly add progress to the php mysqldump fallback method, however database backups are generally so quick it's probably lower priority.

Once we have it working for ZipArchive and PclZip we can look at doing it for zip.

from backupwordpress.

Looks like zip --verbose could help here.

  Verbose mode or print diagnostic version info.

              Normally, when applied to real operations, this  option  enables
              the  display of a progress indicator during compression (see -dd
              for more on dots) and requests  verbose  diagnostic  info  about
              zipfile structure oddities.

              However,  when -v is the only command line argument a diagnostic
              screen is printed instead.  This should now work even if  stdout
              is redirected to a file, allowing easy saving of the information
              for sending with bug reports to Info-ZIP.   The  version  screen
              provides  the help screen header with program name, version, and
              release date, some pointers to the Info-ZIP home  and  distribu-
              tion  sites,  and shows information about the target environment
              (compiler type and version, OS version, compilation date and the
              enabled optional features used to create the zip executable).

Maybe the different archive methods should have their own class, so we can handle their particularities separately

from backupwordpress.

Not sure how we'd stream that progress back to PHP though.

from backupwordpress.

with proc_open ?

from backupwordpress.

Nice! That would mean we could correctly check whether the backup process was still actually running and properly cancel it

http://php.net/proc_open

from backupwordpress.

this would be epic

from backupwordpress.

Actually, I will use ProcessBuilder http://symfony.com/doc/current/components/process.html

from backupwordpress.

Since switching to Process in #1001 we can now get access to progress: http://symfony.com/doc/current/components/process.html#getting-real-time-process-output

from backupwordpress.

@willmot and @pdewouters is this issue still active following merge of #1001 ? If so, what are the actionable tasks here?

from backupwordpress.

Yep still an issue. We don't present meaningful progress to the user currently, just a spinner and basic status message (backing up files etc).

Ideally we'd show more detailed progress so that users can see how long the backup is expected to take and how far through the process currently is.

from backupwordpress.