Knowledge

Data loss

Source 📝

297: 373:
create temporary files in order to boot, and these may overwrite areas of lost data — rendering it unrecoverable. Viewing web pages has the same effect — potentially overwriting lost files with the temporary HTML and image files created when viewing a web page. File operations such as copying, editing, or deleting should also be avoided.
372:
If data loss occurs, a successful recovery must ensure that the deleted data is not over-written. For this reason write operations to the affected storage device should be avoided. This includes not starting the system to which the affected device is connected. This is because many operating systems
339:
was noticed. However, in most situations, there is an inverse correlation between the value of a unit of data and the length of time it takes to notice the loss of that data. Taking this into consideration, many backup strategies decrease the granularity of restorability as the time increases since
323:
Successful recovery from data loss generally requires implementation of an effective backup strategy. Without an implemented backup strategy, recovery requires reinstallation of programs and regeneration of data. Even with an effective backup strategy, restoring a system to the precise state it was
220:
Studies show hardware failure and human error are the two most common causes of data loss, accounting for roughly three quarters of all incidents. Another cause of data loss is a natural disaster, which is a greater risk dependent on where the hardware is located. While the probability of data loss
319:
File system corruption can frequently be repaired by the user or the system administrator. For example, a deleted file is typically not immediately overwritten on disk, but more often simply has its entry deleted from the file system index. In such a case, the deletion can be easily reversed.
380:
device and then attempt to recover lost data. If possible, create an image of the drive in order to establish a secondary copy of the data. This can then be tested on, with recovery attempted, abolishing the risk of harming the source data.
233:
is directly related to the value of the data and the length of time that it is unavailable yet needed. For an enterprise in particular, the definition of cost extends beyond the financial and can also include time. Consider:
221:
due to natural disaster is small, the only way to prepare for such an event is to store backup data in a separate physical location. As such, the best backup plans always include at least one copy being stored off-site.
277:
are an important asset to have when trying to recover after a data loss event, but they do not prevent user errors or system failures. As such, a data backup plan needs to be established and run in unison with a
269:
For hard disk drives, which are a physical storage medium, ensuring minimal vibration and movement will help protect against damaging the components internally, as can maintaining a suitable drive temperature.
253:
The frequency of data loss and the impact can be greatly mitigated by taking proper precautions, those of which necessary can vary depending on the type of data loss. For example, multiple power circuits with
359:
Recovering a single lost file is substantially different from recovering an entire system that was destroyed in a disaster. An effective backup regimen has some proportionality between the magnitude of
376:
Upon realizing data loss has occurred, it is often best to shut down the computer and remove the drive in question from the unit. Re-attach this drive to a secondary computer with a
304:
Data recovery is often performed by specialized commercial services that have developed often proprietary methods to recover data from physically damaged media. Service costs at
58:. Although the two have substantially similar consequences for users, data unavailability is temporary, while data loss may be permanent. Data loss is also distinct from 332:
may not be immediately apparent. An effective backup strategy must also consider the cost of maintaining the ability to recover lost data for long periods of time.
258:
and a generator only protect against power failures, though using an Uninterruptible Power Supply can protect drive against sudden power spikes. Similarly, using a
364:
and the magnitude of effort required to recover. For example, it should be far easier to restore the single lost file than to recover the entire system.
453: 335:
A highly effective backup system would have duplicate copies of every file and program that were immediately accessible whenever a
499: 328:
is extremely difficult. Some level of compromise between granularity of recoverability and cost is necessary. Furthermore, a
263: 429: 62:, an incident where data falls into the wrong hands, although the term data loss has been used in those incidents. 525: 300:
Media that's suffered a catastrophic electronic failure requires data recovery in order to salvage its contents.
619: 400: 461: 27:
on hard drives) or neglect (like mishandling, careless handling or storage under unsuitable conditions) in
207: 703: 699: 51:
lost data. Data loss can also occur if the physical medium containing the data is lost or stolen.
628: 906: 901: 730: 279: 259: 474:
A data spill is sometimes referred to as unintentional information disclosure or a data leak.
422:
Managing catastrophic loss of sensitive data : a guide for IT and security professionals
138: 28: 308:
are usually dependent on type of damage and type of storage medium, as well as the required
860: 8: 800: 785: 713: 137:
Business failure (vendor bankruptcy), where data is stored with a software vendor using
612: 309: 20: 790: 780: 644: 576: 550: 435: 425: 305: 124: 44: 32: 740: 689: 674: 654: 639: 161: 142: 870: 805: 795: 765: 708: 679: 669: 395: 148: 36: 880: 875: 840: 820: 815: 770: 745: 664: 255: 211: 199: 55: 485: 895: 845: 835: 810: 684: 649: 605: 439: 377: 291: 266:
storage only protect against certain types of software and hardware failure.
195: 110: 48: 23:
in which information is destroyed by failures (like failed spindle motors or
54:
Data loss is distinguished from data unavailability, which may arise from a
855: 850: 830: 825: 755: 750: 725: 718: 694: 113:, resulting in data in volatile memory not being saved to permanent memory. 775: 735: 59: 390: 203: 165: 117: 24: 865: 577:"Backup Software, Professional Backup Solution can prevent data loss" 313: 296: 131: 659: 173: 274: 40: 551:"Data Loss Prevention: 10 Tips to Prevent Hard Drive Failure" 169: 179: 244:
The cost of notifying users in the event of a compromise
151:, such as file system corruption or database corruption. 597: 893: 526:"Preventing data loss in a perilous digital age" 47:equipment and processes to prevent data loss or 367: 348:is easier and more complete than recovery from 134:, such as not confirming a file delete command. 613: 191:Theft, hacking, SQL injection, sabotage, etc. 127:or freeze, resulting in data not being saved. 419: 620: 606: 81:Intentional deletion of a file or program 497: 355:Recovery is also related to the type of 295: 91:Accidental deletion of a file or program 574: 238:The cost of continuing without the data 894: 548: 344:. By this logic, recovery from recent 94:Misplacement of physical storage media 601: 100:Inability to read unknown file format 504:TrendLabs Security Intelligence Blog 498:Leopando, Jonathan (2 April 2013). 460:. December 24, 2014. Archived from 352:that happened further in the past. 13: 500:"World Backup Day: The 3-2-1 Rule" 420:Constantine., Photopoulos (2008). 14: 918: 575:Leonard, Prisley (14 June 2017). 549:Connor, Chris (2 November 2013). 285: 39:. Information systems implement 241:The cost of recreating the data 568: 542: 518: 491: 479: 446: 413: 401:List of data recovery software 1: 454:"Data Spill Management Guide" 424:. Rockland, Mass.: Syngress. 406: 248: 368:Initial steps upon data loss 116:Hardware failure, such as a 7: 488:- Graziadio Business Report 384: 194:A malicious act, such as a 10: 923: 289: 635: 145:has not been provisioned. 19:is an error condition in 627: 282:in order to lower risk. 65: 224: 301: 280:disaster recovery plan 260:journaling file system 130:Software bugs or poor 486:The cost of lost data 299: 139:Software-as-a-service 97:Administration errors 801:Protection (privacy) 87:Unintentional action 555:Data Storage Digest 464:on January 23, 2015 21:information systems 306:data recovery labs 302: 77:Intentional action 889: 888: 881:Wrangling/munging 731:Format management 45:disaster recovery 914: 622: 615: 608: 599: 598: 592: 591: 589: 587: 572: 566: 565: 563: 561: 546: 540: 539: 537: 536: 522: 516: 515: 513: 511: 495: 489: 483: 477: 476: 471: 469: 450: 444: 443: 417: 357:Data Loss Event. 350:Data Loss Events 346:Data Loss Events 324:in prior to the 162:Natural disaster 143:SaaS data escrow 922: 921: 917: 916: 915: 913: 912: 911: 892: 891: 890: 885: 861:Synchronization 631: 626: 596: 595: 585: 583: 573: 569: 559: 557: 547: 543: 534: 532: 524: 523: 519: 509: 507: 496: 492: 484: 480: 467: 465: 452: 451: 447: 432: 418: 414: 409: 396:Data truncation 387: 370: 342:Data Loss Event 337:Data Loss Event 330:Data Loss Event 326:Data Loss Event 294: 288: 251: 231:data loss event 227: 149:Data corruption 120:in a hard disk. 68: 12: 11: 5: 920: 910: 909: 904: 887: 886: 884: 883: 878: 873: 868: 863: 858: 853: 848: 843: 838: 833: 828: 823: 818: 813: 808: 803: 798: 793: 788: 786:Pre-processing 783: 778: 773: 768: 763: 758: 753: 748: 743: 738: 733: 728: 723: 722: 721: 716: 711: 697: 692: 687: 682: 677: 672: 667: 662: 657: 652: 647: 642: 636: 633: 632: 625: 624: 617: 610: 602: 594: 593: 567: 541: 517: 490: 478: 445: 430: 411: 410: 408: 405: 404: 403: 398: 393: 386: 383: 369: 366: 340:the potential 290:Main article: 287: 284: 256:battery backup 250: 247: 246: 245: 242: 239: 229:The cost of a 226: 223: 218: 217: 216: 215: 212:physical media 192: 184: 183: 182: 177: 154: 153: 152: 146: 135: 128: 121: 114: 103: 102: 101: 98: 95: 92: 84: 83: 82: 74: 67: 64: 56:network outage 9: 6: 4: 3: 2: 919: 908: 907:Data recovery 905: 903: 902:Computer data 900: 899: 897: 882: 879: 877: 874: 872: 869: 867: 864: 862: 859: 857: 854: 852: 849: 847: 844: 842: 839: 837: 834: 832: 829: 827: 824: 822: 819: 817: 814: 812: 809: 807: 804: 802: 799: 797: 794: 792: 789: 787: 784: 782: 779: 777: 774: 772: 769: 767: 764: 762: 759: 757: 754: 752: 749: 747: 744: 742: 739: 737: 734: 732: 729: 727: 724: 720: 717: 715: 712: 710: 707: 706: 705: 701: 698: 696: 693: 691: 688: 686: 683: 681: 678: 676: 673: 671: 668: 666: 663: 661: 658: 656: 653: 651: 648: 646: 643: 641: 638: 637: 634: 630: 623: 618: 616: 611: 609: 604: 603: 600: 582: 578: 571: 556: 552: 545: 531: 527: 521: 506:. Trend Micro 505: 501: 494: 487: 482: 475: 463: 459: 455: 449: 441: 437: 433: 431:9781597492393 427: 423: 416: 412: 402: 399: 397: 394: 392: 389: 388: 382: 379: 378:write blocker 374: 365: 363: 358: 353: 351: 347: 343: 338: 333: 331: 327: 321: 317: 315: 311: 307: 298: 293: 292:Data recovery 286:Data recovery 283: 281: 276: 273:Regular data 271: 267: 265: 261: 257: 243: 240: 237: 236: 235: 232: 222: 213: 209: 205: 201: 197: 193: 190: 189: 188: 185: 181: 178: 175: 171: 167: 163: 160: 159: 158: 155: 150: 147: 144: 140: 136: 133: 129: 126: 122: 119: 115: 112: 111:Power failure 109: 108: 107: 104: 99: 96: 93: 90: 89: 88: 85: 80: 79: 78: 75: 73: 70: 69: 63: 61: 57: 52: 50: 46: 42: 38: 34: 30: 26: 22: 18: 791:Preservation 781:Philanthropy 760: 645:Augmentation 584:. Retrieved 581:minitool.com 580: 570: 558:. Retrieved 554: 544: 533:. Retrieved 529: 520: 508:. Retrieved 503: 493: 481: 473: 466:. Retrieved 462:the original 457: 448: 421: 415: 375: 371: 361: 356: 354: 349: 345: 341: 336: 334: 329: 325: 322: 318: 316:procedures. 303: 272: 268: 252: 230: 228: 219: 210:or theft of 186: 156: 105: 86: 76: 71: 53: 33:transmission 25:head crashes 16: 15: 851:Stewardship 741:Integration 690:Degradation 675:Compression 655:Archaeology 640:Acquisition 468:January 23, 123:A software 60:data breach 896:Categories 871:Validation 806:Publishing 796:Processing 766:Management 680:Corruption 670:Collection 586:25 October 535:2018-10-26 458:asd.gov.au 407:References 391:Data spill 249:Prevention 204:Ransomware 166:earthquake 118:head crash 72:Procedural 37:processing 876:Warehouse 841:Scrubbing 821:Retention 816:Reduction 771:Migration 746:Integrity 714:Transform 665:Cleansing 530:TechRadar 440:228148168 362:Data Loss 314:cleanroom 132:usability 17:Data loss 846:Security 836:Scraping 811:Recovery 685:Curation 650:Analysis 560:29 April 510:29 April 385:See also 310:security 157:Disaster 856:Storage 831:Science 826:Quality 756:Lineage 751:Library 726:Farming 709:Extract 695:Editing 275:backups 208:hacking 174:tornado 106:Failure 49:restore 29:storage 776:Mining 736:Fusion 438:  428:  176:, etc. 41:backup 200:virus 187:Crime 170:flood 125:crash 66:Types 35:, or 866:Type 761:Loss 719:Load 629:Data 588:2018 562:2015 512:2015 470:2015 436:OCLC 426:ISBN 264:RAID 262:and 225:Cost 196:worm 180:Fire 141:and 43:and 704:ELT 700:ETL 660:Big 312:or 898:: 579:. 553:. 528:. 502:. 472:. 456:. 434:. 206:, 202:, 198:, 172:, 168:, 164:, 31:, 702:/ 621:e 614:t 607:v 590:. 564:. 538:. 514:. 442:. 214:.

Index

information systems
head crashes
storage
transmission
processing
backup
disaster recovery
restore
network outage
data breach
Power failure
head crash
crash
usability
Software-as-a-service
SaaS data escrow
Data corruption
Natural disaster
earthquake
flood
tornado
Fire
worm
virus
Ransomware
hacking
physical media
battery backup
journaling file system
RAID

Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.