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.x and higher.

More Information

Challenge

Product Information:

Company name: DataON
Product Family: Datacenter Storage (DCS)
Status: Veeam Ready - Repository
Classification Description: Verified backup storage that supports all Veeam backup and restore features.

Solution

Product Details:

Model number: DCS-5212
Storage Category: Raid Storage Array
Drive quantity, size, type: 12 – 12TB SAS HDD
Storage configuration: RAID 50 across two spans of (6) HDDs
Firmware version: Broadcom RAID controller: 9380_8i8e; FW: 24.22.0-0061
Connection protocol and speed: CIFS – 10GbE
Additional support: All models and configurations of Storage Backup Server with specifications equivalent or greater than the above

Veeam testing configuration:

Veeam Build Number: 9.5.4.2866

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

Product Information:

Company name: Western Digital
Product Family: Ultrastar Serv24
Status: Veeam Ready - Repository
Classification Description: Verified backup storage that supports all Veeam backup and restore features.

Solution

Product Details:

Model number: Ultrastar Serv24+6
Storage Category: Hybrid Storage
Drive quantity, size, type: 12 – 12TB SAS HDDs, 6 – 3.2TB NVMe SSDs
Storage configuration: RAID1 (6-SSDs for Veeam Repository)
Firmware version: 01
Connection protocol and speed: SAS – 12Gbps
Additional support: All models and configurations of Ultrastar Serv24 with specifications equivalent or greater than the above

Ultrastar Serv24+6 is a high-density hybrid storage server with 24 HDDs and 6 NVMe SSDs. With 28-core dual 2nd generation Intel Xeon Scalable Processor CPUs. It is designed for data and compute intensive environments such as VDI, backup and archive, and big data analytics.

Veeam testing configuration:

Veeam Build Number: 9.5.4.2866

Job Settings:

Repository Settings:

Challenge

Solution

1. Launch the Veeam ONE Settings utility available under the following path:
   
   C:\Program Files\Common Files\Veeam\Veeam ONE Settings\VeeamOneSettings.exe

2. In the menu on the left, select General, open the Database tab and make the necessary changes in the SQL Server section.
   

3. Make sure this account has sufficient privileges on the Veeam ONE database on the SQL Server side, as it will be used for performance data collection.

4. Click the Test Connection button to check whether new configuration settings are correct.

5. Save changes.

6. Restart Veeam ONE Monitor Server service.

Then modify connection settings for Veeam ONE Reporter and Business View. To accomplish that, follow the next steps:

1. In the list of services, locate Veeam ONE Reporter Server service and choose to modify its properties. Open the Log On tab and specify the necessary account for the service in the Log on as section.

2. Make sure this account has sufficient privileges on the Veeam ONE database on the SQL Server side, as it will be used for data collection.

3. Launch the Veeam ONE Settings utility available under the following path:
   
   C:\Program Files\Common Files\Veeam\Veeam ONE Settings\VeeamOneSettings.exe

4. In the menu on the left, select General, open the Web Identity tab and make the necessary changes in the Web identity section.
   

5. Make sure this account has sufficient privileges on the Veeam ONE database on the SQL Server side, as it will be used for overall Web UI operation and reports creation.

6. Save changes.

7. Restart Veeam ONE Reporter Server service.

IMPORTANT!

• Should the database be connected to a different Veeam One installation, make sure there is no version\build mismatch. Otherwise, the application will fail.
• Starting with Veeam One v8, database partitioning became an option. If this option has been in place on the previously used SQL server, follow the steps described in this KB article to implement it on the new SQL server. 
• Starting with Veeam One v9.5, index defragmentation maintenance job for Veeam One database has been implemented. To create this job on the new SQL server download and run this script.

NOTE: 
Veeam One database partitioning jobs (VeeamOneSqlMaintenance_Med and VeeamOneSqlMaintenance_Med) and index defragmentation maintenance job (VeeamOne Maintenance Job) will remain intact on the old SQL server under SQL Server Agent > Jobs node and need to be removed manually.

More Information

Challenge

Solution

More Information

Challenge

You need to be able to access the Internet from the isolated Virtual Lab.

Solution

NOTE: The function documented in this KB enables the virtual lab proxy appliance to act as an internet proxy. This proxy function only passes web browser traffic. This will not allow for any other type of traffic (e.g. ICMP, FTP, or SSH) to leave the isolated environment.

