EXTREMELY IMPORTANT: Please attach a ZIP file containing your Akeeba Backup log file in order for us to help you with any backup or restoration issue. If the file is over 2Mb, please upload it on your server and post a link to it.
Description of my issue:
Hello Nicholas / Akeeba,
On Joomla 2.5.20 and 3.3.0 sites (live and dev/test) I have noticed that when updating an extension where Akeeba Backup creates a System Restore Point before updating the extension that on occasion the next System Restore Point in the list of Restore Points would become "Obsolete".
(The Joomla 3.3.0 sites have now been updated to 3.3.1 but the issue intermittently occurred when they were v3.3.0).
This would not happen every time. I have been trying to find a common element for when this does happen. (Not yet found anything that is obvious to me).
However, now that Akeeba Backup has been updated to v3.11.2 this appears to be happening more regularly.
My normal process for carrying out updates are:
1) "other" (I.e non-joomla, and non-Akeeba extensions);
2) Akeeba Backup;
3) Akeeba AdminTools;
4) Joomla;
On my latest update of Akeeba Backup, 4 of my "other" System Restore Points on one site became Obsolete.
I normally check each extension updated immediately after updating it in case of any issue(s) and have,so far, never needed to use the Restore/Roll Back feature.
Dev/Test sites are done before live sites.
There is one more site for me to do some updates on (Live) - but want to apply caution before proceeding.
I found one of your previous tickets which was similar (ticket 9184) but this was from 30th November 2011 - your great products have been updated several times since then.
Do you have any tips / pointers on how I might be able to pinpoint where my issue lies ?
Perhaps swapping points 1) and 2) above ?
So far, I have been fortunate enough
Regards,
Tim
Description of my issue:
Hello Nicholas / Akeeba,
On Joomla 2.5.20 and 3.3.0 sites (live and dev/test) I have noticed that when updating an extension where Akeeba Backup creates a System Restore Point before updating the extension that on occasion the next System Restore Point in the list of Restore Points would become "Obsolete".
(The Joomla 3.3.0 sites have now been updated to 3.3.1 but the issue intermittently occurred when they were v3.3.0).
This would not happen every time. I have been trying to find a common element for when this does happen. (Not yet found anything that is obvious to me).
However, now that Akeeba Backup has been updated to v3.11.2 this appears to be happening more regularly.
My normal process for carrying out updates are:
1) "other" (I.e non-joomla, and non-Akeeba extensions);
2) Akeeba Backup;
3) Akeeba AdminTools;
4) Joomla;
On my latest update of Akeeba Backup, 4 of my "other" System Restore Points on one site became Obsolete.
I normally check each extension updated immediately after updating it in case of any issue(s) and have,so far, never needed to use the Restore/Roll Back feature.
Dev/Test sites are done before live sites.
There is one more site for me to do some updates on (Live) - but want to apply caution before proceeding.
I found one of your previous tickets which was similar (ticket 9184) but this was from 30th November 2011 - your great products have been updated several times since then.
Do you have any tips / pointers on how I might be able to pinpoint where my issue lies ?
Perhaps swapping points 1) and 2) above ?
So far, I have been fortunate enough
Regards,
Tim
