All checks were successful
GitOps Automatic Deployment / GitOps Automatic Deployment (push) Successful in 8s
11 lines
938 B
Markdown
11 lines
938 B
Markdown
## Purpose
|
|
If you find that you need to migrate cloud backups that are being sent to a server running the Veeam VSCP due to issues like exhausted storage space on existing repositories.
|
|
|
|
### Migrate Backup Repository Data
|
|
- Log into VSPC website and disable all associated jobs that need to be migrated
|
|
- Log into the endpoint (or veeam backup proxy running at the client location, if there is one) and disable the associated job that we need to migrate the data for.
|
|
- Navigate to the directory structure where the backup is located on-disk, such as `E:\Backups\clientname` and move it to the destination backup repository, such as `F:\Backups\clientname`
|
|
- Log back into Veeam Backup & Replication Console and re-scan the new repositories
|
|
|
|
### Move Backup Job Location in VSPC Portal
|
|
At this point, we need to migrate point the backup job(s) that were affected to the new location. This is a job-level change, not company-level change. |