I recreated the backup and opened it on Areca, and the only thing, apparently, is that it doesn't show those two affected months. I was able to recover files from before and from after those two months, so I suppose the backup is OK. Anyway, I will start a new one, just to be sure.
It doesn't help in my case, but thanks anyway.
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,...
First of all, thanks for continuing Areca! I don't know if it's possible to solve my problem or not, but here it is: I have been using Areca for my daily backups, and from time to time I copy the backups to an online storage. Last week we had an energy cut on the building and the disk with the backups died. I went to the online storage and downloaded the copy of the backup. To my surprise, I foud out that when I copied the backups I missed some of the 202404XX_data folders, although I have the zipped...
forget it - I deleted the app
Hi, I have the following weired situation. Can anyone help? I did a huge backup from my NAS to an external disk (FAT32). After hours it under "Fortschritt" (progress) I have a red line saying Backup is "Fertig" (finished) In the protocol I have red errors, the first I append below. Under Journal I have two lines: 1) Backup rollback and 2) Backup (the starting time) But under Archive there is NOTHING and under "Logische Darstellung" (I guess logical view) there is also NOTHING. when I try to continue...
Hi! 1.) yes What I did: I have: /home/alf/PROG/areca /home/alf/PROG/areca7.5 /home/alf/PROG/areca-8.2.4-linux-x86-64 and /home/alf/.areca/workspace /home/alf/.areca 7.5/workspace /home/alf/.areca-8.2.4/workspace (containing the bcfg-files) For testing 8.2.4 I copied the program from areca-8,2,4 to areca and areca-8.2.4/workspace to areca/workspace Then edited the bcfg-files, as you told. All workspaces are shown on start of areca, and I could open them, so I did not import anything. I don't have...
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.
As I had to set up a new machine, because my old one died, I gave it a try. I tried areca 8.2.4 with Java 17 and Java 21. I modified the in 7.5 working bcfg-files None of my workplaces showed any existing file :-( So I am back on areca 7.5 and Java 8, with the same bcfg files, but without modification. An I think, I must stay there. Regards Manfred
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)...
WARNING: Use --enable-native-access=ALL-UNNAMED to avoid a warning
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...
First, thanks for taking the time and effort to help resolve this issue. Here are some thoughts after working through this. There is a third type of recovery. That type is: Recovery of a specific version of a entire subdirectory. This is not a full recovery nor just a single file. When I need to restore something, this is often the one I need. From the Logical View tab you can only select the most recent backup of a directory, not a version on an older archive. Right click the directory > Recover...
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,...
Many Thanks!! I was looking for this
Hi, Thank you again for supporting me. Upon reviewing the log file it seemed like there was indeed a mismatch between Java 32 and 64 bit versions. In hindsight I should've guessed as much as the Java installed to \Program Files (x86) and not \Program Files. My mistake, I believe, was to install Java using their "Windows Online" installer. After installing Java using their "Windows Offline (64-bit)" installer and copying the files and folders from \Program Files\Java\jre1.8.0_461 to \areca-8.2.4-windows-x86-64\jre,...
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, Thank you for taking your time. I have tried your suggestion of adding a system variable to the Java folder in "Program Files (x86)". I also tried copying the\bin folder from C:\Program Files (x86)\Java\jre1.8.0_461 to\areca-8.2.4-windows-x86-64\jre. None of these measures alone gave any different result from before. I then tried running CMD as Administrator and then things got a little different. Running "areca.bat" doesn't give any error messages, only: Areca Backup will continue running if...
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, I never thought I would have to ask this, but what are the steps to get Areca 8 to run on Windows 10?I have Java(TM) SE Runtime Environment (build 1.8.0_461-b11) installed (verified from CMD with "java -version").I downloaded the zip file "areca-8.2.4-windows-x86-64.zip"from https://sourceforge.net/projects/areca-backup/files/areca-stable/areca-backup-8.2.4/ Instructions here: https://areca-backup.sourceforge.io/documentation.php tells me to "run the setup" but no setup file is to be found. Trying...
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.
Hello, I came across this software while trying to find a backup solution and saw you were thankfully continuing the old Areca project. After looking over the project pages here, I found that you do not have a direct link to the new source code on the main project summary page or on the new site. Would it be possible to add the link, or a mirror of the source code in a src folder on the sourceforce project pages?
OK, based on information from what you said above, I did some more digging and testing and I think there is really only one problem which is how it applies the metadata. Looking at these dates from the linux stat command: File: some-old-test-file.txt Size: 38903 Blocks: 80 IO Block: 4096 regular file Device: 259,1 Inode: 36996580 Links: 1 Access: (0664/-rw-rw-r--) Uid: ( 1000/ ron) Gid: ( 1000/ ron) Access: 2025-07-08 03:35:53.878485019 -0500 Modify: 2025-01-21 12:51:50.843453962 -0600 Change: 2025-01-21...
OK, based on information from what you said above, I did some more digging and testing and I think there is really only one problem which is how it applies the metadata. Looking at these dates from the linux stat command: ~~~ File: some-old-test-file.txt Size: 38903 Blocks: 80 IO Block: 4096 regular file Device: 259,1 Inode: 36996580 Links: 1 Access: (0664/-rw-rw-r--) Uid: ( 1000/ ron) Gid: ( 1000/ ron) Access: 2025-07-08 03:35:53.878485019 -0500 Modify: 2025-01-21 12:51:50.843453962 -0600 Change:...
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)...
Hello, Thank you for the reply. Here is some testing I have done. I selected a single file with which to work and is old enough that do not really need it. The file as created looks like this, the Access date is updated by the backup. stat QData-2025-06-12* File: QData-2025-06-12.AM09.03.QDF-backup Size: 80465920 Blocks: 157168 IO Block: 4096 regular file Device: 259,1 Inode: 37266049 Links: 1 Access: (0664/-rw-rw-r--) Uid: ( 1000/ ron) Gid: ( 1000/ ron) Access: 2025-07-08 03:10:15.527034144 -0500...
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...
Linux file date not preserved