Challenge

Cause

Solution

• Account Name
• Product Name and Edition
• Product Version
• Licensing Terms
• License Administrator
• They must all be Active on Support.

More Information

Challenge

Solution

If you are using Cloud Connect, please consult with your provider to ensure you are on the same, or earlier, version than the provider. A tenant cannot be on a newer version than the provider.

Please see the supported versions and system requirements page in the User Guide for the most up-to-date information prior to upgrading. Links included under More Information at the bottom of this article.

Please refer to the following links for steps and more information on upgrading to 9.0, 9.5, or 10.0:

• Upgrade to 9.0: https://helpcenter.veeam.com/backup/vsphere/upgrade_vbr.html
• Upgrade to 9.5: https://helpcenter.veeam.com/docs/backup/vsphere/upgrade_vbr.html?ver=95
• Upgrade to 10.0: https://helpcenter.veeam.com/docs/backup/vsphere/upgrade_vbr.html?ver=100

The latest Veeam updates:
https://www.veeam.com/updates.html

Old versions of Veeam Backup & Replication can be found here:
https://www.veeam.com/older-versions-download.html

7.x
7.x -> 7.0.0.871 -> 9.0.0.902 -> 9.5.0.1922 -> 10.0.0.4461

1. Install Veeam Backup & Replication 7.0 Patch 4 (7.0.0.871)
2. Create a manual configuration Backup
3. Install Veeam Backup & Replication 9.0.0.902
4. Create a manual configuration Backup
5. Install Veeam Backup & Replication 9.5 Update 3 9.5.0.1922
6. Create a manual configuration Backup
7. Install Veeam Backup & Replication v10 

Refer to above links for steps to upgrade.

8.x
8.x -> 8.0.0.2084 -> 9.0.0.902 -> 9.5.0.1922 -> 10.0.0.4461

1. Veeam Backup & Replication 8.0 Update 3: (8.0.0.2084)
2. Create a manual configuration Backup
3. Install Veeam Backup & Replication 9.0.0.902
4. Create a manual configuration Backup
5. Install Veeam Backup & Replication 9.5 Update 3 9.5.0.1922
6. Create a manual configuration Backup
7. Install Veeam Backup & Replication v10 

Refer to above links for steps to upgrade.

9.0.x
9.0.x > 9.5.0.1922 -> 10.0.0.4461

1. Install Veeam Backup & Replication 9.5 Update 3 9.5.0.1922
2. Create a manual configuration Backup
3. Install Veeam Backup & Replication v10 

Refer to the above links for steps to upgrade.

 

More Information

Build numbers and version of Veeam Backup & Replication

Veeam Backup & Replication support for VMware vSphere

Challenge

Product Information:

Company name: Panzura, Inc.
Product Family: Freedom NAS
Status: Veeam Ready - Repository*
Classification Description: Verified backup storage that supports all Veeam backup and restore features.

Solution

Product Details:

Model number: 5500
Storage Category: Cloud-out NAS Storage
Drive quantity, size, type: 12 - 800GB, SAS SSD
Storage configuration: RAID50 via automatic software configuration
Firmware version: 7.0.2.5
Connection protocol and speed: SMB, 2 x 10GbE
Additional support: All models and configurations of Freedom NAS with specifications equivalent or greater than the above

Panzura FreedomTM is an intelligent hybrid cloud storage solution underpinned by Panzura CloudFS. Panzura CloudFS is a scale-out, distributed file system purpose-built for the cloud. Programmatically accessible through REST APIs, it utilizes high performance flash in the data center, and integrates the cloud for economics, scalability, and durability. Unlike NAS, it scales globally across multiple sites and multiple clouds.

Veeam testing configuration:

Veeam Build Number: 9.5.0.1536

Job Settings:

Repository Settings:

Vendor recommended configuration:

Hardware Settings: The default configuration enables auto-tuning for all Panzura settings, which work well with the Veeam application. The caching policy should be set to pinned (as opposed to autotune) to ensure the administrator controls which backup sets are available locally. All Veeam backup data must be pinned locally to ensure fast restores and effective data operations within Veeam, without cloud reads.

