Upgrade from 7.5 to 8.22

Bugtamer — Mon, 14 Jul 2025 15:40:34 -0000

I'm glad you were able to resolve the issue with ACL support.

Regarding the other issue, I was able to reproduce the error with the targets.
In 7.5, the targets load without any error messages in the log, and in 8.2.4 (I imagine other 8 versions), it gives an error. I'll give you more details when I make more progress with the debugging, have a fix, or have any questions.

Thank you for your feedback.

Upgrade from 7.5 to 8.22

Manfred Alfaré — Sat, 12 Jul 2025 22:55:49 -0000

ACL problem in areca 7.5 solved.
Thank you for the tips

Upgrade from 7.5 to 8.22

Manfred Alfaré — Sun, 06 Jul 2025 22:18:04 -0000

Found your post today.

7.5 only runs with Java 8
8.2.3 I tried with Java 21 and with 8.

First try was unpack 8.2.x over 7.5m was not able to read the configuration files.
Later try was, to unpack beside and set the path to the 7.5 workspace directory

I am not able to compile anything :-(

I did this today:
1. Save/copy everything of 7.5
2. make a copy of "/home/alf/.areca/workspace/948527365.bcfg"
3. Name it to /home/alf/.areca/workspace/941234565.bcfg
4. Edited it (uid="941234565",
name="TEST" and path="/media/alf/Ventoy/ArecaBACKUP/941234565"
5. Prepared another USB-Stick (/media/alf/Ventoy/ArecaBACKUP/941234565)
6. Start areca 7.5 Java 8.0
7. Made a Backup
8. Unpack "areca-8.2.4-linux-x86-64.tar.gz"
to "/home/alf/PROG/areca-8.2.4-linux-x86-64"
9. Start it (with Java 21)
10.Cannot import. Only an unencrypted xyz.bcfg is listed.
all .bcfg are in "/home/alf/.areca/workspace"
11. This might be the problem ?:
"ERROR - javax.crypto.BadPaddingException: Given final block not properly padded. Such issues can arise if a bad key is used during decryption."
This error is thrown for every encrypted .bcfg, but not for the unencrypted
12. No directory TEST (Target) in "/home/alf/PROG/areca-8.2.4-linux-x86-64/jdk",
so no areca.yy-mm-dd.log (Areca log).

I've done my best, hope it helps.
Best regards,
Manfred

Upgrade from 7.5 to 8.22

Bugtamer — Thu, 03 Jul 2025 15:05:28 -0000

Sorry for the delay in getting back to you.

Only the first attachment showed an error related to the imports (an EOF, End Of File, error in the history of one of the targets, but near the end of the log). It's not relevant to fix the issue.

(1) When you installed Areca 8.2.3, did you make any modifications to it, or did you use it as-is after extracting it?

I also assume you use the same JRE or JDK for both Arecas.

(2) Could you please Duplicate a "Target" (e.g. 1234567890.bcfg files) in Areca 7.5 and change the sources to backup irrelevant data, make a backup and,
then import it into 8.2.3 (to generate logs) and send me the following files along with the full generated archive so I can review it:

~/.areca/preferences.properties (I assume both Areca 7.5 and 8.2.3 are using this file)
areca/config/fwk.properties (from both versions: 7.5 and 8.2.3)
the generated logs from ~/.areca/workspace/.log/, for example: ~/.areca/workspace/.log/1234567890.yy-mm-dd.log (a log of the 1234567890.bcfg target) and areca.yy-mm-dd.log (Areca log).

You may mask some information if you feel it necessary,
but please try not to change the original charset or alter things in a way that makes it hard to understand the paths or configurations.

Regarding ACL:
com.myJava.file.metadata.posix.basic.DefaultMetaDataAccessor ignores ACL permissions, which is why it doesn’t raise any errors.
However, if you do need ACL support (Linux), you must ensure the following:

filesystem.accessor.impl = com.myJava.file.metadata.posix.jni.JNIMetaDataAccessor (in areca-Backup/config/fwk.properties)
a version of areca-Backup/lib/libarecafs.so that is compatible with your system (you may need to recompile it on your own machine)
and a symlink in areca-Backup/lib/libacl.so that points to something like libacl.<some version number>.so on your system.

One or more of the above might be causing ACL to fail. (In Areca 7.5, there may also be an issue with the parameter order used to compile liblibarecafs.so.)

There are more details in the ACL_troubleshooting.txt I previously indicated (repeating and clarifying here in case it helps another user).

Best regards,
bugtamer

Upgrade from 7.5 to 8.22

Manfred Alfaré — Sat, 28 Jun 2025 23:37:55 -0000

Hi!
The files are O.K., I can work with them in 7.5.
But 8.2.3 cannot open them. The important because the used latest are:
882509893.bcfg (local mounted Cloud)
2105513566.bcfg (Stick)
ACL is not my problem, I get no errors any more in 7.5 after I uncommented

filesystem.accessor.impl = com.myJava.file.metadata.posix.basic.DefaultMetaDataAccessor

in "fwk.properties"

Set path to:
/home/alf/.areca-OLD/workspace
where two additional workspaces lie.
All of them have key included.
Terminal output appended.

Regards
Manfred

Upgrade from 7.5 to 8.22

Bugtamer — Thu, 26 Jun 2025 14:08:31 -0000

Hi
I don't really know what it could be.
Assuming the *.bcfg files aren't corrupted, you could try, if you haven't already, opening the original *.bcfg files instead of importing their backups by opening their workspace, as shown in the image.
Regards

Upgrade from 7.5 to 8.22

Bugtamer — Wed, 25 Jun 2025 20:59:54 -0000

Dear Manfred,
I just saw your message.
I just completed a release, 8.2.3, and have already exhausted the time I was going to spend on Areca. I'll take a look at it another time and see if I can help you with the import.

For now, I'll just point you to where there are notes on how to activate ACL. It seems that in your case you have to recompile libarecafs.so in your own system, follow the steps indicated in path-to/areca-backup/help/ACL_troubleshooting.txt (Markdown format).

Best regards,
bugtamer

Upgrade from 7.5 to 8.22

Manfred Alfaré — Thu, 12 Jun 2025 21:24:44 -0000

Hi!

Yesterday I was very happy when I noticed that areca is being further developed.
I have been using areca for about 10 years on a USB stick and a web space. A few years ago I switched to another web space provider and at the same time I started using a new USB stick.
With the release of Java Ver.11, I entered the absolute paths to the Java 8 installation in areca_run.sh and have been using areca 7.5 to this day (almost) without any problems.

There were complaints that ACL was not working; after a few attempts to fix this, I ignored them.

I first backed up the old areca program directory, including the ~/.areca
After some experiments (and reading the tutorials), I imported the files from the directories
/media/alf/BACKUP_2/ArecaBACKUP/areca_config_backup/2105513566.bcfg
and
/home/alf/MyStorBox/ArecaBACKUP/areca_config_backup/882509893.bcfg
into areca.

The aim was (and is) not to lose the old archives.

Unfortunately this did not work 🙁

There were lots of error messages like this:
25-05-25 02:19 - ERROR - An error occurred while reading the manifest file for the following archive: /media/alf/BACKUP_2/ArecaBACKUP/2105513566/240824
and
25-05-25 06:17 - ERROR - An error occurred while reading the manifest file for the following archive: /home/alf/MyStorBox/BACKUP/882509893/22_04_29.

It was logical that two full backups were created.
All my old archives still exist, but are not recognized by version 8.22.

What can I do?
Apart from going back to version 7.5?

Regards
Manfred

Backup of empty directories

javier — Tue, 13 May 2025 09:34:20 -0000

Hello Bugtamer and thank you for your reply. I was shocked because I could swear my backups did not copy empty folders. Problem was I was making non compressed backups and I was checking the repository and these folders were not there. But after your comment I tried restoring the backup and the empty folders magically appeared. So, problem solved. Thank you very much.

Backup of empty directories

Bugtamer — Mon, 12 May 2025 17:56:04 -0000

Hello Javier.
There are labels in the source code dedicated to tracking empty folders, but these labels aren't being used.

areca-backup\translations\resources_en.properties

targetedition.trackemptydirs.label = Register empty directories
targetedition.trackemptydirs.tooltip = If this option is enabled, empty directories will be stored and recovered. They will be ignored otherwise.

However, if you make a backup, it will make copies of empty folders.

Regards

Recent posts to Discussion

Upgrade from 7.5 to 8.22

Upgrade from 7.5 to 8.22

Upgrade from 7.5 to 8.22

Upgrade from 7.5 to 8.22

Upgrade from 7.5 to 8.22

Upgrade from 7.5 to 8.22

Upgrade from 7.5 to 8.22

Upgrade from 7.5 to 8.22

Backup of empty directories

Backup of empty directories