Challenge

Cause

New fixes:

• “/v2/tenants” get request does not display the “deleted” status for removed companies. 
• Querying “v2/tenants/{id}” and “/v2/tenants/{id}/backupResources” information may take considerable amount of time. 
• A backup policy cannot be created if there are “space” symbols in the encryption hint. 
• A backup policy cannot be created when “processingEnabled” parameter is set to True, and “Credentials” parameter is used.

• After applying a backup policy to a managed Agent, job scheduling settings are displayed incorrectly in the VAC UI, but the settings pushed to the Agent are correct. 
• Site administrators can select Public IP Addresses belonging to a different site when creating a company. 
• Under certain conditions, “Used Storage” counter may display incorrect data on the “Overview” tab. 

• Management agent installed on a Cloud Connect server is incorrectly displayed on the Backup Agents tab. 
• Under certain conditions management agent restarts every hour. 

• Network Extension IP addresses are not filtered by a reseller. Reseller can select IP addresses belonging to unmanaged companies. 
• Reseller can change his or her backup quota to “unlimited” when creating a managed company with “unlimited” quota.

• Only the first 10 000 products are displayed in the mapping area of the plugin. 
• Plugin services may consume excessive memory when there are a lot of tickets created in the ConnectWise Manage application.

• Platform type cannot be detected for old computers and is reported as “Oher.”

• Under certain conditions after installing a private hotfix Veeam.MBP.Service fails to connect to the existing database with the following error message ”Cannot change configuration database: Database version is invalid.” 
• Veeam.MBP.Service fails to start when managed backup agents have duplicate IDs (due to cloning operation) in the configuration database.

• “VM without backup” alarm is triggered for VMs that are migrated between vCenter Servers or are re-registered in the virtual infrastructure.

• Under certain conditions, the management agent may connect to VAC server without authentication.

• Computer renaming leads to duplicated values in the Protected Computers report.

• Under certain conditions, usage report for managed Veeam Backup & Replication servers may not be created within first ten days of a month.

Fixes included from previous patches:

• Cloud Copies counter on the Overview dashboard does not return any data.
• Backup agents managed by Veeam Backup & Replication report 0 restore points available in the backup policy drill down view. 

• Portal administrators can log in only when using a full domain name of the Veeam Availability Console server. 
• Users belonging to a domain user group which is added to a Veeam Availability Console security group cannot log in to the portal.
• Users belonging to a nested domain group cannot log in to the portal.

• Under certain conditions, Veeam.MBP.Service might be consuming excessive memory.
• Under certain conditions, data collection job fails to retrieve information from a Cloud Connect server that has lots of task sessions on cloud gateway servers. This results in displaying these tenants’ companies as deleted in the Veeam Availability Console UI.
• Tenant password changed in Veeam Cloud Connect is not synchronized with Veeam Availability Console.

• Office 365 and Gmail SMTP servers are not supported for notifications.  

• Inaccessible computers cannot be located when using CSV and IP discovery rule options.

• Full Access UI mode cannot be applied to a backup agent.  
• When using Select All checkbox on the Managed Backup Agents tab agent settings are applied to all computers of all managed companies regardless of the selected scope in the Company\Reseller filter.  
• Licensing attribute is not updated for managed backup agents which leads to license expiration on the backup agent.    
• Backup agent files are not validated when the installation is performed from a local folder without using a master management agent. This may result in a corrupted installation/upgrade of the backup agent. 

• Under certain conditions, management agents fail to upgrade with the following error message “The system cannot find the file specified.”

• Workstation and server backup counters in the Veeam Cloud Connect usage report are mixed up.
• Under certain conditions License usage report for Veeam Backup & Replication servers is not generated. 

• Under certain conditions, all VMs with a cloud copy which belong to different locations are reported as VMs from the default location in the invoice. 

• Querying tenant information with SetLinks parameter may take considerable time.
• The vMsBackudUpToCloud counter does not display data about VM and Agent backup copy jobs targeted to a cloud repository.  

• Cloud repository usage is not updated in ConnectWise Manage agreements when there are unknown files (not related to Veeam backups) in the repository. 
• Tickets state synchronization may stop working when triggering a mass-resolve operation in the ConnectWise Manage application. 

Solution

msiexec /update c:\VAC.ApplicationServer.x64_3.0.0.2762.msp /l*v C:\ProgramData\Veeam\Setup\Temp\VACApplicationServerSetup.txt

