Snapshots - Revision history

Favyen Bastani at 05:34, 9 January 2016

2016-01-09T05:34:30Z

Favyen Bastani at 05:34, 9 January 2016

2016-01-09T05:34:19Z

Favyen Bastani at 05:33, 9 January 2016

2016-01-09T05:33:44Z

Favyen Bastani at 22:57, 5 January 2016

2016-01-05T22:57:23Z

Favyen Bastani: /* Provisioning from the snapshot */

2015-10-25T04:18:24Z

‎Provisioning from the snapshot

Favyen Bastani: /* Provisioning from the snapshot */

2015-06-01T15:51:15Z

‎Provisioning from the snapshot

Favyen Bastani: /* Creating a snapshot */

2015-06-01T15:45:32Z

‎Creating a snapshot

Favyen Bastani at 18:38, 20 May 2015

2015-05-20T18:38:59Z

Favyen Bastani: /* Replicating a snapshot (or other image) between regions */

2015-04-30T01:56:01Z

‎Replicating a snapshot (or other image) between regions

Favyen Bastani at 01:55, 30 April 2015

2015-04-30T01:55:10Z

@@ Line 1: / Line 1: @@
 Snapshots allow you to save the state of a virtual machine for backup or templating purposes. If you snapshot while the VM is online, a live snapshot will be performed; live snapshots produce a consistent disk state without the need for downtime by taking advantage of qemu's live block commit functionality. Cold snapshots can also be performed by shutting off the VM before taking the snapshot; cold snapshots provide stronger guarantees on data consistency, in case you have databases or other software that don't synchronously commit data (with live snapshots, written data that is still in-memory in the OS buffer will not be captured).
-Snapshots are billed hourly for storage space only, at $0.03 per GB per month (the first 20 GB of usage is currently free, but this is subject to change).
+Snapshots are billed hourly for storage space only, at $0.03 per GB per month (the first 20 GB of usage is free).
 == Creating a snapshot ==

← Older revision		Revision as of 05:34, 9 January 2016
Line 1:		Line 1:
−	Snapshots allow you to save the state of a virtual machine for backup or templating purposes. If you snapshot while the VM is online, a live snapshot will be performed; live snapshots produce a consistent disk state without the need for downtime by taking advantage of qemu's live block commit functionality. Cold snapshots can also be performed by shutting off the VM before taking the snapshot; cold snapshots ~~are useful to ensure~~ data consistency, in case you have databases or other software that don't synchronously commit data (with live snapshots, written data that is still in-memory in the OS buffer will not be captured).	+	Snapshots allow you to save the state of a virtual machine for backup or templating purposes. If you snapshot while the VM is online, a live snapshot will be performed; live snapshots produce a consistent disk state without the need for downtime by taking advantage of qemu's live block commit functionality. Cold snapshots can also be performed by shutting off the VM before taking the snapshot; cold snapshots provide stronger guarantees on data consistency, in case you have databases or other software that don't synchronously commit data (with live snapshots, written data that is still in-memory in the OS buffer will not be captured).

	Snapshots are billed hourly for storage space only, at $0.03 per GB per month (the first 20 GB of usage is currently free, but this is subject to change).		Snapshots are billed hourly for storage space only, at $0.03 per GB per month (the first 20 GB of usage is currently free, but this is subject to change).

@@ Line 1: / Line 1: @@
-Snapshots allow you to save the state of a virtual machine for backup or templating purposes. For VMs installed from templates, live snapshots can be performed where the VM does not have to be rebooted; on operating installs from ISO, only cold snapshots are supported (snapshot after VM is turned offline).
+Snapshots allow you to save the state of a virtual machine for backup or templating purposes. If you snapshot while the VM is online, a live snapshot will be performed; live snapshots produce a consistent disk state without the need for downtime by taking advantage of qemu's live block commit functionality. Cold snapshots can also be performed by shutting off the VM before taking the snapshot; cold snapshots are useful to ensure data consistency, in case you have databases or other software that don't synchronously commit data (with live snapshots, written data that is still in-memory in the OS buffer will not be captured).
 Snapshots are billed hourly for storage space only, at $0.03 per GB per month (the first 20 GB of usage is currently free, but this is subject to change).
