2015-10-08 03:03:13 +00:00
|
|
|
---
|
2016-01-19 18:08:53 +00:00
|
|
|
layout: "docs"
|
2015-10-08 03:03:13 +00:00
|
|
|
page_title: "vagrant snapshot - Command-Line Interface"
|
|
|
|
sidebar_current: "cli-snapshot"
|
2016-01-19 18:08:53 +00:00
|
|
|
description: |-
|
|
|
|
The "vagrant snapshot" command is used to manage snapshots of the guest
|
|
|
|
machine.
|
2015-10-08 03:03:13 +00:00
|
|
|
---
|
|
|
|
|
|
|
|
# Snapshot
|
|
|
|
|
|
|
|
**Command: `vagrant snapshot`**
|
|
|
|
|
|
|
|
This is the command used to manage snapshots with the guest machine.
|
|
|
|
Snapshots record a point-in-time state of a guest machine. You can then
|
|
|
|
quickly restore to this environment. This lets you experiment and try things
|
|
|
|
and quickly restore back to a previous state.
|
|
|
|
|
2016-01-19 18:08:53 +00:00
|
|
|
Snapshotting is not supported by every provider. If it is not supported,
|
2015-10-08 03:03:13 +00:00
|
|
|
Vagrant will give you an error message.
|
|
|
|
|
|
|
|
The main functionality of this command is exposed via even more subcommands:
|
|
|
|
|
|
|
|
* `push`
|
|
|
|
* `pop`
|
|
|
|
* `save`
|
|
|
|
* `restore`
|
|
|
|
* `list`
|
|
|
|
* `delete`
|
|
|
|
|
|
|
|
# Snapshot Push
|
|
|
|
|
|
|
|
**Command: `vagrant snapshot push`**
|
|
|
|
|
|
|
|
This takes a snapshot and pushes it onto the snapshot stack.
|
|
|
|
|
2016-01-19 18:08:53 +00:00
|
|
|
This is a shorthand for `vagrant snapshot save` where you do not need
|
2015-10-08 03:03:13 +00:00
|
|
|
to specify a name. When you call the inverse `vagrant snapshot pop`, it will
|
|
|
|
restore the pushed state.
|
|
|
|
|
|
|
|
~> **Warning:** If you are using `push` and `pop`, avoid using `save`
|
|
|
|
and `restore` which are unsafe to mix.
|
|
|
|
|
|
|
|
# Snapshot Pop
|
|
|
|
|
|
|
|
**Command: `vagrant snapshot pop`**
|
|
|
|
|
|
|
|
This command is the inverse of `vagrant snapshot push`: it will restore
|
|
|
|
the pushed state.
|
|
|
|
|
2016-03-06 16:14:14 +00:00
|
|
|
## Options
|
|
|
|
|
|
|
|
* `--[no-]provision` - Force the provisioners to run (or prevent them
|
|
|
|
from doing so).
|
|
|
|
|
|
|
|
* `--no-delete` - Prevents deletion of the snapshot after restoring
|
|
|
|
(so that you can restore to the same point again later).
|
|
|
|
|
2015-10-08 03:03:13 +00:00
|
|
|
# Snapshot Save
|
|
|
|
|
|
|
|
**Command: `vagrant snapshot save NAME`**
|
|
|
|
|
|
|
|
This command saves a new named snapshot. If this command is used, the
|
|
|
|
`push` and `pop` subcommands cannot be safely used.
|
|
|
|
|
|
|
|
# Snapshot Restore
|
|
|
|
|
|
|
|
**Command: `vagrant snapshot restore NAME`**
|
|
|
|
|
|
|
|
This command restores the named snapshot.
|
|
|
|
|
2016-03-06 16:14:14 +00:00
|
|
|
* `--[no-]provision` - Force the provisioners to run (or prevent them
|
|
|
|
from doing so).
|
|
|
|
|
2015-10-08 03:03:13 +00:00
|
|
|
# Snapshot List
|
|
|
|
|
|
|
|
**Command: `vagrant snapshot list`**
|
|
|
|
|
|
|
|
This command will list all the snapshots taken.
|
|
|
|
|
|
|
|
# Snapshot Delete
|
|
|
|
|
|
|
|
**Command: `vagrant snapshot delete NAME`**
|
|
|
|
|
|
|
|
This command will delete the named snapshot.
|
|
|
|
|
|
|
|
Some providers require all "child" snapshots to be deleted first. Vagrant
|
2016-01-19 18:08:53 +00:00
|
|
|
itself does not track what these children are. If this is the case (such
|
2015-10-08 03:03:13 +00:00
|
|
|
as with VirtualBox), then you must be sure to delete the snapshots in the
|
|
|
|
reverse order they were taken.
|
|
|
|
|
|
|
|
This command is typically _much faster_ if the machine is halted prior to
|
2016-01-19 18:08:53 +00:00
|
|
|
snapshotting. If this is not an option, or is not ideal, then the deletion
|
2015-10-08 03:03:13 +00:00
|
|
|
can also be done online with most providers.
|