Support

Akeeba Backup for Joomla!

#21777 restauration problem for a joomla 2.5.28 site

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, 06 January 2015 00:46 CST

easytherm
Hi Nicholas and thank you for responding very quickly.

I'm affraid you misunderstood my ticket or I should say my explanations were not clear.
Since I use your excellent product, I have done more than hundred of restaurations. I know about what I speak!

Of course, I don't want to migrate my site with akeeba backup. It would be a nonsense !!
I just explained the context of my problem. Let me explain it the other way:

I need to know why path A and B does not give the same result

path A
host folder empty, database cleared
fresh install of joomla 2.5.28
fresh install of akeeba backup 4.1.0
fresh install of akeeba admin tools 3.4.2
--> working joomla 2.5.28 website
Backup of this working website as backup.jpa
test of migration using joomla upgrade: --> new website in joomla 3.3 works ok

path B
host folder empty, database cleared
restauration of backup.jpa using kickstart
--> working joomla 2.5.28 website (in my opinion should be the same as working joomla 2.5.28 website of path A)
test of migration using joomla upgrade: --> new website in joomla 3.3 not working (server 500 error as described in previous post)

I just can't understand in what the restaured joomla 2.5.28 website is different from the joomla 2.5.28 at the time of the backup.

In my head, this is the essence of akeeba backup. Both should be the same.
So if a website is the same after restauration, than at the time before the backup, it should work the same manner in both situations, which is obviously not the case here.

Please understand that I don't speak about upgrading through akeeba backup/kickstart. I just speak about saving and restoring the same version of joomla.

Can you please reconsider my question in this new point of view? I think I miss something but I need you help to find out what.

best regards

Jacques

nicholas
Akeeba Staff
Manager
The problem is not caused by restoring the site, it's caused by the extensions running in your site. This is also outside the scope of our support.

How to verify my claim:
Create a new Joomla! 2.5 site
Install Akeeba Backup
Take a new backup
Restore the backup on a different site
Upgrade to Joomla! 3.3; the site works therefore the problem is NOT the restoration.

For instructions on upgrading from 2.5 to 3.3 please consult http://www.siteground.com/tutorials/joomla-video/jooml25-to-joomla3/

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!

easytherm
Again, I should explain it with other words.

There are NO extensions on this test. Path A and B are exactly what you propose to me.

This test site just uses Joomla_2.5.28-Stable-Full_Package.zip. Nothing more (ok with joomla's provided sample data, just to show something)
Then I install akeeba backup pro, then Akeeba admin tools pro

There are no other data. Nothing, Nada, no extensions.
I backup then restore on the same location not on another location. Can this be the problem?

nicholas
Akeeba Staff
Manager
When I try the same thing –upgrading to Joomla! 3 by installing the Joomla! 3.3.6 Update ZIP package– I have no problem. Furthermore, as I have already said twice, restoring a backup results in the SAME site.

That said, you are restoring a site to a temporary URL. Please run Kickstart and read the popup text. Do you see that this is not supported because SEF URLs do NOT work with temporary URLs? Ergo, your problem is not the restored sites, it is the SEF URLs which do not work.

In the end of the day:
Backup your LIVE site.
Restore it LOCALLY.
Upgrade it to Joomla! 3.3 LOCALLY
Backup the LOCALLY upgraded Joomla! 3.3 site
DELETE all files/folders/database tables of the LIVE site.
Restore the backup to the LIVE site.

FYI this is how AkeebaBackup.com was migrated from Joomla! 2.5 to 3.2 last year with 10' of down time (this is how long it took me to upload and restore the backup of the upgraded site).

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!

easytherm
Of course I've read the kickstart popup yesterday.. Your are right, on my fault, I tried first on a temp URL ( for example http://107.37.223.47/~blabla/nemoswimclub-com/), then rechecked and redid it on a live site with a real domain name I pay for (www.nemoswimclub.com)

for example I launched kickstart using www.nemoswimclub.com/kickstart-pro.php

When I have to recover a site (in a normal case), I think I do exactly exactly the same. I've done it many times the year beeing.

I see that you recommend to make the upgrade on a local machine. Is there any reason why it couldn't work on a live host using full domain names. Do I miss something??




nicholas
Akeeba Staff
Manager
On the live host you have many moving parts outside your control including file/folders ownership and permissions and PHP timeouts. It's also much, MUCH harder to debug site issues on a live server than on a local server. With all that in mind it is far easier to upgrade your site locally than on a live server.

Moreover, if you upgrade directly on a live server you will necessarily have significant amounts of downtime while you are making sure that the upgrade worked (or restoring a backup if the upgrade failed). If you upgrade locally and transfer the upgraded, tested to be working, site on the live server afterwards you have near zero downtime.

It's not exactly the same case, but you can read http://www.dionysopoulos.me/how-i-transferred-a-7gb-site-with-15-of-downtime/ This was far more difficult than a site upgrade, in the sense that I had to migrate email accounts, CRON jobs and half of the known Universe. A site migration is much simpler since you only have to move the Joomla! site itself.

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!

easytherm
Ok Nicholas,

I'll follow your advise and reinstall my local apache server...

Thank you for your explanations

nicholas
Akeeba Staff
Manager
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!

easytherm
Hi again Nicholas

This time my post is not about a problem, but a positive information.

As explained, I reinstalled my wampserver and tested my above step locally and you know what?

I had exactly the same problem
install joomla 2.5
install akeeba backup
make a backup
migrate to joomla 3.3
delete all files
reinstall last backup
joomla 2.5 run fine
migrate to joomla 3.3 crashes on local server

Ok, I think I may have to drop completely the database ( deleting table content from kickstart may not be sufficient) so I deleted then create the database again.
now I can reinstall joomla 2.5 from backup and migrate to joomla 3.3. works like a charm
(I suppose the joomla 3 table structure is different from joomla's 2.5 so overwriting during kickstart is not sufficient)
I know you told me to delete the database, but I thought the "delete" during reinstallation was sufficient to overwrite all..


I am a bit stubborn and I decided to check the same on my host's server. (dropping then creating the database again). You guess it, it works also.

So now you may close this ticket and I thank you for your patience. Maybe my conclusions may help somebody else..



nicholas
Akeeba Staff
Manager
The instructions given by our support are like the child's game "Simon says". You do as Simon says or you lose ;)

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!