@@ Line 7: / Line 7: @@
 Creating a snapshot in Luna Node Dynamic is easy. Simply go to the [https://dynamic.lunanode.com/panel/vms Virtual Machines] sidebar entry, select your VM, and enter a snapshot label in the snapshot box. You may want to run sync before snapshotting.
-If you are snapshotting a VM that was installed from an ISO image, you will need to shut down the VM before snapshotting. You will also need to have the VM adjusted so that it is set to boot to the first disk and not the CD-ROM (this is accomplished by selecting swap boot order).
+If you are snapshotting a VM that was installed from an ISO image, the VM needs to be adjusted so that it is set to boot to the first disk and not the CD-ROM (this is accomplished by pressing the swap boot order button).
 Note: templates come with software called cloud-init installed that sets up SSH configuration, network interface settings, user accounts, hostname, partitions, and various other settings on the first boot. If you want a pure clone the VM, then you can remove cloud-init before taking the snapshot (apt-get/yum remove cloud-init); however, you will generally need to reconfigure the network settings on virtual machines booted from such a snapshot. See the next section for details on how to use a cloud-config startup script to change the password to something you want.

@@ Line 5: / Line 5: @@
 == Creating a snapshot ==
-Creating a snapshot in Luna Node Dynamic is easy. Simply go to the [https://dynamic.lunanode.com/panel/vms.php Virtual Machines] sidebar entry, select your VM, and enter a snapshot label in the snapshot box. You may want to run sync before snapshotting.
+Creating a snapshot in Luna Node Dynamic is easy. Simply go to the [https://dynamic.lunanode.com/panel/vms Virtual Machines] sidebar entry, select your VM, and enter a snapshot label in the snapshot box. You may want to run sync before snapshotting.
 If you are snapshotting a VM that was installed from an ISO image, you will need to shut down the VM before snapshotting. You will also need to have the VM adjusted so that it is set to boot to the first disk and not the CD-ROM (this is accomplished by selecting swap boot order).

@@ Line 17: / Line 17: @@
 If your VM that you used for the snapshot does not have cloud-init installed, you will most likely need to reset network configuration; this can be done over VNC.
-If you did remove cloud-init, the password of the default administrative user will be reset, and password authentication over SSH disabled. If you are using SSH keys, this will not be a problem -- simply select the SSH key when provisioning the new VM, and this will be forwarded to cloud-init and included in the booted VM. Otherwise, you should include a startup script to set a password and avoid disabling password authentication:
+If you snapshotted a VM that was installed from a template, and did not remove cloud-init, then either select an SSH key or the "Set password via cloud-init" option when provisioning the new VM.
-−
- <nowiki>#cloud-config
-password: [some password]
-chpasswd: { expire: False }
-ssh_pwauth: True</nowiki>
 == Replicating images between regions ==
 Images are stored separately on each region. However, you can replicate a snapshot to another region by selecting the image from the Images sidebar tab, and then scrolling down to the image replication tool. Keep in mind that you will be billed for the storage in both regions (although you do have 20 GB free storage per region).

@@ Line 13: / Line 13: @@
 == Provisioning from the snapshot ==
-You can provision new instances from the snapshot, or re-image existing instances using the snapshot.
+You can provision new instances from the snapshot, or re-image existing instances using the snapshot, as you would with a normal template image.
 == Replicating images between regions ==
 Images are stored separately on each region. However, you can replicate a snapshot to another region by selecting the image from the Images sidebar tab, and then scrolling down to the image replication tool. Keep in mind that you will be billed for the storage in both regions (although you do have 20 GB free storage per region).

← Older revision		Revision as of 01:55, 30 April 2015
Line 14:		Line 14:

	You can provision new instances from the snapshot, or re-image existing instances using the snapshot.		You can provision new instances from the snapshot, or re-image existing instances using the snapshot.
		+
		+	== Replicating a snapshot (or other image) between regions ==
		+
		+	Images are stored separately on each region. However, you can replicate a snapshot to another region by selecting the image from the Images sidebar tab, and then scrolling down to the image replication tool. Keep in mind that you will be billed for the storage in both regions (although you do have 20 GB free storage per region).