More Information

Challenge

Cause

Solution

Database migration (permanent solution)

The best way to resolve the issue would be to move Veeam ONE database to a Standard or Enterprise edition of MS SQL Server. The procedure for configuring Veeam ONE to use a new SQL Server connection is described in the following KB article: http://www.veeam.com/kb1599

Purging old data (temporary workaround)

You can also address the issue by purging old performance data as described below.

You can delete past performance data via a custom SQL script that should be run against Veeam ONE database. Follow these steps to reduce the database size:

• make sure to properly backup Veeam ONE database;
• be aware that this change will touch all of Veeam ONE components: for example in Veeam ONE Reporter you will not be able to build reports that rely on the data that you delete with the script presented below;
• keep in mind that all graphs in Veeam ONE Monitor that rely on the deleted data that will be unavailable;
• unless specifically instructed by Veeam Support, do not modify the SQL statement and do not execute it against other database tables. If the aforementioned workaround does not help to reduce the database size, please contact Veeam Support for further assistance.

CHECKPOINT
DECLARE @dt DATETIME
SET @dt = CONVERT(DATETIME, '2018-01-25 00:00:00.001' ,120)
 
WHILE EXISTS (SELECT * FROM [monitor].[perfsamplelow] WITH(NOLOCK) WHERE [timestamp] < @dt)
BEGIN
    BEGIN TRAN
    DELETE TOP (50000) FROM [monitor].[perfsamplelow] WHERE [timestamp] < @dt
    COMMIT TRAN
    CHECKPOINT
END​
DBCC shrinkfile (N'VeeamOne', 1)​

   2017-01-25 00:00:00.001 - the point in time before which the historical performance data will be purged. Change the date accordingly.
   (year)-(month)-(date)

4. Execute the statement against Veeam ONE database.
NOTE: this operation can cause significant workload on the database and growth of the database transaction log. Make sure you do not have mission-critical databases on this server.
5. Start Veeam ONE Monitor and Reporter services on the Veeam ONE server.

More Information

Challenge

Cause

1. Open the Veeam Backup & Replication console.
2. In the main menu, click Help and select About.

Solution

• Added support for IntelliFlash OS version 3.10.1.x or later.

More Information

Challenge

Cause

Solution

Database migration (permanent solution)

The best way to resolve the issue would be to move Veeam ONE database to a Standard or Enterprise edition of MS SQL Server. The procedure for configuring Veeam ONE to use a new SQL Server connection is described in the following KB article: http://www.veeam.com/kb1599

Purging old data (temporary workaround)

You can also address the issue by purging old performance data as described below.

You can delete past performance data via a custom SQL script that should be run against Veeam ONE database. Follow these steps to reduce the database size:

• make sure to properly backup Veeam ONE database;
• be aware that this change will touch all of Veeam ONE components: for example in Veeam ONE Reporter you will not be able to build reports that rely on the data that you delete with the script presented below;
• keep in mind that all graphs in Veeam ONE Monitor that rely on the deleted data that will be unavailable;
• unless specifically instructed by Veeam Support, do not modify the SQL statement and do not execute it against other database tables. If the aforementioned workaround does not help to reduce the database size, please contact Veeam Support for further assistance.

CHECKPOINT
DECLARE @dt DATETIME
SET @dt = CONVERT(DATETIME, '2018-01-25 00:00:00.001' ,120)
 
WHILE EXISTS (SELECT * FROM [monitor].[perfsamplelow] WITH(NOLOCK) WHERE [timestamp] < @dt)
BEGIN
    BEGIN TRAN
    DELETE TOP (50000) FROM [monitor].[perfsamplelow] WHERE [timestamp] < @dt
    COMMIT TRAN
    CHECKPOINT
END​
DBCC shrinkfile (N'VeeamOne', 1)​

   2017-01-25 00:00:00.001 - the point in time before which the historical performance data will be purged. Change the date accordingly.
   (year)-(month)-(date)

