in my setup, Areca's backup repository is located on a NAS (accessed via SFTP) and I would like to connect more than one client/computer to the repository to do something like a poor man's synchronization. It's no problem to recover the data on all clients - with a different recovery location on each client (e.g. C:\Users\XXX on my Windows machine and /home/user/XXX on Linux). The problem is, however, that I can use only one "global" source (e.g. C:\Users\XXX) for the target definition so I can use only one client to populate the repository. When I change the source on one of the other clients and try to run a backup, all files show up as modified (there is also a warning when the source is changed with predicts exactly this behaviour).
Is there a workaround. Should I use symlinks to emulate the same path to the source directory on all clients? I hope I'm making myself clear.
Thanks,
Johannes
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I don't know if i got your problem right..
Maybe you could try this:
If you change source from arecas gui all files will be marked as new. But you could try to change the source in the bcfg-file directly with an texteditor. Then areca doesn't recognize the change of source...
Mathias
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
in my setup, Areca's backup repository is located on a NAS (accessed via SFTP) and I would like to connect more than one client/computer to the repository to do something like a poor man's synchronization. It's no problem to recover the data on all clients - with a different recovery location on each client (e.g. C:\Users\XXX on my Windows machine and /home/user/XXX on Linux). The problem is, however, that I can use only one "global" source (e.g. C:\Users\XXX) for the target definition so I can use only one client to populate the repository. When I change the source on one of the other clients and try to run a backup, all files show up as modified (there is also a warning when the source is changed with predicts exactly this behaviour).
Is there a workaround. Should I use symlinks to emulate the same path to the source directory on all clients? I hope I'm making myself clear.
Thanks,
Johannes
I don't know if i got your problem right..
Maybe you could try this:
If you change source from arecas gui all files will be marked as new. But you could try to change the source in the bcfg-file directly with an texteditor. Then areca doesn't recognize the change of source...
Mathias