Challenge

The media is write protected. Failed to write data to file

Cause

Solution

• In File Explorer, right-click the drive in question and then click Manage BitLocker.
• On the BitLocker Drive Encryption page, click Turn Off BitLocker, and then click Turn off BitLocker again when prompted.
• When decryption is finished, click Close.

• Right-click the drive in File Explorer.
• Choose Format.
• Click Start.

More Information

If you have further questions, open a support case as follows:

1. Right-click the Veeam Endpoint Backup / Veeam Agent for Windows icon in the system tray and select Control Panel.
2. Click the Support link at the top of the window.
3. Click Technical Support to submit a support case to the Veeam Support Team directly from the product.

Challenge

Cause

Solution

More Information

If you have further questions, open a support case as follows:

1. Right-click the Veeam Endpoint Backup / Veeam Agent for Windows icon in the system tray and select Control Panel.
2. Click the Support link at the top of the window.
3. Click Technical Support to submit a support case to the Veeam Support Team directly from the product.

Challenge

Cause

Solution

More Information

If you have further questions, open a support case as follows:

1. Right-click the Veeam Endpoint Backup / Veeam Agent for Windows icon in the system tray and select Control Panel.
2. Click the Support link at the top of the window.
3. Click Technical Support to submit a support case to the Veeam Support Team directly from the product.

Challenge

Event ID = 5125, Failover Clustering:

Cluster Shared Volume 'VolumeX' ('VolumeX') has identified one or more active filter drivers on this device stack that could interfere with CSV operations. I/O access will be redirected to the storage device over the network through another Cluster node. This may result in degraded performance. Please contact the filter driver vendor to verify interoperability with Cluster Shared Volumes.

Active filter drivers found:
WIMMount (HSM)

Cause

Solution

1. Reboot the Hyper-V host after the Recovery Media creation to disable the WIMMount driver.
2. Stop WIMMount manually.

SERVICE_NAME: wimmount
        TYPE               : 2  FILE_SYSTEM_DRIVER
        STATE              : 1  STOPPED
        WIN32_EXIT_CODE    : 0  (0x0)
        SERVICE_EXIT_CODE  : 0  (0x0)
        CHECKPOINT         : 0x0
        WAIT_HINT          : 0x0

Direct IO will resume after a while.

More Information

If you have further questions, open a support case as follows:

1. Right-click the Veeam Endpoint Backup / Veeam Agent for Windows icon in the system tray and select Control Panel.
2. Click the Support link at the top of the window.
3. Click Technical Support to submit a support case to the Veeam Support Team directly from the product.

Challenge

Solution

1. Log on to the License Management Portal with your Veeam.com user account following this link:
   http://www.veeam.com/manage_licenses.html

2. The "Action" column will show an additional option to merge licenses whenever additional licenses of the same product have been added.
   Merging will allow you to manage your infrastructure as one via a single key with the combined socket totals, rather than segmenting different socket purchases.
    

    

3. Click "Merge" link of any of licenses you are going to merge.

4. On the next screen, select licenses you need to merge using check boxes at the left side, then use "Download File" or "Send via Email" buttons to receive the merged license file:
    

Challenge

Cause

Solution

1. Open Windows Disk Management from Control Panel > Administrative Tools > Computer Management > Disk Management.
2. Identify the volume to shrink. Warning message contains the sequential partition number which can be associated with the volume allocated on the disk. In most cases such partition is the last volume in the disk layout.
3. Calculate the amount of space to shrink. Warning message displays the size in bytes and shrink operation is calculated in Megabytes, so you have to convert bytes to Megabytes and round the result. Divide the value indicated in the warning by 1048576 and round it to get an integer. 
4. Right-click the affected volume and choose Shrink Volume. Specify the value you calculated earlier and click Shrink.
5. When the shrinking operation completes, re-run the backup job to verify the result. 

More Information

