Changeset 105289 in vbox for trunk/doc/manual/en_US/dita/topics/snapshots-take-restore-delete.dita
- Timestamp:
- Jul 12, 2024 9:07:43 AM (6 months ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/doc/manual/en_US/dita/topics/snapshots-take-restore-delete.dita
r105176 r105289 86 86 </image> 87 87 </fig> 88 <p> 89 <ph conkeyref="vbox-conkeyref-phrases/product-name"/> imposes no limits on the number of snapshots 90 you can take. The only practical limitation is disk space on 91 your host. Each snapshot stores the state of the virtual 92 machine and thus occupies some disk space. See 93 <xref href="snapshots-contents.dita#snapshots-contents"/> for details on what is 94 stored in a snapshot. 95 </p> 88 <p><ph conkeyref="vbox-conkeyref-phrases/product-name"/> imposes no limits on the number of 89 snapshots you can take. The only practical limitation is disk space on your host. Each snapshot stores the 90 state of the virtual machine and thus occupies some disk space. See <xref 91 href="snapshots-contents.dita#snapshots-contents"/> for details on what is stored in a snapshot. </p> 96 92 </li> 97 93 <li> 98 <p> 99 <b outputclass="bold">Restore a snapshot.</b> In the 100 Snapshots window, select the snapshot you have taken and 101 click <b outputclass="bold">Restore</b> in the 102 toolbar. By restoring a snapshot, you go back or forward in 103 time. The current state of the machine is lost, and the 104 machine is restored to the exact state it was in when the 105 snapshot was taken. 106 </p> 94 <p><b outputclass="bold">Restore a snapshot.</b> In the Snapshots window, select the snapshot 95 you have taken and click <b outputclass="bold">Restore</b> in the toolbar. By restoring a snapshot, you go 96 back or forward in time. The current state of the machine is lost, and the machine is restored to the exact 97 state it was in when the snapshot was taken. </p> 107 98 <note> 108 <p> 109 Restoring a snapshot will affect the virtual hard drives 110 that are connected to your VM, as the entire state of the 111 virtual hard drive will be reverted as well. This means 112 also that all files that have been created since the 113 snapshot and all other file changes <i>will be 114 lost. </i>In order to prevent such data loss while 115 still making use of the snapshot feature, it is possible 116 to add a second hard drive in 117 <i>write-through</i> mode using the 118 <userinput>VBoxManage</userinput> interface and use it to 119 store your data. As write-through hard drives are 120 <i>not</i> included in snapshots, they 121 remain unaltered when a machine is reverted. See 122 <xref href="hdimagewrites.dita#hdimagewrites"/>. 123 </p> 99 <p>Restoring a snapshot will affect the virtual hard drives that are connected to your VM, as 100 the entire state of the virtual hard drive will be reverted as well. This means also that all files that 101 have been created since the snapshot and all other file changes <i>will be lost. </i>In order to prevent 102 such data loss while still making use of the snapshot feature, it is possible to add a second hard drive in 103 <i>write-through</i> mode using the <userinput>VBoxManage</userinput> interface and use it to store your 104 data. As write-through hard drives are <i>not</i> included in snapshots, they remain unaltered when a 105 machine is reverted. See <xref href="hdimagewrites.dita#hdimagewrites"/>. </p> 124 106 </note> 125 <p> 126 To avoid losing the current state when restoring a snapshot, 127 you can create a new snapshot before the restore operation. 128 </p> 129 <p> 130 By restoring an earlier snapshot and taking more snapshots 131 from there, it is even possible to create a kind of 132 alternate reality and to switch between these different 133 histories of the virtual machine. This can result in a whole 134 tree of virtual machine snapshots. 135 </p> 107 <p>To avoid losing the current state when restoring a snapshot, you can create a new snapshot 108 before the restore operation. </p> 109 <p>By restoring an earlier snapshot and taking more snapshots from there, it is even possible to 110 create a kind of alternate reality and to switch between these different histories of the virtual machine. 111 This can result in a whole tree of virtual machine snapshots. </p> 136 112 </li> 137 113 <li> 138 <p> 139 <b outputclass="bold">Delete a snapshot.</b> This 140 does not affect the state of the virtual machine, but only 141 releases the files on disk that <ph conkeyref="vbox-conkeyref-phrases/product-name"/> used to store 142 the snapshot data, thus freeing disk space. To delete a 143 snapshot, select the snapshot name in the Snapshots window 144 and click <b outputclass="bold">Delete</b> in the 145 toolbar. Snapshots can be deleted even while a machine is 146 running. 147 </p> 114 <p><b outputclass="bold">Delete a snapshot.</b> This does not affect the state of the virtual 115 machine, but only releases the files on disk that <ph conkeyref="vbox-conkeyref-phrases/product-name"/> used 116 to store the snapshot data, thus freeing disk space. To delete a snapshot, select the snapshot name in the 117 Snapshots window and click <b outputclass="bold">Delete</b> in the toolbar. Snapshots can be deleted even 118 while a machine is running. </p> 148 119 <note> 149 <p> 150 Whereas taking and restoring snapshots are fairly quick 151 operations, deleting a snapshot can take a considerable 152 amount of time since large amounts of data may need to be 153 copied between several disk image files. Temporary disk 154 files may also need large amounts of disk space while the 155 operation is in progress. 156 </p> 120 <p>Whereas taking and restoring snapshots are fairly quick operations, deleting a snapshot 121 can take a considerable amount of time since large amounts of data may need to be copied between several 122 disk image files. Temporary disk files may also need large amounts of disk space while the operation is in 123 progress. </p> 157 124 </note> 158 <p> 159 There are some situations which cannot be handled while a VM 160 is running, and you will get an appropriate message that you 161 need to perform this snapshot deletion when the VM is shut 162 down. 163 </p> 125 <p>There are some situations which cannot be handled while a VM is running, and you will get an 126 appropriate message that you need to perform this snapshot deletion when the VM is shut down. </p> 164 127 </li> 165 128 </ol>
Note:
See TracChangeset
for help on using the changeset viewer.