4. Execute the statement against Veeam ONE database.
NOTE: this operation can cause significant workload on the database and growth of the database transaction log. Make sure you do not have mission-critical databases on this server.
5. Start Veeam ONE Monitor and Reporter services on the Veeam ONE server.

More Information

Challenge

Cause

• Optimized for Typical Deployment mode is recommended for small to medium environments up to 100 hosts and 1500 VMs. In this mode, Veeam ONE collects all inventory, configuration and performance metrics, and makes collected data available in dashboards, reports and alarms. This mode provides the greatest data granularity level, but results in a greater load on the Veeam ONE server and a larger size of Veeam ONE database.
• Optimized for Advanced Scalability Deployment mode is recommended for large environments with more than 100 hosts and 1500 VMs. In this mode, Veeam ONE collects all metrics required for alarms and reports. This mode provides a lesser data granularity level than the Typical Deployment mode, and results in a lower load on the Veeam ONE server and a smaller size of the Veeam ONE database.
• Backup Data Only mode is recommended for users who want to focus on Veeam Backup & Replication monitoring and reporting, and do not need a deep visibility of the virtual infrastructure. In this mode, Veeam ONE collects all inventory, configuration and performance metrics from Veeam Backup & Replication servers. It also collects inventory and configuration metrics from virtual infrastructure servers, but skips virtual infrastructure performance metrics. As a result, Veeam ONE dashboards, reports and alarms display backup-related data only; for VMware vSphere and Microsoft Hyper-V objects, performance data is not available. This mode results in the least possible size of the Veeam ONE database and the lowest load on the Veeam ONE server.

Solution

1. Open Veeam ONE Monitor.
2. On the toolbar, click Options and select Server Settings. Alternatively, you can press [CTRL+S] on the keyboard.
3. Open the Other Settings tab.
4. In the Support utility section, click Launch.
5. In the Veeam ONE Settings menu, select Scalability.
6. Choose the necessary data collection mode and click Save.
7. Restart Veeam ONE Monitor Server and Veeam ONE Reporter Server services.

More Information

Challenge

Cause

Solution

More Information

Challenge

If you are a Cloud Provider gathering logs from your infrastructure please see:  https://www.veeam.com/kb2096

This article covers how to properly compile your logs in Veeam Backup & Replication v8.x and newer, as well as what to include when submitting a Support case for technical assistance.
 

Solution

The following animation demonstrates how to compile logs in Veeam Backup & Replication.

1. To compile your logs via the log compilation wizard, click the Menu button in the top left-hand corner of the gui and go to Help -> Support Information in the Veeam Backup & Replication console. 
2. This wizard will allow you various methods to compile logging. For Backup, Replication, and other jobs, select “Export logs for this job.” If multiple jobs are affected, you can multiple-select. For problems with restore or replica failover, you should select “Export logs for these objects” and choose the  production VM  that was backed up or replicated. For issues with the GUI or problems that don’t fall into any of the above categories, select “Export all logs for selected components” and choose “This server.”
3. If possible, compile the logging for each job with issues for at least the last week.
4. You may save these logs to any location. Ensure that the location referenced has free space for compilation.
5. When selecting "Next", the wizard will notify of its progress in the compilation process. 
6. Please attach these to your case via the customer portal by clicking "Add logs" at https://my.veeam.com/#/my-cases 

If you would prefer to upload the logs via SFTP please notify Veeam Support and an engineer will provide SFTP credentials for the case.
To upload logs via SFTP please review this article: https://www.veeam.com/kb1661

More Information

Below are the relative log path lists for Veeam Backup & Replication. If there are difficulties compiling the logging requested via the wizard-based instructions above, please obtain the files from the appropriate directory below and provide Veeam Support a .zip file copy. 