1. Right-click the Veeam Endpoint Backup / Veeam Agent for Windows icon in the system tray and select Control Panel.
2. Click the Support link at the top of the window.
3. Click Technical Support to submit a support case to the Veeam Support Team directly from the product.

Challenge

Cause

Solution

• installation folder, the default path is: C:\Program Files\Veeam\Endpoint Backup
• localDB folder: C:\Windows\System32\config\systemprofile
• logs folder: C:\ProgramData\Veeam
• the folders containing your backup files.

More Information

1. Right-click the Veeam Endpoint Backup icon in the system tray and select Control Panel.
2. Click the Support link at the top of the window.
3. Click Technical Support to submit a support case to the Veeam Support Team directly from the product.

Challenge

Cause

• incorrect boot order in the BIOS;
• the device is not recognized by the BIOS;
• USB 3.x is in use with out-of-date hardware.

Solution

More Information

If the issue persists after following the steps listed in this KB, open a support case as follows:

1. Right-click the Veeam Endpoint Backup / Veeam Agent for Windows icon in the system tray and select Control Panel.
2. Click the Support link at the top of the window.
3. Click Technical Support to submit a support case to the Veeam Support Team directly from the product.

Challenge

Cause

Solution

More Information

Challenge

Cause

Solution

More Information

Challenge

Cause

Solution

More Information

Challenge

Cause

Solution

More Information

C:\Program Files\Veeam\EndPoint Backup\x86>VeeamAgent.exe
LOG: Parsing log parameters ...
LOG: Initializing log file ...
LOG: VeeamAgent.Default.log
PID: 1160
Dispatch port:2500
>
dumpStg
D:\VeeamBackup\Backup Job SUP-A1849\Backup Job SUP-A18492017-03-14T133607.vbk
D:\VeeamBackup\storage.txt

test@test-debian:~$ /usr/sbin/veeamagent
LOG: Parsing log parameters ...
LOG: VeeamAgent.Default.log
PID: 15323
Dispatch port:2500
>
dumpStg
/media/sdb_repo/test-debian1/BackupJob2_2017-04-17T173521.vbk
/home/test/storage.txt

Challenge

Cause

Solution

1. Verify all of the above to identify this issue positively. If the version mismatch does not exist, you may wish to contact Support.
2. On the Veeam server itself, navigate to “C:\Program Files\Veeam\Backup and Replicaton\Backup\Packages” (if default installation path is used).
3. Copy VeeamDeploymentDll.dll and VeeamDeploymentSvc.exe to the target host in the path “C:\Windows\Veeam\Backup”. (You may need to grant permission to perform this copy.)
4. From an Administrator command prompt, run: sc delete veeamdeploysvc
5. Double-click on the service executable on the host, and choose “Repair” as you proceed through the wizard.

Challenge

Product Information: 

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

Solution

Product Details: 

Model number: 5TB, 10TB, 20TB, 40TB 
Number of Drives: 25 
Drive type: 400 GB, 800 GB, 1.6TB SSD
Firmware version: 4.x 
Additional support: Any hardware configuration with an equal or greater hardware configuration
General product family overview: The XtremIO Storage Array from Dell EMC is an all-flash system that leverages a scale-out architecture. The system is built via building blocks, called X-Bricks, which are SAN appliances that can be clustered together to grow performance and capacity as required. The Dell EMC XIOS operating system balances data across all solid-state arrays and supports features such as deduplication, compression, and snapshots. The all-flash architecture is viable for use cases including virtual desktop infrastructures (VDI), server environments, or database and analytics workloads. 

Veeam Details: 

Veeam Build Number: 9.0.0.902 
Veeam Settings:  
Repository Type: Windows 
Deduplication: No 
Compression: Optimal 
Storage Optimization: Local Target 
Per-VM Backup Files: No 
Decompress before storing: No 
Align backup file blocks: No

More Information

Company Information: 

