Quantcast
Channel: Veeam Support Knowledge Base
Viewing all 4486 articles
Browse latest View live

Veeam Availability Console U1 Cumulative Patch 1807

$
0
0

Challenge

Veeam Availability Console U1 Cumulative Patch 1807

Cause

Please confirm you are running version 2.0.2.1750 or later prior to installing this cumulative patch 1807. You can check this under Windows > Programs and features. After upgrading, your build will be version 2.0.2.1807.

As a result of on-going R&D effort and in response to customer feedback, cumulative patch 1807 includes a set of bug fixes, the most significant of which are listed below:

Server

•    Under certain conditions password in the SMTP server settings is reset.

Monitoring & Alarms

•    Job name flittering is ignored in the job session state alarm.

Reporting & Billing

•    Cloud repository quota usage may report incorrect values when Veeam Agent backups are sent to the cloud repository via backup copy jobs. 

ConnectWise Manage Plugin

•    Under certain conditions ConnectWise Manage configurations cannot be created.
 

Solution

To install the cumulative patch 1807:

1. Back up the VAC database.
2. Log off VAC Web UI.
3. Execute VAC.ApplicationServer.x64_2.0.2.1807.msp as administrator on the VAC server, or run this cmdlet as administrator: 
msiexec /update c:\VAC.ApplicationServer.x64_2.0.2.1807.msp /l*v C:\ProgramData\Veeam\Setup\Temp\VACApplicationServerSetup.txt
4. Execute VAC.ConnectorService.x64_1.0.0.254.msp as administrator on the VAC server, or run this cmdlet as administrator: 
msiexec /update c:\VAC.ConnectorService.x64_1.0.0.254.msp /l*v C:\ProgramData\Veeam\Setup\Temp\VACConnectorServiceSetup.txt
5. Log in to VAC Web UI.

More Information