• Windows 2003, XP – C:\Documents and Settings\All Users\Application Data\Veeam\Backup\
• Windows Vista, 7 - C:\Users\All Users\Veeam\Backup\
• Windows 2008/2008 R2/2012 - C:\ProgramData\Veeam\Backup\
• Linux - /var/log/VeeamBackup/

Typical log files requested for a manual log compilation will be:

• The task's folder located in the parent directory, zipped. This will contain all relevant job/task/agent data.

• All logs from the parent directory named svc.*.log, util.*.log, as well as the VeeamBackupManager.log and VeeamShell.log

Please note that the information provided to Veeam for purposes of customer support may be considered protected under certain data protection regulations and/or internal company policies. A list of potentially sensitive data types is available in the following KB article. The Support team may provide with a log scrubbing utility upon request. Veeam will only utilize this information for the specific purpose of providing customer support to you and will protect the information in accordance with its privacy policy. In any event, the information provided will be securely deleted after 45 inactive days as of the last upload to the SFTP. If you would like it deleted sooner, please express this request directly to your support contact once the issue has been resolved. For more information on how we process the collected data, please visit: https://vee.am/processing_of_personal_data

Challenge

Cause

Solution

More Information

Challenge

Product Information:

Company name: FAST LTA, AG
Product Family: Silent Brick System
Status: Veeam Ready - Repository
Classification Description: Verified backup storage that supports all Veeam backup and restore features.

Solution

Product Details:

Model number: FAST LTA - Silent Brick FLASH
Storage Category: Hybrid Storage
Drive quantity, size, type: 12 - SATA FLASH discs via SAS Bus
Storage configuration: SecureNAS - Triple Parity
Firmware version: 2.11
Connection protocol and speed: 10GbE
Additional support: All models and configurations of Silent Brick System with specifications equivalent or greater than the above.

General product family overview: Simplify your backup with Silent Bricks. On-premise storage appliances with integrated data protection for all NAS and VTL requirements. Media replication and rotation. Online, offline and off-site, with support for air gap environments. All in one system. The Silent Brick System is based on modular and transportable storage units called 'Silent Bricks' where each Silent Brick consists of 12 Disks. Depending on the Silent Brick Type these disks may be HDD (Silent Brick ) or SSD ( Silent Brick FLASH ).
The assignment is done on a per Brick Basis where each Brick can act as a Backup to Disk Storage, a virtual Tape Library or an Archival Storage. The redundancy when set up as Backup to Disk Storage is configurable with 2 or 3 Parities per Silent Brick. A SecureNAS Volume can then be spanned over 1 to many Silent Bricks. Extending a SecureNAS Volume is possible on the fly by assigning additional Bricks. The parities will still be on a per Silent Brick Basis. For optimal performance the Silent Brick System offers dual 10GB Ethernet connection.

Veeam testing configuration:

Note: The following settings were used by the vendor to meet Veeam Ready testing requirements and should not be considered best practices. Additional changes or settings may be needed to meet the storage efficiency or performance needs for each environment. For each setting, reference links are provided for further clarification.

Veeam Build Number: 9.5.0.1922

Job Settings:

• Deduplication: Enabled (Default)
• Compression: Optimal (Default)
• Storage Optimization: Local Target (Default)

Repository Settings:

• Repository Type: Shared Folder
• Align backup file blocks: Disabled (Default)
• Decompress before storing: Disabled (Default)
• This repository is backed by rotated hard drives: Enabled
• Per-VM Backup Files: Disabled (Default)

Vendor recommended configuration:

Hardware Settings:

• Jumbo frames used in testing environment
• SMB storage protocol used during testing. Vendor also supports NFS, and ISCSI or Fibre Channel for virtual tape library support.
• Dedicated SMB user for storage share, used default settings for share configuration
• 3 parities used in RAID Z configuration

More Information

Challenge

Cause

Solution

More Information

Challenge

Cause

• version 3.0 (builds 3.0.0.422 – 3.0.0.480)
• version 4.0 (build 4.0.0.1345)
• version 4a (builds 4.0.0.1553 – 4.0.0.1580)
• version 4b (builds 4.0.0.2516 – 4.0.0.2549)