msiexec /update c:\VAC.WebUI.x64_3.0.0.2762.msp /l*v C:\ProgramData\Veeam\Setup\Temp\VACWebUI.txt

msiexec /update c:\VAC.ConnectorService.x64_1.0.1.610.msp /l*v C:\ProgramData\Veeam\Setup\Temp\ConnectorService.txt

msiexec /update c:\VAC.ConnectorWebUI.x64_1.0.1.610.msp /l*v C:\ProgramData\Veeam\Setup\Temp\ConnectorWebUI.txt

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.

More Information

Challenge

Product Information:

Company name: Fujitsu
Product Family: ETERNUS CS
Status: Veeam Ready - Repository
Classification Description: Verified backup storage that supports all Veeam backup and restore features.

Solution

Product Details:

Model number: CS8000
Drive quantity, size, type: 10 - SAS HDD
Firmware version: V6.1A7120-SP03
General product family overview:

ETERNUS CS8000 is a datacenter solution for backup storage for mainframe and open systems. Its intelligent process automation and pooling of storage capacity reduces the TCO for complex backup environments by 40%. Unique scalability in capacity and performance makes ETERNUS CS8000 a viable solution, delivering ongoing cost savings.

Veeam testing configuration:

Veeam Build Number: 9.5.x

Job Settings:

Repository Settings:

More Information

Challenge

Product Information:

Company name: Quest Software, Inc.
Product Family: QoreStor 6.0
Status: Veeam Ready - Repository
Classification Description: Verified backup storage that supports all Veeam backup and restore features.

Solution

Product Details:

Model number: DELL OEM R340p
Storage Category: Software Defined Storage
Drive quantity, size, type: 8 – 1.745TB SATA SSD
Storage configuration: RAID5
Firmware version: V6.0.0 Build 660
Connection protocol and speed: SMB, 2-10GbE bonded LACP
Additional support: All models and configurations of QoreStor 6.0 on hardware platforms with specifications equivalent or greater than the above

Software-defined secondary storage platform for backup. ... Your storage will shrink with QoreStor deduplication. Accelerate backups, variable block deduplication, and direct to storage backup by using QoreStor with Veeam Software.

Veeam testing configuration:

Veeam Build Number: 9.5.4.2753

Job Settings:

Repository Settings:

Vendor recommended configuration:

Hardware Settings:

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

More Information

Challenge

Product Information:

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

Solution

Product Details:

Model number: E-18P
Storage Category: RAID Storage Array
Drive quantity, size, type: 18 – 10TB SAS 7200 RPM drives
Storage configuration: RAID5
Firmware version: S011.1304
Connection protocol and speed: 10 GbE iSCSI
Additional support: All models and configurations of E-Series with specifications equivalent or greater than the above

E-Series P is a high-density, high-performance, highly scalable, ultra-reliable storage system that enables organizations to lower their storage costs, maximize storage uptime, and boost data storage ROI. E-Series P is a versatile SAN or DAS solution to stay ahead of the enormous data growth, demanding workloads, and high resiliency requirements in a variety of businesses, including media & entertainment, government, healthcare, HPC, financial, surveillance and service provider sectors.

Veeam testing configuration:

Veeam Build Number: 9.5.0.1536

Job Settings:

Repository Settings:

Vendor recommended configuration:

Hardware Settings:

• Cache Tuning settings in System Admin page on UI
  • Cache Optimization Setting
  • Write Cache Streaming Mode
• 2GB write cache, 30GB read cache used
• Jumbo frames used (MTU=9000)
• Multipathing used (MPIO, round robin using 2X 10GbE)

Challenge

This article documents how change the temporary staging location where SQL transaction log backups are stored during a Veeam Agent for Windows backup operation when Transaction Log Backup is enabled.

For more information on the Transaction Log Backup process for Veeam Agent for Windows please click here.

Cause

When SQL Transaction Log Backup is enabled, Veeam Agent for Windows copies transaction log files from the log archive destination (set by the Microsoft SQL Server administrator) to a temporary folder on the server. By default the path is: C:\ProgramData\Veeam\Endpoint\SqlLogBackup.

Solution

To change the location where the SQL Transaction Logs are temporarily stored, create the following registry entry on the server.