[[DOWNLOAD|DOWNLOAD CUMULATIVE PATCH|https://www.veeam.com/download_add_packs/availability-console/kb2667/]]

MD5 checksum for KB2667.zip is b4c3f01b8fce8ec130c73c55245479e5

Should you have any questions, contact Veeam Support.

Veeam Availability Console U1 Cumulative Patch 1850

$
0
0

Challenge

Veeam Availability Console U1 Cumulative Patch 1850.

Cause

Please confirm you are running version 2.0.2.1750 or later prior to installing this cumulative patch 1850. You can check this under Windows > Programs and features. After upgrading, your build will be version 2.0.2.1850.

As a result of on-going R&D effort and in response to customer feedback, cumulative patch 1850 includes a set of bug fixes, the most significant of which are listed below:

Server
  • Under certain conditions password in the SMTP server settings is reset
  • Veeam Management Portal Service cannot be started after installing Update 1
  • After deleting WAN accelerator component from the Veeam Cloud Connect inventory, records about backup resources available to the tenant might be duplicated
Management Agent
  • Management agent RAM consumption might significantly increase when running computer discovery process
Discovery Rules
  • After deploying Patch 1824 discovery rules cannot install backup agents to remote computers. To resolve this, install the latest patch and re-create all discovery rules.
Users and Roles 
  • Sub-tenant’s password is reset when changing cloud quota in the assigned backup policy 
UI
  • After upgrading to Update 1, backup resources of the managed company cannot be adjusted when backup portal is running under heavy load. 
Monitoring & Alarms
  • Job name filtering is ignored in the job session state alarm.
  • Storage snapshots are treated as a backup repository resulting in triggered alarms for the repository free space.
  • Under certain conditions Computer with no backup alarm can send false-positive notifications
  • “Item with the same key has already been added” message is displayed when opening the Managed Backup Servers tab in the UI
Notifications:
  • Multiple email addresses cannot be specified in the Global Notification Settings
Reporting & Billing
  • Cloud repository quota usage may report incorrect values when Veeam Agent backups are sent to the cloud repository via backup copy jobs
  • Under certain conditions Cloud replication quota usage is not displayed on the dashboard when logged in using managed company user account
  • Management agent re-installation results in losing collected data about protected VMs from the managed backup server. This affects Overview dashboard and Protected VMs report that display zero protected VMs
  • Overview dashboard and Protected VMs report can display zero protected VMs when using Veeam Cloud Connect 9.5 Update 3a
  • After changing report scheduling settings, reports are sent out using the previous and the new time schedule
ConnectWise Manage Plugin
  • Under certain conditions ConnectWise Manage configurations cannot be created.
  • Under certain conditions not all products created in ConnectWise Manage are accessible for mapping when using the billing function.
  • Companies data cannot be collected from ConnectWise Manage due to the following error "An item with the same key has already been added"
  • Companies with multiple types cannot be collected from ConnectWise Manage  
  • Product quantity in agreements might not be updated when VAC and Manage servers are located in different time zones 

Solution

To install the cumulative patch 1850:

1. Back up the VAC database.
2. Log off VAC Web UI.
3. Execute VAC.ApplicationServer.x64_2.0.2.1850.msp as administrator on the VAC server, or run this cmdlet as administrator: 
msiexec /update c:\VAC.ApplicationServer.x64_2.0.2.1850.msp /l*v C:\ProgramData\Veeam\Setup\Temp\VACApplicationServerSetup.txt
4. Execute VAC.ConnectorService.x64_1.0.0.336.msp as administrator on the VAC server, or run this cmdlet as administrator: 
msiexec /update c:\VAC.ConnectorService.x64_1.0.0.336.msp /l*v C:\ProgramData\Veeam\Setup\Temp\VACConnectorServiceSetup.txt
5. Execute VAC.ConnectorWebUI.x64_1.0.0.336.msp as administrator on the VAC server, or run this cmdlet as administrator: 
msiexec /update c:\VAC.ConnectorWebUI.x64_1.0.0.336.msp /l*v C:\ProgramData\Veeam\Setup\Temp\VACConnectorWebUI.txt
6. Log in to VAC Web UI.

More Information

[[DOWNLOAD|DOWNLOAD CUMULATIVE PATCH|https://www.veeam.com/download_add_packs/availability-console/kb2795/]]

MD5 checksum for KB2795.zip is 297f49fc7434a508e487005d0f86e3e0

Should you have any questions, contact Veeam Support.

Veeam Backup for Microsoft Office 365 v2 cumulative patch KB2809

$
0
0

Challenge

Veeam Backup for Microsoft Office 365 v2 cumulative patch KB2809.

Cause

Please confirm you are running Veeam Backup for Microsoft Office 365 version 2.0.0.567 or 2.0.0.594 (see KB2765 for more details) prior to installing this cumulative patch KB2809. You can check the product version under Help > About in the Veeam Backup for Microsoft Office 365 console. After upgrading, your build version will change to 2.0.0.814.

As a result of ongoing R&D effort and in response to customer feedback, cumulative patch KB2809 delivers optimizations to SharePoint Online and OneDrive for Business interactions, and includes a set of bug fixes, the most significant of which are listed below:
 

New Features

  • Veeam Backup & Replication 9.5 Update 4 along with the corresponding Veeam Explorer for Microsoft Exchange, Veeam Explorer for Microsoft SharePoint compatibility support.

  • Veeam Cloud Connect 9.5 Update 4 compatibility support.
NOTE: Cumulative patch KB2809 is applicable to standalone installations of Veeam Backup for Microsoft Office 365 v2 and installations on top of Veeam Backup & Replication 9.5 Update 4 and Veeam Cloud Connect 9.5 Update 4. Cumulative patch KB2809 is NOT applicable to installations on top of Veeam Backup & Replication 9.5 Update 3 or 3a and Veeam Cloud Connect 9.5 Update 3 or 3a.

 

Resolved Issues

SharePoint Online and OneDrive for Business processing

  • Slow backup processing which may finally be affected by throttling and may fail with the error 429.
  • Backup of default system lists with versioning enabled may fail with the “Failed to request item versions for list: User Information List (list ID: {}). Access denied. You do not have permission to perform this action or access this resource” warning.
  • Backup of an item with an attachment containing non-ASCII symbols in its file name may fail with the “File Not Found” error.
  • Backup job runs for a long time with seemingly no progress and may fail with the “The underlying connection was closed” error.
  • Backup of an item which content type is not defined (ContentTypeId is null) may fail on saving item’s version with the “JetError -1504, JET_errNullInvalid” error.

Exchange Online processing

  • Adding group mailboxes to on-premises Microsoft Exchange 2010 backup jobs may fail with the following error: “Exception occurred while executing a task. Cannot bind parameter 'Filter' to the target. Exception setting "Filter": "The value "GroupMailbox" could not be converted to type Microsoft.Exchange.Data.Directory.Recipient.RecipientTypeDetails.” .

Restore

  • A successfully backed up mailbox may not be visible during a restore session under certain conditions.
  • SharePoint Online lists’ and libraries’ fields may not be restored for certain content types (i.e. “Comments” for “Document Sets”)
  • SharePoint Online items with shared links may restore successfully, but the following error is shown upon completion in the restore session summary: “Object reference not set to an instance of an object on server. The object is associated with property File.”  
  • Adding Microsoft Exchange database manually to the Veeam Explorer for Microsoft Exchange scope may fail with the “Value does not fall within the expected range” error.

Server

  • Some restore points are not synced properly between a management server and a backup proxy after recreating/moving a corresponding repository.

Solution

To install the cumulative patch KB2809:
  1. Download VBO2.0-KB2809.msp.
  2. Execute VBO2.0-KB2809.msp as administrator on the Veeam Backup for Microsoft Office 365 server.
  3. Execute VeeamExplorerForExchange.msi as administrator on the on each machine where Veeam Explorer for Exchange is installed.
  4. Execute VeeamExplorerForSharePoint.msi as administrator on the on each machine where Veeam Explorer for SharePoint is installed.
If there are any remote proxies in your environment please update those as described here.

 

More Information

[[DOWNLOAD|DOWNLOAD CUMULATIVE PATCH|https://www.veeam.com/download_add_packs/backup-microsoft-office-365/kb2809/]]

MD5 checksum for kb2809.zip is 0c5d817e56d3782df21069b247062bd7

Should you have any questions, contact Veeam Support.

What does question mark in Veeam Explorer for SQL mean?

$
0
0

Challenge

In Veeam Explorer for SQL some of the databases listed have a question mark.

Cause

Question mark indicates lack of metadata for a database which may cause restore to be not fully functioning. Moreover restore points for such databases are not shown in the Enterprise Manager.
Most probable reasons are:
-    Due to lack of permissions metadata was not properly collected. Point-in-time restore will not be available.
-    Database was excluded from application-aware image processing. Such a database is in crash-consistent state.
-    Application-aware image processing was disabled for the whole virtual machine. Databases are in crash consistent state.
-    Database files are located on the disks excluded in job settings. Restore for such a database will not work.

Solution

If fully functioning restore is essential, resolve the underlying issue. Note that new run of image-level backup is required, although restore from existing backup still will be partly unavailable.

Veeam Backup and Replication does not start after Enterprise Manager update 9.5 U4

$
0
0

Challenge

Both Veeam Backup and Replication and Enterprise Manager are installed on the same server. Enterprise Manager is updated to Update 4 with instance license, while Veeam backup and Replication is still running an older version. After Enterprise manager update it will not start with the following error message:

User-added image

Cause

Veeam Backup and Replication 9.5 Update 3a or earlier do not support instance-based licenses

Solution

1. Close Veeam Backup and Replication shell

2. Remove license information from registry:
User-added image
3. Start Veeam Backup and Replication shell (it will be running in a Free mode)

4. Remove ESXi hosts version 4.1 which are no longer supported.

5. Close Veeam Backup and Replication shell and upgrade with instance license

Removing a License from Veeam Backup and Replication or Enterprise Manager

$
0
0

Challenge

You need to remove an existing Veeam Backup and Replication (VBR), Veeam Agent for Windows (VAW) or Veeam Agent for Linux (VAL) license from Veeam Backup and Replication (VBR) or Enterprise Manager (EM).

Cause

A license has to be removed from VBR/EM.

Solution

In order to determine which section of this article to use, you must know if Enterprise Manager is controlling the licenses within Veeam Backup & Replication. If you are unsure, attempting to change the license file within Veeam Backup & Replication will tell you. If it allows you to click the Install button within the license section without a message about Enterprise Manager then Enterprise Manager is not in use.

 


If licenses are managed by Enterprise Manager:

 

NOTE: Due to internal issue this scenario isn't working in 9.5 U4

 

  1. Open an administrative command prompt.
  2. Navigate to the EM installation folder (default path in the example below):
    cd C:\Program Files\Veeam\Backup and Replication\Enterprise Manager
  3. Remove the license by running
    Veeam.Backup.EnterpriseService.exe -removelicense [vaw, val]
  4. After running this command, restart Veeam Backup Enterprise Manager service so that the license information is updated in the UI.

 


If licenses are managed by Veeam Backup & Replication

  1. Open an administrative command prompt.
  2. Navigate to the VBR installation folder (default path in the example below):
    cd C:\Program Files\Veeam\Backup and Replication\Backup
  3. Remove the license by running
    Veeam.Backup.Manager.exe -removelicense [all, vbr, vaw, val]

More Information

Note:These commands can also be run from PowerShell.

Note: specify the desired parameter without brackets.

Example commands:

  • To remove the Veeam Agent for Windows license from Veeam Enterprise Manager:
    Veeam.Backup.EnterpriseService.exe -removelicense vaw
  • To remove Veeam Agent for Linux from Veeam Backup & Replication:
    Veeam.Backup.Manager.exe -removelicense val

If no parameter is specified, all existing licenses will be removed.

HCL Tape - ULT3580-TD4 QuestDell

$
0
0

Challenge

VeeamReadyTape

Product Information:

Company name: Quest Software
Product Family: DR Series Appliance
Status: Veeam Ready - Tape
Classification Description: Tape solution 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: (Veeam Option: Use native SCSI commands instead of Windows driver)
Media type tested: DR-VTL
Additional Support:

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.

Veeam testing configuration:

Veeam Build Number: 9.5.0.823

 

Vendor recommended configuration:

Vendor Settings:

  • 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.
  • DR series system using iSCSI to access VTL
  • IBM tape Drivers are mandatory to install for Drives and can be downloaded from IBM site: Driver name - IBMTape.x64_w12R2_6248_WHQL_Cert

How to disable TLS 1.0 with no impact on Veeam ONE functionality

$
0
0

Challenge

There are several issues could occur after disabling TLS 1.0 protocol on the Veeam ONE server:
  1. Veeam ONE 9.5 server may lose a connection to the SQL Server for runtime operations
  2. Veeam ONE 9.5 server may lose a connection to the SQL Server during the initial installation
  3. “Veeam Licensing” web server is unavailable when only TLS 1.2 protocol is enabled
  4. Veeam ONE Reporter website doesn’t work when only TLS 1.2 protocol is enabled

Cause

TLS 1.0 is no longer officially supported.

Solution

1. Veeam ONE server may lose a connection to the SQL Server for runtime operations
Solution: install an updated SQL Server Native Client (11.0) to the Veeam ONE server machine

2. Veeam ONE server may lose a connection to the SQL Server during the initial installation
Solution: use https://www.veeam.com/KB2265

3. “Veeam Licensing” web server is unavailable when only TLS 1.2 protocol is enabled
Solution: enable TLS 1.1

4. Veeam ONE Reporter website doesn’t work when only TLS 1.2 protocol is enabled
Solution: enable TLS 1.1 or explicitly activate “DES” cipher support on the Veeam ONE server machine
 

More Information

Should you have any questions, contact Veeam Support.

ERROR_NO_DEVICE_ID received while trying to load a driver using Veeam Agent Recovery Media

$
0
0

Challenge

When performing a Bare Metal restore using Veeam Agent Recovery Media storage or network devices are not visible in the system. When you try to load a driver for the device an ERROR_NO_DEVICE_ID error is being received:
User-added image

Solution

Make sure that the driver *.inf file is a correct one and has DEVICE_ID entries specific for your device. You can compare DEVICE_IDs by clicking “Show unknown devices” in the “Tools - Load Driver” window.
User-added image
Close the “Load Driver” window, click “Command Prompt” and type

drvload path_to_your_driver_inf_file:

User-added image

After that, you'll be able to use your storage or network devices:
User-added image

Veeam ONE compatibility patch for Veeam Backup & Replication 9.5 Update 4

$
0
0

Challenge

After upgrading Veeam Backup & Replication servers to version 9.5 Update 4, Veeam Cloud Connect monitoring and reporting in Veeam ONE 9.5 Update 3 will stop working.

Cause

This issue is caused by incompatibility of Veeam Backup & Replication 9.5 Update 4 and Veeam ONE 9.5 Update 3. To resolve this issue, confirm you are running Veeam ONE version 9.5.0.3801 prior to installing this compatibility patch.

Solution

There are several ways of applying the hotfix:

Using SQL Server Management Studio
 

  1. Open Veeam ONE Monitor client and check the lower part of the window for the SQL instance name and Veeam ONE database name.
User-added image

Alternatively, check the same via Veeam ONE Settings Utility (C:\Program Files\Common Files\Veeam\Veeam ONE Settings).
 
  1. Open Microsoft SQL Server Management Studio with the Administrator permissions (may need to be installed separately KB1761).
  2. Connect to the ServerName\Instance of the server that has the Veeam ONE database.
  3. Expand the Databases tree and select "VeeamOne" database. 
  4. Right-click on the database > New Query.
User-added image
  1. Copy the following query and run it against the database:
IF OBJECT_ID('monitor.[ENUM_CTVI_PV]', 'C') IS NOT NULL
  ALTER TABLE monitor.BpCloudTenantVersionInfo
   DROP CONSTRAINT [ENUM_CTVI_PV];​​
  1. If the query was performed correctly, you will get the following status in the SQL Server Management Studio: Commands completed successfully.

Using SQL command line

In case you do not have the Management Studio installed, run the hotfix against the Veeam ONE database using the SQLCMD utility:
 
  1. Open Veeam ONE Monitor client and check the lower part of the window for the SQL instance name and Veeam database name.
User-added image

Alternatively, check the same via Veeam ONE Settings Utility (C:\Program Files\Common Files\Veeam\Veeam ONE Settings).
 
  1. Open Windows command line or PowerShell prompt using the Veeam ONE Service account and run the hotfix against the Veeam ONE database:
     
    for default instances (change the database name in the query if it differs from yours):
sqlcmd -S SqlServerName -q "USE VeeamOne IF OBJECT_ID('monitor.[ENUM_CTVI_PV]', 'C') IS NOT NULL ALTER TABLE monitor.BpCloudTenantVersionInfo DROP CONSTRAINT [ENUM_CTVI_PV];"

for named instances (change the database name in the query if it differs from yours):
 
sqlcmd -S SqlServerName\SqlInstanceName -q "USE VeeamOne IF OBJECT_ID('monitor.[ENUM_CTVI_PV]', 'C') IS NOT NULL ALTER TABLE monitor.BpCloudTenantVersionInfo DROP CONSTRAINT [ENUM_CTVI_PV];"
 
 
In case you have SQL server authentication enabled you may define username and password (change the database name in the query if it differs from yours):
 
sqlcmd -S SqlServerName\SqlInstanceName -U username -P password -q "USE VeeamOne IF OBJECT_ID('monitor.[ENUM_CTVI_PV]', 'C') IS NOT NULL ALTER TABLE monitor.BpCloudTenantVersionInfo DROP CONSTRAINT [ENUM_CTVI_PV];"

More Information

Should have any questions, contact Veeam Support.

Consistent backup failures after installing vSphere 6.7 U1

$
0
0

Challenge

After updating vCenter to 6.7U1, processing of all VMs fails with "Object reference not set to an instance of an object."

Cause

The issue is triggered by an update to the vSphere API version in vCenter 6.7 U1.

Solution

Create the following registry value on the Veeam Backup and Replication server. You must be on Veeam 9.5 Update 3a

Please, note that value and data fields should not contain any spaces.
 
Location: HKLM\SOFTWARE\Veeam\Veeam Backup and Replication
Value: VMwareOverrideApiVersion
Type: Multi-String Value (REG_MULTI_SZ)
Data: 6.7.1=6.7 

After creating the registry value above, you must reboot the Veeam Backup and Replication server.

More Information

More information regarding this workaround can be found here: https://forums.veeam.com/vmware-vsphere-f24/vsphere-6-7-u1-support-t54673.html

This is a temporary workaround against the specific error, which will allow the jobs to complete successfully. Overriding VMware API version may potentially cause issues with other Veeam functionality, because we don't know the specific API changes that made VMware increment the API version. We're working with VMware to obtain these details while continuing to test vSphere 6.7 U1 with the workaround applied.

The release vehicle for the official out-of-the-box support for vSphere 6.7 U1 will be our next release (Update 4). We'll be able to determine supportability of vSphere 6.7 U1 with the workaround applied after full regression testing cycle is done against the U1 GA code (usually takes 3-4 weeks).

All auto-tests of Update 3a with the workaround enabled have completed successfully, so all base Veeam Backup & Replication functionality is now confirmed to work with vSphere 6.7 U1. The forum post above will be updated once the full regression testing cycle completes.

Mapping an existing Veeam Agent backup chain to a Veeam Backup & Replication repository

$
0
0

Challenge

You need to map an existing Veeam Agent backup chain to a Veeam Backup & Replication repository.

Cause

There are no features in Veeam Agent that would allow mapping existing backups to Veeam Backup & Replication, however it is possible to copy a local backup chain to a Veeam Backup & Replication repository and continue using it.

Solution

Here is the list of steps for mapping a local backup chain to a Veeam Backup & Replication repository.

1. Create a backup with Veeam Agent at any temporary backup destination of your choice.

If a Veeam Backup & Replication repository was used,
  • remove the existing Veeam Agent backup job from jobs (right click > Delete)
  • remove the backup files from configuration: right click Disk (backups) > Endpoint Backups > Remove from configuration

2. Place the backup chain into the required folder.

2.1 Example for a non-cloud repository

Backup files reside in C:\VeeamBackup\Backup Job 1 and need to be moved to a Veeam Backup & Replication repository into the following folder: C:\Backup.

Under C:\Backup you will need to create a folder named after the account that is used to access the repository. In this example, the account is DOMAIN1\user1, so the folder name would be DOMAIN1_user1.

The complete path to the backup files would be C:\Backup\DOMAIN1_user1\Backup Job 1

2.2 Example for a cloud repository

The backup files reside in C:\VeeamBackup\Backup Job 1 and need to be moved to a cloud Veeam repository into following folder: C:\Backup.

Under C:\Backup you will need to create a folder named after the tenant account that is used to access the repository. If the account name is Tenant2, the complete path to the backup files would be C:\Backup\Tenant2\Backup Job 1

If a subtenant is used with the account name Subtenant3, the path will be C:\Backup\Tenant2\users\Subtenant3\Backup Job 1

3. Rescan the Veeam Backup & Replication repository. Here is a brief guide on repository rescan. 
Note: For backups that you are mapping to cloud, rescan the repository hosting the tenant backups on the provider side.

4. The Veeam Agent backup should appear under Disk > Imported.
Note: When a backup chain is mapped to cloud, it will not be displayed under Disk > Imported.

5. Point the Veeam Agent job to the required Veeam Backup & Replication repository. Do not run it immediately, just close the wizard after making the changes.

6. On the Veeam Backup & Replication machine, the backup should be moved from the Imported section to Backup > Disk. Make sure that backups are located in Backups > Disks (not Disk (imported)).

7. Run the Veeam Agent backup job. It should continue the imported backup chain.

Note: The described solution works for Veeam Backup & Replication repository and Veeam Cloud Connect repository.

More Information

NOTES: 1. If local backup encryption was enabled during the initial job configuration, additional steps may be needed to complete the mapping.

For non-cloud repositories
Importing a backup chain to a Veeam Backup and Replication server puts the imported chain in the Disk (encrypted) tab. Before the backup chain can be continued, you will need to right click on the encrypted backup chain and enter the password.

For cloud repositories
In some cases it may be necessary to enter the password in order to continue the backup chain. If entering the password is required, you will be prompted to do so when the job starts.

2. If Backup & Replication repository’s encryption is enabled at the repository, you should decrypt it using password specification (Right click > Specify password) to finish the import procedure.

3. Migration to local VBR SOBR is described in kb2236 (the outlined method is completely relevant for Veeam Agent backups).
Put everything in the nutshell, here are the steps:
  1. Map the backup to a simple VBR repository.
  2. Run said backup.
  3. Add the simple repository to the SOBR repository (make sure VBR processed the existing backup to SOBR extent – as an indication, you will be prompted for it with a special message first and by the end of the process SOBR’s extents will have job’s VBM).
  4. Put a new SOBR extent into maintenance mode and evacuate all the backups from it. This procedure will place the existing temporary repository’s backup to other active extents.
  5. Change the backup job configuration on the VAW side to the SOBR repository and then check the backup from there.
4. Migration to a Cloud Connect SOBR has its own specific moments. The guide below contains all required steps required for a proper migration:
 
1) Get the successful backup to a simple VCC repository. It depends on the use case but the thing is that it is not possible to map VAW backup to VCC SOBR directly, first VAW backup should be mapped to a simple repository. Once it is done, feel free to proceed with SOBR migration;
2) Copy VBM and VBK, VIB files to SOBR extents and replace 'space' symbols with 'underscore' (_), e.g. 'Backup Job hostname' to 'Backup_Job_hostname' in the name of the job and the VBM-file.
The backup points itself (VBK, VIB) should be moved to the only extent, whereas VBM should be placed to all the SOBR's extents.
3) Then rename the old local repository VBM to VBM_old and rescan the simple VCC repository. This will clean VCC database of the old job's info.
4) Delete the existing tenant's quota and add a new SOBR's one. It's possible to achieve via tenant's properties by replacing the simple VCC repository with the SOBR one in 'Cloud repositories' section.
5) Rescan the SOBR repository.
6) Reconfigure the Veeam Agent job to a VCC SOBR repository
 
