Support

Site Restoration

#38880 long file name causes restoration to fail

Posted in ‘Site restoration’
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

PHP version
8.0.28
CMS Type
Joomla!
CMS Version
4.2.8
Backup Tool Version
9.5.1
Kickstart version
7.2.0

Latest post by tampe125 on Thursday, 20 April 2023 04:48 CDT

dawehnes

Please see old ticket 38235 for detailed information.

We are having trouble restoring our daily backup.  The backup uses profile 2 and is automatically FTPed to a windows PC in my basement.  An attempt at restore identifies the two attached files as the cause of the failure.

I removed those files yesterday, and I was able to restore from the backup taken last night.  So, there is something about these files.

Our site allows individuals to upload PDF and JPG files.  We have a 2MB limit to the file size, but allow the file name to be quite long.  In the old ticket, I referenced these two files as having been uploaded into directory /uploads/2022/.  The individual has re-uploaded them for this year, so they were now in /uploads/2023/.

Is there a maximum file name length that Akeeba supports?

(The login username I setup for you for ticket 38235 is still available to you.)

Dave W

tampe125
Akeeba Staff

Hello,

the length of the filename is imposed by your operating system, not Akeeba Backup. If it's too long, Windows won't allow it, full stop. There's nothing that we (you and us) can do to fix that.

The only solution, if those are not critical files, is to flag the option "Ignore most errors" on Kickstart interface. Since those are "minor" issues, the restoration script won't stop if we can't copy a file.

Davide Tampellini

Developer and Support Staff

🇮🇹Italian: native 🇬🇧English: good • 🕐 My time zone is Europe / Rome (UTC +1)
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

dawehnes

Sorry, I guess I made an assumption that the length of the file name was the issue, based upon the earlier ticket.  I have downloaded them to my Windows desktop and they open just fine.  So the file names are compatible with Windows 10, where I am trying to do the restoration.

In that earlier ticket, you postulated that the issue was that the files were being modified at the time of the backup.  In the current case, the files were created on 2/13/2023 and should not have been touched since then.

So if it isn't a file name issue, and it isn't an issue of the files being updated, then why can't Akeeba restore the system when these files are included?

Dave

tampe125
Akeeba Staff

what's the full path where you're restoring your site? If the path plus the filename is longer than 256 chars, you're going to have problems.

Does it always happen to those two files? You can do a quick test: rename it to x.pdf and y.pdf, take a backup and try again. Does it successfully work?

Davide Tampellini

Developer and Support Staff

🇮🇹Italian: native 🇬🇧English: good • 🕐 My time zone is Europe / Rome (UTC +1)
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!