Support

Please look at the bottom of this page (under Support Policy Summary) for our support policy summary, containing important information regarding our working hours and our support policy. Thank you!

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,

I did look at various tickets based on keywords first, and didn't see an answer to this question ...

I have a site I've been working on which is in a subdirectory of a subdirectory of a domain, i.e.:

mydomain.com/SUBDIR_LEVEL1/SUBDIR_LEVEL2/

Akeeba Backup Pro has been storing this site's backups in: mydomain.com/SUBDIR_LEVEL1/BACKUPS/

I've backed up and restored the site to a new subdirectory at the same level, i.e.:

mydomain.com/SUBDIR_LEVEL1/SUBDIR_#2_LEVEL2/

I did this to create a new location to update Joomla! and old components and leave the original work intact, as it's been sitting for a little while and everything is out of date, and there is a custom component which I expect may break in small ways due to Joomla! changes.

It seemed to me potentially disastrous to have this second site also save its backups in "mydomain.com/SUBDIR_LEVEL1/BACKUPS/". So I created a separate backup directory for the copied site, and changed its backup location in Akeeba Backup Configuration.

However, I notice that the new site, while saving new backups in the new location, is still pulling all the old backups' information (it's been running nightly as a chron job) under "Manage Backups" from "mydomain.com/SUBDIR_LEVEL1/BACKUPS/" -- i.e., since those URLs are in the database.

Is there anything dangerous about this setup in terms of file or data corruption, etc.? I'm thinking its OK, with the separate backup directory, but wanted to check. I have already rebuilt the new site's .htaccess using Admin Tools, and .htaccess files in the higher level directories of the domain are presently empty.

Thanks for your help,

Sam

Sam,

It is not a problem to have the old backups in Manage Backups. That's just a side effect of moving the site. Those records should be grayed out because the backups are no longer in the Output folder.

Thank you Dale ...

A smallish followup question - the entries for the old backups are not grayed out, and the downloads are still accessible. Although attempting to click on the buttons for accessing the old backups' logs gives you a message that "The log file, akeeba.log, does not exist in your output directory", if you click the "Download" for the old backups themselves, you get them.

Does that change your answer at all? I'm thinking not; they are on the same server, still, and the new site has the relative URL in the database, so it can get them - no harm in that, I guess?

Thanks again,

Sam

Sam,

I guess that does make sense, it is remembering where the backups were stored when they were done, not where they would go if they were done now. And in this case, they still exist on that path.

DON'T delete these backup records! The new site knows where they are and will really delete them. If the records for the old site really bother you, you could move the backups to a temporary directory, delete the records in the new site, then move them back. I don't think the old site would notice, they would still be in Manage Backups. Even if they get marked as obsolete, we could import them into the Manage Backups screen on the old site. Don't go to the Manage Backups screen on the old site while the backups are in the temporary directory.

The software doesn't care, the only danger is that you might restore an old site backup over the new site.

OK Dale, that seems sensible ... Feel free to close the ticket, and thanks again for your help.

You're welcome!