5. If Veeam Agent is managed by VAC, then, there are no limitations for VCC seeding and all the steps above are completely relevant. The guide below contains more details regarding specific VAC-related steps:
  1. Create two identical VAC backup policies – one for a local backup and one for a cloud backup
  2. Apply the Local policy to the desired machine. You can find how to apply a policy here
  3. Let the Local Policy Job run to its desired location. In our example, that is “E:\VeeamBackup” and under this folder will be a new folder named “Backup Job <Hostname>”.
  4. Apply the Cloud Policy *NOTE: It is important to only apply the policy at this step*. After the policy applies, a folder will be created on the cloud repository for the machine under the tenant folder. The final folder path will be <Default Repository Path>\<Tenant account>\Users\<Tenant Account>_<Hostname>. For example, in our test we are going to the default repository with the path of C:\Backup, using a tenant account named “test”, and the machine name is AgentHostname, so the final path will be: C:\Backup\test\Users\test_AgentHostname
  5. Copy the local backups “Backup Job <Hostname” to the Cloud folder made in the previous step “<Default Repository Path>\<Tenant account>\Users\<Tenant Account>_<Hostname>” to end up with a final path of “<Default Repository Path>\<Tenant account>\Users\<Tenant Account>_<Hostname>\Backup Job <Hostname>”For subtenant-based policy - C:\Backup\[TenantName]\Users\[SubtenantName]\Backup job [CompName], for tenant-based policy - C:\Backup\[TenantName]\Backup job [CompName]
  6. Rescan the Veeam Backup & replication repository hosting the tenant backups on the provider side. Here is a brief guide on repository rescan
  7. On the Backup Agent machine, delete the local backup that we made with the local policy
  8. Begin the backup to the Cloud Repository, run the job on Agent site (if VAC account related issue occurs - restart VAC Management Agent Service on Tenant site);
 