What's New

• Support for Office 365 tenants using modern app-only authentication with disabled legacy protocols. In the new mode, VBO performs all its backup and restore operations using an Azure AD application instead of user credentials. This new mode addresses the needs of customers using Microsoft Security Defaults in their Office 365 tenant organizations.
• Support for leveraging auxiliary backup applications to enable faster SharePoint Online and OneDrive for Business backups for Office 365 tenants using modern app-only authentication.

Enhancements

• The built-in product auto upgrade feature now automatically installs the new and missing Veeam Explorers that come as part of Veeam Backup for Microsoft Office 365 package, as well as the newest patches for Veeam Backup for Microsoft Office 365.
• Enhanced UI for Backup Accounts Manager allowing for easier selection of a security group and managing dozens of accounts.

Considerations and limitations

When protecting Office 365 tenants using modern app-only authentication, consider the following:

• Discovery Search and Public Folder mailboxes are not supported.
• Dynamic Distribution groups are not supported.
• The type property for shared and resource/equipment mailboxes cannot be resolved. Such mailboxes will be available for backup with a general ‘User’ type.
• SharePoint Web Parts can only backed up if their ‘exportmode’ property is enabled. Non exportable Web Parts are not supported.
• OneNote restore is not supported.
• SharePoint Web Part customized template cannot be preserved upon a restore. All Web Parts will be restored with the default template.
• The ‘Allow multiple responses’ setting in survey lists within team modern sites is not preserved upon a restore.
• The ‘Measure-VBOOrganizationFullBackupSize’ cmdlet is not supported.

IMPORTANT NOTE:

• standalone installations of Veeam Backup for Microsoft Office 36
  • version 3.0 (builds 3.0.0.422 — 3.0.0.480)
  • version 4.0 (build 4.0.0.1345)
  • version 4a (builds 4.0.0.1553 (see KB3035) and 4.0.0.1580 (see KB3089))
  • version 4b (builds 4.0.0.2516 (see KB3065) and 4.0.0.2549 (see KB3119))
• installations on top of Veeam Backup & Replication v10 and Veeam Cloud Connect v10
   

• Veeam Backup & Replication 9.5 Update 4, 4a or 4b
• Veeam Cloud Connect 9.5 Update 4, 4a or 4b

Resolved Issues

• After an upgrade from Veeam Backup for Microsoft Office 365 version 4a to version 4b synchronization between the Proxy and Archiver services fails because of object storage repository status check.
• Applying retention policy fails with the “JetError -1605, JET_errKeyDuplicate, Illegal duplicate key”.
• After a username has been changed in Office 365, a new username is not reflected in the output of the “Get-VBOLicensedUser” PowerShell cmdlet and the built-in License Overview report.
• After existing backup data migration to an object storage repository, old restore points are missing some of the SharePoint data.
• Deleting an organization with configured auxiliary backup accounts from the Veeam Backup for Microsoft Office 365 scope fails with the "Organization with the same name already exists" or “JetError -1809, JET_errPermissionDenied” error.
• Backup data migration from a local backup repository to an Azure Blob storage repository completes with the “Failed to move all objects” warning.
• Under certain conditions, executing of the “Disable-VBOJob” PowerShell cmdlet hangs.
• Cohesity S3 object storage cannot be added as an object storage repository

• When downloading attachments during a SharePoint Online site backup, job fails with the “Failed to backup list: File not found in the database” error.
• Backup of a OneDrive account fails with the "Item has been changed during backup" error.
• Under certain conditions, backup of an archive mailbox in a hybrid organization setup fails with the “ErrorInvalidUserPrincipalName” error.

