VCSP/MSP Managed Recovery

Depending on your Cloud Connect Architecture, choose the correct procedures to recover your tenant’s information.

• Windows Based Repository
• Linux Based Repository
• SAN/LUN Repository
• Object Storage Repository
• Cloud Gateway/Gateway Pool Recovery

Windows Based Repository

1. Determine Windows Folder Location for Tenants data

2. Verify network connectivity from created Tenant Backup server under Basic Concept Step 4 to Windows Repository server

3. Add an SMB share based (can use Administrative Share) Repository to Tenant Backup Server This will prevent any issues with different versions/patch levels between VCSP VCC Veeam Backup server and Tenant Veeam Backup server and not push backup components to Repository Server.

   • Be sure to limit access to just the Tenant Folder location!

   • When adding, check the box to Import existing backups

4. Restore Tenant Configuration File if available
5. Perform Instant Recovery or Full Recovery into dedicated Tenant recovery environment
6. Present environment to Tenant thru VPN/MPLS/Portal access
   DO NOT WRITE ANY BACKUPS INTO REPOSITORY!

• DR Test – environment can be destroyed

• DR Event – VCSP should create another repository to write backups to during DR event

Linux Based Repository

1. Determine Linux Folder Location for Tenants data
2. Verify network connectivity from created Tenant Backup server under Basic Concept Step 4 to Linux Repository server

3. Add an NFS based Repository to Tenant Backup Server This will prevent any issues with different versions/patch levels between VCSP VCC Veeam Backup server and Tenant Veeam Backup server and not push backup components to Repository Server.

   • Be sure to limit access to just the Tenant Folder location!

   • When adding, check the box to Import existing backups

4. Restore Tenant Configuration File if available
5. Perform Instant Recovery or Full Recovery into dedicated Tenant recovery environment
6. Present environment to Tenant thru VPN/MPLS/Portal access
   DO NOT WRITE ANY BACKUPS INTO REPOSITORY!

• DR Test – environment can be destroyed

• DR Event – VCSP should create another repository to write backups to during DR event

SAN/LUN Repository

1. Determine SAN/LUN volume on storage device for Tenants data

   • Is SAN presented as LUN to Windows or Linux? Or SMB/NFS share?

   • This will determine how to present the snapshot to the Tenant Veeam Backup Server

2. Create a snapshot of volume

3. Present storage snapshot as storage for repository

   • Windows mounted LUN – would recommend a new Windows server build with attached snapshot LUN

   • Linux mounted LUN – would recommend a new Linux server build with attached snapshot LUN

   • SMB or NFS – create new share to the snapshot location

4. Verify network connectivity from created Tenant Backup server under Basic Concept Step 4 to storage snapshot location presented

5. Add storage snapshot presented as Repository to Tenant Backup Server

   • Be sure to limit access to just the Tenant Folder location!

   • When adding, check the box to Import existing backups

6. Restore Tenant Configuration File if available
7. Perform Instant Recovery or Full Recovery into dedicated Tenant recovery environment
8. Present environment to Tenant thru VPN/MPLS/Portal access
   DO NOT WRITE ANY BACKUPS INTO REPOSITORY!

• DR Test – environment can be destroyed

• DR Event – VCSP should create another repository to write backups to during DR event

Object Storage Repository

1. Determine Object Bucket/Folder Location for Tenants data
2. Verify network connectivity from created Tenant Backup server under Basic Concept Step 4 to Object Storage location

3. Add the Object location as a Repository to Tenant Backup Server This will prevent any issues with different versions/patch levels between VCSP VCC Veeam Backup server and Tenant Veeam Backup server and not push backup components to Repository Server.

   • Be sure to limit access to just the Tenant Folder location!

   • When adding, check the box to Import existing backups

4. Restore Tenant Configuration File if available
5. Perform Instant Recovery or Full Recovery into dedicated Tenant recovery environment
6. Present environment to Tenant thru VPN/MPLS/Portal access
   DO NOT WRITE ANY BACKUPS INTO REPOSITORY!

• DR Test – environment can be destroyed

• DR Event – VCSP should create another repository to write backups to during DR event

Cloud Gateway/Gateway Pool Recovery

1. Create Cloud Gateway pool based on local LAN inside VCSP Environment
2. Pause Tenant jobs to Cloud Connect
3. Switch Tenant Cloud Connect access to use the LAN Cloud Gateway Pool
4. Verify network connectivity from created Tenant Backup server under Basic Step 4 to Object Storage location

5. Add the Object location as a Repository to Tenant Backup Server This will prevent any issues with different versions/patch levels between VCSP VCC Veeam Backup server and Tenant Veeam Backup server and not push backup components to Repository Server.

   • Be sure to limit access to just the Tenant Folder location!

   • When adding, check the box to Import existing backups

6. Restore Tenant Configuration File if available
7. Perform Instant Recovery or Full Recovery into dedicated Tenant recovery environment
8. Present environment to Tenant thru VPN/MPLS/Portal access
   DO NOT WRITE ANY BACKUPS INTO REPOSITORY!

• DR Test – environment can be destroyed

• DR Event – VCSP should create another repository to write backups to during DR event