Check the mapping result. Make sure that there were no folders with suffix _1, _2 created on the Cloud repository Tenant's folder during initial run.


If you have any questions, open a case with Veeam Support.

Consistent backup failures after installing vSphere 6.7 U1

$
0
0

Challenge

After updating vCenter to 6.7U1, processing of all VMs fails with "Object reference not set to an instance of an object."

Cause

The issue is triggered by an update to the vSphere API version in vCenter 6.7 U1.

Solution

Create the following registry value on the Veeam Backup and Replication server. You must be on Veeam 9.5 Update 3a

Please, note that value and data fields should not contain any spaces.
 
Location: HKLM\SOFTWARE\Veeam\Veeam Backup and Replication
Value: VMwareOverrideApiVersion
Type: Multi-String Value (REG_MULTI_SZ)
Data: 6.7.1=6.7 

After creating the registry value above, you must reboot the Veeam Backup and Replication server.

More Information

More information regarding this workaround can be found here: https://forums.veeam.com/vmware-vsphere-f24/vsphere-6-7-u1-support-t54673.html

This is a temporary workaround against the specific error, which will allow the jobs to complete successfully. Overriding VMware API version may potentially cause issues with other Veeam functionality, because we don't know the specific API changes that made VMware increment the API version. We're working with VMware to obtain these details while continuing to test vSphere 6.7 U1 with the workaround applied.