• In the BaaS setup, SharePoint site list explore from a tenant side fails with the "Object synchronization method was called from an unsynchronized block of code" error.
• Under certain conditions, files are skipped during SharePoint Online restore to the original location.
• Under certain conditions, folders cannot be created during SharePoint Online restore to the original location.
• During SharePoint Online restore using REST API, the "GET Libraries" request fails with the "Invalid root web permissions" error.
• OneNote items export fails with the "Failed to create cab file" error.
• SharePoint Online document restore fails with the “A file or folder with the name already exists” and “User ID login not found on SharePoint server” errors, if a folder containing this document has been moved to another location.
• OneDrive export completes with the “No items were saved” message.
• An attempt to start a restore session via REST API fails after numerous attempts to get the new access token for a specific user account.
• Under certain conditions, export of an Exchange item to a PST or MSG fails with the “Value cannot be null” error.

Solution

• Download the ZIP archive: VeeamBackupOffice365_4.0.1.519.zip.
• Run the Veeam.Backup365_4.0.1.519.msi from the downloaded ZIP archive and follow the wizard steps to install Veeam Backup for Microsoft Office 365.
• Run the VeeamExplorerForExchange_4.0.1.519.msi from the downloaded ZIP archive and follow the wizard steps to install Veeam Explorer for Microsoft Exchange.
• Run the VeeamExplorerForSharePoint_4.0.1.519.msi from the downloaded ZIP archive and follow the wizard steps to install Veeam Explorer for Microsoft SharePoint. Note that Veeam Explorer for Microsoft OneDrive for Business is distributed in one package with Veeam Explorer for Microsoft SharePoint and will be installed automatically.  

More Information

Challenge

• Discovery Search and Public Folder mailboxes are not supported.
• Dynamic Distribution groups are not supported.
• The type property for shared and resource/equipment mailboxes cannot be resolved. Such mailboxes will be available for backup with a general ‘User’ type.
• SharePoint Web Parts can only backed up if their ‘exportmode’ property is enabled. Non exportable Web Parts are not supported. 

• OneNote restore is not supported.
• SharePoint Web Part customized template cannot be preserved upon a restore. All Web Parts will be restored with the default template.
• The ‘Allow multiple responses’ setting in survey lists within team modern sites is not preserved upon a restore.
• PowerShell
• The ‘Measure-VBOOrganizationFullBackupSize’ cmdlet is not supported.

• The ‘Measure-VBOOrganizationFullBackupSize’ cmdlet is not supported.

Solution

Challenge

Cause

Solution

Prerequisites:

• You need access to both Service Provider (SP) and tenant Veeam backup consoles.
• You need a second SP Veeam backup server (in addition to the original SP Veeam backup server and tenant Veeam backup server) where the metadata file of the affected backup will be imported. The second Veeam backup server can be used on the tenant side instead of the SP side, but in this case, SP has to provide the tenant with the original .vbm file and the list of storage files on a repository.
• You need one local repository connected to the second Veeam backup server.
• You need to back up original .vbm file by copying it to another folder outside the tenant quota.
• If the backup is encrypted, you need to know the password of the backup.
• To avoid any possible issues at steps 4–5, we recommend to use Veeam Backup & Replication version 9.5.4.2753 or higher in both tenant and SP installations.

Steps:

1. Connect to the tenant Veeam backup console.
2. Open Home – > Jobs.
3. Find your cloud job that processes the backup you want to modify, right-click the job and select Disable. The option can be greyed-out if the job is not scheduled to run at some particular time.
4. Open the Home –> Backups –> Cloud view.
5. Press and hold the [CTRL] key and right-click the backup you want to modify.
6. Select the Remove from configuration option.
7. Connect to the SP infrastructure.

Perform the following steps on the SP side until you see a notice to connect to the tenant infrastructure.

8.  Locate tenant quota in the SP repository used for storing tenant backups.

           Example:

The path to repository root is C:\VeeamBackup\. You can check this path in Backup Infrastructure –> Backup Repositories in the SP Veeam Backup & Replication console.
The tenant name is “Tenant1”.
The cloud job name is “CloudBackup”.
The path to tenant backup in the quota will be: C:\VeeamBackup\Tenant1\CloudBackup.

You can perform the following steps on the tenant side if the second Veeam backup server is deployed there and the tenant gets the required .vbm file from its SP.

