When using the (default on) check archive function when backuping to an encrypted "local" archive, Areca writes the archive data under the same directory as where the archive is. This can cause security problems if the local repository is for example on a network server and you don't want to move your data there unencrypted. Or worse, like in my case when the directory is actually a FTP/WebDAV...
2009-09-06 06:53:03 UTC in Areca Backup