The release vehicle for the official out-of-the-box support for vSphere 6.7 U1 will be our next release (Update 4). We'll be able to determine supportability of vSphere 6.7 U1 with the workaround applied after full regression testing cycle is done against the U1 GA code (usually takes 3-4 weeks).

All auto-tests of Update 3a with the workaround enabled have completed successfully, so all base Veeam Backup & Replication functionality is now confirmed to work with vSphere 6.7 U1. The forum post above will be updated once the full regression testing cycle completes.

Collecting Diagnostic Information for Veeam Agent for Microsoft Windows

$
0
0

Challenge

This KB article shows how to collect the diagnostic information that may be needed if you create a Veeam Agent for Microsoft Windows support case.

Solution

Gather logs using the four sections below. Once logs have been gathered, upload them to the FTP provided by the Veeam Support engineer. After the upload is completed you must notify the Veeam Support engineer.

If you need to use a secure FTP, this article contains secure FTP instructions.

All steps below are to be done from within the OS of the machine that is having an issue.

1. Veeam Agent guest logs

Navigate to and ZIP the contents of this folder:

%Programdata%\veeam\endpoint (This folder is hidden by default, please copy, paste provided path and archive this folder)

2. VSS Diagnostics

Run the following commands from administrative command prompt, then zip the resulting files.

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

Once submitted to Veeam Support, these log files can be deleted.

User-added image

3. Event Logs

Export the logs in .evtx format, with Display Information.

Export the System and Application logs as follows:

  1. Open Event Viewer (eventvwr.msc).
  2. Locate the log to be exported in the left-hand column.
  3. Right-click the name of the log and select Save All Events As.
  4. Enter a file name that includes the log type and the server it was exported from.

    For example, when exporting the Application event log from a server named HV01, enter Application_HV01.

  5. In Save as type, select Event Files.
  6. Include the display information.

    User-added image

  7. Be sure to include the LocaleMetaData folder when packaging the logs for upload.

    User-added image

4. File System Minifilter Diagnostics

Run the command below from an administrative command prompt. 

fltmc instances > C:\filter.log

Once submitted to Veeam Support, this log can be deleted.

More Information

For more details on how Veeam Support processes the collected data: https://vee.am/processing_of_personal_data

Restoring domain controller from an application-aware backup

$
0
0

Challenge

Application Aware Image Processing is required to be enabled and working as per Microsoft in order to functionally restore from a DC.

Since Active Directory implements multi-master replication, where multiple domain controllers sync changes with each other, one of the key challenges is the DC recovery process. This article outlines different DC restore scenarios and goes into some specifics of when and why this or that type of restore is required as well as gives instructions on the manual steps to perform proper DC recovery from backup created with Veeam B&R.

Before going into details, it is worth stressing that by default Veeam B&R performs automated non-authoritative restore of domain controller and in most cases when you need to recover failed DC, authoritative restore is not required.

The following situations are possible:
  • Restoring single lost DC in a multi-DC environment
  • Restoring entire AD infrastructure (AKA “all DC’s are lost”)
  • Restoring from Active Directory corruption

Depending on the scenario, different steps (or no steps at all) are required to perform DC restore. All of the scenarios assume application-aware image processing was enabled in the backup job that backed up the DC being restored.

Solution

Restoring single lost DC in a multi-DC environment or in environment with only a single DC

This scenario, actually the most common one, incurs restoring just one of the multiple DC’s when there are still other functional DC’s in the environment that the restored DC can replicate changes from.
DC recovery with Veeam B&R in this case is fully automated and does not require any user interaction. If your backup was done with application-aware image processing enabled in the backup job settings, Veeam B&R performs a non-authoritative restore of the DC, where the restored VM should first boot in Directory Services Restore Mode (DSRM) mode and then reboot automatically immediately to boot up next time normally.
The domain controller itself will understand that it has been recovered from backup and will allow normal replication to update everything that has been changed since the backup took place.
The automatic recovery should also work for environments with only a single DC.



Restoring entire AD infrastructure (AKA “all DC’s are lost”)

As mentioned above, the automatic recovery process performs a non-authoritative restore, where the DC reboots and starts looking for other DC’s to sync up. However, in a scenario where all DC’s are gone, there are no other partners available and replication may take quite long (15-30 minutes) to start. To avoid wasting the time attempting to contact replication partners, it is recommended to restore two of the domain controllers at once, power them on, wait for their reboot and force one of them to become authoritative for SYSVOL, so that they can start replicating. Then restoring other DC’s will be similar to the first scenario, i.e. will be 100% automatic.