──────────────────────────────────────────────────────────
Veeam Backup & Replication 7.x, 8.x, 9.x
──────────────────────────────────────────────────────────
 
Within the configuration of the Virtual Lab, on the Proxy tab, select the Allow proxy appliance to act as internet proxy for virtual machines in this lab check box. In the Port field, specify a port for HTTP traffic. By default, port 8080 is used. In the Production proxy field, you can optionally specify an IP address or a fully qualified domain name of an Internet-facing proxy server that VMs must use to access the Internet.
 
After a VM has been started using this Virtual Lab you must adjust the proxy settings to enable internet access. To do this, open Internet Options > Connections > LAN Settings > Proxy server and specify the IP address of the proxy appliance on the isolated network and port number.





──────────────────────────────────────────────────────────
Veeam Backup & Replication 5.x and 6.x
──────────────────────────────────────────────────────────

1. Open the registry editor and create the following key:
   HKLM\SOFTWARE\VeeaM\Veeam Backup and Replication\SureBackup
   
   The following features can be enabled:
   1. Enable Internet access from inside lab.
      Create a new DWORD in the above key (1=enabled,0=disabled):
      
      v5: VLabProxyEnable
      v6: VLabProxyEnabled
       
   2. Customize the proxy port
      Create the following DWORD.
      If the DWORD is not created port 8080 is used.
      Note: Remember to change the option to decimal before entering a value.
      
      VLabProxyHTTPPort
       
   3. Set upstream proxy server.
      For use if Virtual Lab production interface cannot access internet.
      If this String does not exist, the proxy appliance must have direct internet access from its production network interface.
      Create the following String.
      
      VLabProxyServer
      
      Note: Authentication on upstream proxy (username/password) is NOT supported.
       
2. Restart Veeam Backup Service.
3. Create a NEW virtual lab.

Remember to adjust proxy settings in the Internet Options on every sandboxed VM. To do that, open Internet Options > Connections > LAN Settings > Proxy server, and specify the proxy appliance IP address on the isolated network and the port number.

 

Challenge

Solution

More Information

Challenge

Cause

Solution

1. Download archive with u4b_FIX_Licensing.Reporting.CC.GetInstancesInfo.sql file, extract and copy it to the SQL server, which hosts the Veeam Cloud Connect database or any other machine that can connect to the SQL instance in question.
2. Connect to the SQL instance by using Microsoft SQL Studio. When connecting, please provide valid credentials with full permissions.
3. Find your Veeam Cloud Connect database (its default name is VeeamBackup). Right-click it and select New Query.
4. Open file u4b_FIX_Licensing.Reporting.CC.GetInstancesInfo.sql by using the text editor, copy all its content and paste it to the query window from step 3.
5. Run the query by clicking Execute or pressing F5. Make sure that the query is executed successfully.
6. The fix is applied immediately, restart of Veeam services is not required.

More Information

Challenge

Cause

Solution

<configuration>
  <appSettings>
    <add key="ExposeShadowVolumes" value="True"/>
  </appSettings>
</configuration>

More Information

Challenge

Connecting to the Office 365 organization fails with the “Check Exchange plan: No Exchange plan found” or “Check SharePoint plan: No SharePoint plan found” error.
 

Cause

Some of the Office 365 Exchange or SharePoint service plans assigned to the Office 365 organization cannot be automatically identified as valid by Veeam Backup for Microsoft Office 365. This happens because assigned Office 365 plans are missing from the list of valid ones.

Solution

To resolve this issue, add missing Plans IDs to the list:

1. Get the current Office 365 plan IDs assigned for the organization. You can do this via ‘MSOnline’ AzureAD module and the following PowerShell One-Liners: *

   Note: This script is provided as is as a courtesy for Gathering Plan IDs from MSOnline. Please be aware that the commands and parameters may be altered by Microsoft in the future, which may cause the script to function incorrectly. There is no support provided for this script, and should it fail, we ask that you please contact Microsoft support. This script may be updated in the future to reflect changes to the Office 365 Powershell Environment

   • To call "get-msolaccountsku" (use the CMDLET), call "Connect-MsolService" first. This requires the following modules to be installed and activated:

     install-module AzureAD
     install-module AzureADPreview
     install-module MSOnline

   • To get the list of Exchange Online service plans IDs:

     (get-msolaccountsku).servicestatus.serviceplan | where {$_.ServiceType -match "Exchange"} | ft ServiceName,ServicePlanId

   • To get the list of SharePoint Online service plans IDs:

     (get-msolaccountsku).servicestatus.serviceplan | where {$_.ServiceType -match "SharePoint"} | ft ServiceName,ServicePlanId

