Phase2 - Required migration for Veeam Cloud Connect Backup (VCC-B) - More than thirty (30) days retention scenario

TABLE OF CONTENTS

• Description
• Requirements
• Important Notes
• Procedure
  • Rescan the Service Provider
  • Map the newly discovered orphaned backup chain(s) to your old job(s)
  • Delete the old backup chain from your old Cloud repository
• Next steps (Second part) 
  • Rescan the Service Provider
  • Remove the missing Cloud repository from Veeam’s inventory
  • Rescan the Service Provider once more

Description

Here are steps to be completed to map the original backup chain. At this point, your old backup chain has been migrated to your new cloud repository.

Requirements

• This procedure only applies for the scenario with more than thirty (30) days retention
    
• Only complete the following steps once you have received the second email from Sherweb to map your old Backup chain that was moved to your new Cloud repository.

Important Notes

For customers with multiple affected VCC-B tenants for this migration, this procedure must be completed for each tenant.

Procedure

Rescan the Service Provider

• In your Veeam Backup & Replication (VBR) server, navigate to the Backup Infrastructure section and click on Service Providers.
  
  
• Locate your Veeam Service Provider (VSP) pointing to our Cloud infrastructure. If you have multiple VSP, ours can easily be identified by its Name. It will either be:
  • vccan01.yourcloudservers.com
  • gw.ca.vspc-cloud.com
    
    
    
    
    
• Right-click on the VSP and select Rescan.
  
  
  
  
  
• Once completed, navigate to Home. Under the Backup section, you will see a new backup chain under “Cloud (Orphaned)”. For each job(s), you will have 3 backup chains.
  
  Note: Only the backup(s) with a retention level of more than thirty (30) days have been moved. If you have backup jobs with thirthy (30) days or less of retention level, it will be your responsibility to delete those once the retention is reached.
  • The backup chain for the new job targeted at your new Cloud repository
  • Two backup chains for the old job now targeting the old and new Cloud repositories
    
     

Map the newly discovered orphaned backup chain(s) to your old job(s)

• Navigate to the Jobs section and locate the old job. Right-click and select Edit.
  
  
  
  
  
• In the Storage section of the job configuration, change the Backup repository target to point at your new Cloud repository. Once the new repository selected, click on Map backup.
  
  
  
  
  
• Select the backup chain associated to the "_old" job and press OK.
  
  
  
  
  
• Then complete the job edit process.
  
  
• You will now notice, both old and new jobs are targeted at your new Cloud repository, and are both accessible for restore operations.
  
  
  
  
  
• Confirm you can browse and restore from the old backup on the new cloud repository
  
  

Delete the old backup chain from your old Cloud repository

• You will now notice that the orphaned backup chain now resides on your old backup repository.
  
  
  
  
  
• Right-click on the job name and select Delete from disk.
  
  
  
  
  Note: Only the backup(s) with a retention level of more than thirty (30) days have been moved. If you have backup jobs with thirty (30) days or less of retention level, it will be your responsibility to delete those once the retention is reached.
  
  
• Let us know once you have completed this phase 2 (first part) so we can remove your old Cloud repository from your VCC-B setup and give you the green light for next steps (second part of phase 2).

Next steps (Second part) 

Here are next steps to be completed once you have let us know your old backup chain was mapped successfully and any old chain deleted.

As a requirement for next steps (second part of the phase 2), this implies you have received a third email form us mentioning the instructions given below.

Rescan the Service Provider

• In your Veeam Backup & Replication (VBR) server, navigate to the Backup Infrastructure section and click on Service Providers.
  
  
• Locate your Veeam Service Provider (VSP) pointing to our Cloud infrastructure. If you have multiple VSP, ours can easily be identified by its Name. It will either be:
  • vccan01.yourcloudservers.com
  • gw.ca.vspc-cloud.com
    
    

• Right-click on the VSP and select Rescan.
  
  

• This process will fail with an error message saying it cannot sync a Cloud repository.
  This is normal since we removed your old Cloud repository from you tenant’s config in the backend.
  
  

Remove the missing Cloud repository from Veeam’s inventory

• In your Veeam Backup & Replication (VBR) server, navigate to the Backup Infrastructure, under Backup Repositories there will be a sub item called “Unavailable”, click on it.
  
  
• Locate your old Cloud repository showing unavailable, right-click on it and select Remove.
  
  

Rescan the Service Provider once more

• Follow the step above another time to rescan the service provider