1 | 13 | ||||||||||||||||||||||||
16 | |||||||||||||||||||||||||
2 | |||||||||||||||||||||||||
3 | |||||||||||||||||||||||||
5 | 4 | ||||||||||||||||||||||||
15 | |||||||||||||||||||||||||
14 | 18 | ||||||||||||||||||||||||
6 | |||||||||||||||||||||||||
17 | |||||||||||||||||||||||||
7 | |||||||||||||||||||||||||
8 | |||||||||||||||||||||||||
9 | |||||||||||||||||||||||||
10 | |||||||||||||||||||||||||
11 | |||||||||||||||||||||||||
12 | |||||||||||||||||||||||||
1. A detailed strategy outlining how data will be backed up regularly to prevent loss in case of system failure.
2. The process of resending data packets that have been lost or corrupted during transmission.
3. The additional storage space required to store parity blocks, reducing the overall usable capacity of a RAID system.
4. Seismic activity that can cause physical damage to data storage infrastructure leading to data loss.
5. The process of verifying the integrity of network data by sending a request packet and comparing the echoed response packet.
6. The malfunction or damage of physical components in ICT systems that can lead to data loss.
7. The potential legal liabilities faced by organizations due to data loss, including fines, penalties, and lawsuits for failing to protect sensitive information.
8. A value calculated from the data to verify its integrity and detect errors.
9. Electrical discharge during thunderstorms that can cause power surges leading to data loss.
10. Mistakes or negligence by individuals operating or managing ICT systems that may result in data loss.
11. A technique where data is divided into blocks and stored across multiple disks, including parity blocks.
12. A device or location used to store backup data, such as a hard drive or cloud storage.
13. A technique used in computer networks to handle lost or corrupted data packets by retransmitting them automatically.
14. The process of deriving parity information from the data blocks.
15. Information sent from the receiver to the sender to indicate whether data packets have been successfully received or not.
16. Systems that need to be continuously operational without any downtime.
17. The assurance that data remains accurate, consistent, and complete throughout its lifecycle.
18. Storing older or infrequently accessed data in a separate location to prevent loss without cluttering the primary storage.