2. Make sure that no backup jobs or restore sessions are running.
3. Stop the Veeam.Archiver.Service and Veeam.Archiver.Proxy services.

4. Navigate to the C:\ProgramData\Veeam\Backup365 directory on the VBO365 server, create a backup of the Congif.xml file by copying it to another location, then (Only after making the pre-edit copy) edit the Config.xml file by adding the following lines between <Archiver> tags:

   <Options>
   <O365Plans AdditionalExchangePlans="your-Exchange-plans-IDs" AdditionalSharePointPlans="your-SharePoint-plans-IDs" />
   </Options>

    

   If you do not have any sharepoint plans, do not add the AdditionalSharePointPlans to the line mentioned

   NOTE: You will have to add the Plans as the examples shown in the following screenshot. The GUIDs are entered in Coma Separated Value within the Quotation after each of the key values in the <O365Plans line.

5. Start the Veeam.Archiver.Service and the Veeam.Archiver.Proxy services.
6. Open ‘Add organization’ wizard and retry the procedure.

More Information

In case the issue persists after these changes, please, contact Veeam Support.

Challenge

Cause

[28.03.2019 08:50:09] <01> Info     [CTapeSourceBackupJob][<Job name>] Last backed up full tape storage creation time: 15/03/2019 0:00:00, backupId: 028285e1-8086-4f52-a44d-0094521b6a09, objectId: 00000000-0000-0000-0000-000000000000 mediaSet: Simple
[28.03.2019 08:50:09] <01> Info     [CTapeDailySynthesizedBackupCalendarSpecifics] Only latest virtual full backup is required. Skipping older virtual full backup creation
[28.03.2019 08:50:09] <01> Info     [CTapeDailySynthesizedBackupCalendarSpecifics] Virtual full backup dates between 16/03/2019 0:00:00 and 28/03/2019 8:50:09: 28/03/2019 0:00:00
[28.03.2019 08:50:09] <01> Info     [CTapeSynStorageCandidatesFinder] Analyzing syn candidates for 28/03/2019 0:00:00 to Simple mediaset
[28.03.2019 08:50:09] <01> Info     [CTapeSourceBackupJob] Vbk in tape creation time 05/03/2019 0:00:00, but in repository creation time is 09/03/2019 0:00:00. Supposed vbk '<File name>.vbk' was transformed
[28.03.2019 08:50:09] <01> Info     [CTapeSynDateAnalyzeResult] Full point was found. Details: Synthesized full backup was not created for 28/03/2019 because there is no VBK map for this date
[28.03.2019 08:50:09] <01> Info     [CTapeSynStorageCandidatesFinder] completed
[28.03.2019 08:50:09] <01> Info         [CTapeSynStorageCandidatesFinder] Found candidates:<Empty>
[28.03.2019 08:50:09] <01> Info     [CTapeSynStorageCandidatesFinder] Build virtual full storages for object: 00000000-0000-0000-0000-000000000000 is completed: 0,1064889 sec
[28.03.2019 08:50:09] <01> Info             [CTapeStorageFilterParams] Skip increment according settings: <File name>.vib:d6131d07-ef49-4bff-801f-0768fd894326:11/03/2019 22:45:10:11/03/2019 0:00:00:KbBlockSize1024:512
[28.03.2019 08:50:09] <01> Info             [CTapeStorageFilterParams] Skip increment according settings: <File name>.vib:36fc42d7-4c6b-4a41-bf83-1e5ff627e0f2:12/03/2019 22:39:30:12/03/2019 0:00:00:KbBlockSize1024:512
[28.03.2019 08:50:09] <01> Info             [CTapeStorageFilterParams] Skip full according settings: <File name>.vbk:e50cea1b-e22b-4433-85f9-31ffe8dc2611:28/03/2019 2:36:23:09/03/2019 0:00:00:KbBlockSize1024:512
[28.03.2019 08:50:09] <01> Info             [CTapeStorageFilterParams] Skip increment according settings: <File name>.vib:ae314a8c-ac10-42e3-8aeb-3e4e3dec942b:27/03/2019 2:21:54:27/03/2019 0:00:00:KbBlockSize1024:512

