Raid volumes gone?

Backup, Restore, Netbak Replicator, Cloud Storage Services
Post Reply
geirgp
New here
Posts: 5
Joined: Sat Feb 18, 2012 3:36 am

Raid volumes gone?

Post by geirgp » Sat Mar 09, 2019 5:37 am

My NAS went offline today. It wouldn't respond at all over the network and even the physical display seemed dead. So i did a forced shut down. When it came back online things were not as I expected.

What I know after some digging:
* Raid volume is missing. Cannot find any of my data.
* Can access both SSH and web ui (admin user intact)
* On ssh access I can no longer find that my raid volume is mounted
* Cannot inspect RAID volumes in web ui: The "Control Panel" becomes unresponsive when I try to open the "Storage Manager" - I've found that the Javascript console in Chrome shows an error "Uncaught TypeError: Cannot read property 'TreeGrid' of undefined". (not that I know what it means, but I guess the front-end javascript application is not receiving the data it expects from the backend).
* Event log indicate that the NAS has restarted and rebuilt the RAID volume several times in the last week. No power outages afaik. The last rebuild did NOT complete before I cut the power today
* Rebuilding raid has not occured (as per event.log) after i cut the power.
* From the system report (below) I do not recognize the "raid" -part. I expected one 16TB RAID 5 volume of 3 disks and possibly 1 spare (i was at some stage intending to use the last disk as a single volume for backup instead of a spare, don't remember if i did that or not).

3 Snippets below:
* system report
* exported version of most recent lines from /mnt/HDA_ROOT/.logs/event.log
* most recent lines of /mnt/HDA_ROOT/.logs/kmsg (notice the Unhandled fault at the end)

I have no idea what to try next. Advice needed please!

QNAP NAS Report - from a script I found somewhere else on this forum

Code: Select all

*********************
** QNAP NAS Report **
*********************

NAS Model:      TS-419P II
Firmware:        Build
System Name:    NASCBFF4C
Workgroup:
BusyBox v1.01 (2018.10.28-19:01+0000) multi-call binary

Usage: dirname FILENAME

Strips non-directory suffix from FILENAME

Base Directory:
NAS IP address: 192.168.1.101

Default Gateway Device: eth0

          inet addr:192.168.1.101  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST NOTRAILERS RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:31919 errors:0 dropped:0 overruns:0 frame:0
          TX packets:27852 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:532
          RX bytes:8779066 (8.3 MiB)  TX bytes:22653260 (21.6 MiB)
          Interrupt:11


DNS Nameserver(s):192.168.1.1


HDD Information:

Volume Status


Personalities : [raid1] [linear] [raid0] [raid10] [raid6] [raid5] [raid4]
md13 : active raid1 sda4[0] sdd4[5] sdc4[4] sdb4[3]
		 458880 blocks super 1.0 [4/4] [UUUU]
		 bitmap: 1/8 pages [4KB], 32KB chunk

md9 : active raid1 sdd1[6] sdb1[4] sda1[0] sdc1[5]
		 530112 blocks super 1.0 [4/4] [UUUU]
		 bitmap: 0/9 pages [0KB], 32KB chunk

unused devices: <none>

Disk Space:

Filesystem                Size      Used Available Use% Mounted on
/dev/ram0                32.9M     16.5M     16.4M  50% /
tmpfs                    64.0M    216.0k     63.8M   0% /tmp
/dev/sda4               371.0M    358.3M     12.7M  97% /mnt/ext
/dev/md9                509.5M    137.2M    372.3M  27% /mnt/HDA_ROOT
/dev/ram2                32.9M    419.0k     32.5M   1% /mnt/update
tmpfs                    64.0M      2.3M     61.7M   4% /samba
tmpfs                    16.0M     32.0k     16.0M   0% /samba/.samba/lock/msg.lock
tmpfs                    16.0M         0     16.0M   0% /mnt/ext/opt/samba/private/msg.sock
tmpfs                     1.0M         0      1.0M   0% /mnt/rf/nd

Mount Status:

/proc on /proc type proc (rw)
none on /dev/pts type devpts (rw,gid=5,mode=620)
sysfs on /sys type sysfs (rw)
tmpfs on /tmp type tmpfs (rw,size=64M)
none on /proc/bus/usb type usbfs (rw)
/dev/sda4 on /mnt/ext type ext3 (rw)
/dev/md9 on /mnt/HDA_ROOT type ext3 (rw,data=ordered)
/dev/ram2 on /mnt/update type ext2 (rw)
tmpfs on /samba type tmpfs (rw,size=64M)
tmpfs on /samba/.samba/lock/msg.lock type tmpfs (rw,size=16M)
tmpfs on /mnt/ext/opt/samba/private/msg.sock type tmpfs (rw,size=16M)
tmpfs on /mnt/rf/nd type tmpfs (rw,size=1m)


Memory Information:

              total         used         free       shared      buffers
  Mem:       515492       442500        72992            0        22952
 Swap:            0            0            0
Total:       515492       442500        72992

NASReport completed on 2019-03-08 21:15:41 (/tmp/nasreport) 
Recent event log

Code: Select all

Number	Type	Date	Time	Users	Content
719	Warn	08/03/2019	20:29:47	System	[Microsoft Networking] /etc/config/smb.conf setup 'map to guest' not found. Repaired.
718	Warn	08/03/2019	20:29:46	System	[Microsoft Networking] /etc/config/smb.conf setup 'guest account' not found. Repaired.
717	Warn	08/03/2019	20:28:22	System	The firmware versions of the system built-in flash (4.3.3 Build 20181029) and the hard drive (1.0.0 Build 0000) are not consistent. It is recommended to update the firmware again for higher system stability.
716	Info	08/03/2019	20:28:21	System	System started.
715	Info	08/03/2019	04:25:14	System	[RAID5 Disk Volume: Drive 1 2 3] Start resyncing.
714	Warn	08/03/2019	04:24:51	System	[RAID5 Disk Volume: Drive 1 2 3] The file system is not clean. It is suggested that you go to [Storage Manager] to run Check File System"."
710	Info	08/03/2019	04:09:52	System	System started.
709	Warn	08/03/2019	04:09:52	System	The system was not shut down properly last time.
708	Info	08/03/2019	03:42:58	System	[RAID5 Disk Volume: Drive 1 2 3] Start resyncing.
707	Warn	08/03/2019	03:42:35	System	[RAID5 Disk Volume: Drive 1 2 3] The file system is not clean. It is suggested that you go to [Storage Manager] to run Check File System"."
703	Info	08/03/2019	03:27:27	System	System started.
702	Warn	08/03/2019	03:27:26	System	The system was not shut down properly last time.
701	Info	08/03/2019	03:23:05	System	[RAID5 Disk Volume: Drive 1 2 3] Start resyncing.
697	Info	08/03/2019	03:07:34	System	System started.
696	Warn	08/03/2019	03:07:34	System	The system was not shut down properly last time.
695	Info	08/03/2019	00:14:25	System	[Antivirus] Virus definitions updated.
694	Info	07/03/2019	23:04:33	System	[RAID5 Disk Volume: Drive 1 2 3] Start resyncing.
693	Warn	07/03/2019	23:04:10	System	[RAID5 Disk Volume: Drive 1 2 3] The file system is not clean. It is suggested that you go to [Storage Manager] to run Check File System"."
689	Info	07/03/2019	22:49:08	System	System started.
688	Warn	07/03/2019	22:49:08	System	The system was not shut down properly last time.
687	Info	07/03/2019	22:30:43	System	[RAID5 Disk Volume: Drive 1 2 3] Resyncing done.
686	Info	07/03/2019	07:29:36	System	[Antivirus] Virus definitions updated.
685	Info	06/03/2019	04:34:00	System	[RAID5 Disk Volume: Drive 1 2 3] Start resyncing.
684	Warn	06/03/2019	04:33:34	System	[RAID5 Disk Volume: Drive 1 2 3] The file system is not clean. It is suggested that you go to [Storage Manager] to run Check File System"."
680	Info	06/03/2019	04:18:23	System	System started.
679	Warn	06/03/2019	04:18:23	System	The system was not shut down properly last time.
678	Info	06/03/2019	03:23:08	System	[RAID5 Disk Volume: Drive 1 2 3] Start resyncing.
677	Warn	06/03/2019	03:22:45	System	[RAID5 Disk Volume: Drive 1 2 3] The file system is not clean. It is suggested that you go to [Storage Manager] to run Check File System"."
673	Info	06/03/2019	03:07:40	System	System started.
672	Warn	06/03/2019	03:07:39	System	The system was not shut down properly last time.
671	Info	06/03/2019	01:00:28	System	[Antivirus] Virus definitions updated.
670	Info	05/03/2019	22:13:31	System	[RAID5 Disk Volume: Drive 1 2 3] Start resyncing.
669	Warn	05/03/2019	22:13:08	System	[RAID5 Disk Volume: Drive 1 2 3] The file system is not clean. It is suggested that you go to [Storage Manager] to run Check File System"."
665	Info	05/03/2019	21:58:07	System	System started.
664	Warn	05/03/2019	21:58:07	System	The system was not shut down properly last time.
660	Info	05/03/2019	21:50:14	System	System started.
659	Warn	05/03/2019	21:50:14	System	The system was not shut down properly last time.
ksmg

Code: Select all

(..)
<5>[   72.226822] eth0: link up, full duplex, speed 1 Gbps
<5>[   72.288267] eth1: link up, full duplex, speed 1 Gbps
<4>[   80.259379] EXT2-fs (mtdblock5): warning: mounting unchecked fs, running e2fsck is recommended
<6>[   83.164281] kjournald starting.  Commit interval 5 seconds
<6>[   83.165743] EXT3-fs (md9): using internal journal
<6>[   83.165761] EXT3-fs (md9): mounted filesystem with ordered data mode
<6>[   83.288957] md: bind<sda1>
<7>[   83.365552] RAID1 conf printout:
<7>[   83.365560]  --- wd:1 rd:4
<7>[   83.365565]  disk 0, wo:1, o:1, dev:sda1
<7>[   83.365571]  disk 2, wo:0, o:1, dev:sdc1
<6>[   83.366564] md: recovery of RAID array md9
<6>[   83.366584] md: minimum _guaranteed_	speed: 5000 KB/sec/disk.
<6>[   83.366598] md: using maximum available idle IO bandwidth (but not more than 200000 KB/sec) for recovery.
<6>[   83.366619] md: using 128k window, over a total of 530112k.
<6>[   83.607330] md: md9: recovery done.
<7>[   83.725546] RAID1 conf printout:
<7>[   83.725553]  --- wd:2 rd:4
<7>[   83.725558]  disk 0, wo:0, o:1, dev:sda1
<7>[   83.725564]  disk 2, wo:0, o:1, dev:sdc1
<6>[   88.523500] md: bind<sdb1>
<7>[   88.615864] RAID1 conf printout:
<7>[   88.615873]  --- wd:2 rd:4
<7>[   88.615879]  disk 0, wo:0, o:1, dev:sda1
<7>[   88.615885]  disk 1, wo:1, o:1, dev:sdb1
<7>[   88.615890]  disk 2, wo:0, o:1, dev:sdc1
<6>[   88.617205] md: recovery of RAID array md9
<6>[   88.617227] md: minimum _guaranteed_	speed: 5000 KB/sec/disk.
<6>[   88.617241] md: using maximum available idle IO bandwidth (but not more than 200000 KB/sec) for recovery.
<6>[   88.617262] md: using 128k window, over a total of 530112k.
<6>[   88.966731] md: md9: recovery done.
<7>[   89.065589] RAID1 conf printout:
<7>[   89.065595]  --- wd:3 rd:4
<7>[   89.065600]  disk 0, wo:0, o:1, dev:sda1
<7>[   89.065606]  disk 1, wo:0, o:1, dev:sdb1
<7>[   89.065611]  disk 2, wo:0, o:1, dev:sdc1
<6>[   93.806224] md: bind<sdd1>
<7>[   93.865615] RAID1 conf printout:
<7>[   93.865622]  --- wd:3 rd:4
<7>[   93.865628]  disk 0, wo:0, o:1, dev:sda1
<7>[   93.865633]  disk 1, wo:0, o:1, dev:sdb1
<7>[   93.865639]  disk 2, wo:0, o:1, dev:sdc1
<7>[   93.865644]  disk 3, wo:1, o:1, dev:sdd1
<6>[   93.866789] md: recovery of RAID array md9
<6>[   93.866809] md: minimum _guaranteed_	speed: 5000 KB/sec/disk.
<6>[   93.866823] md: using maximum available idle IO bandwidth (but not more than 200000 KB/sec) for recovery.
<6>[   93.866844] md: using 128k window, over a total of 530112k.
<6>[   94.186392] md: md9: recovery done.
<7>[   94.245683] RAID1 conf printout:
<7>[   94.245689]  --- wd:4 rd:4
<7>[   94.245695]  disk 0, wo:0, o:1, dev:sda1
<7>[   94.245701]  disk 1, wo:0, o:1, dev:sdb1
<7>[   94.245706]  disk 2, wo:0, o:1, dev:sdc1
<7>[   94.245711]  disk 3, wo:0, o:1, dev:sdd1
<2>[  102.130501] EXT3-fs error (device md9): ext3_free_blocks_sb: bit already cleared for block 36864
<2>[  103.076766] EXT3-fs error (device md9): ext3_free_blocks_sb: bit already cleared for block 36870
<2>[  104.067663] EXT3-fs error (device md9): ext3_free_blocks_sb: bit already cleared for block 36871
<2>[  104.071641] EXT3-fs error (device md9): ext3_free_blocks_sb: bit already cleared for block 36876
<2>[  104.072131] EXT3-fs error (device md9): ext3_free_blocks_sb: bit already cleared for block 36877
<2>[  104.072529] EXT3-fs error (device md9): ext3_free_blocks_sb: bit already cleared for block 36878
<2>[  104.076788] EXT3-fs error (device md9): ext3_free_blocks_sb: bit already cleared for block 36879
<2>[  104.116999] EXT3-fs error (device md9): ext3_free_blocks_sb: bit already cleared for block 36880
<2>[  104.135926] EXT3-fs error (device md9): ext3_free_blocks_sb: bit already cleared for block 36881
<2>[  104.136489] EXT3-fs error (device md9): ext3_free_blocks_sb: bit already cleared for block 36882
<2>[  104.136826] EXT3-fs error (device md9): ext3_free_blocks_sb: bit already cleared for block 36883
<2>[  104.137141] EXT3-fs error (device md9): ext3_free_blocks_sb: bit already cleared for block 36884
<2>[  104.152036] EXT3-fs error (device md9): ext3_free_inode: bit already cleared for inode 7032
<2>[  104.365549] EXT3-fs error (device md9): ext3_free_blocks_sb: bit already cleared for block 40962
<2>[  104.366158] EXT3-fs error (device md9): ext3_free_blocks_sb: bit already cleared for block 40963
<2>[  104.366607] EXT3-fs error (device md9): ext3_free_blocks_sb: bit already cleared for block 40964
<2>[  104.367444] EXT3-fs error (device md9): ext3_free_blocks_sb: bit already cleared for block 40965
<2>[  104.367826] EXT3-fs error (device md9): ext3_free_blocks_sb: bit already cleared for block 40966
<2>[  104.368655] EXT3-fs error (device md9): ext3_free_blocks_sb: bit already cleared for block 40967
<2>[  104.369013] EXT3-fs error (device md9): ext3_free_blocks_sb: bit already cleared for block 40968
<2>[  104.369380] EXT3-fs error (device md9): ext3_free_inode: bit already cleared for inode 7035
<4>[  104.554991] active port 0 :139
<4>[  104.555011] active port 1 :445
<4>[  104.555021] active port 2 :20
<3>[  105.201182] Unable to find swap-space signature
<4>[  105.879026] EXT2-fs (mtdblock5): warning: mounting unchecked fs, running e2fsck is recommended
<3>[  123.571203] Unable to find swap-space signature
<4>[  125.896723] EXT2-fs (mtdblock5): warning: mounting unchecked fs, running e2fsck is recommended
<3>[  129.548735] Unable to find swap-space signature
<3>[  134.791109] Unable to find swap-space signature
<5>[  172.871411] eth0: stopped
<5>[  172.879825] eth1: stopped
<5>[  174.570592] eth0: link down
<5>[  174.570620] eth0: started
<5>[  174.677912] eth1: link down
<5>[  174.677938] eth1: started
<5>[  178.311775] eth0: link up, full duplex, speed 1 Gbps
<5>[  178.316818] eth1: link up, full duplex, speed 1 Gbps
<5>[  190.874835] eth0: stopped
<5>[  190.900024] eth0: link down
<5>[  190.900048] eth0: started
<5>[  190.982500] eth1: stopped
<5>[  191.007630] eth1: link down
<5>[  191.007653] eth1: started
<5>[  194.447948] eth0: link up, full duplex, speed 1 Gbps
<5>[  194.654842] eth1: link up, full duplex, speed 1 Gbps
<2>[  195.326197] EXT3-fs error (device md9): ext3_free_blocks_sb: bit already cleared for block 88067
<2>[  203.746858] EXT3-fs error (device md9): ext3_free_blocks_sb: bit already cleared for block 88071
<2>[  209.476409] EXT3-fs error (device md9): ext3_free_blocks_sb: bit already cleared for block 33219
<4>[  231.365358] active port 0 :139
<4>[  231.365380] active port 1 :445
<4>[  231.365389] active port 2 :20
<2>[  232.491723] EXT3-fs error (device md9): ext3_free_blocks_sb: bit already cleared for block 71680
<4>[  237.318106] [usb.001.001] /sys/devices/platform/orion-ehci.0/usb1 added.
<2>[  248.547646] EXT3-fs error (device md9): ext3_free_blocks_sb: bit already cleared for block 73740
<4>[  249.132496] EXT2-fs (mtdblock5): warning: mounting unchecked fs, running e2fsck is recommended
<6>[  253.513313] warning: process `pic_raw' used the deprecated sysctl system call with 8.1.2.
<4>[  255.378354] rule type=2, num=0
<4>[  255.638831] MAC:00:08:9B:CB:FF:4C
<5>[  255.642450] eth0: link down
<4>[  255.642463] page 3, reg 18  = 4a85
<5>[  255.643378] eth0: link up, full duplex, speed 1 Gbps
<4>[  255.643827] WOL enable
<4>[  255.649594] MAC:00:08:9B:CB:FF:4D
<5>[  255.653227] eth1: link down
<4>[  255.653240] page 3, reg 18  = 4a85
<5>[  255.654159] eth1: link up, full duplex, speed 1 Gbps
<4>[  255.654609] WOL enable
<2>[  259.682070] EXT3-fs error (device md9): ext3_free_blocks_sb: bit already cleared for block 61440
<2>[  259.710869] EXT3-fs error (device md9): ext3_free_blocks_sb: bit already cleared for block 61441
<2>[  259.728479] EXT3-fs error (device md9): ext3_free_blocks_sb: bit already cleared for block 61442
<2>[  259.866909] EXT3-fs error (device md9): ext3_free_blocks_sb: bit already cleared for block 61443
<2>[  259.869667] EXT3-fs error (device md9): ext3_free_blocks_sb: bit already cleared for block 61444
<6>[  260.745522] Loading iSCSI transport class v2.0-871.
<5>[  261.067029] iscsi: registered transport (tcp)
<4>[  261.567409] iscsid (7499): /proc/7499/oom_adj is deprecated, please use /proc/7499/oom_score_adj instead.
<4>[  261.645263] ------------[ cut here ]------------
<4>[  261.645298] WARNING: at fs/inode.c:298 drop_nlink+0x60/0x6c()
<4>[  261.645311] Modules linked in: iscsi_tcp(O) libiscsi_tcp(O) libiscsi(O) scsi_transport_iscsi(O) fbdisk(O) ipv6 uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core v4l2_common videodev v4l2_int_device snd_usb_caiaq snd_usb_audio hid_logitech snd_usbmidi_lib snd_hwdep snd_pcm_oss snd_mixer_oss snd_pcm snd_seq_oss snd_seq_midi snd_seq_midi_event snd_seq snd_rawmidi snd_page_alloc snd_seq_device snd_timer snd soundcore md4 ecb hmac mac80211 cfg80211 lib80211 fnotify(PO) etxhci_hcd cifs nfsd exportfs nfs auth_rpcgss lockd sunrpc udf isofs ufsd(PO) jnl(O) ext4 jbd2 sysinfo(O) usblp usbhid cryptodev(O) mv_cesa sha512_generic sha256_generic sha1_generic aes_generic dm_crypt dm_mod raid456 async_raid6_recov async_pq async_xor async_memcpy async_tx raid6_pq xor raid10 raid0 linear nls_utf8 nls_iso8859_2 nls_cp850 nls_cp437 vfat fat appletalk psnap llc quota_v2 quota_v1 quota_tree fuse hal_netlink(O) hid ehci_hcd ext3 jbd
<4>[  261.645587] Backtrace:
<4>[  261.645608] [<c0013b30>] (dump_backtrace+0x0/0x120) from [<c00140f8>] (dump_stack+0x18/0x1c)
<4>[  261.645627]  r7:00000000 r6:c00bba5c r5:c0371f80 r4:0000012a
<4>[  261.645651] [<c00140e0>] (dump_stack+0x0/0x1c) from [<c003025c>] (warn_slowpath_common+0x54/0x6c)
<4>[  261.645675] [<c0030208>] (warn_slowpath_common+0x0/0x6c) from [<c0030298>] (warn_slowpath_null+0x24/0x2c)
<4>[  261.645694]  r9:dd1af7b8 r8:df2318b0 r7:df1fccc8 r6:df2318b0 r5:df377380
<4>[  261.645712] r4:dd062318
<4>[  261.645728] [<c0030274>] (warn_slowpath_null+0x0/0x2c) from [<c00bba5c>] (drop_nlink+0x60/0x6c)
<4>[  261.645795] [<c00bb9fc>] (drop_nlink+0x0/0x6c) from [<bf020278>] (ext3_rename+0x33c/0x638 [ext3])
<4>[  261.645815]  r5:df377380 r4:cafbfda8
<4>[  261.645862] [<bf01ff3c>] (ext3_rename+0x0/0x638 [ext3]) from [<c00b0630>] (qnap_vfs_rename+0x280/0x3b0)
<4>[  261.645889] [<c00b03b0>] (qnap_vfs_rename+0x0/0x3b0) from [<c00b07a0>] (vfs_rename+0x1c/0x24)
<4>[  261.645913] [<c00b0784>] (vfs_rename+0x0/0x24) from [<c00b3188>] (sys_renameat+0x1e0/0x33c)
<4>[  261.645935] [<c00b2fa8>] (sys_renameat+0x0/0x33c) from [<c00b3308>] (sys_rename+0x24/0x28)
<4>[  261.645958] [<c00b32e4>] (sys_rename+0x0/0x28) from [<c00100a0>] (ret_fast_syscall+0x0/0x2c)
<4>[  261.645977] ---[ end trace f1ccea15ad5beb9a ]---
<3>[ 3465.061143] Alignment trap: not handling instruction 6273752d at [<b6d6b5b2>]
<1>[ 3465.061170] Unhandled fault: alignment exception (0x001) at 0xbef7122a

aspomwell
Know my way around
Posts: 115
Joined: Thu Jun 22, 2017 2:27 am

Re: Raid volumes gone?

Post by aspomwell » Sat Mar 09, 2019 5:48 am

Obligatory post to say "open a ticket with QNAP"

I'd suggest doing it through your NAS to get a ticket number and then call them, otherwise you may wait for days. I'd also not waste any time, as it's nearly end of day Friday and you won't get anyone to answer the phone until monday if you wait much longer.

Sorry I can't be more specific. :(
TVS-673 16GB 6x6TB WD Red WD60EFRX-68L0BN1 in RAID6

RakoczyPhoto
First post
Posts: 1
Joined: Fri Aug 05, 2016 5:31 am

Re: Raid volumes gone?

Post by RakoczyPhoto » Wed Sep 11, 2019 4:46 am

I hope I'm not in a similar boat. But I cannot find a phone number to call and I cannot "do it through my NAS" as the NAS isn't seeming to boot up. I cannot access it on my network and the red status light on the unit simply blinks...

P3R
Guru
Posts: 10884
Joined: Sat Dec 29, 2007 1:39 am
Location: Stockholm, Sweden (UTC+01:00)

Re: Raid volumes gone?

Post by P3R » Wed Sep 11, 2019 5:42 am

RakoczyPhoto wrote:
Wed Sep 11, 2019 4:46 am
But I cannot find a phone number to call...
On the Qnap website goto Support, Support & Resources, Contact us
RAID have never ever been a replacement for backups. Without backups on a different system (preferably placed at another site), you will eventually lose data!

A non-RAID configuration (including RAID 0, which isn't really RAID) with a backup on a separate media protects your data far better than any RAID-volume without backup.

All data storage consists of both the primary storage and the backups. It's your money and your data, spend the storage budget wisely or pay with your data!

Post Reply

Return to “Backup & Restore”