Note: During the restore procedure, make sure the restored DC’s DNS records point to available DNS servers (e.g. to itself).

The procedure for designating DC as authoritative for SYSVOL varies based on whether FRS or DFS-R is used for SYSVOL replication. To determine if you are using FRS or DFSR for SYSVOL in the production environment check the value of the HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\DFSR\Parameters\SysVols\Migrating Sysvols\LocalState registry subkey. If this registry subkey exists and its value is set to 3 (ELIMINATED), DFS-R is being used. If the subkey does not exist, or if it has a different value, FRS is being used.

If domain level is Windows 2008 or above you could also use the command dfsrmig.exe /getglobalstate to monitor if we are in the ‘ELIMINATED’ state and we are using DFSR.
If you are still using the FRS to replicate SYSVOL you need to perform an authoritative restore of the SYSVOL on first DC restored using burflags
To perform an authoritative restore of the SYSVOL when using FRS, use the following steps:
  • Start the Registry Editor 
  • Navigate to "HKLM\System\CurrentControlSet\Services\NtFrs\Parameters\Backup/Restore\Process at Startup" 
  • Double-click on "BurFlags" 
  • Assign it a value of D4 (hex) or 212 (dec) 
  • Stop the NTFRS Service 
  • Start the NTFRS Service 
Or you can use the following commands
  • REG ADD "HKLM\System\CurrentControlSet\Services\NtFrs\Parameters\Backup/Restore\Process at Startup" /v BurFlags /t REG_DWORD /d 212 /f 
  • NET STOP NTFRS 
  • NET START NTFRS 
You could monitor the status of the replication by searching for the Event ID 13516
“The File Replication Service is no longer preventing the computer <Computer_name> from becoming a domain controller. The system volume has been successfully initialized and the Netlogon service has been notified that the system volume is now ready to be shared as SYSVOL.”

If you are using DFS-R as the more widely used these days the steps to implement basically consist of setting the following registry values:

Key: HKLM\System\CurrentControlSet\Services\DFSR\Restore
Value: SYSVOL (REG_SZ) = “authoritative”

Key: HKLM\SYSTEM\CurrentControlSet\Control\BackupRestore\SystemStateRestore
Value: LastRestoreId (REG_SZ) = any GUID value (e.g. 10000000-0000-0000-0000-000000000000)
 

If the first restored DC already hosts operations master roles, set the following registry value in order to bypass initial synchronization requirements and not to wait for another partners to replicate the directory partitions:
Key: HKLM\System\CurrentControlSet\Services\NTDS\Parameters
Value: Repl Perform Initial Synchronizations (REG_DWORD) = 0

Note: Don’t forget to reset this value back to 1 after domain recovery is completed, so that domain controller has successful replication with its partners before starting to service client requests.

After setting the values above, restart the domain controller.

Notes:
• If you’re restoring DC without FSMO roles, you might want to transfer them to it manually after the restore, using the ntdsutil seize command.
• This type of restore is similar to what Veeam B&R performs automatically when restoring DC within SureBackup isolated virtual lab.

 


Restoring from Active Directory corruption

Scenario where no DC’s are actually lost, however, AD itself is damaged in some way (corrupt objects or schema) and you need to restore from the backup created before corruption occurred. In this case you need to restore one of the multiple DC’s when other DC’s are still operating a damaged copy of AD and force all of them to accept replication changes from the restored DC. This is where authoritative restore of the DC is required.

Note: It is recommended to perform restore with network disabled to prevent DC from accepting changes from other controllers after the default non-authoritative restore.
Note: For an easier item-level recovery of Active Directory objects (without the need to restore the domain controller itself), consider using Veeam Explorer for Active Directory.

To perform an authoritative restore:

1. Restore the DC and let it complete the default non-authoritative restore (wait until it reboots second time).
2. During this second boot, press F8 to get to DSRM mode.
3. Log in with DSRM account and password.
4. Open a command prompt and run ntdsutil command.
5. At the "ntdsutil:" prompt, type "authoritative restore" and press Enter.
6. To mark a single object as authoritative, type restore object <distinguished_name>, where <distinguished_name> is the DN of the object as determined in step 1.
To mark a subtree of objects as authoritative, type restore subtree <distinguished_name>, where <distinguished_name> is the DN of the subtree as determined in step 1.
This will mark the container object and everything it contains as authoritative. Note: If the DN contains one or more spaces, enclose the entire DN in quotes.
7. At the Authoritative Restore Confirmation dialog box, click Yes.
8. Upon restore completion, type "quit" and press Enter to exit the ntdsutil utility.
9. Reboot server.
10. Perform an authoritative restore of the SYSVOL, as was already discussed above.

 

More Information

Veeam recovery of a domain controller
Active Directory backup and recovery with Veeam
Recovering Your Active Directory Forest
Windows Server - How to Perform an Authoritative Restore of Active Directory Object
Restoring The SYSVOL (Non-)Authoritatively When Either Using NTFRS Or DFS-R (Part 1)
Restoring The SYSVOL (Non-)Authoritatively When Either Using NTFRS Or DFS-R (Part 2)
Restoring The SYSVOL (Non-)Authoritatively When Either Using NTFRS Or DFS-R (Part 3)

VDDK error: 13 - Troubleshooting

$
0
0

Challenge

Backup/Replication jobs fail with:
 
VDDK error: 13.You do not have access rights to this file

Solution

Below is a list of possible solutions to this issue sorted by what transport mode was being using when this error occurred.
Note: There are many causes for VDDK 13, this list is not intended to be all encompassing.

Using Transport Mode: Network Mode
  • Solution 1:
    In some instances, you may receive this error when permissions are not correctly set. To confirm, please follow the steps outlined in the following KB article to test ports, permissions, and DNS resolution
    http://www.veeam.com/kb1198
