georg wrote:
Right ! And ... in other words ... the "mirror copy" is (to use keks's term) a "snapshot" taken once every 24 hours (until you turn it off).
I'm sorry
By saying "snapshot" I meant a concept like it is implemented e.g. in NetApp-Filers.
There, the snapshop is a file-wise bit-by-bit comparison of the current state of HDD compared to the state of the HDD at the time of the last snapshot-run.
You can configure there how often the snapshot is taken and for how long these snapshots are kept before deleted.
In our company-environment these snapshots are stored virtually on the same share in a hidden write-protected folder with subfolders for every snapshot event like here:
\~snapshot\hourly.0
\~snapshot\hourly.1
\~snapshot\hourly.2
...
\~snapshot\nightly.0
\~snapshot\nightly.1
\~snapshot\nightly.2
...
\~snapshot\weekly.0
\~snapshot\weekly.1
\~snapshot\weekly.2
...
"hourly" means noon, "nighly" is midnight. Under each of these folder you can browse the complete directory tree as it is existent in the root directory also. So you do not see only the changed files but all files.
So, you have a backup-copy twice a day. Then after a few days only a weekly snapshot is kept. After a few weeks nothing is kept anymore.
However, I understood that such or a similar backup-strategy is not implemented by rsync in naslite (which doesn't matter at all
)
Mirroring I personally knew from MS-robocopy and there I used the /mon switch. With /mon:1 you can force the service to mirror every single change on your HDD. I assumed this "as mirror" and therefore I was a little bit confused by Tony's statement
Quote:
the standing rsync mirror is always there to bail me out of trouble
Because then, in the moment you overwrite a file it would also be changed on the mirror disk...
But now, everything is clear since of course mirroring does not
necessarily mean that every single change on the HDD
has to be replicated immediately. It depends on the mirroring settings...
To cut a long story short: thank you for the explanations and sorry for the confusion I may have caused
... and now ... let's proceed with the power consumption numbers of your systems