Hi,
I have a question regarding the use of a single 2.5" SMR hard disk for a weekly backup.
I currently have different backups (cloud, internal and external replication), as well as a weekly backup where I mount a hard drive locally as a single-drive pool and remove the drive after the backup has been completed and store it externally (I just like to play it safe
).
So far I have been using 3.5" CMR disks (WDC WD40EFRX and WD80EFAX). For various reasons I am considering using 2.5" hard disks instead (e.g. Seagate Barracuda ST5000LM000). I need at least 4TB and the problem is that 2.5" hard disks are then always SMR disks.
I am aware of the problem with ZFS and SMR disks, but I wonder if this in principle only applies to pools consisting of several disks or also to pools consisting of a single hard disk?
No resilvering can take place, but the disks are still heavily loaded when writing for the first time and possibly also when creating backups.
Is it possible to circumvent the problem by limiting the write rate or something else? Since the backup disk usually remains in the server until the next day, it is not a problem if the backup needs more time.
I would be grateful for an answer.
Dieter
I have a question regarding the use of a single 2.5" SMR hard disk for a weekly backup.
I currently have different backups (cloud, internal and external replication), as well as a weekly backup where I mount a hard drive locally as a single-drive pool and remove the drive after the backup has been completed and store it externally (I just like to play it safe
So far I have been using 3.5" CMR disks (WDC WD40EFRX and WD80EFAX). For various reasons I am considering using 2.5" hard disks instead (e.g. Seagate Barracuda ST5000LM000). I need at least 4TB and the problem is that 2.5" hard disks are then always SMR disks.
I am aware of the problem with ZFS and SMR disks, but I wonder if this in principle only applies to pools consisting of several disks or also to pools consisting of a single hard disk?
No resilvering can take place, but the disks are still heavily loaded when writing for the first time and possibly also when creating backups.
Is it possible to circumvent the problem by limiting the write rate or something else? Since the backup disk usually remains in the server until the next day, it is not a problem if the backup needs more time.
I would be grateful for an answer.
Dieter