Thread replies: 8
Thread images: 1
Thread images: 1
I want to use my NAS as a backup temporarily.
The setup will be FreeNAS + stripped vdev(RAID0), per disk. This means each HDD will separate from each other, no redundancy. This should be fine since each HDD is just a backup.
Then maybe 1~2 years from now when I've bought more HDD's, I'll wipe the entire Nas and go stripped mirror vdev(RAID1), use the NAS as my main storage and then use my current JBOD as backup.
Is there anything wrong with this? Or maybe I should just make 1 giant pool of RAID 0, and take the risk that if 1 drive dies, the entire pool dies, and then deal with spending 9 days(30TB @ 350Mb/s) transferring the data back.
Remember, this is just a temporarily solution until I can afford more HDDs. I just really need a backup of my data.
>>
Dont know if anyone is knowledgeable, but I've decided I'm going to do for my temp backup:
3 disks per pool, stripped vdev.
This should give me 900MB read/write speeds, which is enough to saturate my fiber connection.
This way I only spend maybe 3 days repairing the array if a drive dies.
>>
>>62343626
Keep in mind that you cant add additional drives to a pool. Number 1 reason to not use zfs for home usage and instead go with snapraid + mergerfs
>>
>>62344400
>Keep in mind that you cant add additional drives to a pool
Are you sure?
I read that you should be able to add new disks to a pool. The NEW disk gets wiped, but all the data in the pool should remain intact.
Even so, why would it matter if I can just create another pool of drives?
>>
>>62344469
http://louwrentius.com/the-hidden-cost-of-using-zfs-for-your-home-nas.html
> Even so, why would it matter if I can just create another pool of drives?
>>
Seems OP knows this, but just to make it abundantly clear:
RAID IS NOT A BACKUP.
With that out of the way, and assuming you really are just using this as a backup of an already existing storage array, what you propose is perfectly reasonable.
>>62345115
>>62344400
That's vdevs. You can't just add a new disk to a vdev, you can add new vdevs to a pool.
In the first scenario where OP is hdd limited and is using what he calls "raid0", he simply puts the new disk in, creates a vdev which contains only that new disk, and adds the vdev to the pool.
In the second scenario where OP is not hdd limited and is using what he calls "raid1", he simply puts 2 new disks in, creates a vdev in which the disks are mirrors of each other, and adds the vdev to the pool.
>>
>>62345152
also, I really wouldn't bother with any vdev fuckery besides mirroring. "RAIDZ" is dildos and why people like those two spout shit like "you can't add drive to a pool". RAIDZ, like all raids, certainly does not constitute a real backup.
>>
>>62345183
and finally I highly suggest this set of guides:
https://pthree.org/2012/12/04/zfs-administration-part-i-vdevs/
Thread posts: 8
Thread images: 1
Thread images: 1