Mandatory information about my setup:
Have I read the related troubleshooter articles above before posting (which pages?)? YES
Have I searched the tickets before posting? YES
Have I read the documentation before posting (which pages?)? YES
Joomla! version: 2.5.2
PHP version: 5.3.5
MySQL version: 5.1.56-log
Host: (optional, but it helps us help you)
Akeeba Backup version: 3.4.2
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:
I think there is a bug in the "post-processing engine" that is being used to send backup files to box.net.
Situation:
-In the profile configuration the output directory is set to "Default Output Directory" (/homefolder_site/administrator/components/com_akeeba/backup/)
-The 2 authorisation steps towards box.net were succesfull
-The destination directory at box.net has been configured
-The option to delete local backup files when finishing the backup has been chosen
First issue:
-When the backup starts one can see in the "Default Output Directory" that backup files are being generated
-After the local backup has been completed these files are correctly transferred to the directory specified on box.net
-Then it happens: the local backup files are not being deleted but they are moved to the administrator's root directory, meaning that they will be included in the next backup and so doubling the volume that has to be backed up. The next backup this volume again will be doubled (4 x normal volume), the next time ...
To make sure that the problem is not located in my hoster's server I made backups towards a Dropbox account using the same options. This is working fine, after being transferred to Dropbox, the local backup files are being deleted from the default output directory.
Second issue:
Also the logfile that is being generated when using the the "post-processing engine" for box.net is moved to the administrator's root directory and therefore is not showing up in the Akeeba backup interface. The log that is being showed in the Akeeba interface is the log of the last backup before the backup to Box.net was performed.
The attached logfiles are coming from the administrator's root directory (akeeba.backend.log & akeeba.frontend.log)
I am not a native English speaker so I hope my explanation is understandable and not too confusing.
Best regards,
Georges
Have I read the related troubleshooter articles above before posting (which pages?)? YES
Have I searched the tickets before posting? YES
Have I read the documentation before posting (which pages?)? YES
Joomla! version: 2.5.2
PHP version: 5.3.5
MySQL version: 5.1.56-log
Host: (optional, but it helps us help you)
Akeeba Backup version: 3.4.2
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:
I think there is a bug in the "post-processing engine" that is being used to send backup files to box.net.
Situation:
-In the profile configuration the output directory is set to "Default Output Directory" (/homefolder_site/administrator/components/com_akeeba/backup/)
-The 2 authorisation steps towards box.net were succesfull
-The destination directory at box.net has been configured
-The option to delete local backup files when finishing the backup has been chosen
First issue:
-When the backup starts one can see in the "Default Output Directory" that backup files are being generated
-After the local backup has been completed these files are correctly transferred to the directory specified on box.net
-Then it happens: the local backup files are not being deleted but they are moved to the administrator's root directory, meaning that they will be included in the next backup and so doubling the volume that has to be backed up. The next backup this volume again will be doubled (4 x normal volume), the next time ...
To make sure that the problem is not located in my hoster's server I made backups towards a Dropbox account using the same options. This is working fine, after being transferred to Dropbox, the local backup files are being deleted from the default output directory.
Second issue:
Also the logfile that is being generated when using the the "post-processing engine" for box.net is moved to the administrator's root directory and therefore is not showing up in the Akeeba backup interface. The log that is being showed in the Akeeba interface is the log of the last backup before the backup to Box.net was performed.
The attached logfiles are coming from the administrator's root directory (akeeba.backend.log & akeeba.frontend.log)
I am not a native English speaker so I hope my explanation is understandable and not too confusing.
Best regards,
Georges
