AWS CLI for cloud-to-cloud migration scenarios
Only backups from destinations that utilize our jetindex engine can be migrated to JetBackup Storage buckets. Backups from Legacy Destinations (SSH (Legacy), Local (Legacy)) can NOT be migrated because they use a different storage format.
To begin, you will need to install the AWS CLI and configure it using your AWS Access Key and Secret Key. You can follow the instructions located here for guidance.
Once you have configured the AWS CLI, you must create an additional profile specifically for your JetBackup Storage account. You can find detailed instructions on how to do this here.
- Transfer all backup job files from your source AWS bucket to a local directory by running the following command:
aws s3 --profile=your_source_cloud_profile cp s3://<source_bucket>/ <local_directory> --recursive --exclude "*" --include "jetbackup_*_*_*"
- To transfer all of your files from a local directory to your new target bucket, run the following command:
aws s3 --profile=jetbackup --endpoint-url=https://eu-central-2.storage.jetbackup.com cp <local_directory>/ s3://<destination_bucket>/ --recursive --exclude "*" --include "jetbackup_*_*_*"
- Lastly, after migrating your backups to your JetBackup Storage bucket, initiate a reindex for the JetBackup Storage destination to sync the snapshots and ensure that they are visible in JetBackup.
jetbackup5api -F reindexDestination -D "_id={$DESTINATION_ID}"
It is recommended to keep your original destination you migrated from disabled to prevent potential backup conflicts.
Feedback
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.