Note: This registry change is to be made on the machine where Veeam Agent for Windows is installed, and is running the backup with SQL Transaction Log backup enabled.

Key: HKLM\SOFTWARE\Veeam\Veeam Endpoint Backup
Type: REG_SZ (String Value)
Name: SqlTempLogPath
Value: Path to desired location (without trailing backslash)

Note: if the backup job is managed by Veeam Backup & Replication, then the path for the registry should be:

Key: HKLM\SOFTWARE\Veeam\Veeam Backup and Replication

The key should be created manually in the Agent machine registry if it does not exist.

Example

More Information

Challenge

Cause

Solution

More Information

Challenge

Product Information:

Company name: Quest Software, Inc.
Product Family: QoreStor 6.0
Status: Veeam Ready - Repository
Classification Description: Verified backup storage that supports all Veeam backup and restore features.

Solution

Product Details:

Model number: DELL OEM R340p
Storage Category: Software Defined Storage
Drive quantity, size, type: 8 – 1.745TB SATA SSD
Storage configuration: RAID5
Firmware version: V6.0.0 Build 660
Connection protocol and speed: SMB, 2-10GbE bonded LACP
Additional support: All models and configurations of QoreStor 6.0 on hardware platforms with specifications equivalent or greater than the above

Software-defined secondary storage platform for backup. ... Your storage will shrink with QoreStor deduplication. Accelerate backups, variable block deduplication, and direct to storage backup by using QoreStor with Veeam Software.

Veeam testing configuration:

Veeam Build Number: 9.5.4.2753

Job Settings:

Repository Settings:

Vendor recommended configuration:

Hardware Settings:

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

More Information

Challenge

Product Information:

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

Solution

Product Details:

Model number: E-18P
Storage Category: RAID Storage Array
Drive quantity, size, type: 18 – 10TB SAS 7200 RPM drives
Storage configuration: RAID5
Firmware version: S011.1304
Connection protocol and speed: 10 GbE iSCSI
Additional support: All models and configurations of E-Series with specifications equivalent or greater than the above

E-Series P is a high-density, high-performance, highly scalable, ultra-reliable storage system that enables organizations to lower their storage costs, maximize storage uptime, and boost data storage ROI. E-Series P is a versatile SAN or DAS solution to stay ahead of the enormous data growth, demanding workloads, and high resiliency requirements in a variety of businesses, including media & entertainment, government, healthcare, HPC, financial, surveillance and service provider sectors.

Veeam testing configuration:

Veeam Build Number: 9.5.0.1536

Job Settings:

Repository Settings:

Vendor recommended configuration:

Hardware Settings:

• Cache Tuning settings in System Admin page on UI
  • Cache Optimization Setting
  • Write Cache Streaming Mode
• 2GB write cache, 30GB read cache used
• Jumbo frames used (MTU=9000)
• Multipathing used (MPIO, round robin using 2X 10GbE)

Challenge

Cause

• Backup of failover clusters is supported in Veeam Agent for Microsoft Windows managed by Veeam Backup & Replication only. You cannot process a failover cluster by Veeam Agent for Microsoft Windows operating in the standalone mode.
• Agent license with a server counter must be installed in Veeam Backup & Replication to enable Agent Management features including failover cluster support.
• Veeam Agent for Microsoft Windows supports Windows Server Failover Clusters running Microsoft Windows Server 2008 R2 and later.
• Workgroup clusters, multi-domain clusters, and mixed OS version clusters are not supported.
• Cluster Shared Volumes (CSV) are skipped automatically during the backup.
• The following Microsoft Failover Cluster applications are supported: Microsoft SQL Server Failover Cluster Instances (Microsoft SQL Server 2008 SP4 or newer), Microsoft SQL AlwaysOn Availability Groups, Microsoft Exchange Database Availability Groups (Microsoft Exchange Server 2010 or newer).
• AlwaysOn Clusterless Availability Groups are not supported.
• Managed by backup server job with failover cluster type does not support the file-level backup mode.
• Recovery must be performed via Veeam Backup & Replication console.
• Clustered Storage Spaces are not supported in the current product versions listed above. If you have a requirement to deploy Veeam Agent across such clusters, consider using a non-cluster protection group with cluster nodes added one by one and a simple server backup job with these nodes.

Solution

Microsoft Windows Server Failover Clusters, Microsoft SQL Server Failover Cluster Instances, SQL Always On Availability Groups

