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

Collecting Additional Diagnostic Information for Oracle Processing Cases

$
0
0

Challenge

An issue with backing up of the Oracle database server and/or removal of Oracle archived logs is suspected. Veeam Technical Support would like to gather some information from your servers and databases in order to investigate this issue.

Cause

Additional logs have to be gathered manually from the guest OS on the VM in question, because they are NOT captured by the Support Wizard automatically.

Solution

NOTE: If Application-Aware Image Processing is disabled, enable it and run the job again to update the log files within the guest OS.
 
The following actions need to be performed within the guest OS of the VM in question. 
NOTE: all Veeam Backup and Replication tasks against the guest in question must be stopped during this collection process. Otherwise the accuracy of the information will be affected.
 
 
For Windows
 
1.  Navigate to the following directory:
 
 %programdata%\Veeam\Backup
  
2.  Collect files and folders matching the following Syntax:
 
VeeamGuestHelper_ddmmyyyy.log
VeeamLogShipper_ddmmyyyy.log
OracleLib.*.log
%backup job name%_Oracle_Redo_Log_Backup - entire folder
 
3.  Open an elevated command prompt and run the following commands:
 
vssadmin list writers > C:\vsswriters.txt
vssadmin list providers > C:\vssproviders.txt
 
4.  Export Windows Event Logs as shown here.

5. Connect to your instance as sysdba:
 
sqlplus / as sysdba
 
and run the following queries:
 
SQL> select * from v$version;
SQL> select status from v$instance;
SQL> select log_mode from v$database;
SQL> select name from v$controlfile;
SQL> select username,sysdba from v$pwfile_users;
SQL> show parameter spfile;
SQL> show parameter pfile;
SQL> select instance from v$thread;
SQL> select name from v$database;
Save output of above queries in a text file for support engineer.

 
For Linux
 

1.  Navigate to the following directories:
 
/var/log/VeeamBackup
/tmp
/tmp/VeeamBackup
 
get all the files with the following filename masks:
 
VeeamOracleAgent.*.log
Agent.LogBackup_cli.*.log
 
2. Login to the server shell with the user credentials specified in 'Guest OS credentials' field as shown here. After that issue the following commands to get basic environment information:
 
