Manage User Backups

existenz

Verified User
Joined
Jul 18, 2003
Messages
542
Location
/dev/null
It does not seem to work for me on my home machine. Safari the browser times out because it is waiting for more than 60 seconds to open the page:

http://domain.com:2222/CMD_USER_BACKUP

I was not able to duplicate this problem in IE. Not sure if Mozilla etc have the same problem. Smaller sites backup fine the larger ones don't.

The other problem is that the button is greyed out after hitting submit. So if you want to do a backup of one site then another it is not possible. Not sure if it was designed that way?
 
As you report, I also am having no problems with IE. Haven't tested it on any other browser though.

However, on the timeouts, can we possibly not have the browser wait while it does the backup? Can't DA just invoke something that does the work? (and when it's done, the users will show up in the backed-up listing)
 
I was thinking of that.. like the process just keeps on chugging away, but the browser is sent the next page before anything happens. This feature can be considered beta in a way, as it hasn't been tested outside of the build system. Just a note: the process *does* keep on going no matter what.. so even if you lose your internet connection 2 seconds in, the process *should* finish up. The timeout in DA is 60 minutes, so that should be enough time.

I wonder if browsers would like it better with an incremental output as it's going along? Then Reseller can watch it as it goes, to see where it is and figure out how much longer it will take. It would probably be an ugly plain text html page, but it would be dynamic and offer reassurance that its working. This works only if the 60 second limit isn't a hard limit, even if the page has been loading slowly. (ie, 60 seconds from the intial load, or 60 from the last data received).

Let me know what you think, or suggesstions on how this can be made better.

John
 
John,

Go with the plain ugly page :D . I see that it seems to make the backup. For the next release (assuming you don't have time) if you make a page like the one when we update the license or DA that says it has been scheduled that would be better.
 
Ok, well have a bit of a poll here for what we want:

1) realtime dynamic page that give steady output as the backup goes along. The page would be very simple html and wouldn't be very pretty, but would provide the most information.

2) add it to the task queue. You wouldn't really know what's going on after you send it in.. if any errors occur, you might be in the dark. We could make it send a message upon completion.

3) Let the directadmin program do it, but close the pipe immediately (sends them a message, but closes it before the backup starts). This would be close to #2, but the directadmin binary would be doing it right away, vs #2 where the dataskq would be running it upto 1 minute away. This isn't a very sound way of doing it as it uses up on the of the DA deamons which may lock people out if everyone is doing a backup at the same time (not to mention bog down the system if multiple copies are doing it). the dataskq would only run one at a time.. so, #2 is probably better.

So, #2 would probably be the best, but let me know what you guys think. There is also the ftp upload time to consider, so a background process might be the best.

John
 
Or it could write to/update a .html page as it completes each step...

backup02142004.html
backup02152004.html

etc.

Just have the page update as each domain/acct is completed, and the pages could be stored for "posterity" - and you could come back to check on the page periodically.

Just a thought
 
I had an idea of a "status" bar that would dynamically update as the backup task chugs along. An iframe on the backups page would work prefect for this.

Of course even with this goodie, the task queue will still manage backups. That is, you'll probably have to refresh the page after the backup task has initiated to see the bar.

Maybe? :)
 
Back
Top