Specific fault tolerance configurations may have Azure load balancer deployed - https://docs.microsoft.com/en-us/azure/load-balancer/load-balancer-ha-ports-overview
In this scenario, make sure that the corresponding rules are added the load balancer configuration, otherwise part of the Veeam traffic will be dropped - https://docs.microsoft.com/en-us/azure/load-balancer/configure-load-balancer-outbound-cli

Microsoft Exchange Database Availability Group

Starting with Veeam Backup & Replication 9.5 Update 4, Microsoft Exchange database availability group (DAG) nodes are now automatically processed in a sequential manner, so it is possible to use Veeam Agent for Microsoft Windows to process Microsoft Exchange Database Availability Groups (DAGs).

The procedure of adding a DAG to a Veeam Agent backup job differs depending on the type of the DAG that you want to process:

• For a regular DAG, the backup job configuration procedure is the same as for any failover cluster mentioned above, so all the steps above are relevant
• For an IP Less DAG (a DAG without an Administrative Access Point), the backup job configuration procedure is similar to the same procedure for standalone servers. To process an IP Less DAG, you must create a Veeam Agent backup job for servers in the Veeam backup console and add  all nodes of the IP Less DAG (the steps below show it in detail) to this job.

Then add servers that act as DAG nodes to a Veeam Agent backup job for servers configured in Veeam Backup & Replication.

During the backup process, Veeam Backup & Replication detects that servers in the backup job are part of a DAG, and creates a transactionally consistent backup of Microsoft Exchange databases running on these servers (only passive database copies are processed, active ones are excluded from VSS freeze operations; however, the job still copies all the correspondent EDB-files of all databases from all the nodes).

Application-aware processing should be enabled for a consistent backup, log truncation and application-item restore possibility.

Challenge

If more than 100 jobs are running simultaneously, and the user attempts to start more jobs, they may fail to start with the following error message:

Error Job <JobName> cannot be started. SessionId: <UUID>, Timeout: [361 sec]

Cause

This issue is due to many session running which causes the Veeam services to be impacted by the Desktop Heap limitation. This is because the Desktop Heap size for services is much smaller than that for applications.

Solution

To resolve this issue the Desktop Heap size must be increased via a registry modification.

Because this change will affect the desktop heap of all services (also known as non-interactive window stations), do not make the new value larger than necessary.

1. Run regedit and navigate to
   HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\SubSystems

2. Find string named "Windows"

3. Edit the Value data to change the third "SharedSection" value only.
   Do not modify any other values.

4. Press OK
5. Reboot the machine

More Information

More information can be found at http://support.microsoft.com/kb/947246

Challenge

• If the Entire computer mode and Include external USB drives check box are selected, removable devices are skipped during the backup.
• If the Volume level backup mode is selected, removable devices are not available at the Volumes step of the wizard.

Cause

Solution

• wmic logicaldisk — if this query specifies the device type as 2, then the device is not supported.
• wmic shadowcopy call create Volume "Volume Name" , then vssadmin list shadows — the first query creates a volume shadow copy, the second query verifies if the volume shadow copy was created. If it was not created, the device is not supported.

More Information

Challenge

[18.07.2019 15:49:24] <01> Warning TapeDrive alert: The tape drive has a problem with the application client interface
...
[18.07.2019 15:49:58] <01> Error Tape error: '1117' (The request could not be performed because of an I/O device error) (Veeam.Backup.Common.CCppComponentException)
[18.07.2019 15:49:58] <01> Error in c++: TapeHandle failed to get tape drive parameters.
[18.07.2019 15:49:58] <01> Error in c++: Tape initialization FAILED.

Cause

Solution

1. Download the hotfix. It contains the agents both for x64 and x86 architectures.
2. Check the current version of Veeam Backup & Replication. It must be 9.5.4.2866.
3. Make sure that no jobs are running, close the console, and stop all Veeam services.
4. Right-click on the installation file and click "Run as administrator"
5. Go through the wizard to install private fix.
6. Relaunch Veeam Backup Console and let Veeam automatically update hosts added to the Veeam server.
7. Disconnect the tape drive from the power for a couple of minutes.

More Information

Challenge