9. Copy the cloud backup metadata file (.vbm file) from the tenant quota to the second Veeam backup server.
10. Put the .vbm file in the root folder of the local repository connected to the second Veeam backup server.
11. Open the Backup Infrastructure –> Backup Repositories view in the Veeam backup console of the second Veeam backup server.
12.  Find the local repository in the list, right-click it and select Rescan.
13. After the rescan process completes, you will see the imported backup in the Home –> Backups –> Disk (Imported) node. 
    If the backup is encrypted, you will see the backup in the Home –> Backups –> Disk (Encrypted) node. Find the backup in the list, right-click it, select Specify the password and use the latest password specified in the cloud job settings.
14. Right-click the imported backup and select Properties.
    All unavailable restore points will have red marks. Your goal is to remove the restore points that are missing on the cloud repository. Compare the list of points in the backup chain on the original repository and find the missing restore points. If there are some points dependent on the missing point, they must also be deleted from .vbm.
15. In the Backup Properties window, find the point you want to remove from .vbm.
16. Right-click the point and select the Forget option.
    If there are any points that depend on the missing point, select the first missing point and choose Forget –> This and dependent backups.
17. After the operation completes, copy the .vbm file from the local repository on the second Veeam backup server back to the tenant job folder in the tenant quota on the cloud repository.
    If the modification was made on the second Veeam backup server on the tenant side, pass the modified .vbm file to the SP.
    If the cloud quota for the tenant is created on a scale-out backup repository (SOBR), the metadata file should be copied to tenant job folders on every extent of SOBR.
18. Remove the backup from configuration on the second Veeam backup server on the SP side and do not forget to delete the .vbm file from the local repository.
19. Connect to the tenant Veeam backup console.
20. Open the Backup Infrastructure -> Backup Repositories view.
21. In the inventory pane, find the cloud repository where the affected backup is stored, right-click it and select Rescan.
22. During the rescan operation, in the statistics window, you will see that the backup was imported.
    The modified backup should appear in the Home –> Backups –> Cloud node in the tenant Veeam backup console.
    If you open the backup properties, you will see that the points removed at previous steps are no longer in the backup file list.
23. Open Home –> Jobs and find the cloud job associated with this backup.
24. Right-click the job, select Edit, proceed to the Storage step of the wizard and select Map backup.
25. Select the modified cloud backup from the cloud repository. Then, click OK to finish mapping.
26. Save the settings and enable the job. Then run it or wait for the job to run upon schedule.
    When the job runs after modifications for the first time, it is supposed to create an incremental restore point and back up data that has changed since the last restore point in the cloud backup chain was created.
27. Check the list of restore points on the repository and in the backup properties. If some points are absent in properties but exist on the repository, you can remove these files from the repository to free up the quota space.

Challenge

• Discovery Search and Public Folder mailboxes are not supported.
• Dynamic Distribution groups are not supported.
• The type property for shared and resource/equipment mailboxes cannot be resolved. Such mailboxes will be available for backup with a general ‘User’ type.
• SharePoint Web Parts can only backed up if their ‘exportmode’ property is enabled. Non exportable Web Parts are not supported. 

• OneNote restore is not supported.
• SharePoint Web Part customized template cannot be preserved upon a restore. All Web Parts will be restored with the default template.
• The ‘Allow multiple responses’ setting in survey lists within team modern sites is not preserved upon a restore.
• PowerShell
• The ‘Measure-VBOOrganizationFullBackupSize’ cmdlet is not supported.

• The ‘Measure-VBOOrganizationFullBackupSize’ cmdlet is not supported.

Solution

Challenge

Product Information:

Company name: Hitachi Vantara
Product Family: Hitachi Content Platform
Status: Veeam Ready – Object & Veeam Ready – Object with Immutability
Classification Description: Verified object storage solutions that has been tested with Veeam Backup & Replication Cloud Tier and object storage immutability features.

Solution

Product Details:

