In my experience, migrating/syncing the cpool/pool/pc folder using rsync
(hard links in tact) isn't a practical exercise (but is technically
possible).
The size of your cpool/pool/pc data set will have exponential
implications on the time required to sync (even if no data changes hands).
The
Il 17/12/2015 16:04, absolutely_f...@libero.it ha scritto:
>> Hi.
>>
>> let's say I can't use DRDB or mdadm at all.
>> If I sync every "pc", one by one, between two storage, this could be working
>> (even if suboptimal)?
>> I know that rsync is able to recognize hardlinks (-H) only in same session
If you hate yourself, why not! ;-)
I suspect you need knowledge on how BPC organizes the pool to find every
reference to every single file belonging to a single PC...
On the web you can find already made scripts that do something similar
(I don't remember the links), but my guess is that rsync
;>> example keeping only the last 2 backups rather than a long backup
>>>> history... Easy to adjust to fit your available storage and business
needs.
>>>>
>>>> Slightly more work up front, but easy to perform restores without
depending
>>>> o
On 14.12.15 14:33, absolutely_f...@libero.it wrote:
> Hi Paolo,
> thank you for your quick reply.
>
> My pool is 2.5 TB.
>
> Sincerely, speed is not crucial in my case: I just need to store data on a
> different location, for disaster recovery.
> My doubt is: if I keep two pools synced with
Hi,
sorry, using rsync for this purpose is absolutely not recommended!
As always, it depends on what you want to get. If you do not mind having
old data as long as you have it, it might be fine with rsync running
once a month. You have a pool of 2.5TB- on my pool of 1.4TB I aborted
rsync after
Hi Paolo,thank you for your quick reply.
My pool is 2.5 TB.
Sincerely, speed is not crucial in my case: I just need to store data on a
different location, for disaster recovery.My doubt is: if I keep two pools
synced with rsync, will I able to use it? Or should I care about something in
