Hot answers tagged

12

The real problem regarding URE and RAID5 is that, upon encoutering even a single URE, many hardware controllers simply abort the RAID reconstruction and declare the array death, putting all your data offline. While this is the "safest bet" regarding potential data corruption, it is not always the best thing to do (eg: think about a URE affecting a free/not-...


2

Anything on the volume is at risk If you are stating that you have a concern regarding URE on a volume/LUN that has suffered from a RAID 5/6 drive failure then all of the data on that volume would be at risk. Ensure you are storing your data on a different volume/LUN than your backup is stored on. Best practice would state your backup is on a completely ...


2

In principle, yes, but if you store your backup on a RAID6 (as an example), you will have the benefit of the redundancy, so the total error rate will be much lower, and with it the chance of an URE during recovery. If you use a tape backup solution, the error rates are much lower to begin with (SAS: 1x10^-15 - 1x10^-16, LTO7: 1x10^-19).


1

As an alternative, consider putting the folder under version control with SVN (if it's a lot of binary files, I recommend against Git). SVN has a lot of advantages over rsync and a few downsides: SVN handles binary files very well, sending only compressed deltas across the wire Everything is versioned, so accidental deletes can be undone Very efficient ...


1

full means that you cannot write anymore information to it (because it reached quota or just full). on archive means that data has been already archived (deleted from source and are available on backup storage). Append -> still writing to / or have possibility to write on.



Only top voted, non community-wiki answers of a minimum length are eligible