Using Transport Mode: Hotadd Mode
 
  • Solution 1:
    https://www.veeam.com/kb1054
    VMware Tools must be installed and up-to-date on the Veeam server and any Veeam proxies
     
  • Solution 2:
    https://www.veeam.com/kb1775
    Stuck Hotadded Disks – Review all virtual proxies for disks attached that do not belong to the VM in question, remove the disks not owned by this VM without deleting from the datastore. Once deleted, consolidate snapshots on the affected VMs.

     
  • Solution 3:
    kb.vmware.com/kb/2003638
    Orphaned Snapshots – Consolidate snapshots on affected VMs

     
  • Solution 4:
    http://www.veeam.com/kb1875
    Permissions - Please configure the account leveraged to access the vCenter as an Administrator within vCenter

     
  • Solution 5:
    http://www.veeam.com/kb1882
    Automount – In some cases, it may be necessary to perform an automount scrub to clear any existing mount points that are no longer in the system.

    Run the following via CMD Prompt on the proxy server:
    diskpart
    automount disable
    automount scrub
    exit

     
  • Solution 6:
    http://www.veeam.com/patches.html
    Patching – Please ensure that all VMware and Veeam components are fully up to date.

     
  • Solution 7:
    In some rare instances, performing a storage vMotion has been known to resolve the issue due to a locked VM file on the datastore where the VM files reside.

     
  • Solution 8:
    In some rare instances, restarting the vCenter appliance or alternatively restarting the ESXi management agents (https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1003490) may yield positive results if all above testing does not resolve the issue.
     
  • Solution 9:
    Veeam Proxy has a Veeam replica with the same bios UUID within the vCenter Server. The following can be observed in 

    Job.Job_name.log:
    [time stamp] < threadID> Info VM VeeamProxy _replica(vm-100001) has the same bios uuid as proxy VeeamProxy.local in the DB

    Agent.Job_name.VM_name.Hotadd.Attacher.log:
    [time stamp] < threadID> vdl| [vddk] time stamp  error -[07132] [Originator@6876 sub=transport] Cannot use mode hotadd to access [datastore_name] VM_name/VM_name.vmdk: Cannot mount using this method. (Mounting VM vm-101 using transport hotadd failed : Cannot access datastore for one of the disks of Virtual Machine VM_name..)

    The behavior is observed when a Veeam Proxy is replicated with Veeam B&R, the replication process preserves the original VM bios UUID for restore purposes. To work around the issue setup a dedicated VM as a Veeam Proxy, replicating Veeam Proxies is not usually necessary due to ease of deployment.
 
  • Solution 10:
​​​​​​​In some rare cases you may encounter a limitation for the amount of disks attached to virtual SCSI controller (max. 15 disks). In this case you may try to add another SCSI controller to proxying server in use by the job. Please keep in mind that there's a limitation for the amount of SCSI  controllers - 4 per VM. 

Using Transport Mode: Direct SAN
 
Solution 1:
When receiving VDDK Error 13 when leveraging DirectSAN access mode, please confirm that the LUNs are presented to the proxy correctly and have the proper permissions. For assistance deploying & troubleshooting DirectSAN please follow the below KB articles:

More Information

Additional Troubleshooting(All versions):
  • Manual Hotadd - http://www.veeam.com/kb1184
  • Hotadd Requirements - http://www.veeam.com/kb1054
  • Deploy an additional standalone proxy to isolate failures to a single specified proxy
  • To isolate a specific transport mode as the point of failure, you may also test the other transport modes to ensure that connectivity is correctly established and backup jobs work as intended via the other transport mode.
Additional Troubleshooting (vSphere 5.1 and below):
http://www.veeam.com/kb1777
Backup via Standalone host – Configure backup job to backup via Standalone host rather than through vCenter; this will isolate vCenter as the point of failure. If backup via standalone host is successful, you can attempt restarting the vCenter as well as the management agents on the host(s) where the proxies/VM(s) reside.

Information: Hotadd will only work when the proxy is on the same host as the object being backed up

Additional Troubleshooting (vSphere 5.5):
When attempting to hotadd leveraging a standalone host configuration (that is managed by a vCenter object) with vSphere 5.5 you will receive VDDK Error 13, as well as the error listed below:

Error message: [00680 error 'transport'] Reconfigure attempt failed for VM "2" with Vmomi::MethodFault::Exception ("vim.fault.HostAccessRestrictedToManagementServer")\n

To resolve this particular issue, please leverage Network Mode or Direct SAN transport mode as this configuration is not supported due to limitations of VMware

Information: For more information regarding ‘HostAccessRestrictedToManagementServer’ please see below VMware documentation.

http://pubs.vmware.com/vsphere-55/index.jsp?topic=%2Fcom.vmware.wssdk.apiref.doc%2Fvim.fault.HostAccessRestrictedToManagementServer.html

 

Veeam Backup for Office 365 Timeout Errors

$
0
0

Challenge

A Veeam Backup for Microsoft Office 365 job fails with a timeout error.  

These commonly are reported as one of the following errors:
  • Unexpected End of File
  • Exchange Web Services error code: ErrorExceededConnectionCount
  • Error: Failed to get folder properties
  • Error: You have exceeded the available concurrent connections for your account.  Try again once your other requests have completed.
  • Error: Unexpected end of file has occurred. The following elements are not closed: m:Data, m:ExportItemsResponseMessage, m:ResponseMessages, m:ExportItemsResponse, s:Body, s:Envelope. Line 1, position 21397505.
But are not limited to these errors.

 

Cause

There are multiple causes for these timeout errors. The most common being a bad connection to the Exchange Web Service (EWS) from the Veeam Backup for Microsoft Office 365 server or proxy. This can be caused by flooding of open worker threads to the Exchange Web Services server, network traffic saturating the throughput of the connection, a slow internet connection to the Office 365 EWS server amongst other issues.

Solution

Performance settings to help with timeout errors can be adjusted through the proxy performance settings (Concurrent Threads, and limit network bandwidth). If you are still unable to get a Veeam Backup for Microsoft Office 365 due to these timeout errors after adjusting the Proxy Settings, you can contact Veeam Support to further fine-tune the settings.

VDDK error: 13 - Troubleshooting

$
0
0

Challenge

Backup/Replication jobs fail with:
 
VDDK error: 13.You do not have access rights to this file

Solution

Below is a list of possible solutions to this issue sorted by what transport mode was being using when this error occurred.
Note: There are many causes for VDDK 13, this list is not intended to be all encompassing.

Using Transport Mode: Network Mode
  • Solution 1:
    In some instances, you may receive this error when permissions are not correctly set. To confirm, please follow the steps outlined in the following KB article to test ports, permissions, and DNS resolution
    http://www.veeam.com/kb1198
