We use syncBack for a long time. But, at the end, many times it´s useless, as follows:
1- many times HDs goes corrupting slowly, that is, goes corrupting this and that file, a directory tree, etc.
2- many of these "failures" are copied by syncback in a daily basis
3- as we normaly do a "mirror" copy, means that SB also deletes some of these "corrupted" áreas.
4- at the end, when HD really corrupts (does not work or log bucnh of erros or goes in intermitent state), we get backup.
5- fact is that normally this backup is almost useless, as many directories and files are not there too.
==> my question:
a) how to solve that (Due to the large volume of files, I cant have many copies, versioning, and must delete from backup files that I really deleted from original HD, to make room to new files.
b) in other words, syncBack can distinguish betwen a manual delete (file or directory structure) and a hard disk failure delete, as exposed above?
c) or there is any trick for that, as I suppose most of you HDs also has this "slow failure" problem
Thanks
Jose
1- many times HDs goes corrupting slowly, that is, goes corrupting this and that file, a directory tree, etc.
2- many of these "failures" are copied by syncback in a daily basis
3- as we normaly do a "mirror" copy, means that SB also deletes some of these "corrupted" áreas.
4- at the end, when HD really corrupts (does not work or log bucnh of erros or goes in intermitent state), we get backup.
5- fact is that normally this backup is almost useless, as many directories and files are not there too.
==> my question:
a) how to solve that (Due to the large volume of files, I cant have many copies, versioning, and must delete from backup files that I really deleted from original HD, to make room to new files.
b) in other words, syncBack can distinguish betwen a manual delete (file or directory structure) and a hard disk failure delete, as exposed above?
c) or there is any trick for that, as I suppose most of you HDs also has this "slow failure" problem
Thanks
Jose