[11.07.2019 20:07:56] <  5652> mt |   Drive encryption status:
[11.07.2019 20:07:56] <  5652> mt |   Encryption Mode: Disabled
[11.07.2019 20:07:56] <  5652> mt |   Decryption Mode: Disabled
[11.07.2019 20:07:56] <  5652> mt |   Raw Decryption Mode Disabled (RDMD): Disabled
[11.07.2019 20:07:56] <  5652> mt |   Volume Contains Encrypted Logical Blocks (VCELB): Disabled
[11.07.2019 20:07:56] <  5652> mt |   Logical Block encryption parameters: Application Managed
[11.07.2019 20:07:56] <  5652> mt |   Hardware encryption is available
[11.07.2019 20:07:56] <  5652> mt | ERR | [MT]SCSI PASS THROUGH DIRECT ended with Scsi Error Fixed format, current;  Sense key: Illegal Request. Additional sense: Invalid field in command information unit
[11.07.2019 20:07:56] <  5652> mt | >>  |tr:Failed to enable hardware encryption, tapeHandle: 0x00000000000006a4
[11.07.2019 20:07:56] <  5652> mt | >>  |tr:Failed to create TapeReader.
[11.07.2019 20:07:56] <  5652> mt | >>  |tr:Failed to create TapeFileReader, setPba: 614675, localFla: 136589546, restFileSize: 4621392384
[11.07.2019 20:07:56] <  5652> mt | >>  |An exception was thrown from thread [5652].

1. The tape library is hardware.
2. Encryption is enabled in the target media pool settings (https://helpcenter.veeam.com/docs/backup/vsphere/add_media_pool_encryption.html?ver=95u4).
3. In the tape library settings, the encryption is set to Application managed (this setting is configured on the vendor side).

Solution

1. Download the hotfix. It contains the agents both for x64 and x86 architectures.
2. Check the current version of Veeam Backup & Replication. It must be 9.5.4.2866.
3. Make sure that no jobs are running, close the console, and stop all Veeam services.
4. Right-click on the installation file and click "Run as administrator"
5. Go through the wizard to install private fix.
6. Relaunch Veeam Backup Console and let Veeam automatically update hosts added to the Veeam server.

More Information

Challenge

Product Information:

Company name: Fujitsu
Product Family: ETERNUS CS
Status: Veeam Ready - Repository
Classification Description: Verified backup storage that supports all Veeam backup and restore features.

Solution

Product Details:

Model number: CS8000
Drive quantity, size, type: 10 - SAS HDD
Firmware version: V6.1A7120-SP03
General product family overview:

ETERNUS CS8000 is a datacenter solution for backup storage for mainframe and open systems. Its intelligent process automation and pooling of storage capacity reduces the TCO for complex backup environments by 40%. Unique scalability in capacity and performance makes ETERNUS CS8000 a viable solution, delivering ongoing cost savings.

Veeam testing configuration:

Veeam Build Number: 9.5.x

Job Settings:

Repository Settings:

More Information

Challenge

Product Information:

Company name: Fujitsu (Fujitsu Technology Solutions)
Product Family: ETERNUS CS
Status: Veeam Ready - Repository
Classification Description: Verified backup storage that supports all Veeam backup and restore features.

Solution

Product Details:

Model number: CS8000 V7.1
Storage Category: RAID Storage Array
Drive quantity, size, type: 24 – 960GB SSD 2.5” drives
Storage configuration: RAID5
Firmware version: V7.1A2140-SP00
Connection protocol and speed: CIFS 10GbE
Additional support: All models and configurations of ETERNUS CS8000 with specifications equivalent or greater than the above

Veeam testing configuration:

Veeam Build Number: 9.5.4.2615

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)

More Information

Challenge

[18.07.2019 15:49:24] <01> Warning TapeDrive alert: The tape drive has a problem with the application client interface
...
[18.07.2019 15:49:58] <01> Error Tape error: '1117' (The request could not be performed because of an I/O device error) (Veeam.Backup.Common.CCppComponentException)
[18.07.2019 15:49:58] <01> Error in c++: TapeHandle failed to get tape drive parameters.
[18.07.2019 15:49:58] <01> Error in c++: Tape initialization FAILED.

Cause

Solution

1. Download the hotfix. It contains the agents both for x64 and x86 architectures.
2. Check the current version of Veeam Backup & Replication. It must be 9.5.4.2866.
3. Make sure that no jobs are running, close the console, and stop all Veeam services.
4. Right-click on the installation file and click "Run as administrator"
5. Go through the wizard to install private fix.
6. Relaunch Veeam Backup Console and let Veeam automatically update hosts added to the Veeam server.
7. Disconnect the tape drive from the power for a couple of minutes.

