-
Suggestion
-
Resolution: Fixed
-
None
-
6
-
12
-
NOTE: This suggestion is for Confluence Server. Using Confluence Cloud? See the corresponding suggestion.
The progress bar used in the restore process should also be applied to making backups
- is related to
-
- Closed
- relates to
-
- Closed
-
- Closed
[CONFSERVER-7053] Confluence should display the progress of a backup
+1 Sometimes good to know a progress instead of checking in filesystem
this is a sever limitation of the product. Jira easily shows the progress.
It's a much needed solution, since we're in world for pipeline process, Not sure why Atlassian is not evening thinking about it. Engineering team should provide such ideas to the product building team.
+1 here as well...it would be super helpful to see the status of a backup, especially for larger installations.
+1, just raised a support ticket because of that lacking "feature", including escalation, 4 people involved...
Coming up to the 11 year anniversary for this issue. We have an importing progress bar, how hard can an exporting one be?
In Chrome 59, when attempting a manual backup for a large site that takes 12h to complete an export, if I leave the request pending, Chrome will refresh the page 2 more times, every 7.5 minutes, triggering 2 more backup actions. This caused the export to fail as the disk filled up with 3 simultaneous backup files with all attachments in each. Very frustrating when the backup takes 12h to execute.
This of course would be avoided if the request completed, at the very least advising that a backup has commenced and to check server logs for details.
2017-07-04 16:07:04,270 INFO [http-9015-7] [atlassian.confluence.upgrade.AbstractUpgradeManager] getExportBuildNumber Backward compatibility for export: Checking...
2017-07-04 16:14:35,750 INFO [http-9015-8] [atlassian.confluence.upgrade.AbstractUpgradeManager] getExportBuildNumber Backward compatibility for export: Checking...
2017-07-04 16:22:44,248 INFO [http-9015-4] [atlassian.confluence.upgrade.AbstractUpgradeManager] getExportBuildNumber Backward compatibility for export: Checking...
Adam Millgate
added a comment - This gets my vote. It's insane that the server does not provide any feedback to the browser that a backup is taking place. I'm currently running a backup and have to keep checking the size of files in file system to make sure something is happening.
When is this going to be implemented? You have it on the import screen, and that's just the reverse of what is happening here.
Adam Millgate
added a comment - This gets my vote. It's insane that the server does not provide any feedback to the browser that a backup is taking place. I'm currently running a backup and have to keep checking the size of files in file system to make sure something is happening.
When is this going to be implemented? You have it on the import screen, and that's just the reverse of what is happening here. 
Vicky Thai
added a comment - This issue was opened years ago but there is still no progress bar. It took me 3 hours to do a backup, and a progress bar along with some indication of the time remaining would not only give the user some peace of mind that the backup is actually taking place, it would let them know if it is going to take too long and let the user do something about it (like defer the backup task to a time with lower server load). When running the backup inside a web browser, at the bottom it just keeps saying 'Waiting for....' and it drove me nuts to have to check it from time to time to see if anything had changed. This issue definitely gets my vote!!
Vicky Thai
added a comment - This issue was opened years ago but there is still no progress bar. It took me 3 hours to do a backup, and a progress bar along with some indication of the time remaining would not only give the user some peace of mind that the backup is actually taking place, it would let them know if it is going to take too long and let the user do something about it (like defer the backup task to a time with lower server load). When running the backup inside a web browser, at the bottom it just keeps saying 'Waiting for....' and it drove me nuts to have to check it from time to time to see if anything had changed. This issue definitely gets my vote!! I would have to agree, some sort of progress bar other than the mini progress bar at the bottom of browsers would at least give a user some peace of mind that something useful is actually happening. This would be especially reassuring when rather large backups are being created.
Roberto Dominguez
added a comment - Another (serious) side effect of this issues is that a user (i.e. me) would try to run the backup again... and again... and it turns out that the thread running the backup does not die, therefore you are left running a few backups one after the other... this one gets my vote...
Roberto Dominguez
added a comment - Another (serious) side effect of this issues is that a user (i.e. me) would try to run the backup again... and again... and it turns out that the thread running the backup does not die, therefore you are left running a few backups one after the other... this one gets my vote... 
Mark Sheppard
added a comment - I totally agree with this. When trying to do a manual backup (to try and work out why the automatic backups were failing) I got a "503 Service unavailable" HTTP error from the Apache server we use as a frontend to Confluence, as the backup took longer than whatever the default mod_ajp timeout is. In the end I worked around the issue by re-enabling the default HTTP connector on port 8080 in Tomcat and connecting directly to that.
Mark Sheppard
added a comment - I totally agree with this. When trying to do a manual backup (to try and work out why the automatic backups were failing) I got a "503 Service unavailable" HTTP error from the Apache server we use as a frontend to Confluence, as the backup took longer than whatever the default mod_ajp timeout is. In the end I worked around the issue by re-enabling the default HTTP connector on port 8080 in Tomcat and connecting directly to that. 
Stefan Prange
added a comment - Hi,
not having a progress bar means that the browser simply waits for a response while the server, i.e. Confluence, processes the export resp. backup request.
For very large spaces the export takes a lot of time (> 5 minutes). This leads to a situation where the browser stops waiting because of a timeout.
Or maybe it's the webserver which waits unavailingly for the application server.
But anyway, the user's experience in our case is, that the export does not succeed.
The browser shows the following error message:
*~
Proxy Error
The proxy server received an invalid response from an upstream server.
The proxy server could not handle the request POST /wikis/spaces/doexportspace.action.
Reason: Error reading from remote server
*~
So I think there has to be some sort of feedback from the server to the browser during the export.
That's why there should be a progress bar during export, too. Not only during the import.
I attached a modified screenshot of the import's progress bar to make clear what a solution could look like.
Kind regards,
Stefan Prange
Stefan Prange
added a comment - Hi,
not having a progress bar means that the browser simply waits for a response while the server, i.e. Confluence, processes the export resp. backup request.
For very large spaces the export takes a lot of time (> 5 minutes). This leads to a situation where the browser stops waiting because of a timeout.
Or maybe it's the webserver which waits unavailingly for the application server.
But anyway, the user's experience in our case is, that the export does not succeed.
The browser shows the following error message:
*~
Proxy Error
The proxy server received an invalid response from an upstream server.
The proxy server could not handle the request POST /wikis/spaces/doexportspace.action.
Reason: Error reading from remote server
*~
So I think there has to be some sort of feedback from the server to the browser during the export.
That's why there should be a progress bar during export, too. Not only during the import.
I attached a modified screenshot of the import's progress bar to make clear what a solution could look like.
Kind regards,
Stefan Prange
Hi All,
This issue was fixed as part of the improvement to our backup/restore system released in Confluence 8.3.0. A progress bar is now shown during both backup and restore processes.
Thanks,
Jacqueline Bietz
Product Manager, Confluence Data Center