Support

Akeeba Backup for Joomla!

#9252 backup status is Obsolete

Posted in ‘Akeeba Backup for Joomla! 4 & 5’
This is a public ticket

Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.

Environment Information

Joomla! version
n/a
PHP version
n/a
Akeeba Backup version
n/a

Latest post by nicholas on Tuesday, 03 January 2012 12:58 CST

Monday, 02 January 2012 20:35 CST

user52972
PHP Built on: Linux server.ob-media.net 2.6.18-238.19.1.el5 #1 SMP Fri Jul 15 07:31:24 EDT 2011 x86_64

Database Version: 5.1.56-log

Database Collation: utf8_general_ci

PHP Version: 5.2.17

Web Server: Apache/2.2.21 (Unix) mod_ssl/2.2.21 OpenSSL/0.9.8e-fips-rhel5 mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635

Web Server to PHP interface: cgi

Joomla! Version: Joomla! 1.5.25 Stable [ senu takaa ama mamni ] 14-November-2011 18:00 GMT

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.7 (KHTML, like Gecko) Chrome/16.0.912.63 Safari/535.7


No idea where the log file is located
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.

Latest backup (both backend and Lazy Scheduling) are now showing a status of Obsolete.

Using Amazon S3 storage. Everything was working fine until this evening.

I deleted all of the backup logs AND removed the S3 files. Still getting the same status.

Akeeba version "Akeeba Backup Professional 3.3.10 (2011-12-04)"

-jay

Tuesday, 03 January 2012 02:27 CST

nicholas
Just upgrade to 3.3.11 and take a new backup. The status should now read "Remote", not "Obsolete". Also, please read the documentation regarding the meaning of the "Obsolete" backup status. It is normal to see that in pre-3.3.11 versions of Akeeba Backup for archives stored on S3. Essentially, you are transferring a file to S3 and removing it from your site's server. This means that the backup archive is not on the server, hence "Obsolete". The change in 3.3.11 is that we print a status of "Remote" instead of "Obsolete" when we see that the backup archive was transferred to remote storage right after backup, to reduce confusion.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Tuesday, 03 January 2012 11:40 CST

user52972
The Upgrade to 3.3.11 worked:

Akeeba Backup Professional 3.3.11 (2012-01-02)



However when I run the backup it's still saying that it's obsolete.


"
	 93	Backup taken on Tuesday, 03 January 2012 12:35	 03.01.12	00:00:17	Obsolete	Backend	Full site backup	1	(19.43 Mb)	â

Tuesday, 03 January 2012 11:41 CST

nicholas
OK, we're in good track. I want you to take a look at your jos_ak_stats table using phpMyAdmin and tell me if you see a field called remote_filename in that table.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Tuesday, 03 January 2012 11:49 CST

user52972
Remote filename is there and the value is "NULL."

-j



------------------------------------------
SQL result

Host: localhost
Database: harvardc_joom1
Generation Time: Jan 03, 2012 at 12:45 PM
Generated by: phpMyAdmin 3.4.7.1 / MySQL 5.1.56-log
SQL query: SELECT * FROM `jos_ak_stats` LIMIT 2, 1 ;
Rows: 1

id	description	comment	backupstart	backupend	status	origin	type	profile_id	archivename	absolute_path	multipart	tag	filesexist	remote_filename	total_size
93	Backup taken on Tuesday, 03 January 2012 12:35		2012-01-03 17:35:22	2012-01-03 17:35:39	complete	backend	full	1	site-www.harvardclassifieds.com-20120103-123522.jpa	/home/harvardc/public_html/administrator/components/com_akeeba/backup/site-www.harvardclassifieds.com-20120103-123522.jpa	1	backend	0	NULL	20372540

Tuesday, 03 January 2012 11:51 CST

nicholas
Is the file uploaded to S3? Does the file exist on your server, in the backup output directory?

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Tuesday, 03 January 2012 12:07 CST

user52972
The file is on S3:
Size:	19.4 MB
Last Modified:	Tue Jan 03 12:35:44 GMT-500 2012
Owner:	Me
ETag:	9cd4e10c8a8495f8d50375bee058a5c8
Expiry Date:	None
Lifecycle Rule:	N/A


And is *NOT* on the server at:/home/harvardc/public_html/administrator/components/com_akeeba/backup


-jhay

Tuesday, 03 January 2012 12:13 CST

nicholas
Please go to Akeeba Backup, Configuration, find the Data Processing engine, click on the Configure button next to it. On the pane which opens below, is the "Process each part immediately" checked? If it is, the Obsolete status is perfectly normal. If not, please send me a Personal Message (I am user "nicholas") with the following information:
- A link back to this thread, so that I know why you're sending me the PM
- The URL to your site's back-end
- Super Administrator username and password
so that I can take a look.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Tuesday, 03 January 2012 12:41 CST

user52972
The "Process each part immediately" is checked.

Not sure what you mean when you say the correct status is "Obsolete".

I want to configure it so that I can see the links to the backup files in S3. What do I need to change?

Thanks,

-jay

Tuesday, 03 January 2012 12:44 CST

nicholas
You will have to uncheck the "Process each part immediately" checkbox. Due to some architectural limitations, when this option is checked Akeeba Backup can't correctly keep track of whether a backup archive has completed being transferred to S3, therefore displays its status as "Obsolete". Unchecking this box will first create the backup on your site's server, then upload it and finally remove it from your site's server. This allows Akeeba Backup to correctly track the status of the S3 transfer and report the status of the backup as "Remote", showing the links to the archives on S3.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Tuesday, 03 January 2012 12:57 CST

user52972
It is now displaying "Remote" AND I can see the files on S3. Thank you for your patience.

-jay

Tuesday, 03 January 2012 12:58 CST

nicholas
Awesome! You're welcome :)

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Support Information

Working hours: We are open Monday to Friday, 9am to 7pm Cyprus timezone (EET / EEST). Support is provided by the same developers writing the software, all of which live in Europe. You can still file tickets outside of our working hours, but we cannot respond to them until we're back at the office.

Support policy: We would like to kindly inform you that when using our support you have already agreed to the Support Policy which is part of our Terms of Service. Thank you for your understanding and for helping us help you!