More Information

Challenge

[11.07.2019 20:07:56] <  5652> mt |   Drive encryption status:
[11.07.2019 20:07:56] <  5652> mt |   Encryption Mode: Disabled
[11.07.2019 20:07:56] <  5652> mt |   Decryption Mode: Disabled
[11.07.2019 20:07:56] <  5652> mt |   Raw Decryption Mode Disabled (RDMD): Disabled
[11.07.2019 20:07:56] <  5652> mt |   Volume Contains Encrypted Logical Blocks (VCELB): Disabled
[11.07.2019 20:07:56] <  5652> mt |   Logical Block encryption parameters: Application Managed
[11.07.2019 20:07:56] <  5652> mt |   Hardware encryption is available
[11.07.2019 20:07:56] <  5652> mt | ERR | [MT]SCSI PASS THROUGH DIRECT ended with Scsi Error Fixed format, current;  Sense key: Illegal Request. Additional sense: Invalid field in command information unit
[11.07.2019 20:07:56] <  5652> mt | >>  |tr:Failed to enable hardware encryption, tapeHandle: 0x00000000000006a4
[11.07.2019 20:07:56] <  5652> mt | >>  |tr:Failed to create TapeReader.
[11.07.2019 20:07:56] <  5652> mt | >>  |tr:Failed to create TapeFileReader, setPba: 614675, localFla: 136589546, restFileSize: 4621392384
[11.07.2019 20:07:56] <  5652> mt | >>  |An exception was thrown from thread [5652].

1. The tape library is hardware.
2. Encryption is enabled in the target media pool settings (https://helpcenter.veeam.com/docs/backup/vsphere/add_media_pool_encryption.html?ver=95u4).
3. In the tape library settings, the encryption is set to Application managed (this setting is configured on the vendor side).

Solution

1. Download the hotfix. It contains the agents both for x64 and x86 architectures.
2. Check the current version of Veeam Backup & Replication. It must be 9.5.4.2866.
3. Make sure that no jobs are running, close the console, and stop all Veeam services.
4. Right-click on the installation file and click "Run as administrator"
5. Go through the wizard to install private fix.
6. Relaunch Veeam Backup Console and let Veeam automatically update hosts added to the Veeam server.

More Information

Challenge

Cause

You have reached the limit of simultaneously opened SSH sessions.

Solution

You may increase the limit of SSH connections on the linux repository by changing etc/ssh/sshd_conf settings:

ClientAliveInterval 30
TCPKeepAlive yes
ClientAliveCountMax 99999
MaxSessions 200
MaxStartups 100:30:200

Challenge

Product Information:

Company name: Adistec
Product Family: Data Protection Appliance Series
Status: Veeam Ready - Repository
Classification Description: Verified backup storage that supports all Veeam backup and restore features.

Solution

Product Details:

Model number: DPA M (M24)
Storage Category: Integrated Data Protection Appliance
Drive quantity, size, type: 4, 8TB, SAS HDD | (32TB total)
Storage configuration: RAID5 configured HDDs (12Gbps SAS) with read/write cache
Firmware version: V2
Connection protocol and speed: 10GbE ISCSI
Additional support: All models and configurations of DPA M with specifications equivalent or greater than the above: M, L & XL

Adistec Data Protection Appliances for VEEAM combine: customized Intel hardware platform, Veeam Availability Suite software, and Adistec Enterprise Cloud services resulting in a robust solution to protect your customer’s data supported by Adistec Total Support and Veeam. Simplify the Backup Storage’s infrastructure, eliminate complexity and maximize data availability and protection with this turnkey solution at an affordable price. Three models available in one and two RUs, with single Quad-Core or dual Octa-Core processors configuration. Starting with four 3.5” disks up to twelve, getting 16TB to 120TB of usable capacity.

Veeam testing configuration:

Veeam Build Number: 9.5.0.1536

Job Settings:

Repository Settings:

Vendor recommended configuration:

Hardware Settings:

• HDD – 1GB read cache on RAID controller, write back policy using backup battery
• Jumbo Frames used during testing (9000 MTU)
• Multipathing using Windows Server NIC teaming

More Information