| About Areca | End user documentation | Technical informations |
|---|---|---|
| Home | Plugins | Regular expressions |
| Features | Versions history | Translations |
| Plugins | Tutorial | Config backup |
| Screenshots | User’s manual | |
| Download | FAQ | |
| Bug & feature requests | Support & Contact | |
| Forums |
Please read Areca’s FAQ before submitting issues or feature requests !
You can use Areca’s command-line interface to create backup scripts (*.bat or *.sh scripts), and schedule their execution with Linux’s crontab or Windows’ scheduler.
Windows scheduling : http://support.microsoft.com/kb/308569
Linux scheduling : http://en.wikipedia.org/wiki/Cron
No, Areca doesn’t support VSS, but you can use the ArecaVSS plugin (www.arecavss.com), which will add VSS support to Areca.
This will allow Areca to read and store files that are locked by the system or programs (such as outlook *.pst files)
Areca uses the file’s size and last modification time to detect modified files. If one of these attributes is modified (whatever its value is), the file is flagged as modified.
Since v7.2.17, Areca can also inspect the file’s content to detect modifications of its content (which is much slower than detection based on attributes)
Yes - since v4.5, Areca can store your files on FTP servers.
If FTP storage is used, it is highly advisable to compress your archives. (You can use zip64 or standard zip compression)
It is also advisable to use the “FTP Test” feature (which can be found on the FTP parameters window) to check that your FTP server is compatible with Areca.
Yes - since v4.5.1, Areca can store files on FTPs servers.
Areca supports SSL and TLS, as well as implicit and explicit modes.
Yes - since v7.2, Areca can store files on SFTP servers.
No, Areca can only store your backups on your file system (ie local or remote directories)
You can use standard zip compression if your archives will be smaller than 4GB. For bigger archives, use zip64 compression.
Of course, it is useless to use compression when your source files are already compressed (for instance JPG, MP3, AVI files) : No space will be gained and it will result in unnecessary time consumption during backup.
Areca supports encryption, but it is implemented at the file system access level (ie it is not implemented as zip encryption). This allows to benefit from the same encryption layer, whether the target is compressed or not.
In other words, if you choose target encryption and compression, Areca will encrypt the archives exactly the same way as if you choose target encryption without compression.
Yes : since version 7.0, Areca supports ACL and extended attributes on Linux.
This feature uses native code (unlike Areca’s backup engine, which has been written in Java) and is currently only compiled for 32 bits Linux systems with glibc2.6.
Note that this native code needs the "acl" library.
That’s quite simple : download Areca’s sources on SourceForge (zip file available on the download page), uncompress it, open the “jni” directory and run the “compile.sh” script.
It will create a “libarecafs.so” file. Copy this file in Areca’s “lib” directory.
ACL and extended attributes support are not enabled by default. You have to modify your configuration to activate it.
Open the “fwk.properties” file which is located in Areca’s configuration subdirectory and set the “filesystem.accessor.impl” to “com.myJava.file.metadata.posix.jni.JNIMetaDataAccessor” (the default value is “com.myJava.file.metadata.posix.basic.DefaultMetaDataAccessor”)
On startup, Areca displays some information about the “filesystem accessor” which is used (you should see something like “Loading configured file metadata accessor : [com.myJava.file.metadata.posix.jni.JNIMetaDataAccessor]” in your log file or log tab)
This error can occur when you store your backups on a remote directory (over a network) which is not available (network error).
Areca needs extended accesses to the FTP storage directory in order to use it.
More precisely, the FTP user must be granted to following rights :
Areca has been tested with the following FTP servers :
Note that - depending on the FTP server configuration - file sizes can be restricted (for instance, files over 1GB won’t be accepted)
Solution proposal (special thanks to “Mirkosoft”) :
“I could solve my issue with ftp timeouts: the problem was the firewall built into windows.
(The following is valid for windows 7 ultimate on a 64 bit system. Not approved on other systems)
As mentioned, I’m using ftp over ssl.
The windows firewall tries to perform stateful inspection on ftp traffic. Using ssl, this traffic becomes unreadable to the firewall and thus the connection is interrupted after about 10 minutes or so.
There are two possible solutions to this:
1. Disable the windows firewall completely. Not recommend for most users.
2. Disable stateful inspection on ftp traffic using the command line. This may be achieved by calling netsh advfirewall set global StatefulFtp disable
The state of ftp inspection may be checked by calling netsh advfirewall show global Statefulftp
This solves all of the mentioned timeout problems for me.”
| Top | Copyright (c) 2005-2015 Olivier PETRUCCI | archive.org |