Hi Manfred, I dedicate some of my free time to the Areca project, and I've been busy lately. So, sorry for not replying for so long. I remember that editing the XML and removing _e worked in tests on my local machine. Regarding the location of the files (configurations and archives), it's probably not relevant. It is worth noting, however, that it's preferable not to overwrite one version of Areca with another, especially to avoid overwriting areca/config/fwk.properties, which contains ACL preferences...
Hi Stefan, It occurs to me that working in a Unix-like environment might have caused a problem with ACL permissions, something that wouldn't happen in Windows; either with read or write permissions (as applicable). Areca's ACL support needs to be compatible with the system it's trying to read from or write to, and it also needs to have sufficient permissions to do so. You can check if any ACL errors appear in the Log panel when you start Areca. If so, there's specific help for troubleshooting these...
Hi Artur, In theory, you should be able to decompress the data, but its metadata (creation dates, read-only access, ACLs, etc. - I don't recall if the path is also considered metadata) might not be fully recoverable due to the missing folders. In my experience as a user (I'm not the original developer), I seem to recall having to decompress the archives twice in some specific cases to extract the original files. Areca includes an "external" decompression and decryption tool for these types of operations,...
Hi Manfred, 1) On the new PC, are the archives in the same location as on the old one? 2) I understand you've already tried opening the workspace. - Menu "Workspace" - Option "Open workspace...". 3) Have you tried importing the *.bcfg files (modified or not)? - Menu "Workspace" - Option "Import...". 4) Do any error or warning messages appear in the logs? Regards.
Hi Philip, Yes, I think it's as you indicate, something to be prepared for in the near future. From what I've been able to find out, it seems that a new parameter (e.g., java --enable-native-access=ALL-UNNAMED [...] or anything more specific than ALL-UNNAMED) will need to be added to the launchers (areca_run.bat and areca_run.sh), but I haven't been able to test it to confirm since I haven't been able to reproduce the message. Could you tell me: Operating system (I've tested both Windows and Linux)...
WARNING: Use --enable-native-access=ALL-UNNAMED to avoid a warning
Hi Philip, Yes, I think it's as you indicate, something to be prepared for in the near future. From what I've been able to find out, it seems that a new parameter (e.g., java --enable-native-access=ALL-UNNAMED [...] or anything more specific than ALL-UNNAMED) will need to be added to the launchers (areca_run.bat and areca_run.sh), but I haven't been able to test it to confirm since I haven't been able to reproduce the message. Could you tell me: Operating system (I've tried both Windows and Linux)...
Linux file date not preserved
Since I haven't received any further messages, I understand the issue is closed with the advice provided above. If not, feel free to reopen the issue. Regards
Linux file date not preserved
We'll use the notation Areca A for the locally installed version and Areca B for the downloaded version (usually a new version). Rename (or move to another folder) Areca A to avoid a name conflict later. It's recommended that the new name or location identify that version to allow you to restore that specific version. Download and unzip the Areca B version to the destination folder. If you don't want to make any changes to your Areca workflow, rename Areca B to the name Areca A had before applying...
Now that you mention recovering a folder, I also remember that you can arbitrarily restore files and folders if you select/deselect them while holding down the Control key, and this can be done both in the Archive detail and the Logical view. I was only able to reproduce your issue when the original files and folders were overwritten by the restored ones and the restoration required elevating Areca’s privileges using sudo to make changes (for example: read-only destination, a different user/group...
Run the following commands under the Areca folder. Windows From the Command Prompt: areca_cl.bat GNU/Linux $ ./bin/areca_cl.sh Output INFO - - ------------------------------------------------------------------ INFO - - Areca Backup INFO - - Copyright 2005-2025, Olivier PETRUCCI INFO - - List of valid arguments : INFO - INFO - - Show informations about Areca : INFO - - infos INFO - INFO - - Describe targets : INFO - - describe -config (xml configuration file or directory) INFO - INFO - - Launch a...
Hi, Let's take it one step at a time: There are two types of recoveries: 1. Simple recovery of a specific version of a file 2. Full recovery of an entire archive Each of these opens the same recovery window but with different options but under the same window title, and with no distinction as to the purpose (!). The simple recovery has Location and Check content of recovered files, while the full recovery has those same fields and some additional ones. The image you shared corresponds to a full recovery,...
Hi, Well, I meant to copy all the contents under the C:\Program Files (x86)\Java\jre1.8.0_461 folder to \areca-8.2.4-windows-x86-64\jre so bin\ is under jre among all other contents but without the jre1.8.0_461 folder in between. This won't be your case, but I'll leave it for documentation purposes. The 32-bit or 64-bit version of Areca isn't chosen based on whether the operating system is 32 or 64-bit, but rather on whether the Java version is 32 or 64-bit. In this case, it would give an error similar...
Hi, If you were able to run java -version without errors, it should work. In any case, you can try the following: Set JAVA_HOME Variable in Windows, Mac OS X, and Linux, but in your case with JRE. Or leave a copy of the JRE in areca-backup-8.x.y\jre. If you see this path, areca-backup-8.x.y\jre\bin will be where Areca expects to find it. I hope this helps you. Regards.
Hi. After several tests, I've reproduced your error, but only when there's a symlink in the archive from which a file is retrieved; if there's no symlink, there's no error, as far as I've been able to test. There is a comment that says "Last modification date and mode. They are not set on symlinks (not supported)" within setMetaData() for JNIMetaDataAccessor.java but it "works" for DefaultMetaDataAccessor.java (without ACL support) so ends with a warning but the files are recovered with the last...
Hi. After several tests, I've reproduced your error, but only when there's a symlink in the archive from which a file is retrieved; if there's no symlink, there's no error, as far as I've been able to test. I'm just mentioning this as feedback; I'm still pending to implement a fix. Regards.
We'll use the notation Areca A for the locally installed version and Areca B for the downloaded version (usually a new version). Rename (or move to another folder) Areca A to avoid a name conflict later. It's recommended that the new name or location identify that version to allow you to restore that specific version. Download and unzip the Areca B version to the destination folder. If you don't want to make any changes to your Areca workflow, rename Areca B to the name Areca A had before applying...
Currently, the option to control this feature is not accessible from the user interface. So, it can only be changed by manually editing the target configuration file (system_user_name/.areca/workspace/ *.bcfg): register_empty_directories="true" by default: empty directories are saved in backups register_empty_directories="false" Restart Areca again to read the configuration changes.
Hi @ssuizaa I think this will be useful to you (Backup of empty directories, aventin's forums). Regards
Currently, the option to control this feature is not accessible from the user interface. So, it can only be changed by manually editing the target configuration file (system_user_name/.areca/workspace/ *.bcfg): register_empty_directories="true" by default: empty directories are saved in backups register_empty_directories="false"
Hi, I answer @malfare on the topic "Upgrade from 7.5 to 8.22" from the Aventin Help forum, which I also answer here due to moderation issues on their forum and, for context, I'm including the beginning of the conversation thread: 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....
Hi, I only share the improvements to Areca that I implement for myself, and I occasionally help a user if I can and when I have time. So I don’t want to spend more of my personal time on the extra work that explicitly linking to the repo would involve. In any case, thanks for your interest.
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.
Linux file date not preserved
Hi, TL;DR The date issue isn't a bug, it seems to be a feature. The second issue about applying metadata to each file in the directory does seem to be a bug. So I'll focus on the 2nd bug. Given its age, Areca uses java.io.File (among other custom/helper classes) to represent or interact with files, and this class only supports the last modified date. I haven't seen any of those custom classes yet that handle other date types. Given its age, Areca uses java.io.File (among other custom/helper classes)...
Linux file date not preserved
Hi, Yes, it's fine to open tickets here. Test environment OS: Linux Mint JDK: OpenJDK 1.8 Temurin Areca: 8.2.4 (version 8 has only superficial changes compared to 7.5 so far — they even have the same old dependencies) I restored a single file, messages.txt, it both to a USB partition and to my desktop. I ran three recovers from the GUI (none from the TUI) to check consistency, from: Archive detail (Archives tab >> right-click on an archive >> Archive detail... >> Archive content) Logical view Logical...
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...
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
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, bugtam...
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
Dear @Neustradamus and @tostis, For now, I don't need to change my build pipeline, but I'll keep it in mind. I need to look into GitHub organizations (or similar, GitLab, etc.) to see if it's worth it. Regards.