I just downloaded Akeeba Core 3.2b4 along with Remote Control 4.0.3 and am testing them now on all my websites, both Windows & Linux based servers. Here are my observations:
1) New to Remote Control is the check box option to "Delete files from server after download" which I REALLY like, although I'm not positive it's working as expected. Also noteworthy is that when I select that check box and click OK, then edit the configuration again, that check box is no longer selected. So the option doesn't "stick" when selected. Not sure if this is by design or not.
2) Remote Control was already upgraded to 4.0.3 and open ready to backup my next site, but I had to install Akeeba 3.2b4 first. Once installed, I ran the Configuration Wizard and was ready to backup via RC, but got an error. Once I closed and re-opened RC, the backup worked without any issues. It would appear that once RC is opened, it "remembers" what version of Akeeba was on the website and won't work properly until closed/reopened.
3) I thought it best to go into the Akeeba Component under Administer Backup Files and do some cleaning up of all those backup files. I deleted all other instances of previous backups in order to verify the removal of the backup once it's downloaded locally. That test is still in progress, but I thought it worth mentioning to not forget about this location in the component.
4) From within the Akeeba Backup Component, I clicked on VIEW LOG and saw several options in the drop down box. Those options are: JSON API, Backend, Lazy Plugin, and Remote API. Another nifty discovery today, although once the backups are deleted, some of those options will disappear.
5) When the option to send an email is checked, it should be noted that the email message arrives long before the backup file is downloaded. Just another observation on my part.
So far, the site that has lots of Joomla tutorials on it (MP4s) seems to be downloading the JPA file just fine now, although it's painfully slow. Must have something to do with all this snow we have on the ground. :-) I will be interested to see if the backup file gets deleted from the backend of Joomla. I'm not sure the first backup test did, but then again I hadn't cleaned out all the old/obsolete backup files prior to that test.
I plan to configure my backups to run while I'm still asleep, but would like to know two things:
1) Is there any way to retain the checkbox to delete the backup file from the server after download is complete?
2) Do you recommend staggering the backups, especially if one of them is rather large? Or is the only limitation our own given Internet speeds? I probably wouldn't backup 10 sites all at the same time, but stagger them every 15 minutes or so. Better option?
Thanks again, Nicholas, for a speedy update to both the Akeeba Core AND Remote Control. Absolutely perfect for automating a process that should be done on a regular basis to prevent data loss.
KUDOS!!
1) New to Remote Control is the check box option to "Delete files from server after download" which I REALLY like, although I'm not positive it's working as expected. Also noteworthy is that when I select that check box and click OK, then edit the configuration again, that check box is no longer selected. So the option doesn't "stick" when selected. Not sure if this is by design or not.
2) Remote Control was already upgraded to 4.0.3 and open ready to backup my next site, but I had to install Akeeba 3.2b4 first. Once installed, I ran the Configuration Wizard and was ready to backup via RC, but got an error. Once I closed and re-opened RC, the backup worked without any issues. It would appear that once RC is opened, it "remembers" what version of Akeeba was on the website and won't work properly until closed/reopened.
3) I thought it best to go into the Akeeba Component under Administer Backup Files and do some cleaning up of all those backup files. I deleted all other instances of previous backups in order to verify the removal of the backup once it's downloaded locally. That test is still in progress, but I thought it worth mentioning to not forget about this location in the component.
4) From within the Akeeba Backup Component, I clicked on VIEW LOG and saw several options in the drop down box. Those options are: JSON API, Backend, Lazy Plugin, and Remote API. Another nifty discovery today, although once the backups are deleted, some of those options will disappear.
5) When the option to send an email is checked, it should be noted that the email message arrives long before the backup file is downloaded. Just another observation on my part.
So far, the site that has lots of Joomla tutorials on it (MP4s) seems to be downloading the JPA file just fine now, although it's painfully slow. Must have something to do with all this snow we have on the ground. :-) I will be interested to see if the backup file gets deleted from the backend of Joomla. I'm not sure the first backup test did, but then again I hadn't cleaned out all the old/obsolete backup files prior to that test.
I plan to configure my backups to run while I'm still asleep, but would like to know two things:
1) Is there any way to retain the checkbox to delete the backup file from the server after download is complete?
2) Do you recommend staggering the backups, especially if one of them is rather large? Or is the only limitation our own given Internet speeds? I probably wouldn't backup 10 sites all at the same time, but stagger them every 15 minutes or so. Better option?
Thanks again, Nicholas, for a speedy update to both the Akeeba Core AND Remote Control. Absolutely perfect for automating a process that should be done on a regular basis to prevent data loss.
KUDOS!!
