From cde208f687e43e4c7d503a0f2767ff16a5d5278d Mon Sep 17 00:00:00 2001 From: Nicole Rappe Date: Fri, 26 Sep 2025 16:56:08 -0600 Subject: [PATCH] Update Workflows/Veeam Backup & Replication/Migrating VSPC Backup Repositories.md --- ...epositories.md => Migrating VSPC Backup Repositories.md} | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) rename Workflows/Veeam Backup & Replication/{Migrating Veeam Service Provider Console Backup Repositories.md => Migrating VSPC Backup Repositories.md} (55%) diff --git a/Workflows/Veeam Backup & Replication/Migrating Veeam Service Provider Console Backup Repositories.md b/Workflows/Veeam Backup & Replication/Migrating VSPC Backup Repositories.md similarity index 55% rename from Workflows/Veeam Backup & Replication/Migrating Veeam Service Provider Console Backup Repositories.md rename to Workflows/Veeam Backup & Replication/Migrating VSPC Backup Repositories.md index eca1941..3bc74c4 100644 --- a/Workflows/Veeam Backup & Replication/Migrating Veeam Service Provider Console Backup Repositories.md +++ b/Workflows/Veeam Backup & Replication/Migrating VSPC Backup Repositories.md @@ -2,7 +2,7 @@ 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