System image: Difference between revisions

Revision as of 13:29, 18 October 2021

Revision as of 03:15, 23 April 2024

Line 1:

{{Refimprove|date=December 2013}}

In [[computing]], a '''system image''' is a [[serialization|serialized]] copy of the entire [[State (computer science)|state]] of a [[computer system]] stored in some [[SecondaryComputer data storage|non-volatile]] form, such as a [[Computer file|file]]. A system is said to be capable of using system images if it can be shut down and later restored to exactly the same state. In such cases, system images can be used for [[backup]].

If a system has all its state written to a disk (i.e. on a [[disk image]]), then a system image can be produced by simply copying thatthe disk to a file elsewhere, often with [[disk cloning]] applications. On many systems a complete system image cannot be created by a disk cloning program running within that system because information can be held outside of disks and volatile memory, for example in non-volatile memory like boot ROMs.

[[Hibernate (OS feature)|Hibernation]] is an example that uses an image of the entire machine's [[Random-access memory|RAM]].

A system is said to be capable of using system images if it can be shut down and later restored to exactly the same state. In such cases, system images can be used for [[backup]].

==Disk images==

{{Main article|Disk image}}

[[HibernateHibernation (OS featurecomputing)|Hibernation]] is an example that uses an image of the entire machine's [[Random-access memory|RAM]].

If a system has all its state written to a disk, then a system image can be produced by simply copying that disk to a file elsewhere, often with [[disk cloning]] applications. On many systems a complete system image cannot be created by a disk cloning program running within that system because information can be held outside of disks and volatile memory, for example in non-volatile memory like boot ROMs.

==Process images==

Line 27:

== See also ==

* [[Disk image]]

* [[ISO image]]