Using Transport Mode: Hotadd Mode
 
  • Solution 1:
    https://www.veeam.com/kb1054
    VMware Tools must be installed and up-to-date on the Veeam server and any Veeam proxies
     
  • Solution 2:
    https://www.veeam.com/kb1775
    Stuck Hotadded Disks – Review all virtual proxies for disks attached that do not belong to the VM in question, remove the disks not owned by this VM without deleting from the datastore. Once deleted, consolidate snapshots on the affected VMs.

     
  • Solution 3:
    kb.vmware.com/kb/2003638
    Orphaned Snapshots – Consolidate snapshots on affected VMs

     
  • Solution 4:
    http://www.veeam.com/kb1875
    Permissions - Please configure the account leveraged to access the vCenter as an Administrator within vCenter

     
  • Solution 5:
    http://www.veeam.com/kb1882
    Automount – In some cases, it may be necessary to perform an automount scrub to clear any existing mount points that are no longer in the system.

    Run the following via CMD Prompt on the proxy server:
    diskpart
    automount disable
    automount scrub
    exit

     
  • Solution 6:
    http://www.veeam.com/patches.html
    Patching – Please ensure that all VMware and Veeam components are fully up to date.

     
  • Solution 7:
    In some rare instances, performing a storage vMotion has been known to resolve the issue due to a locked VM file on the datastore where the VM files reside.

     
  • Solution 8:
    In some rare instances, restarting the vCenter appliance or alternatively restarting the ESXi management agents (https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1003490) may yield positive results if all above testing does not resolve the issue.
     
  • Solution 9:
    Veeam Proxy has a Veeam replica with the same bios UUID within the vCenter Server. The following can be observed in 

    Job.Job_name.log:
    [time stamp] < threadID> Info VM VeeamProxy _replica(vm-100001) has the same bios uuid as proxy VeeamProxy.local in the DB

    Agent.Job_name.VM_name.Hotadd.Attacher.log:
    [time stamp] < threadID> vdl| [vddk] time stamp  error -[07132] [Originator@6876 sub=transport] Cannot use mode hotadd to access [datastore_name] VM_name/VM_name.vmdk: Cannot mount using this method. (Mounting VM vm-101 using transport hotadd failed : Cannot access datastore for one of the disks of Virtual Machine VM_name..)

    The behavior is observed when a Veeam Proxy is replicated with Veeam B&R, the replication process preserves the original VM bios UUID for restore purposes. To work around the issue setup a dedicated VM as a Veeam Proxy, replicating Veeam Proxies is not usually necessary due to ease of deployment.
 
  • Solution 10:
​​​​​​​In some rare cases you may encounter a limitation for the amount of disks attached to virtual SCSI controller (max. 15 disks). In this case you may try to add another SCSI controller to proxying server in use by the job. Please keep in mind that there's a limitation for the amount of SCSI  controllers - 4 per VM. 

Using Transport Mode: Direct SAN
 
Solution 1:
When receiving VDDK Error 13 when leveraging DirectSAN access mode, please confirm that the LUNs are presented to the proxy correctly and have the proper permissions. For assistance deploying & troubleshooting DirectSAN please follow the below KB articles:

More Information

Additional Troubleshooting(All versions):
  • Manual Hotadd - http://www.veeam.com/kb1184
  • Hotadd Requirements - http://www.veeam.com/kb1054
  • Deploy an additional standalone proxy to isolate failures to a single specified proxy
  • To isolate a specific transport mode as the point of failure, you may also test the other transport modes to ensure that connectivity is correctly established and backup jobs work as intended via the other transport mode.
Additional Troubleshooting (vSphere 5.1 and below):
http://www.veeam.com/kb1777
Backup via Standalone host – Configure backup job to backup via Standalone host rather than through vCenter; this will isolate vCenter as the point of failure. If backup via standalone host is successful, you can attempt restarting the vCenter as well as the management agents on the host(s) where the proxies/VM(s) reside.

Information: Hotadd will only work when the proxy is on the same host as the object being backed up

Additional Troubleshooting (vSphere 5.5):
When attempting to hotadd leveraging a standalone host configuration (that is managed by a vCenter object) with vSphere 5.5 you will receive VDDK Error 13, as well as the error listed below:

Error message: [00680 error 'transport'] Reconfigure attempt failed for VM "2" with Vmomi::MethodFault::Exception ("vim.fault.HostAccessRestrictedToManagementServer")\n

To resolve this particular issue, please leverage Network Mode or Direct SAN transport mode as this configuration is not supported due to limitations of VMware

Information: For more information regarding ‘HostAccessRestrictedToManagementServer’ please see below VMware documentation.

http://pubs.vmware.com/vsphere-55/index.jsp?topic=%2Fcom.vmware.wssdk.apiref.doc%2Fvim.fault.HostAccessRestrictedToManagementServer.html

 

HCL - QNAP TS-1232XU-RP

$
0
0

Challenge

VeeamReadyArchive

Product Information:

Company name: QNAP Systems, Inc
Product Family: TS-x32XU series
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: TS-1232XU-RP
Storage Category: RAID Storage Array
Drive quantity, size, type: 12- 4TB SATA HDD
Storage configuration: RAID6
Firmware version: 4.3
Connection protocol and speed: SMB, 10 GbE
Additional support: All models and configurations of TS-x32XU with specifications equivalent or greater than the above

General product family overview:

The TS-1232XU-RP is built to deliver high performance, flexible expansion capabilities and versatile applications at an affordable and cost-effective price for small/medium-sized businesses. Two 10GbE SFP+ ports are capable of high-speed transmission of time-critical business data and a PCI Express (PCIe) 2.0 ×2 slot (×4 length) provides flexibility for expanding connectivity and/or storage with M.2 SATA/PCIe NVMe SSDs, via QNAP's QM2 expansion cards. The TS-1232XU-RP is also equipped with a redundant power supply to ensure uninterrupted services.

 

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.0.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)
Per-VM Backup Files: Disabled (Default)
 

Vendor recommended configuration:

Hardware Settings:

  • Array compression used during testing – no
  • Array deduplication used during testing – no
  • Jumbo frames used during testing (MTU=9000)

HCL - QSAN XCubeNAS XN8012R

$
0
0

Challenge

VeeamReadyRepo

Product Information:

Company name: QSAN Technology, Inc.
Product Family: XCubeNAS XN8000
Status: Veeam Ready - Repository
Classification Description: Verified backup storage that supports all Veeam backup and restore features.

*This Veeam Ready test was performed with an SSD/Flash configuration. As such, this classification only applies to configurations in which the same amount or more SSD drives are used. The use of non-SSD drives may negatively impact performance.

Solution

Product Details:

Model number: XN8012R
Storage Category: Hybrid RAID Storage
Drive quantity, size, type: 4 – 2TB SSD
Storage configuration: RAID5
Firmware version: QSM 3.1.1
Connection protocol and speed: iSCSI, 10 GbE
Additional support: All models and configurations of XCubeNAS XN8000 with specifications equivalent or greater than the above

General product family overview:

QSAN Storage Manager 3 (QSM 3) is a NAS operation system specially designed for QSAN XCubeNAS series. The core of QSM is Linux kernel and in-house fine-tuning 128-bit ZFS. The ZFS has high scalability and can be managed easily, also with the ability to maintain the data integrity. QSM 3 not only inherits the amazing native features of ZFS, its powerful storage features ensure persistent, reliable storage management, protection against data corruption, seamless capacity expansion, several data integrity mechanisms, pool and disk encryption protection, unlimited snapshots, and unlimited clones.

 

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.0.0.1922

Job Settings:

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

Repository Settings:

Repository Type: Windows
Align backup file blocks: Disabled (Default)
Decompress before storing: Disabled (Default)
Per-VM Backup Files: Disabled (Default)
 

Vendor recommended configuration:

Hardware Settings:

  • Array deduplication used in testing – No
  • Array compression used in testing – Yes
Viewing all 4486 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>