55 lines
2.4 KiB
Markdown
55 lines
2.4 KiB
Markdown
|
---
|
||
|
|
title: "Cluster migration"
|
||
|
|
layout: docs
|
||
|
|
---
|
||
|
|
||
|
|
*Using Backups and Restores*
|
||
|
|
|
||
|
Velero can help you port your resources from one cluster to another, as long as you point each Velero instance to the same cloud object storage location. In this scenario, we are also assuming that your clusters are hosted by the same cloud provider. **Note that Velero does not natively support the migration of persistent volumes snapshots across cloud providers.** If you would like to migrate volume data between cloud platforms, please enable [restic][2], which will backup volume contents at the filesystem level.
|
||
|
|
|
||
|
|
1. *(Cluster 1)* Assuming you haven't already been checkpointing your data with the Velero `schedule` operation, you need to first back up your entire cluster (replacing `<BACKUP-NAME>` as desired):
|
||
|
|
|
||
|
|
```
|
||
|
|
velero backup create <BACKUP-NAME>
|
||
|
|
```
|
||
|
|
||
|
The default backup retention period, expressed as TTL (time to live), is 30 days (720 hours); you can use the `--ttl <DURATION>` flag to change this as necessary. See [how velero works][1] for more information about backup expiry.
|
||
|
|
|
||
|
1. *(Cluster 2)* Configure `BackupStorageLocations` and `VolumeSnapshotLocations`, pointing to the locations used by *Cluster 1*, using `velero backup-location create` and `velero snapshot-location create`. Make sure to configure the `BackupStorageLocations` as read-only
|
||
|
|
by using the `--access-mode=ReadOnly` flag for `velero backup-location create`.
|
||
|
|
|
||
|
|
1. *(Cluster 2)* Make sure that the Velero Backup object is created. Velero resources are synchronized with the backup files in cloud storage.
|
||
|
|
|
||
|
|
```
|
||
|
|
velero backup describe <BACKUP-NAME>
|
||
|
|
```
|
||
|
|
|
||
|
|
**Note:** The default sync interval is 1 minute, so make sure to wait before checking. You can configure this interval with the `--backup-sync-period` flag to the Velero server.
|
||
|
|
|
||
|
|
1. *(Cluster 2)* Once you have confirmed that the right Backup (`<BACKUP-NAME>`) is now present, you can restore everything with:
|
||
|
|
|
||
|
|
```
|
||
|
|
velero restore create --from-backup <BACKUP-NAME>
|
||
|
|
```
|
||
|
|
|
||
|
|
## Verify both clusters
|
||
|
|
|
||
|
|
Check that the second cluster is behaving as expected:
|
||
|
|
|
||
|
|
1. *(Cluster 2)* Run:
|
||
|
|
|
||
|
|
```
|
||
|
|
velero restore get
|
||
|
|
```
|
||
|
|
|
||
|
|
1. Then run:
|
||
|
|
|
||
|
|
```
|
||
|
|
velero restore describe <RESTORE-NAME-FROM-GET-COMMAND>
|
||
|
|
```
|
||
|
|
|
||
|
|
If you encounter issues, make sure that Velero is running in the same namespace in both clusters.
|
||
|
|
|
||
|
|
[1]: how-velero-works.md#set-a-backup-to-expire
|
||
|
|
[2]: restic.md
|