Nope. It's another right they took away from the moderators a while ago.OneCD wrote:I'd lock it @dolbyman, but seems I no longer have that option. Anyone else?
TS-251 Backup from Disk1 to Disk2
-
Don
- Guru
- Posts: 12289
- Joined: Thu Jan 03, 2008 4:56 am
- Location: Long Island, New York
Re: TS-251 Backup from Disk1 to Disk2
Use the forum search feature before posting.
Use RAID and external backups. RAID will protect you from disk failure, keep your system running, and data accessible while the disk is replaced, and the RAID rebuilt. Backups will allow you to recover data that is lost or corrupted, or from system failure. One does not replace the other.
NAS: TVS-882BR | F/W: 5.0.1.2346 | 40GB | 2 x 1TB M.2 SATA RAID 1 (System/VMs) | 3 x 1TB M.2 NMVe QM2-4P-384A RAID 5 (cache) | 5 x 14TB Exos HDD RAID 6 (Data) | 1 x Blu-ray
NAS: TVS-h674 | F/W: 5.0.1.2376 | 16GB | 3 x 18TB RAID 5
Apps: DNSMasq, PLEX, iDrive, QVPN, QLMS, MP3fs, HBS3, Entware, DLstation, VS, +
Use RAID and external backups. RAID will protect you from disk failure, keep your system running, and data accessible while the disk is replaced, and the RAID rebuilt. Backups will allow you to recover data that is lost or corrupted, or from system failure. One does not replace the other.
NAS: TVS-882BR | F/W: 5.0.1.2346 | 40GB | 2 x 1TB M.2 SATA RAID 1 (System/VMs) | 3 x 1TB M.2 NMVe QM2-4P-384A RAID 5 (cache) | 5 x 14TB Exos HDD RAID 6 (Data) | 1 x Blu-ray
NAS: TVS-h674 | F/W: 5.0.1.2376 | 16GB | 3 x 18TB RAID 5
Apps: DNSMasq, PLEX, iDrive, QVPN, QLMS, MP3fs, HBS3, Entware, DLstation, VS, +
-
OneCD
- Guru
- Posts: 12155
- Joined: Sun Aug 21, 2016 10:48 am
- Location: "... there, behind that sofa!"
Re: TS-251 Backup from Disk1 to Disk2
It's getting harder to help QNAP maintain this site.Don wrote:Nope. It's another right they took away from the moderators a while ago.
Is forkless getting his site going again?
-
schumaku
- Guru
- Posts: 43578
- Joined: Mon Jan 21, 2008 4:41 pm
- Location: Kloten (Zurich), Switzerland -- Skype: schumaku
- Contact:
Re: TS-251 Backup from Disk1 to Disk2
There seems to be some misunderstanding by the OP on the way QNAP has implemented QTS.
The QTS internal HDD are holding multiple partitions. Some of them are always in RAID1 (either spanning all or a defined number of two for the swap). This does include a partition with a RAID1 which does hold the configuration data.
Further on, QTS does not boot from a HDD - it does operate as an embedded Linux in a volatile RAM disk, which is populated from a Flash device at boot time.
To make things a little bit more complicated, some system resp. App data is held (typically, unless reconfigured) on the first storage volume.
It's a common consent not only here in the community that operating at least this first volume (which resides on top of an LVM2 anyway, using a part or all of the storage space) on a RAID1. Recovery from a broken HDD is obviously dammed easy be just replacing the failing or broken storage block.
Said that - the copy of a whole disk - as this is what you want to achieve does not fit to the QTS design.
To overcome accidential file deletion or the recovery from cryptolocker, the approach would be to make use of a set of scheduled snapshots, say hourly for some time, than daily, then monthly.
If you insist to have this on different internal storage spaces (with single disks being the smallest possible implementation) you could consider using snapshot replication instead. Ideally, the target would be a different QTS NAS (of course). We'll re using snapshot replication on smaller home as well as the biggest QTS installations in the field - but always to redundancy NAS to allow simple service continuity.
Reinventing the wheel or attempting to change QTS bottom up to achieve your storage design is not the best idea, and won't survive the next firmware update of course - mainly to the reason I've listed above.
Hope this does clarify things a little bit - without head banging, guess we're all old (and experienced, but not bold) enough.
Regards
-Kurt
The QTS internal HDD are holding multiple partitions. Some of them are always in RAID1 (either spanning all or a defined number of two for the swap). This does include a partition with a RAID1 which does hold the configuration data.
Further on, QTS does not boot from a HDD - it does operate as an embedded Linux in a volatile RAM disk, which is populated from a Flash device at boot time.
To make things a little bit more complicated, some system resp. App data is held (typically, unless reconfigured) on the first storage volume.
It's a common consent not only here in the community that operating at least this first volume (which resides on top of an LVM2 anyway, using a part or all of the storage space) on a RAID1. Recovery from a broken HDD is obviously dammed easy be just replacing the failing or broken storage block.
Said that - the copy of a whole disk - as this is what you want to achieve does not fit to the QTS design.
To overcome accidential file deletion or the recovery from cryptolocker, the approach would be to make use of a set of scheduled snapshots, say hourly for some time, than daily, then monthly.
If you insist to have this on different internal storage spaces (with single disks being the smallest possible implementation) you could consider using snapshot replication instead. Ideally, the target would be a different QTS NAS (of course). We'll re using snapshot replication on smaller home as well as the biggest QTS installations in the field - but always to redundancy NAS to allow simple service continuity.
Reinventing the wheel or attempting to change QTS bottom up to achieve your storage design is not the best idea, and won't survive the next firmware update of course - mainly to the reason I've listed above.
Hope this does clarify things a little bit - without head banging, guess we're all old (and experienced, but not bold) enough.
Regards
-Kurt