Harddisk backup,

[To-M]

The reason for Snapshot in Local Backup is that when the backup is performing the snapshot provides data integrity. You can choose only from snapshots with no create- and remove-time assigned as well. When you change source lv, available shares and snapshot will also change. Also, even if you choose more than one share to backup each share will be backuped into separate file.

[To-M]

dear Sys-b:

I also wanted to let you know that we do support local synchronization as well. In such a case you need to specify your own IP and choose destination volume. Please do not forget to enable synchronization on source and destination share!

[sys-b]

Update:

Synchrosation works The main volume lv00 needed a snapshot volume.
Maining i needed to delete the lv00 volume then create it again. Only this time a litte smaller and with snapshot size. Now i can syncronise one volume with the other.
I wonder how big a snapshot volume needs to be..... the size of a file a as large as an entire volume. 6gb bigest file snapshot volume also 6 gb or volume 110GB snapshot also 110GB.... Just wondering i will test it next week. Futher more remains that the main volume lv00 can be selected as part of synchronization. Lv01 same as lv00 (data + snapshot space) then lv01 with shares can't be selected first. lv00 though no problem!
I also tested the speed..... 11mb/sec with sync.... on the same nas (used ip 127.0.0.1)
and 4mb/sec by local backup.... lv00 > lv01 is this normal... Network seems to be faster!?!?!? have the following raidcard (areca 1160).

setup 8 disks raid6 (412GB) to 1 disk raid0 (300GB)
lv00 divided in 200GB data and 200Gb snapshot and 4GB swap
lv01 300GB data

Keeping you informed of the progress...

[To-M]

Typical recommendation of how big a snapshot volume needs to be is usually 10% of the total amount you need. So lets say that you only plan to protection of your LV01 300GB data then 30GB would be needed.

I would contact Areca concerning the speed and verify the settings on this controller.