Company name: Dell EMC 
Company overview: As a member of the Dell Technologies family of businesses, Dell EMC serves a key role in providing the essential infrastructure for organizations to build their digital future, transform IT and protect their most important asset, information. Dell EMC enables our enterprise customers’ IT and digital business transformation through trusted hybrid cloud and big data solutions, built upon a modern data center infrastructure that incorporates industry-leading converged infrastructure, servers, storage and cybersecurity technologies. 

Dell EMC brings together Dell’s and EMC’s respective strong capabilities and complementary portfolios, sales teams and R&D. We seek to become the technology industry’s most trusted advisor, providing capabilities spanning strategy development, consultative services and solution deployment and support to help our customers and partners drive the digital transformation of their businesses.

Challenge

Product Information: 

Product Family: Quest Software DR Series Appliance
Status: Veeam Ready - Tape 
Classification Description: Tape device where available hardware features have been tested to work with Veeam. 

Solution

Product Details: 

Model number: DR4300, DR4300e and DR6300  
Library firmware version: 0104 
Drive firmware version: 0104 
Driver for tape drive: 6.2.4.8 
Driver for media changer: 2.3.0.0 
Media Type: DR-VTL 
General product family overview: DR’s Virtual Tape Library (VTL) is an emulation of a physical tape library (SUN/STK L700) on a disk-based deduplication and compression system such as the DR Series system. The tape library is exposed to a Data Management Application (DMA) as if it is a physical library with tape drives and cartridges, which the application uses for backup. 

DR series system supports following VTL tape access protocols – 

• NDMP 
• FC 
• iSCSI (Configured in this document) 

Note: 

1. Changer gets detected as "Unknown Medium Changer" and it is supported for Veeam. Just need to change the changer properties in Veeam to use native SCSI commands. 
2. IBM tape Drivers are mandatory to install for Drives and can be downloaded from IBM site: 
Driver name - IBMTape.x64_w12R2_6248_WHQL_Cert 

Veeam Details: 

Veeam Build Number: 9.5.0.823

More Information

Company Information: 

Company name: Quest Software 
Company overview: Quest Software is the leading partner working tirelessly to make sure your information technology is designed for you and by you. This is our mission, and we're in this together.

Challenge

Product Information: 

Product Family: iXsystems Z Series 
Status: Veeam Ready - Repository 
Classification Description:  Verified backup storage that supports all Veeam backup and restore features.

Solution

Product Details: 

Model number: Z20 
Number of Drives: 14 x 1.2 TB 7200 RPM SAS Dual Port, 1 x 100GB SAS SSD write cache, 1 x 400GB SAS SSD read cache 
Drive type: SAS/SSD 
Firmware version: 9.10 
Additional support: Any hardware configuration with an equal or greater hardware configuration 
General product family overview: The Z20 is the entry-level product for the TrueNAS enterprise hybrid Z Series storage family, based on the open source FreeNAS operating system.  TrueNAS delivers multi-protocol storage using the OpenZFS filesystem and volume manager.  All TrueNAS systems offer HA controller capabilities and well as storage expandability. 

Veeam Details: 

Veeam Build Number: 9.5.0.823 
Veeam Settings:  

• Repository Type: Windows iSCSI 
• Deduplication: No 
• Compression: Yes 
• Storage Optimization: Local Target 
• Per-VM Backup Files: Yes 
• Decompress before storing: No 
• Align backup file blocks: No 

More Information

Company Information: 

Company name: iXsystems 
Company overview:  iXsystems believes that Open Source technology has the power to change the world through its process of open and collaborative innovation. This principle fuels all product design at iXsystems. By leveraging decades of expertise in hardware design, its contributions to many Open Source software communities, and corporate stewardship of leading Open Source projects (including FreeNAS and PC-BSD), iXsystems has become an industry leader in building innovative storage solutions and superior enterprise servers for a global marketplace that relies on open technology. 

iXsystems creates open source driven enterprise storage and server hardware and software solutions for thousands of clients, many with relationships lasting decades. We are headquartered in Silicon Valley with all products built and supported in the US. The Open Source ecosystem enables us to deliver the highest value and best ROI for our clients. 

