Doc updates where volume flags are concered

Signed-off-by: Justin Nauman <justin.r.nauman@gmail.com>
This commit is contained in:
Justin Nauman
2017-08-16 23:13:38 -05:00
parent d39d6f96fa
commit 618de63d23
2 changed files with 4 additions and 4 deletions

View File

@@ -144,7 +144,7 @@ As mentioned before, Ark runs in two different modes:
* **Ark server**: Runs all of the Ark controllers. Each controller watches its respective custom resource for API operations, performs validation, and handles the majority of the cloud API logic (e.g. interfacing with object storage and persistent volumes).
Looking at a specific example--an `ark backup create test-backup --snapshot-volumes` command triggers the following operations:
Looking at a specific example--an `ark backup create test-backup` command triggers the following operations:
![19]
@@ -156,7 +156,7 @@ Looking at a specific example--an `ark backup create test-backup --snapshot-volu
4. Once the data has been aggregated, the `BackupController` makes a call to the object storage service (e.g. Amazon S3) to upload the backup file.
5. If the `--snapshot-volumes` flag is specified, Ark also makes disk snapshots of any persistent volumes, using the appropriate cloud service API.
5. By default, Ark also makes disk snapshots of any persistent volumes, using the appropriate cloud service API. (This can be disabled via the option `--snapshot-volumes=false`)
## Further documentation

View File

@@ -35,7 +35,7 @@ Heptio Ark can help you port your resources from one cluster to another, as long
1. *(Cluster 1)* Assuming you haven't already been checkpointing your data with the Ark `schedule` operation, you need to first back up your entire cluster (replacing `<BACKUP-NAME>` as desired):
```
ark backup create <BACKUP-NAME> --snapshot-volumes
ark backup create <BACKUP-NAME>
```
The default TTL is 24 hours; you can use the `--ttl` flag to change this as necessary.
@@ -45,7 +45,7 @@ Heptio Ark can help you port your resources from one cluster to another, as long
4. *(Cluster 2)* Once you have confirmed that the right Backup (`<BACKUP-NAME>`) is now present, you can restore everything with:
```
ark restore create <BACKUP-NAME> --restore-volumes
ark restore create <BACKUP-NAME>
```
[0]: #disaster-recovery