cat /etc/*release
uname -a
env
 
3. Collect information about guest components installed on your virtual machine:
 
a) In case of VMware
 
- Login to your Linux server
- Run the following commands
 
# vmtoolsd -v
# service vmtoolsd status
 
or
 
#  systemctl status vmtoolsd
 
b) In case of Hyper-V
 
- Login to your Linux server
- Run the following commands
 
# lsmod | grep hv_utils
# modinfo hv_vmbus
# ps -ef | grep hv
 
- Login to your Hyper-V host where this virtual machine is running
- Run the following command in PowerShell (replace VM with your actual virtual machine name)
 
PS> Get-VMIntegrationService -VMName "VM"
 
4. Connect to your instance as sysdba from same user in shell as it was in step 2:
 
sqlplus / as sysdba
 
and run the following queries:
SQL> select * from v$version;
SQL> select status from v$instance;
SQL> select log_mode from v$database;
SQL> select name from v$controlfile;
SQL> select username,sysdba from v$pwfile_users;
SQL> show parameter spfile;
SQL> show parameter pfile;
SQL> select instance from v$thread;
SQL> select name from v$database;
 
Save the output of above queries in a text file for Veeam Support.
 
5. Get the following files from your Oracle database installation (ask your database administrator if you are not sure about the exact location of these files)
 
oratab (by default it's located in /etc)
inventory.xml (by default it's located in $ORACLE_BASE/oraInventory)
oraInst.loc (by defaults it's located in $ORACLE_HOME)
 
Collect the logs and shell outputs from the steps above, bundle them in a compressed file, and share with 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.

NOTE: Veeam Backup for Microsoft Office 365 RESTful API Service will not be started automatically after the update. Please start it manually to continue using REST API.

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.

Configuration for VMware VSAN

$
0
0

Challenge

Optimize Veeam configuration for use with VMware VSAN

Cause

You can use any VMware Backup Proxy to backup VMs from your VSAN cluster. You may however want to reduce the network traffic generated from the data being read by the backup proxy.

Solution

Configure virtual proxies to make use of Hotadd. This can be any supported Windows server deployed as a VM on a host that has access to the VSAN cluster; the Proxy VM's disks should also be located on the protected VSAN cluster. If you have a backup proxy on each ESXi host in the VSAN cluster, Veeam Backup & Replication chooses the most appropriate backup proxy to reduce the backup traffic on the VSAN cluster network. To ensure this always happens you can configure a DRS VM-Host rule on each host to keep the proxy resident on each host.
 

More Information

For more information on backing up VMs on VSAN using Virtual Appliance Mode see the Help Center sections covering the Requirements for Backup Proxy Servers as well as the Virtual Appliance Mode for VMs on VSAN
 
Backup Proxy System Requirements
Virtual Appliance Mode for VMs on VSAN

Veeam Agent for Linux support of Red Hat Enterprise Linux

$
0
0

Challenge

This article describes Veeam Agent for Linux support of different kernel versions of Red Hat Enterprise Linux and its derivatives.
 

Cause

Last-minute kernel patches for Red Hat Enterprise Linux and its derivatives may cause Veeam Agent for Linux to go unstable (veeam.com/kb2786).
 

Red Hat Enterprise Linux versionVAL build numberKernel supported up to
7.x3.0.0.8653.10.0-957.1.3
6.x3.0.0.8652.6.32-754.9.1


 

HCL - Neverfail HS-SMB-24

$
0
0

Challenge

VeeamReadyRepo

Product Information:

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

Solution

Product Details:

Model number: HS-SMB-24
Drive quantity, size, type: 8 - 4TB SAS HDD
Storage configuration: RAID6
Firmware version: 2.3.108 and newer.
Connection protocol and speed: SMB, 10GbE
Additional support: Note: the HybriStor HS-SMB-24 maximum file size is 16TB with this firmware version. VMs larger than 16TB (or ~28TB if compression is enabled) may exceed this limit.

Veeam testing configuration:

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

Veeam Build Number: 9.5.0.1536

Job Settings:

Deduplication: Disabled
Compression: None
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: Enabled

HCL - Tegile IntelliFlash

$
0
0

Challenge

VeeamReadyRepo

Product Information:

Company name: Tegile – A Western Digital Brand
Product Family:  IntelliFlash T-Series, HD-Series
Status: Veeam Ready - Repository
Classification Description: Verified backup storage that supports all Veeam backup and restore features.

Solution

Product Details:

Model number: T4100
Drive quantity, size, type: 3x 500GB SSD | 13x 2TB HDD
Firmware version: 3.7
Connection protocol and speed: iSCSI, 10GbE
Additional support: All models and configurations of Tegile T or HD-Series with specifications equivalent or greater than the above

General product family overview:

Tegile enterprise storage arrays accommodate different grades of storage media—from hard disks to high-performance flash memory. Using patented IntelliFlash™ software architecture, data is organized and placed on the most appropriate media to deliver optimal performance with the best possible economics. Native SAN and NAS protocols enable you to simplify data management by storing application data, virtual machines, and unstructured data—all on a single array.

 

Veeam testing configuration:

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

Veeam Build Number: 9.5.0.1038

Job Settings:

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

Repository Settings:

Repository Type: Windows
Align backup file blocks: Enabled
Decompress before storing: Enabled
Per-VM Backup Files: Enabled

Configuration for VMware VSAN

$
0
0

Challenge

Optimize Veeam configuration for use with VMware VSAN

Cause

You can use any VMware Backup Proxy to backup VMs from your VSAN cluster. You may however want to reduce the network traffic generated from the data being read by the backup proxy.

Solution

Configure virtual proxies to make use of Hotadd. This can be any supported Windows server deployed as a VM on a host that has access to the VSAN cluster; the Proxy VM's disks should also be located on the protected VSAN cluster. If you have a backup proxy on each ESXi host in the VSAN cluster, Veeam Backup & Replication chooses the most appropriate backup proxy to reduce the backup traffic on the VSAN cluster network. To ensure this always happens you can configure a DRS VM-Host rule on each host to keep the proxy resident on each host.
 

More Information

For more information on backing up VMs on VSAN using Virtual Appliance Mode see the Help Center sections covering the Requirements for Backup Proxy Servers as well as the Virtual Appliance Mode for VMs on VSAN
 
Backup Proxy System Requirements
Virtual Appliance Mode for VMs on VSAN

Veeam Agent for Linux support of Red Hat Enterprise Linux

$
0
0

Challenge

This article describes Veeam Agent for Linux support of different kernel versions of Red Hat Enterprise Linux and its derivatives.
 

Cause

Last-minute kernel patches for Red Hat Enterprise Linux and its derivatives may cause Veeam Agent for Linux to go unstable (veeam.com/kb2786).
 

Red Hat Enterprise Linux versionVAL build numberKernel supported up to
7.x3.0.0.8653.10.0-957.1.3
6.x3.0.0.8652.6.32-754.9.1


 


How to Backup a Windows Failover Cluster with Veeam Agent for Microsoft Windows

$
0
0

Challenge

Starting from version 9.5 Update 3, Veeam Backup & Replication lets you deploy and manage Veeam Agent for Microsoft Windows on computers in your infrastructure. Veeam Agent for Microsoft Windows 2.1 adds full support for mission-critical Microsoft Failover Clusters, SQL Server-based Microsoft Failover Clusters, SQL Always On Availability Groups, and Exchange Database Availability Groups.

This is a “how to” step-by-step guide on backing up your Windows Failover Cluster.

Cause

Before you begin

Сonsider the following:
  • 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, Windows Server 1709 core edition 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).
  • When using Basic Availability Groups on Microsoft SQL Server 2016 Standard Edition, consider that secondary replica node cannot be backed up because the secondary node is not readable. See the following article for more information.
  • 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.

Solution

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


1. Create an Active Directory protection group

Protection Group is a container or folder to organize hosts you are willing to protect 

User-added image

To create a protection group navigate to Inventory, select Physical & Cloud Infrastructure node and hit Add Group button at the ribbon. Select Microsoft Active Directly objects as a type for this Protection Group.

User-added image

At the Active Directory step specify the domain name and account (if required) and select the Active Directory cluster name object.


User-added image

The AD cluster name account can be found in Active Directory Users and Computers or Failover Cluster Manager.

User-added image
User-added image

Make sure that you didn’t exclude any required host at the Exclusion step of the wizard.

User-added image

Specify the common master account and set custom credentials for particular hosts if needed.

User-added image

Check the box to Install backup agent at the Options step of the wizard to install backup agents automatically during the rescan (installation can be performed manually if required).

User-added image

Rescan the protection group to discover the newly added cluster account, all its nodes and install backup agent to every node. Once the rescan is completed you should see the cluster and all child nodes under the protection group

NOTE To avoid installation issues, make sure that all required network and DNS requirements are fulfilled.


User-added image

2. Configure the backup job

Once you install the backup agent on every node, you can create a cluster job. Navigate to Home node, click the Backup Job button at the ribbon and select Backup > Windows computer.

User-added image

Failover Clusters must be processed by backup server jobs with the Failover cluster type. 

User-added image

At the Computers step of the wizard hit Add and select cluster account or the parent protection group for this cluster.

User-added image

NOTE: each cluster node will consume a Server License host counter:

User-added image

Select the backup mode. Only volume-level backup and entire system backup modes are available for the failover cluster job.

User-added image

Define the appropriate application-aware processing options at the Guest Processing step of the wizard. For example, SQL log backup/truncation settings would be applicable to a SQL cluster.

User-added image

Start the job. The cluster job will track node changes and perform log backup respectively.

User-added image

User-added image


Microsoft Exchange Database Availability Group

Starting Veeam Backup & Replication Update 4 Microsoft Exchange database availability groups (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 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.

Create a protection group with the DAG nodes:

User-added image

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



User-added image

User-added image

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 (Veeam Agent process only passive database copies, active ones are excluded from VSS freeze operations).

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

User-added image

User-added image

For Veeam Backup & Replication released before 9.5 Update 4, it is not possible to process a DAG as a regular failover cluster. It is recommended to process each server that acts as a DAG cluster node in a separate Veeam Agent backup job configured in Veeam Backup & Replication. In the backup job settings, specify a backup schedule in a way that these backup jobs start at a different time and do not overlap.

 

HCL - iXsystems X20

$
0
0

Challenge

VeeamReadyRepo

Product Information:

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

Solution

Product Details:

Model number: X20
Drive quantity, size, type: 18 - 2TB 7200RPM SAS HDD
Firmware version: 11.1
Connection protocol and speed: iSCSI, 10GbE
Additional support: All models and configurations of iXsystems X-Series with specifications equivalent or greater than the above

General product family overview:

TrueNAS X20 Modular 2U Rack Mount with Hot-Swappable Storage Controllers and Global Fault Notification LED

 

Veeam testing configuration:

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

Veeam Build Number: 9.5.0.1038

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: Enabled

How to Backup a Windows Failover Cluster with Veeam Agent for Microsoft Windows

$
0
0

Challenge

Starting from version 9.5 Update 3, Veeam Backup & Replication lets you deploy and manage Veeam Agent for Microsoft Windows on computers in your infrastructure. Veeam Agent for Microsoft Windows 2.1 adds full support for mission-critical Microsoft Failover Clusters, SQL Server-based Microsoft Failover Clusters, SQL Always On Availability Groups, and Exchange Database Availability Groups.

This is a “how to” step-by-step guide on backing up your Windows Failover Cluster.

Cause

Before you begin

Сonsider the following:
  • 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, Windows Server 1709 core edition 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).
  • When using Basic Availability Groups on Microsoft SQL Server 2016 Standard Edition, consider that secondary replica node cannot be backed up because the secondary node is not readable. See the following article for more information.
  • 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.

Solution

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


1. Create an Active Directory protection group

Protection Group is a container or folder to organize hosts you are willing to protect 

User-added image

To create a protection group navigate to Inventory, select Physical & Cloud Infrastructure node and hit Add Group button at the ribbon. Select Microsoft Active Directly objects as a type for this Protection Group.

User-added image

At the Active Directory step specify the domain name and account (if required) and select the Active Directory cluster name object.


User-added image

The AD cluster name account can be found in Active Directory Users and Computers or Failover Cluster Manager.

User-added image
User-added image

Make sure that you didn’t exclude any required host at the Exclusion step of the wizard.

User-added image

Specify the common master account and set custom credentials for particular hosts if needed.

User-added image

Check the box to Install backup agent at the Options step of the wizard to install backup agents automatically during the rescan (installation can be performed manually if required).

User-added image

Rescan the protection group to discover the newly added cluster account, all its nodes and install backup agent to every node. Once the rescan is completed you should see the cluster and all child nodes under the protection group

NOTE To avoid installation issues, make sure that all required network and DNS requirements are fulfilled.


User-added image

2. Configure the backup job

Once you install the backup agent on every node, you can create a cluster job. Navigate to Home node, click the Backup Job button at the ribbon and select Backup > Windows computer.

User-added image

Failover Clusters must be processed by backup server jobs with the Failover cluster type. 

User-added image

At the Computers step of the wizard hit Add and select cluster account or the parent protection group for this cluster.

User-added image

NOTE: each cluster node will consume a Server License host counter:

User-added image

Select the backup mode. Only volume-level backup and entire system backup modes are available for the failover cluster job.

User-added image

Define the appropriate application-aware processing options at the Guest Processing step of the wizard. For example, SQL log backup/truncation settings would be applicable to a SQL cluster.

User-added image

Start the job. The cluster job will track node changes and perform log backup respectively.

User-added image

User-added image


Microsoft Exchange Database Availability Group

Starting Veeam Backup & Replication Update 4 Microsoft Exchange database availability groups (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 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.

Create a protection group with the DAG nodes:

User-added image

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



User-added image

User-added image

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 (Veeam Agent process only passive database copies, active ones are excluded from VSS freeze operations).

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

User-added image

User-added image

For Veeam Backup & Replication released before 9.5 Update 4, it is not possible to process a DAG as a regular failover cluster. It is recommended to process each server that acts as a DAG cluster node in a separate Veeam Agent backup job configured in Veeam Backup & Replication. In the backup job settings, specify a backup schedule in a way that these backup jobs start at a different time and do not overlap.

 

How to merge Veeam licenses

$
0
0

Challenge

This article describes the process of merging Veeam licenses.


 

Cause

A license file installed in your Veeam software replaces the information from the previous license. A merged license file allows for increased socket capacity by combining licenses from multiple Support IDs.

Please note that the merged license key will use the earliest support expiration date of all product keys.

Important: Only License Administrators can merge licenses.

Solution

NOTE! Licenses can be merged only if the following terms match:

Perpetual License Keys

•    First name, Last name, Email, Company for Perpetual License Keys
•    Edition
•    License Type
•    Product name

Subscription License Keys

•    Licensee company, Licensee e-mail, Licensee first name, Licensee last name
•    Edition
•    License Type

Your License Administrator may obtain a merged license file by following the steps below.

1.    Log on to the Veeam My Account dashboard and go to License management >> Production Licenses(U4) (https://my.veeam.com/#/licenses/u4-licenses)

2.    If you are managing multiple accounts, please select the account you are performing the merge for. Once you have made the selection all the products under the account will be visible.
User-added image

3. To start the merge process, please use the License merge link:
User-added image

4.    Now you can select the Products and the contracts you want to merge. You can select several compatible product licenses to merge into one license file.
User-added image


5.    After you have selected the contracts you want to merge, you will have to click the Preview button to view the new licenses information.
User-added image

6.    After you have verified the information’s of the page you will have to use the “Merge Licenses” button to finalize the merge process.
 

More Information

1.    To revert the License Key merge operation, Customers may choose “Cancel merge” to destroy the merged license and revert to original product License Keys.
2.    License Key split option on the Customer portal is available to selected Customers only. All contract split operations require opening a licensing support case at https://my.veeam.com.
3.    Please note that the license auto-update feature does NOT correctly update merged licenses created on the license management portal. If you have enabled auto-update, disable it before installing a merged license from the license management portal.
4.    More info about the merge policy here
 

HCL - Infortrend - EonStor DS

$
0
0

Challenge

VeeamReadyRepo

Product Information:

Company name: Infortrend
Product Family: EonStor DS
Status: Veeam Ready - Repository
Classification Description: Verified backup storage that supports all Veeam backup and restore features.

Solution

Product Details:

Model number: DS 1016R2
Storage Category: 
Drive quantity, size, type: 16 - 6TB NL-SAS HDD
Storage configuration: 
Firmware version: 6.61F.10
Connection protocol and speed: FC, 8Gb
Additional support: All models and configurations of Infortrend EonStor DS-Series with specifications equivalent or greater than the above

General product family overview:

EonStor DS is a high availability SAN storage solution designed for enterprises. It’s hardware design features multiple form factors, flexible host boards to choose from, and stable, reliable modular design with high expandability; as for software, it comes with complete data services and easy-to-use management interfaces. It is ideal for all SAN environments and enterprise applications (such as backup). The whole product line is fast, flexible, and reliable, so that you can find the perfect storage device according to your performance or budget needs.

 

Veeam testing configuration:

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

Veeam Build Number: 9.5.0.1536

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)

How to merge Veeam licenses

$
0
0

Challenge

This article describes the process of merging Veeam licenses.


 

Cause

A license file installed in your Veeam software replaces the information from the previous license. A merged license file allows for increased socket capacity by combining licenses from multiple Support IDs.

Please note that the merged license key will use the earliest support expiration date of all product keys.

Important: Only License Administrators can merge licenses.

Solution

NOTE! Licenses can be merged only if the following terms match:

Perpetual License Keys

•    First name, Last name, Email, Company for Perpetual License Keys
•    Edition
•    License Type
•    Product name

Subscription License Keys

•    Licensee company, Licensee e-mail, Licensee first name, Licensee last name
•    Edition
•    License Type

Your License Administrator may obtain a merged license file by following the steps below.

1.    Log on to the Veeam My Account dashboard and go to License management >> Production Licenses(U4) (https://my.veeam.com/#/licenses/u4-licenses)

2.    If you are managing multiple accounts, please select the account you are performing the merge for. Once you have made the selection all the products under the account will be visible.
User-added image

3. To start the merge process, please use the License merge link:
User-added image

4.    Now you can select the Products and the contracts you want to merge. You can select several compatible product licenses to merge into one license file.
User-added image


5.    After you have selected the contracts you want to merge, you will have to click the Preview button to view the new licenses information.
User-added image

6.    After you have verified the information’s of the page you will have to use the “Merge Licenses” button to finalize the merge process.
 

More Information

1.    To revert the License Key merge operation, Customers may choose “Cancel merge” to destroy the merged license and revert to original product License Keys.
2.    License Key split option on the Customer portal is available to selected Customers only. All contract split operations require opening a licensing support case at https://my.veeam.com.
3.    Please note that the license auto-update feature does NOT correctly update merged licenses created on the license management portal. If you have enabled auto-update, disable it before installing a merged license from the license management portal.
4.    More info about the merge policy here
 

HCL - Fujitsu ETERNUS CS800 (S7)

$
0
0

Challenge

VeeamReadyRepo

Product Information:

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

*This Veeam Ready test was performed with storage having a configuration that includes SSD/Flash. As such, this classification only applies to similar 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: CS800 S7
Storage Category: Data Protection Appliance
Drive quantity, size, type: 2 – 1.2TB, SAS 10K RPM 2.5" | 6 – 960GB, SSD SATA 6Gb/s 2.5" | 36 – 10TB, SAS 7200 RPM 3.5"
Storage configuration: SSD disk configuration for MetaData (MD) storage only, with data storage located on 6x RAID6 (36 x 10TB SAS 7.2k RPM 3.5")
Firmware version: 3.5.0_S7
Connection protocol and speed: SMB, 10 GbE
Additional support: All models and configurations of CS800 S7 with specifications equivalent or greater than the above

General product family overview:

FUJITSU Storage ETERNUS CS800 is a turnkey data protection appliance and provides a simple and affordable solution for customers which follow a disk backup strategy with deduplication. The advanced deduplication technology reduces typical disk capacity requirements for disk to disk backup by up to 95%.

 

Veeam testing configuration:

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

Veeam Build Number: 9.5.0.1922

Job Settings:

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

Repository Settings:

Repository Type: Shared Folder (CIFS)
Align backup file blocks: Disabled (Default)
Decompress before storing: Disabled (Default)
Per-VM Backup Files: Enabled
 

Vendor recommended configuration:

Hardware Settings:

  • Jumbo frames on network interface used during testing

Support Partners Case Management

$
0
0

Challenge

A new feature on the ProPartner Portal allows all registered users of your organization to submit and manage Veeam support tickets on behalf of your customers. Previously, with Case Administrator feature only certain employees at a partner organization had rights to manage their customers’ support cases. And with this new feature, all registered members of your team now get access to your customer’s cases in only a few clicks.

This short video explains the main features of the new functionality and will walk you through its main steps.

Please note: to use this functionality you must have an active ProPartner registration.

Solution

Requesting rights to manage cases

To access this new feature you need to be logged into the ProPartner portal.

Find the desired contract and submit a request to manage cases by clicking the Request permission button. Once the request is submitted the button is replaced with Pending approval status, and an e-mail about the new request is sent to the Primary License Administrator of the selected contract.

User-added image
 

Approval of requests

The Primary License Administrator of the contract will receive an email notification about the new request to manage cases. Additionally, all requests will be visible to any License Administrators and can be Accepted or Declined in their My Account:

User-added image

Any users with the following roles on the contract can approve a request:

  • Primary license administrator

  • Secondary license administrator

  • License administrator

After the request is approved or declined, the user from the partner's account who submitted the request will receive a communication from Veeam about the request status.

 

Opening a case via the ProPartner Portal

Once the request is approved, ProPartner users will see an Open a Case button on the ProPartner page:
User-added image
Clicking the button will take you to a predefined Open a Case form.
Fill in the remaining required fields, click Next and submit the case as you normally would with any other case.

More Information

For any questions please feel free to reach out to supportmanagement@veeam.com

How to configure antivirus exclusions to prevent interaction with Veeam Backup & Replication

$
0
0

Challenge

This article documents antivirus exclusions that have been found to help prevent antivirus software from interrupting Veeam Backup & Replication communications with components such as proxies and repositories or with the guest OS of VMs that are being backed up or replicated.

Cause

In some rare instances antivirus can prevent certain executables, processes, or agents from being correctly deployed or leveraged from the Veeam server, proxy, repository, or even the guest OS.

Solution

Antivirus Exclusions:

Folders on the Veeam Server:

  • C:\Program Files\Veeam
  • C:\Program Files (x86)\Veeam
  • C:\Program Files\Common Files\Veeam
  • C:\Program Files (x86)\Common Files\Veeam
  • VBRCatalog ( [HKLM\SOFTWARE\Veeam\Veeam Backup Catalog] CatalogPath value)
  • NFS (Configured in each repository, stored in [HKLM\SOFTWARE\Wow6432Node\Veeam\Veeam NFS] RootFolder value)
  • C:\VeeamFLR\*
  • C:\Windows\Veeam
  • %programdata%\Veeam

Folder on Guest OS for VSS:

  • C:\Windows\VeeamVssSupport (folder might be missing, depends on backup job settings)
  • C:\Windows\VeeamLogShipper (folder might be missing, depends on backup job settings)

Folders on VMware Backup Proxies and CIFS Repository Gateway:

  • C:\Program Files(x86)\Veeam
  • C:\Windows\Veeam

Folders on Windows Repositories:

  • C:\Program Files(x86)\Veeam
  • C:\Windows\Veeam
  • %programdata%\Veeam
  • *Also include the path the backup files*

Folders on WAN Accelerator:

  • C:\Program Files(x86)\Veeam
  • C:\Windows\Veeam
  • *Path of WAN cache on WAN accelerators*

Files:

  • VeeamAgent.exe
  • VeeamAgent64.exe
  • *.vmdk
  • *.flat

Due to the complex nature of antivirus software some additional exclusions may be needed.
If your antivirus has a logging or history system please review this to see actions it may have taken that may affect Veeam Backup & Replication operations.

Release Notes for Veeam Management Pack 8.0 Update 6

$
0
0

Challenge

Release Notes for Veeam Management Pack 8.0 Update 6

Cause

Please confirm you are running Veeam Management Pack 8.0 prior to installing this update. You can check this in Operations Manager console under Administration | Management Packs, the build number should be 8.0.0.2218 or later.

To install the update, import the management packs through Operations Manager console > Administration > Management Packs > Import Management Packs.

To obtain Veeam MP 8.0 for System Center - Update 6, please download it here.

NOTE: It is important that you update Veeam Management Pack Core Services to Support TLS 1.2 Protocol for Update 6.

Solution

New in This Release
  • Additional Hypervisor support vSphere 6.7. VMware vSphere 4.0 and later (including vSphere 6, vSphere 6.5, vSphere 6.7 and vSphere 6.7 U1) 
  • Monitoring SQL Transaction Log Backup Job. Veeam MP separately monitors SQL Transaction Log Backup jobs running inside backup jobs with the enabled application-aware processing option. For this purpose, Veeam MP includes a new Veeam SQL Transaction Log Backup Jobs view and Veeam Backup: SQL Transaction Log Job Status monitor.
  • Improved performance of Morning Coffee Dashboards. In previous versions, Morning Coffee Dashboards tended to load slowly for large-scale environments. In Veeam MP 8.0 Update 6, the performance of Morning Coffee Dashboards has been significantly improved.
  • New metric for Veeam VMware Collector. Due to the Ops Mgr Health Service (Monitoring Agent Service) limitations that appear when a Veeam VMware Collector processes a large amount of data, it is required to distribute monitoring load among multiple Veeam VMware Collectors in large environments. To assess monitoring load on Veeam VMware Collectors more precisely, Veeam MP provides a new % Object Monitoring Load metric.
Resolved Issues
  • No monitoring for Hyper-V hosts that exceeded license limit. Veeam MP license limits the number of Hyper-V hosts enabled for monitoring in Ops Mgr. Earlier, if the number of licensed Hyper-V hosts was exceeded and new hosts were added to the Ops Mgr infrastructure, Ops Mgr automatically stopped monitoring the old infrastructure and started monitoring the newly added hosts. In Veeam MP 8.0 Update 6, the issue was resolved, and Ops Mgr continues monitoring the old infrastructure.
  • Ops Mgr event log shows excessive BackupCopyJobSessionFinished events. In previous versions, the Ops Mgr event log contained a large number of 3101 events caused by errors in backup copy job status collection process. In Veeam MP 8.0 Update 6, the issue was resolved.
Known Issues and Limitations
  • Collector Autodeploy limitations. If you use the Collector Auto-Deployment feature to automatically deploy Veeam VMware Collectors on Management Servers, keep in mind that it will install clear 8.0 version without patches. When installation completes, run the ISO\Update\VeeamMP80_Update6.exe installation file on each Veeam Collector to install patches.  
  • Veeam MP for Hyper-V stops collecting storage metrics. If a storage migrates to another volume, the storage performance collection will halt and Veeam MP will stop collecting the following metrics: Storage IOPS, Storage KB Total/sec, Storage Flush Count and Storage Error Count. Note that this issue does not affect migration between hosts. To work around the issue, restart the Ops Mgr agent after storage migration.

More Information

Should you have any questions, contact Veeam Support.

Veeam Backup & Replication upgrade fails with an error "Database version downgrade detected....Reboot and restart the setup"

$
0
0

Challenge

The upgrade to Veeam Backup & Replication U4 fails with "Database version downgrade detected....Reboot and restart the setup". You may find following error in the C:\ProgramData\Veeam\Setup\Temp\BackupSrvLog.log:

***Veeam***  SRV: [31.01.2019 11:39:43]:<00000001> [VEEAM] Database version has been incremented to <5186>
***Veeam***  SRV: [31.01.2019 11:39:43]:<00000001> [VEEAM] Executing version command (ContentType=[Schema], Version=<5186>)
***Veeam***  SRV: [31.01.2019 11:39:43]:<00000001> [VEEAM] Adding trusted hosts (InitialCatalog=[VeeamBackup], DatabaseVersion=<5186>)
***Veeam***  SRV: [31.01.2019 11:39:44]:<00000001> [VEEAM] [SQL|ERROR] declare @id uniqueidentifier;
***Veeam***  SRV: [31.01.2019 11:39:44]:<00000001> [VEEAM] [SQL|ERROR] set @id = '52107791-e0ff-4538-a26e-4717962aef77';
***Veeam***  SRV: [31.01.2019 11:39:44]:<00000001> [VEEAM] [SQL|ERROR] declare @usn bigint;
***Veeam***  SRV: [31.01.2019 11:39:44]:<00000001> [VEEAM] [SQL|ERROR] exec IncrementUsn @usn output;
***Veeam***  SRV: [31.01.2019 11:39:44]:<00000001> [VEEAM] [SQL|ERROR] BEGIN
***Veeam***  SRV: [31.01.2019 11:39:44]:<00000001> [VEEAM] [SQL|ERROR] INSERT INTO [dbo].[Backup.Model.HostSshFingerprint]
***Veeam***  SRV: [31.01.2019 11:39:44]:<00000001> [VEEAM] [SQL|ERROR] (
***Veeam***  SRV: [31.01.2019 11:39:44]:<00000001> [VEEAM] [SQL|ERROR] [id], [network_name], [accepted_fingerprint], [current_fingerprint], [public_key], [agent_id], [network_name_hash], [last_update_time], [usn]
***Veeam***  SRV: [31.01.2019 11:39:44]:<00000001> [VEEAM] [SQL|ERROR] )
***Veeam***  SRV: [31.01.2019 11:39:44]:<00000001> [VEEAM] [SQL|ERROR] VALUES  
***Veeam***  SRV: [31.01.2019 11:39:44]:<00000001> [VEEAM] [SQL|ERROR] (
***Veeam***  SRV: [31.01.2019 11:39:44]:<00000001> [VEEAM] [SQL|ERROR] @id, '<IP Address>', '', '', '', '00000000-0000-0000-0000-000000000000', '', '<Day>/<Month>/Year <time>', @usn
***Veeam***  SRV: [31.01.2019 11:39:44]:<00000001> [VEEAM] [SQL|ERROR] )
***Veeam***  SRV: [31.01.2019 11:39:44]:<00000001> [VEEAM] [SQL|ERROR] END;
***Veeam***  SRV: [31.01.2019 11:39:44]:<00000001> [VEEAM] [SQL|ERROR] GO
***Veeam***  SRV: [31.01.2019 11:39:44]:<00000001> [VEEAM|ERROR] Conversion failed when converting date and/or time from character string. (System.Data.SqlClient.SqlException)

Cause

This is a known issue and it is being actively investigated now.

Solution

In the meantime we suggest using the following workaround:
  1. Open Control Panel.
  2. Click on the Clock, Language, and Region link.
  3. Click on the Change date, time, or numbers formats link.
  4. Under the Formats tab, please set Format: English (United States)
  5. Click Apply.
  6. Click OK.

Path to NFS datastore has been changed after upgrade to Veeam Backup & Replication U4

$
0
0

Challenge

After upgrading to Veeam Backup & Replication U4, Veeam vPower NFS datastore location might be changed, because in Update 4 the disk with the biggest capacity is selected by default.

Cause

This is a known issue in the Veeam Backup & Replication U4.

Solution

Please update the path to Veeam vPower NFS datastore manually in the Backup repository wizard for each reposiotry. Feel free to refer to our helpcenter for more information.
Viewing all 4469 articles
Browse latest View live


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