Model number: HCP for Cloud Scale
Storage Category: Software Defined Object Storage
Drive quantity, size, type: 396 – 10TB SAS (over two nodes)
Storage configuration: storage drives packaged in (2) HCP S11 nodes (the S3 back store). 20+6 erasure coding (EC)
Firmware version: 1.5
Connection protocol and speed: S3 compatible, 10 GbE
Additional support: All models and configurations of HCP for Cloud Scale with HCP S-Nodes with specifications equivalent or greater than the above.

General product family overview:
Hitachi Content Platform for Cloud Scale (HCP for Cloud Scale) is a software-defined object storage solution that is based on a massively parallel microservice architecture and is compatible with the Amazon S3 application programming interface (API). HCP for Cloud Scale is especially well suited to service applications requiring high bandwidth and compatibility with Amazon S3 APIs.

"HCP for Cloud Scale v1.x" and "HCP v8.x" are two different products. "HCP v8.x" is currently not compatible with Veeam.

Veeam testing configuration:

Veeam Build Number: 10.0.0.4461

Vendor recommended configuration:

Challenge

Product Information:

Company name: Dell EMC
Product Family: PowerStore
Status: Veeam Ready - Repository
Classification Description: Verified backup storage that supports all Veeam backup and restore features.

Solution

Product Details:

Model number: 7000X
Storage Category: All Flash Storage
Drive quantity, size, type: 21 (mixed sizes) - NVMe SSD (Total Capacity - 1.7TB)
Storage configuration: RAID5
Firmware version: 1.0.1.1.3.092
Connection protocol and speed: iSCSI, 25 GbE
Additional support: All models and configurations of PowerStore X with specifications equivalent or greater than the above

The ground-breaking Dell EMC PowerStore achieves new levels of operational simplicity and agility, utilizing a container-based architecture, advanced storage technologies, and intelligent automation to unlock the power of your data. Based on a scale-out architecture and hardware-accelerated advanced data reduction, PowerStore is designed to deliver enhanced resource utilization and performance that keeps pace with application and system growth. Utilizing the proven capabilities of VMware ESXi, PowerStore X models with AppsON provide the unique ability to host data-intensive and storage applications directly on the PowerStore system with a storage-based virtualization environment, with the flexibility of seamless movement of applications between the storage system and external VMware servers.

Veeam testing configuration:

Veeam Build Number: 10.0.0.4461

Job Settings:

Repository Settings:

Vendor recommended configuration:

Hardware Settings:

• array deduplication used in testing
• array compression used in testing

Challenge

Product Information:

Company name: Nexsan
Product Family: Unity Series
Status: Veeam Ready - Repository
Classification Description: Verified backup storage that supports all Veeam backup and restore features.

Solution

Product Details:

Model number: 2200
Storage Category: Unified Hybrid Storage
Drive quantity, size, type: 14 – mixed capacity NL-SAS drives. 1- 740GB SAS SSD, 1 – 360GB SAS SSD
Storage configuration: RAID10 for HDDs, 740GB SSD for write cache, 360GB SSD for read cache
Firmware version: 6.1.0.71242
Connection protocol and speed: NFS 10 GbE
Additional support: All models and configurations of Unity with specifications equivalent or greater than the above

Unity, the next generation unified storage, supports Fibre Channel and iSCSI connectivity in addition to NAS protocols. HDD and SSD support can be tailored for the best mixed application deployment environment or all-flash configurations for high performance needs. The latest Intel® Xeon® processors and increased memory allow for more IOPs, lower latency, and power to expand.

Veeam testing configuration:

Veeam Build Number: 10.0.0.4461

Job Settings:

Repository Settings:

Vendor recommended configuration:

Hardware Settings:

• No array deduplication used in testing
• No array compression used in testing
• Jumbo frames used in testing (MTU=9000)

Challenge

Cause

az account list output table

For more information on isolation and access control in Azure Active Directory, see Microsoft Docs. For more information on what the Azure CLI is, how to install and use it, see Microsoft Docs.

Solution