Challenge

Cause

Solution

More Information

Challenge

Cause

Solution

Challenge

• When you add a Windows Server 2016 Hyper-V cluster to Veeam console.
• When you take a backup of a VM with a shared virtual disk located on the Windows Server 2016 Hyper-V cluster

Cause

Solution

Get-ClusterResource "Virtual Machine Cluster WMI" | Get-ClusterParameter ConfigStoreRootPath

$path = "C:\ClusterStorage\Volume1\Hyper-V\Shared"
Get-ClusterResource "Virtual Machine Cluster WMI" | Set-ClusterParameter -Name ConfigStoreRootPath -Value $path

Challenge

When accessing backup files on a CIFS (SMB) repository, Veeam Backup and Replication reports either of the following errors:
 
The specified network name is no longer available. (code 59, 0x8007003B)
 
An unexpected network error occurred. (code 64, 0x80070040)
 
Veeam Backup & Replication uses SMB connections for backup repositories, guest processing, and when first adding a Windows server to the Backup Infrastructure. This KB only addresses error messages that occur in the context of a backup file path, such as:
 
The specified network name is no longer available. Failed to read data from the file [\\10.0.0.81\backups\SQL VM New\SQL VM New2015-09-23T200441.vbk].
 
Note: If the failure is occurring in a tape job and no UNC path is specified in the error message, please contact Veeam Support.

Cause

These error messages are passed directly from Microsoft Windows, and indicate that some unknown problem led to a sudden failure of the connection between the repository gateway (acting as Server Message Block client) and the SMB server (typically a NAS appliance).



There are many possible reasons the SMB connection might fail: 

• Network issues are a common reason, constituting a potentially unlimited variety of hardware failure or network hardware configuration problems; such issues may or may not involve packet loss.
• Simple firewalls may block a connection consistently, while advanced firewalls might destroy an existing connection seemingly at random or under very specific conditions.
• Either client or server might close the connection due to one of a number of timeouts or retry limits either at the SMB protocol layer or the underlying TCP layer; such limits are often encountered due to network congestion or excessive load on the storage.
• The NAS may stop responding entirely due to hardware or software issues; it may in some cases be misconfigured. Appliances using post-process deduplication may stop responding if the process starts prematurely.

Solution

• If the repository share is located on a Windows server, try creating a Windows repository on that server instead of a CIFS (SMB) repository.
• Reboot both the SMB client machine (repository gateway) and the SMB server (NAS).
• If other storage is available, try writing the backup to the other storage as both verification of the problem and as a temporary workaround.
• Consider reconfiguring the NAS as iSCSI or an NFS mount on a separate Linux repository server, depending on what is supported by the NAS. This change may involve data loss. iSCSI usually offers the best performance.
• Writing backup files to SMB shares over a slow or unreliable network, such as a WAN connection, is not recommended. Deploy a gateway server with a fast connection to the share.
• To rule out interference from a firewall, temporarily disable any software firewalls (including certain antivirus products) on the SMB client or server, as well as any hardware firewalls between them.

• Open the repository settings and enable Limit combined data rate. If you can measure the existing data rate, start with a limit between 50% and 70% of that value to verify that reducing throughput prevents the error. If the network is still congested after limiting the repository data rate, and the source of the congestion is due to other Veeam processes, enable throttling for the relevant connections. 

• Change the gateway server in the repository settings to test whether particular routes to the share perform better than others. For example, if connections from any Windows server on an ESXi host tend to fail, but connections from a physical Windows machine do not fail, the root cause probably involves that ESXi host or its network connection. 

• If the SMB connection consistently fails after 10 hours, it may be due to expiration of a Kerberos service ticket. The most reliable workaround is to create non-domain credentials on the NAS, then specify those credentials in the repository settings. For more information and other possible workarounds, see this SAMBA mailing list discussion and the Authentication Expiration Timer heading in this MSDN blog post.