Solution

More Information

Challenge

This error can present in two distinct ways:

A failure during the Backup Job run:

Error: This functionality requires using paid Veeam Agent edition

A failure during the [Agent discovery session]:

Error: Remote deployment and management is available for licensed agents only. Please change your backup server settings to allow managed agents to consume the license, then perform a protection group rescan.

Cause

Solution

Challenge

Cause

Solution

1. Place the Exchange Virtual Machines disks on the fastest disks (Datastores) that are available.
2. Disable all background scanning and/or maintenance tasks occurring in Exchange, or any other tools that are being leveraged against the system at the time of backup.
3. Perform the Exchange Backup singularly as opposed to concurrently with other jobs.
4. Adjust Microsoft settings for failover sensitivity (in bold, run from command line):
   1. cluster /prop SameSubnetDelay=2000:DWORD (Default: 1000)
   2. cluster /prop CrossSubnetDelay=4000:DWORD (Default: 1000)
   3. cluster /prop CrossSubnetThreshold=10:DWORD (Default: 5)
   4. cluster /prop SameSubnetThreshold=10:DWORD (Default: 5)
   5. To check settings, use: cluster /prop (see note)
5. Add the line snapshot.maxConsolidateTime = "1" to the .vmx (configuration) file for the primary node. Please note that this is an undocumented vmx alteration, and should be validated by VMware support prior to using.
6. Reduce total amount of disks (.vmdk's) for primary node if possible, reducing impact of snapshot operations.
7. If possible, migrate the virtual machine from NFS type to VMFS formatted storage.
8. Use Network (NBD) mode setting on Source Backup Proxy as opposed to Appliance (hotadd) mode for your backup and/or replication jobs in Veeam.
9. Test snapshot operations directly to ESX(i) host instead of vCenter.  (In some cases, gaps in communication between vCenter and ESX(i) host can impact snapshot operations, including VSS operation timing.)

1. Install-WindowsFeature -name RSAT-Clustering-CmdInterface

1. Get-cluster | fl *subnet*  - provides current settings for timeout
2. Altering cluster settings:
   1. (get-cluster).SameSubnetThreshold = 20 (Default 10 in Windows 2012R2)
   2. (get-cluster).SameSubnetDelay = 2000 (Default 1000 in Windows 2012R2)
   3. (get-cluster).CrossSubnetThreshold = 40 (Default 20 in Windows 2012R2)
   4. (get-cluster).CrossSubnetDelay = 4000 (Default 1000 in Windows 2012R2)

More Information

Challenge

Solution

• Improved backup performance in some cases due to not enough queue depth on read operations.
• In some cases, the proxy appliance would schedule too many parallel tasks causing resource and performance issues. The bug has been fixed to offer optimal operation.
• Resolved issue with configuration backups being larger than required due to ignoring of configuration backup settings.
• Fixed bug with deleted VM retention not properly cleaning backups of deleted VMs.
• Fixed bug with Veeam Availability for Nutanix AHV service crashes in rare circumstances.
• Fixed bug with backup failures on highly loaded proxy appliances.

More Information

Challenge

Cause

Solution

1. Place the Exchange Virtual Machines disks on the fastest disks (Datastores) that are available.
2. Disable all background scanning and/or maintenance tasks occurring in Exchange, or any other tools that are being leveraged against the system at the time of backup.
3. Perform the Exchange Backup singularly as opposed to concurrently with other jobs.
4. Adjust Microsoft settings for failover sensitivity (in bold, run from command line):
   1. cluster /prop SameSubnetDelay=2000:DWORD (Default: 1000)
   2. cluster /prop CrossSubnetDelay=4000:DWORD (Default: 1000)
   3. cluster /prop CrossSubnetThreshold=10:DWORD (Default: 5)
   4. cluster /prop SameSubnetThreshold=10:DWORD (Default: 5)
   5. To check settings, use: cluster /prop (see note)
5. Add the line snapshot.maxConsolidateTime = "1" to the .vmx (configuration) file for the primary node. Please note that this is an undocumented vmx alteration, and should be validated by VMware support prior to using.
6. Reduce total amount of disks (.vmdk's) for primary node if possible, reducing impact of snapshot operations.
7. If possible, migrate the virtual machine from NFS type to VMFS formatted storage.
8. Use Network (NBD) mode setting on Source Backup Proxy as opposed to Appliance (hotadd) mode for your backup and/or replication jobs in Veeam.
9. Test snapshot operations directly to ESX(i) host instead of vCenter.  (In some cases, gaps in communication between vCenter and ESX(i) host can impact snapshot operations, including VSS operation timing.)

1. Install-WindowsFeature -name RSAT-Clustering-CmdInterface

1. Get-cluster | fl *subnet*  - provides current settings for timeout
2. Altering cluster settings:
   1. (get-cluster).SameSubnetThreshold = 20 (Default 10 in Windows 2012R2)
   2. (get-cluster).SameSubnetDelay = 2000 (Default 1000 in Windows 2012R2)
   3. (get-cluster).CrossSubnetThreshold = 40 (Default 20 in Windows 2012R2)
   4. (get-cluster).CrossSubnetDelay = 4000 (Default 1000 in Windows 2012R2)

More Information

Challenge

This article explains how to collect the diagnostic information required for a Veeam Agent for Microsoft Windows support case.

Solution

To encourage quicker support case processing, attach the following logs to the support case:

• Veeam Agent logs
• VSS diagnostics
• Event logs
• File system minifilter diagnostics

You can collect logs in the following ways: 

• Automatically using the script that is attached to this article.
• Manually in case the script fails to retrieve required logs.

Collect Logs Automatically

[[DOWNLOAD|DOWNLOAD SCRIPT|File URL: https://storage.veeam.com/tmp/File_kb3025_713f5f0e22.zip]]

Download the script from the link above.

1. Extract the script to any folder on the computer where Veeam Agent for Microsoft Windows is installed (for example, C:\temp\).
2. Open the folder with the script. Depending on the OS settings, you might be prompted to make execution policy changes to run the script.

4. Run the script with PowerShell. The script executes simple select queries, no system changes are made.

If the script runs successfully, the warning message will appear. 

After the script execution, the message about the successful execution will appear. The script creates a new folder with the VeeamAgentLogs_<DDMMYYYY> name, where <DDMMYYYY> is the current date, and stores the collected information into this folder. 

5. Attach the folder with all the contents to the support case.

If the script fails to collect the logs, proceed to collect the information manually as outlined below.

 

Collect Logs Manually

The following steps are to be done on the computer where Veeam Agent for Microsoft Windows is installed.

1. Collect Veeam Agent Logs

1. Navigate to the following folder: C:\%Programdata%\Veeam\Endpoint (this folder is hidden by default, copy and paste the provided path). 
2. Archive the content of this folder.

2. Collect VSS Diagnostics

1. Run the following commands using the administrative command prompt:

• vssadmin list writers > C:\vss_writers.log
• vssadmin list providers > C:\vss_providers.log
• vssadmin list shadows > C:\vss_shadows.log
• vssadmin list shadowstorage > C:\vss_shadow_storage.log

2. Archive the resulting files.

3. Collect Event Logs

1. Run the Event Viewer (eventvwr.msc).
2. In the left menu, find the Application logs.
3. Right-click the Application logs and select Save All Events As.
4. Enter the file name that includes the log type and the computer name the logs were exported from (for example, when exporting Application logs from a computer named HV01, enter Application_HV01).
5. In Save as type, select Event Files (*.evtx).
6. Include the display information.

7. Repeat steps 3—7 for the System logs.
8. Archive the logs. Include the LocaleMetaData folder in the archive as well.

4. Collect File System Minifilter Diagnostics

1. Run the fltmc instances > C:\filter.log command using the administrative command prompt.

Send Logs to the Veeam Support

1. Create a support case.
2. U​​pload the logs to the FTP server provided by the Veeam Support engineer. If you need a Secure FTP, see this article.
3. After the upload, notify the Veeam Support engineer.

More Information

Challenge

When backing up to a deduplication storage appliance from Veeam Backup & Replication, performance or deduplication ratio is low without using best practice settings. 

Solution

The default options of Veeam Backup & Replication are intended for non-deduplication storage.

If you use deduplication storage systems, you need to additionally configure the backup architecture and Veeam settings to achieve best performance. Below are some hardware and software configuration options that can be used with deduplication storages. In some cases, you may need to combine more than one option, but in all cases, it is strongly encouraged that you consult your deduplication appliance vendor and/or a value added reseller to discuss individual needs.

For the general architecture planning, Veeam’s best practices is to follow the industry 3-2-1 backup rule:

3: Maintain at least three copies of your data and applications. That’s the one copy you’re using and two backups. This way, if one of your backups is unavailable for any reason (for example, if you store the backup in the same locations with the copy you use and both go down), you can still recover what you need.

2: Store your backups on at least two different types of media or storage controller logics. One reason for this is that each type of media has its own vulnerabilities, and you don’t want both of your backups susceptible to the same problem. 

For example: run your business on a general purpose fast storage system and store your backups on a storage system that is specialized for this purpose, or a separate server with local disks.

1: Keep one of the backups in a different location. Consider a crisis in your primary data center, such as a fire or power failure. If all your copies are collocated, they can all be affected, taking down your organization.

To achieve this, use the Veeam best practices. However, each deduplication storage vendor has specific unique feature sets that allow the usage of their storages in different ways. Please check the following links for vendor specific guidelines:

• Best Practices for HPE
• Best Practices for ExaGrid
• Best Practices for Dell EMC DataDomain
• Best Practices for Quantum

General Deduplication Storage Best Practices

Step 1:  Creating backups on the first site with long term retention.

Step 2: Add offsite target.

In addition to the above scenarios, you can use the following options to create an offsite copy of your data.

3. Place a deduplication storage on primary side and use object storage or tape on second site. Use Veeam backup to tape jobs or Veeam scale-out backup repository cloud tier (connection to object storages) to store data offsite.

The scenario above reflects general best practices. Please contact your deduplication storage vendor for further guidance and check the vendor links provided above for additional usable scenarios with the specific storage.
 

Best Practices For Deduplication Storage Systems

Backup Chains

• General Deduplication Storages / ExaGrid / Quantum DXI + Backup Copy Job That Reads From Source Backup Chain:

 

•  HPE StoreOnce Catalyst / Dell EMC DataDomain DDboost  + Copy Over WAN + Backup Copy Job:

The previous described option provides fast processing in situations that do not involve transport over WAN links. Also, optimized integration with Catalyst and Dell EMC DDBoost allows using synthetic processing. For these environments uncheck the “Read the entire restore point from source backup instead of synthesizing it from increments” but leave the weekly GFS backup enabled.

• Special Scenarios Based on Vendor Own Guidelines + Backup Job With Active Full or Synthetic Full Backup:

Inline Deduplication

However for deduplication devices that have a non deduplicated landing zone (Like ExaGrid) and backup only VMs, you can save some space: to do this, enable inline deduplication



 

Compression

Block Size

• Storage optimization: Local target (large blocks)

• Storage optimization: Local target 

Use this option for ExaGrid.

Block Alignment

Encryption

Health Check

  
Veeam Defragmentation And Compact Settings

More Information

Challenge

Collecting recovery media files Details: This access control list is not in canonical form and therefore cannot be modified.

Solution

To resolve this issue a modification must be performed within the registry of the Windows OS being backed up by Veeam Agent for Windows.

1. Open Registry Editor (Run: regedit)
2. Navigate to HKLM\SOFTWARE\Veeam\Veeam Endpoint Backup\
3. Add a New>String Value
4. Name it RecoveryImageTempPath
5. Set the value data to be C:\Temp
6. Restart the Veeam Agent for Microsoft Windows service (PowerShell: Restart-Service -Name VeeamEndpointBackupSvc )

Challenge

Cause

Solution

• Public role (default permissions)
• CREATE ANY DATABASE permissions
• db_owner role on the Veeam ONE database
• db_datareader permissions on the master database
• public, db_datareader, SQLAgentUserRole permissions on the msdb database
• [For Always-On Availability Groups] VIEW SERVER STATE permissions

More Information

Challenge

Product Information:

Company name: NetApp
Product Family: AltaVault
Status: Veeam Ready – Archive
Classification Description: Verified disk archive storage that can be used as a Backup Copy target. Synthetic full backups, granular restores, and vPower features may not provide sufficient performance or be supported.

Solution

Product Details:

Model number: AVA-V2
Firmware version: 4.2
Additional support: AVA-V2 or later

General product family overview:
Looking to leverage public and private cloud storage as part of your backup and archive strategy? Game-changing NetApp® AltaVault® cloud-integrated storage speeds recovery and reduces your risk, enabling you back up data with security to any cloud.

Veeam testing configuration:

Veeam Build Number: 9.0.0.1491

Job Settings:

Repository Settings: