Disk image

From HandWiki
Revision as of 18:47, 6 February 2024 by TextAI (talk | contribs) (update)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Short description: Computer file containing the contents and structure of a disk volume


A disk image is a snapshot of a storage device's structure and data typically stored in one or more computer files on another storage device.[1][2] Traditionally, disk images were bit-by-bit copies of every sector on a hard disk often created for digital forensic purposes, but it is now common to only copy allocated data to reduce storage space.[3][4] Compression and deduplication are commonly used to reduce the size of the image file set.[3][5] Disk imaging is done for a variety of purposes including digital forensics,[6][2] cloud computing,[7] system administration,[8] as part of a backup strategy,[1] and legacy emulation as part of a digital preservation strategy.[9] Disk images can be made in a variety of formats depending on the purpose. Virtual disk images (such as VHD and VMDK) are intended to be used for cloud computing,[10][11] ISO images are intended to emulate optical media[12] and raw disk images are used for forensic purposes.[2] Proprietary formats are typically used by disk imaging software. Despite the benefits of disk imaging the storage costs can be high,[3] management can be difficult[6] and they can be time consuming to create.[13][9]

Background

Disk images were originally (in the late 1960s) used for backup and disk cloning of mainframe disk media. Early ones were as small as 5 megabytes and as large as 330 megabytes, and the copy medium was magnetic tape, which ran as large as 200 megabytes per reel.[14] Disk images became much more popular when floppy disk media became popular, where replication or storage of an exact structure was necessary and efficient, especially in the case of copy protected floppy disks.

Disk image creation is called disk imaging and is often time consuming, even with a fast computer, because the entire disk must be copied.[13] Typically, disk imaging requires a third party disk imaging program or backup software. The software required varies according to the type of disk image that needs to be created. For example, RawWrite and WinImage create floppy disk image files for MS-DOS and Microsoft Windows.[15][16] In Unix or similar systems the dd program can be used to create raw disk images.[2] Apple Disk Copy can be used on Classic Mac OS and macOS systems to create and write disk image files.

Authoring software for CDs/DVDs such as Nero Burning ROM can generate and load disk images for optical media. A virtual disk writer or virtual burner is a computer program that emulates an actual disc authoring device such as a CD writer or DVD writer. Instead of writing data to an actual disc, it creates a virtual disk image.[17][18] A virtual burner, by definition, appears as a disc drive in the system with writing capabilities (as opposed to conventional disc authoring programs that can create virtual disk images), thus allowing software that can burn discs to create virtual discs.[19]

Uses

Digital forensics

Forensic imaging is the process of creating a bit-by-bit copy of the data on the drive, including files, metadata, volume information, filesystems and their structure.[2] Often, these images are also hashed to verify their integrity and that they have not been altered since being created. Unlike disk imaging for other purposes, digital forensic applications take a bit-by-bit copy to ensure forensic soundness. The purposes of imaging the disk is to not only discover evidence preserved in digital information but also to examine the drive to gather clues of how the crime was committed.

Virtual disk image

In cloud computing, creating a virtual disk image of optical media or a hard disk drive is typically done to make the content available to one or more virtual machines. Virtual machines emulate a CD/DVD drive by reading an ISO image. This can also be faster than reading from the physical optical medium.[20] Further, there are less issues with wear and tear. A hard disk drive or solid-state drive in a virtual machine is implemented as a disk image (i.e. either the VHD format used by Microsoft's Hyper-V, the VDI format used by Oracle Corporation's VirtualBox, the VMDK format used for VMware virtual machines, or the QCOW format used by QEMU). Virtual hard disk images tend to be stored as either a collection of files (where each one is typically 2GB in size), or as a single file. Virtual machines treat the image set as a physical drive.

System administration

Rapid deployment of clone systems

Educational institutions and businesses can often need to buy or replace computer systems in large numbers. Disk imaging is commonly used to deploy the same configuration across workstations.[8] Typically, disk imaging software (such as Ghost or Clonezilla) is used to make an image of a completely configured system.[21] This image is then written to a computer's hard disk which is sometimes described as restoring an image.[22] This restoration is sometimes done over a computer network using multicasting or BitTorrent to devices that need to have their configuration restored.[23][22] This reduces the need to maintain and update individual systems manually. Imaging is also easier than automated setup methods because an administrator does not need to have knowledge of the prior configuration to copy it.[22] Disk imaging requires for all devices to be identical and provides no flexibility in adjusting the configuration.

Network-based image deployment typically uses a PXE server to boot a minimal operating system over the network that contains the necessary components to image or restore storage media in a computer.[23] This is usually used in conjunction with a DHCP server to automate the configuration of network parameters including IP addresses. Typically, multicasting, broadcasting or unicasting is used to restore an image to many computers at a time but these approaches do not work well if one or more computers experience a problem such as UDP packet loss.[22] As a result, some imaging solutions instead use the BitTorrent protocol to transfer the data.

Backup strategy

A disk image contains all files, faithfully replicating all data, including file attributes and the file fragmentation state. For this reason, it is also used for backing up optical media (CDs and DVDs, etc.), and allows the exact and efficient recovery after experimenting with modifications to a system or virtual machine. Typically, disk imaging can be used to quickly restore an entire system to an operational state after a disaster.[24]

Digital preservation

Libraries and museums are typically required to archive and digitally preserve information without altering it in any manner.[9][25] Emulators frequently use disk images to emulate floppy disks that have been preserved. This is usually simpler to program than accessing a real floppy drive (particularly if the disks are in a format not supported by the host operating system), and allows a large library of software to be managed. Emulation also allows existing disk images to be put into a usable form even though the data contained in the image is no longer readable without emulation.[12]

Limitations

Disk images can sometimes be slower than reading from the disk directly because of a performance overhead.[3] Other limitations can be the lack of access to software required to read the contents of the image. For example, prior to Windows 8, third party software was required to mount disk images.[26][27] Disk imaging is time consuming and the space requirements are high. When imaging multiple computers with only minor differences, much data is duplicated unnecessarily, wasting space.[3]

Speed and failure

Disk imaging can be slow, especially for older storage devices. A typical 4.7 GB DVD can take an average of 18 minutes to duplicate.[9] Floppy disks read and write much slower than hard disks. Therefore, despite their small size, it can take several minutes to copy a single disk. In some cases, disk imaging can fail due to bad sectors or physical wear and tear on the source device.[12] Utilities such as dd are not designed to recognize or cope with failures. Therefore, any failure results in being unable to create an image of the drive.[25]

See also

References

  1. ↑ 1.0 1.1 Colloton, Eddy; Farbowitz, Jonathan; Rodríguez, Caroline Gil (2022-11-02). "Disk Imaging as a Backup Tool for Digital Objects" (in en). Conservation of Time-Based Media Art. pp. 204–222. doi:10.4324/9781003034865-17. ISBN 9781003034865. https://www.taylorfrancis.com/chapters/edit/10.4324/9781003034865-17/disk-imaging-backup-tool-digital-objects-eddy-colloton-jonathan-farbowitz-caroline-gil-rodr%C3%ADguez. 
  2. ↑ 2.0 2.1 2.2 2.3 2.4 Woods, Kam; Lee, Christopher A.; Garfinkel, Simson (2011-06-13). "Extending digital repository architectures to support disk image preservation and access". Proceedings of the 11th Annual International ACM/IEEE Joint Conference on Digital Libraries. New York, NY, USA: Association for Computing Machinery. pp. 57–66. doi:10.1145/1998076.1998088. ISBN 978-1-4503-0744-4. https://doi.org/10.1145/1998076.1998088. 
  3. ↑ 3.0 3.1 3.2 3.3 3.4 Pullakandam, R.; Lin, X.; Hibler, M.; Eide, E.; Ricci, R. (October 23–26, 2011). "High-performance Disk Imaging With Deduplicated Storage". 23rd ACM Symposium on Operating Systems Principles. Cascais, Portugal. https://www.sigops.org/s/conferences/sosp/2011/posters/summaries/sosp11-final15.pdf. 
  4. ↑ Kävrestad, Joakim (2017), Kävrestad, Joakim, ed., "Vocabulary" (in en), Guide to Digital Forensics: A Concise and Practical Introduction, SpringerBriefs in Computer Science (Cham: Springer International Publishing): pp. 125–126, doi:10.1007/978-3-319-67450-6_12, ISBN 978-3-319-67450-6, https://doi.org/10.1007/978-3-319-67450-6_12, retrieved 2023-01-12 
  5. ↑ Lee, Sang Su; Kyong, Un Sung; Hong, Do Won (2008). "A high speed disk imaging system". 2008 IEEE International Symposium on Consumer Electronics. pp. 1–3. doi:10.1109/ISCE.2008.4559553. https://ieeexplore.ieee.org/document/4559553. 
  6. ↑ 6.0 6.1 Garfinkel, Simson L. (2009). "Automating Disk Forensic Processing with SleuthKit, XML and Python". 2009 Fourth International IEEE Workshop on Systematic Approaches to Digital Forensic Engineering. pp. 73–84. doi:10.1109/SADFE.2009.12. ISBN 978-0-7695-3792-4. https://ieeexplore.ieee.org/document/5341559. 
  7. ↑ Kazim, Muhammad; Masood, Rahat; Shibli, Muhammad Awais (2013-11-26). "Securing the virtual machine images in cloud computing". Proceedings of the 6th International Conference on Security of Information and Networks. New York, NY, USA: Association for Computing Machinery. pp. 425–428. doi:10.1145/2523514.2523576. ISBN 978-1-4503-2498-4. https://doi.org/10.1145/2523514.2523576. 
  8. ↑ 8.0 8.1 Blackham, N.; Higby, C.; Bailey, M. (June 2004). "Re-Imaging Computers For Multipurpose Labs". 2004 American Society for Engineering Education Annual Conference. Salt Lake City, Utah. doi:10.18260/1-2--14125. https://peer.asee.org/re-imaging-computers-for-multipurpose-labs. 
  9. ↑ 9.0 9.1 9.2 9.3 Day, Michael; Pennock, Maureen; May, Peter; Davies, Kevin; Whibley, Simon; Kimura, Akiko; Halvarsson, Edith (2016). "The preservation of disk-based content at the British Library: Lessons from the Flashback project" (in en). Alexandria: The Journal of National and International Library and Information Issues 26 (3): 216–234. doi:10.1177/0955749016669775. ISSN 0955-7490. http://journals.sagepub.com/doi/10.1177/0955749016669775. 
  10. ↑ Arunkumar, G.; Venkataraman., Neelanarayanan (2015-01-01). "A Novel Approach to Address Interoperability Concern in Cloud Computing" (in en). Procedia Computer Science. Big Data, Cloud and Computing Challenges 50: 554–559. doi:10.1016/j.procs.2015.04.083. ISSN 1877-0509. 
  11. ↑ Barrowclough, John Patrick; Asif, Rameez (2018-06-11). "Securing Cloud Hypervisors: A Survey of the Threats, Vulnerabilities, and Countermeasures" (in en). Security and Communication Networks 2018: e1681908. doi:10.1155/2018/1681908. ISSN 1939-0114. 
  12. ↑ 12.0 12.1 12.2 Colloton, E.; Farbowitz, J.; Fortunato, F.; Gil, C. (2019). "Towards Best Practices In Disk Imaging: A Cross-Institutional Approach". Electronic Media Review 6. https://resources.culturalheritage.org/emg-review/volume-6-2019-2020/colloton/. 
  13. ↑ 13.0 13.1 Stewart, Dawid; Arvidsson, Alex (2022). Need for speed : A study of the speed of forensic disk imaging tools. http://urn.kb.se/resolve?urn=urn:nbn:se:hh:diva-47045. 
  14. ↑ "IBM Mainframe Operating Systems". http://www.demorton.com/Tech/$OSTL.pdf. 
  15. ↑ McCune, Mike (2000) (in en). Integrating Linux and Windows. Prentice Hall Professional. ISBN 978-0-13-030670-8. https://books.google.com/books?id=0SM3PEH9gagC&q=rawwrite&pg=PR1. 
  16. ↑ Li, Hongwei; Yin, Changhong; Xu, Yaping; Guo, Qingjun (2010). "Construction of the Practical Teaching System on Operating Systems Course". 2010 Second International Workshop on Education Technology and Computer Science. 1. pp. 405–408. doi:10.1109/ETCS.2010.184. ISBN 978-1-4244-6388-6. https://ieeexplore.ieee.org/document/5458788. 
  17. ↑ "Phantom Burner Overview". Phantombility, Inc. http://www.phantombility.com/en/prod/phantomburner/. 
  18. ↑ "Virtual CD - The original for your PC". Virtual CD website. H+H Software GmbH. http://www.virtualcd.de/vcd/apps/overview/original.cfm?lg=0. 
  19. ↑ "Virtual CD/DVD-Writer Device". SourceForge. Geeknet, Inc.. http://sourceforge.net/projects/virtualmedia/. 
  20. ↑ "pcguide.com - Access Time". http://www.pcguide.com/ref/cd/perfAccess-c.html. 
  21. ↑ Bowling, Jeramiah (2011-01-01). "Clonezilla: build, clone, repeat". Linux Journal 2011 (201): 6:6. ISSN 1075-3583. https://dl.acm.org/doi/10.5555/1924401.1924407. 
  22. ↑ 22.0 22.1 22.2 22.3 Shiau, Steven J. H.; Huang, Yu-Chiang; Tsai, Yu-Chin; Sun, Chen-Kai; Yen, Ching-Hsuan; Huang, Chi-Yo (2021). "A BitTorrent Mechanism-Based Solution for Massive System Deployment". IEEE Access 9: 21043–21058. doi:10.1109/ACCESS.2021.3052525. ISSN 2169-3536. Bibcode: 2021IEEEA...921043S. 
  23. ↑ 23.0 23.1 Shiau, Steven J. H.; Sun, Chen-Kai; Tsai, Yu-Chin; Juang, Jer-Nan; Huang, Chi-Yo (2018). "The Design and Implementation of a Novel Open Source Massive Deployment System" (in en). Applied Sciences 8 (6): 965. doi:10.3390/app8060965. ISSN 2076-3417. 
  24. ↑ "Fast, Scalable Disk Imaging with Frisbee". https://www.cs.utah.edu/flux/papers/frisbee-usenix03/frisbee-www.html. 
  25. ↑ 25.0 25.1 Durno, John; Trofimchuk, Jerry (2015-01-21). "Digital forensics on a shoestring: a case study from the University of Victoria". The Code4Lib Journal (27). ISSN 1940-5758. https://journal.code4lib.org/articles/10279?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed:+c4lj+. 
  26. ↑ "Accessing data in ISO and VHD files". Building Windows 8 (TechNet Blogs). Microsoft. 30 August 2011. http://blogs.msdn.com/b/b8/archive/2011/08/30/accessing-data-in-iso-and-vhd-files.aspx. 
  27. ↑ "Mount-DiskImage". Microsoft. https://learn.microsoft.com/en-us/powershell/module/storage/mount-diskimage. 

External links



Retrieved from "https://handwiki.org/wiki/index.php?title=Disk_image&oldid=3373258"