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

Veeam Availability Orchestrator stops collecting vCenter asset information

$
0
0

Challenge

There is an issue with the embedded Veeam ONE component of Veeam Availability Orchestrator 1.0 release. The issue results in Veeam ONE not recognizing new VMware vCenter assets approximately 90 days after installation.

Cause

There is a synchronization issue between Veeam ONE Monitor and Veeam ONE Reporter components.

Solution

The issue can be easily resolved by following the steps below:

For new VAO installations:
Download the updated ISO image from our Veeam.com website. The ISO already contains the patch and can be installed normally.

For existing VAO installations:
1. Download VAO updater
MD5: 734167ff040d6b399970d5d57bf50f26
2. Run the updater

NOTE: The updater should be run on every Veeam Availability Orchestrator server.

The patch installation on an existing system can be confirmed by checking the modified timestamp on the following files: 
%PROGRAMFILES%\Veeam\Availability Orchestrator\Veeam ONE Reporter Server\SchedulingService.exe <created date 07.08.2018>
%PROGRAMFILES%\Veeam\Availability Orchestrator\Veeam ONE Reporter Web\Bin\ReporterApp.dll <created date 07.08.2018>

More Information

Should you have any questions, contact Veeam Support.

Backup configuration is not saved after configuring backup job

$
0
0

Challenge

After installing Veeam Agent for Microsoft Windows and configuring a backup job, the settings are not shown in the Control Panel, and Veeam Agent for Microsoft Windows keeps prompting to configure backup settings.

Cause

The Windows OS was installed with non-English region and culture settings. As a result, these settings were applied to the Windows system account.
Veeam Agent for Microsoft Windows is based on Microsoft .NET Framework which has some limitations in term of particular OS cultures

 

Solution

You will need to set Format to English (United States) for the system account.

Go to the Region settings (press Win + R > type intl.cpl > press Enter)

  1. On the Formats tab
    1. set Format to English (United States)
  2. On the Administrative tab
    1. click Copy Settings
      1. check that Format is set to English for Current user
      2. Enable the Welcome screen and system accounts checkbox
      3. Click OK to save settings and return to the Administrative tab.
  3. Click OK to close the Region settings and save settings.
  4. Restart your machine

Once the necessary changes are applied to the system account, a non-English Format can be set for the Current user account. Note, that the Format has to remain English (United States) for the system account.

More Information

Here is an example of a working configuration:

User-added image

How to configure Veeam Agent for Microsoft Windows email notifications for Gmail

$
0
0

Challenge

This article describes how to configure Veeam Agent for Microsoft Windows email notifications for Gmail account.

Cause

In some rare cases the ‘Access for less secure apps’ may need to be turned on > https://support.google.com/a/answer/6260879?hl=en
The following Gmail KB-article contains more details regarding SMTP settings which should be used > https://support.google.com/a/answer/176600?hl=en

Once everything is done, feel free to send a test message and make sure that everything is set up properly to finish the configuration.
 

Solution

Follow the steps below to configure email notification in a desirable way.

1. Open Veeam Agent for Microsoft Windows GUI and go to the ‘Setting’ tab.
User-added image
2. Tick the ‘Enable email notifications’ check box and click on the ‘Configure and test’ link.
User-added image
3. Fill all the fields and type your email account with its password.
User-added image
4.Click on ‘Show SMTP settings’ once you fill all the info.
User-added image
Use Gmail SMTP connection details to set it up.

SMTP server DNS name or IP address – smtp.gmail.com    
Port – 587
Username – your Gmail user name like ‘your_email_address@gmail.com’
Ensure that the ‘Use secure connection (SSL/TLS)’ checkbox is checked.
 

How to Configure Email Notifications in Veeam Agent for Windows

$
0
0

Solution

The process for configuring email notifications with Veeam Agent for Windows is documented here.

For information about SMTP server settings for Gmail accounts, see the following KB: https://www.veeam.com/kb2704

More Information

For issues specific to using Gmail or Google Apps Mail for notifications, please reference: https://www.veeam.com/kb1974

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 have any questions, contact Veeam Support.

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 * from dba_role_privs where granted_role='DBA';
 
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 * from dba_role_privs where granted_role='DBA';
 
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. 
 

Specified database is not valid

$
0
0

Challenge

The installation cannot be continued due to the error message:
"Specified database is not valid. Please choose Veeam ONE database or create a new database to proceed."

Cause

The error message occurs when you install Veeam ONE using previously created and in some cases migrated database the version of which is higher than the installer.

Solution

Follow the steps below:

1. Install Veeam ONE using a temporary database which will be created automatically once you start the installation. Make sure the database name is different from the default database name "VeeamOne" to avoid any conflicts with the original database in case it is located on the same SQL Server.
2. Change Veeam ONE database connection settings to connect previously created Veeam ONE database using Veeam ONE Settings Utility;
3. Remove temporary created database using SQL Server Management Studio.

More Information

Should you have any questions, contact Veeam Support.

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

How to move the Veeam Backup & Replication or Enterprise manager to another server

$
0
0

Challenge

You need to move Veeam Backup & Replication or Enterprise manager software and/or database to a new server.

Solution

Veeam Backup & Replication migration


Note: This section will refer to the server where Veeam Backup & Replication is installed prior to the move as the “old server”, and the location after the move as the “new server”.


There are two methods to perform Veeam Backup & Replication migration task:

 


Migrate using Configuration Backup

Perform the following steps on the old server:

  1. Stop and disable all jobs.
  2. Manually perform a configuration backup.
  3. Close Veeam GUI and stop all Veeam Services.

Perform the following steps on the new server:

  1. Install Veeam Backup & Replication with a brand new DB.
  2. Apply the latest patch to Veeam Backup & Replication: http://www.veeam.com/patches.html
  3. Make sure all local drives that were being used as repositories on the old server are now attached with the same drive letters on the new server.
  4. Perform configuration backup restore:
    Note: It will be necessary to re-enter the password for every account during restore of non-encrypted configuration backups.
  5. Run a test job to make sure everything moved correctly.

 


Migrate using SQL Backup

IMPORTANT: Use this option only if Configuration Backup is not available. If encryption was used on the previous installation, a newly installed backup server will not be able to decrypt such information if attached to the existing database, so any encrypted information will have to be supplied manually – existing encrypted backups have to be re-imported to provide the password.

Perform the following steps on the old server:

  1. Stop and disable all jobs.
  2. Close Veeam GUI and stop all Veeam Services.
  3. Create backup of the SQL database. (http://vee.am/kb1471)

    To find out where the VeeamBackup database is located, open regedit on the old server and navigate to: [HKLM\SOFTWARE\Veeam\Veeam Backup and Replication]
     
    There you will find 3 dword values:
    • SqlServerName
    • SqlInstanceName
    • SqlDatabaseName

 

Perform the following steps on the new server:

  1. Install Veeam Backup & Replication with a brand new DB.
  2. Apply the latest patch to Veeam. http://www.veeam.com/patches.html
  3. Make sure all local drives that were being used as repositories on the old server are now attached with the same drive letters on the new server.
  4. Restore the Veeam database to the instance on the new server or on a SQL server which will host Veeam DB.
    Click (here) for information regarding restoring databases.
  5. To associate Veeam with the restored database, please use the DBConfig Utility to change the Database that Veeam is connecting to.
  6. Restart Veeam Services to apply the changes.
  7. Open the Veeam console and using the “Manage Credentials” button from the main menu and check the passwords for every account to confirm they are up to date.
  8. Run a test job to make sure everything moved correctly.
 

Enterprise manager migration


Note: This section describes how to move the Enterprise Manager (EM) database to a different SQL if the EM is installed separetly from the Backup & Replication.


  1. Relocate VeeamBackupReporting DB to the new SQL server. See http://vee.am/kb1250
  2. On the Veeam Backup & Replication server, open the following directory:
    C:\Program Files\Veeam\Backup and Replication\Backup
  3. On the EM server, open the following directory:
    C:\Program Files\Veeam\Backup and Replication\Enterprise Manager
  4. Сopy the following files from the VBR folder to the EM one:
    • Veeam.Backup.Configuration.Tool.exe
    • Veeam.Backup.DBConfig.exe
    • Veeam.Backup.Tool.Core.dll
    • Veeam.Backup.Backup.UI.dll
  5. Run the copied ‘Veeam.Backup.DBConfig.exe’ as Administrator
  6. Follow the steps described here to connect the EM to the new DB location: https://helpcenter.veeam.com/docs/backup/hyperv/using_dbconfig_utility.html?ver=95

More Information

In situations where physical local storage is used please see the following KB that details how to relocate Veeam Backup and Replication backup file locations: https://www.veeam.com/kb1729

For steps on migrating the Veeam database to another SQL Instance or Server, please refer to KB1250.

VMware Cloud on AWS Support. Considerations and Limitations

$
0
0

Challenge

VMware Cloud on AWS is a vSphere environment running on AWS hardware, that needs some specific preparation to allow Veeam Backup & Replication v9.5 Update 3a or newer to work with it. Besides the below-listed preparation and limitations, you can interact with it within Backup & Replication like any other vSphere environment to backup, restore and replicate VM workloads.

Some of VMware features and permissions are not granted by default at the start of VMware Cloud on AWS (VMC). Thus, some depending Veeam Backup & Replication features will be limited or not operating. Depending on VMware update releases for VMware Cloud on AWS, the situation may change and the features from the table below may become available. Please contact your VMware administrator for timely update.

Solution

 Implementation step 1 - Backup & Replication  

  1. Use a new Windows Server and install Veeam Backup & Replication v9.5 Update 3a or newer if you do not have a Veeam Backup Server. The Server can run within any VMware cloud on AWS SDDC, AWS S3 or on-premises environments, if the network connection to the VMC vCenter/Veeam Servers potentially the VMs (for Guest processing) is possible.
  2. Add DNS network settings so that this Server can resolve Internet DNS names to be able to resolve the fully qualified domain name of the VMC vCenter server
  3. Check the below information carefully for any known limitations and configuration steps before you proceed.

Implementation step 2 - VMware Cloud on AWS

Firewall Configuration for vCenter connection

The Veeam Backup and Replication Server and Veeam proxy server should be connected to the VMware vCenter using HTTPS through TCP port 443. At VMware Cloud on AWS there is no need to open ports to the ESXi hosts itself. As the vCenter Server is by design of VMware Cloud on AWS on another network (Management Network), you need to configure one of the following 3 options:
 
  1. Usage of the vCenter public IP for customers with NSX-v (default) 
    • Open Port TCP 443 from Backup Server and Proxy Server to the predefined vCenter object on the Compute Network. User-added image
    • Allow the Compute Gateway Public IP to communicate over TCP 443 with the predefined vCenter object on the Management Network.
      User-added image
  2. Usage of a VPN tunnel for customers with VMware NSX-v 
    To be able to directly access the vСenter within VMC, please follow the VMC internal guidelines to create a VPN tunnel from the compute network to the management network: https://docs.vmware.com/en/VMware-Cloud-on-AWS/services/com.vmware.vmc-aws.getting-started/GUID-30BED7B3-D312-4DF3-BD7A-66F8D1C619DC.html
    Please update your DNS Servers to resolve the FQDN of the vСenter to its private IP address. If you want to use hosts entries on the Veeam Server for it, add them on all Veeam Backup and Proxy Servers.
    If your Backup & Replication (Management) Server is outside of the VMC cluster, please implement the same VPN connection for it.
  3. Usage of the local connection for customers with VMware NSX-t 
    NSX-t allows VMC customers to directly access the management network over the built-in firewall. TCP Port 443 needs to be opened from all Veeam Backup and Veeam Proxy Servers as a Source with the vCenter internal IP as a target.
    a) Configure DNS entry of the vCenter for local IP address usage.

    Go to your SDDC Management – Settings – vCenter FQDN and select the Private vCenter IP address. User-added image
    Hint: If you configure the vCenter DNS record for the internal IP address, you will lose VMC connection from Backup and Replication Server outside of VMC. You can use the local hosts file or any other DNS method to resolve the vCenter FQDN with the public IP address on the Veeam Server outside of VMC. Optionally, use the Public IP address for the VMC internal and external Veeam Server.

    b) Open firewall ports for vCenter Server access

    On the Management Network
    User-added image
    On the Compute Gateway
    User-added image


Implementation step 3 - add vCenter

Add vCenter to the Veeam console as described here: https://helpcenter.veeam.com/docs/backup/vsphere/add_vmware_server.html?ver=95
  1. Create a vCenter User with required rights (Active Directory linked mode) described here, or use the cloudadmin@vmc.local user.
  2. When adding a vCenter server, specify the fully qualified domain name (FQDN) that ends with vmwarevmc.com or vmc.vmware.com (depending on the URL shown in the VMC interface for the vCenter).
Implementation step 4 - add Veeam Proxy

For any VMware Cloud on AWS SDDC Cluster, roll out at least one Veeam Proxy Server to be able to process HotAdd / Virtual Appliance Backup Mode. The Backup & Replication itself can be used when installed at the SDDC Cluster (Proxy preinstalled). Please look at the Veeam documentation for details: https://helpcenter.veeam.com/docs/backup/vsphere/add_vmware_proxy.html?ver=95

Implementation step 5 - add Veeam Repository

VMware Cloud on AWS has only one accessible vSAN disk. It would not make sense to use that disk for production workloads and backups. An external Backup device needs to be added. Depending on the use case there are several ways to achieve this with different economic factors. Please find below an example of an Amazon S3 EC2 Linux Server (e.g. EC2 C4 Server with EBS ST1 storage) used as a backup target over the VMware Cloud on AWS integrated ENI network connection:

User-added image

To connect the EC2 Server(s) used as Veeam Repositories the following Firewall configuration is needed:
  1. On the Compute Network:
    1. Open TCP 22 (SSH) port from Veeam Backup server and Veeam proxy server to the Amazon VPC where the EC2 Server was installed. You can as well define the exact IP addresses of the repository server as Destination.
    2. Open TCP 2500-5000 ports for Veeam Data Transport in both directions for same servers. It is recommended to use the VMware Cloud on AWS integrated high throughput/low latency ENI network connection to avoid any traffic costs.User-added image
  2. Open the same ports on the Inbound Firewall of the Amazon EC2 server used as a repository server. As the Firewall Rule Source you should add all Veeam Backup Servers (including Proxy/Repository/MountServer/Console/…) instead of 0.0.0.0/0                                                                                                                                                                 User-added image

Implementation step 6 - add secondary backup target

It is suggested to create a backup copy to an additional place. Depending on the use case there are several ways to achieve this with different economic factors. Among other ways the following technologies can be used:
  1. Veeam Backup Copy Job to a second EC2 Server used as an additional Repository. The second EC2 Server can be placed on another AWS Availability Zone or AWS Geo Location.
  2. AWS Storage Gateway Software in VTL mode can be used to emulate a Tape Library to write data to S3. Veeam Backup to Tape Jobs can be used with it. For details see: https://www.veeam.com/wp-using-aws-vtl-gateway-deployment-guide.html
  3. Veeam Backup Copy Job to on premises or Veeam Cloud Connect (Enterprise). There is no special configuration needed for this use case beside network and firewall connections. For standard Repository usage on premises it is recommended to create a VPN tunnel from VMware Cloud on AWS to the on premises datacenter. This can be done by the VMC integrated VPN functionality, by Veeam PN or Third Party.
Additional Scenarios
  1. VMware Cloud on AWS used as Restore target. 
    1. Implementation steps 1-4 are needed.
  2. Veeam VM Replication.
    1.  Implementation steps 1-5 are needed. The Repository Server (when NOT used for Backups, can run within the VMware Cloud on AWS SDDC to store the Veeam Replication data. On premises to VMC, VMC to VMC and VMC to on premises is possible. Usage of Veeam Availability Orchestrator is possible in specific scenarios, see VAO deployment guide: https://helpcenter.veeam.com/docs/vao/deployment/welcome.html?ver=10

More Information

VMware Cloud on AWS specific problems and solutions:

Problem

Impossible to add the VMware Cloud on AWS vCenter server to the managed server, VMs within this vCenter are not visible in the list of VMs or an Error is displayed in the Veeam Jobs “Processing SQL Error: File does not exist or locked. …”

Solution

  1. Create a vCenter User with required rights (Active Directory linked mode) described here, or use the cloudadmin@vmc.local user.
  2. When adding a vCenter server, specify the fully qualified domain name (FQDN) that ends with vmwarevmc.com or vmc.vmware.com (depending on the URL shown in the VMC interface for the vCenter).


Problem

When working with Restore or VM Replication wizard, users may face some issues accessing VMware Cloud on AWS vCenter server. By design, VMware does not provide customers access to the background infrastructure and used datastores.

Solution

For proper operation, you can select the specific areas marked as “Workload” or “Compute”. Avoid using the non-accessible areas, for example:
  • vsanDatastore datastore
  • Management VMs folder
  • Mgmt-ResourcePool resource pool


Problem

Backup & Replication stop working after VMware Cloud on AWS was automatically updated to Version 1.3 or newer.

Solution

UPDATE: New VMware Cloud on AWS SDDC 1.3 or newer (including the latest version 1.5) requires updated Veeam Backup & Replication components. Please download Update 3a Veeam Backup & Replication 9.5 here


Problem

Some of the Backup & Replication Features are not working correctly because of limitations of the VMware Cloud on AWS environment (compared with a standard vSphere environment).

Solution

Affected Veeam FeatureLimitationWorkaround

Instant VM Recovery

Currently, VMware Cloud on AWS (VMC) does not allow for NFS usage

Use a combination of a Veeam backup job and replication job for proactive restore capabilities

Other OS File Level Recovery

Currently, VMC does not allow for NFS

Start Linux File-Level Recovery from a backup copy on-premises

Quick Migration

Quick Migration cannot migrate VMs to VMC if they are running

Use Veeam Replication and permanent failover to achieve similar functionality
For Free Edition, shut down the VM before migration

SureBackup, Sure Replica, OnDemand Labs, Virtual Lab

Currently, VMC  does not allow NFS and network manipulation

As for SureReplica, you can perform it if the replication target is a non-VMC vSphere environment (e.g., replicate VM from VMC to on-premises)

VM Guest Interaction and Windows File Restore by VIX or WebService API

Currently, VMC does not allow usage of VMware Webservice API

If you want to perform Veeam Guest processing or Windows File-Level Recovery, then connect to a VM over the network from Veeam Backup & Replication

VM Replication ReIP

ReIP is not available on VMC

 

Windows Dynamic disks are not supported

Currently, VMC does not allow to process dynamic disks at Hot-Add (Virtual Appliance mode) backup

VMware will provide a hotfix for this soon

Non-Unicode VM names

Currently, VMC does not allow non-Unicode characters for VM names within their APIs used ad VMC

 

VM Replication-based File Level Recovery

 

Use file restore from backups or use a VM replica on a non VMC environment to start the File recovery

How to view your Support ID number

$
0
0

Challenge

When opening a case via the Customer Support Portal, you are prompted to enter a Support ID.

User-added image

Solution

A Support ID number (sometimes referred to as a Contract Number) is a string of 8 numerical characters with typically one or two leading zeros (e.g., 01234567) and can be most easily located in one of three ways.
 
1. Viewing the License Information through the User Interface of a Veeam application.
If you have already installed a production license to your Veeam application, you may find the Support ID in the License Information window of that application. 
Please see the “More Information” section below for guides to accessing the License Information window in various Veeam applications.
 
2.  Veeam Customer Portal
https://my.veeam.com/#/licenses/production

In the Production Licenses section of the Veeam Customer portal, you can view the Support IDs of all licenses associated with your Company Account, as well as any additional licenses for which your login is the License Administrator.

User-added image

3. A Veeam production .lic license file
 
If you have received a Veeam .lic license file, you may open that license file using a text editor (such as Notepad) to view the contents.  Please use caution as altering the contents of the license file will render the license unusable; only the filename may be changed.  The Support ID is typically located after “Support ID=” and usually near to the bottom.

User-added image

 

More Information

In addition to having your Support ID number, you will need to be the License Administrator or a Case Administrator in order to open a case on the Veeam Customer Portal.  More information here: https://www.veeam.com/kb2211
 
Below are links to individual user guides describing how to locate the License Information window for the most recent releases of various Veeam products at the time of this KBs publication or update.
 
Veeam Backup & Replication 9.5
(User Guide for VMware vSphere - https://helpcenter.veeam.com/docs/backup/vsphere/install_license.html?ver=95 )
  • From the main menu, select License.
 Veeam ONE 9.5
(Deployment Guide - https://helpcenter.veeam.com/docs/one/deployment/install_license.html?ver=95 )
  • Launch Veeam ONE Monitor.
  • On the toolbar, click Help and select License Information.
 Veeam Agent for Microsoft Windows 2.2
(User Guide - https://helpcenter.veeam.com/docs/agentforwindows/userguide/settings_mode.html?ver=21 )
  • Double-click the Veeam Agent for Microsoft Windows icon in the system tray or right-click the Veeam Agent for Microsoft Windows icon in the system tray and select Control Panel.
  • At the top of the window, click the About tab.
  • In the Version section, click Manage license and edition.
 Veeam Agent for Linux 2.0.1
(User Guide - https://helpcenter.veeam.com/docs/agentforlinux/userguide/license_manage_cmd_view.html?ver=20 )
  • You can view information about the installed license. Use the following command:
veeamconfig license show
 Veeam Backup Enterprise Manager
(User Guide - https://helpcenter.veeam.com/docs/backup/em/viewing_changing_current_license.html?ver=95 )
  • Log on to Veeam Backup Enterprise Manager using an account with the Portal Administrator role.
  • Open the Configuration tab.
  • Open the Licensing section on the left of the Configuration view.
 
Veeam Availability Console 2.0 Update 1
(Administrator Guide for Service Providers - https://helpcenter.veeam.com/docs/vac/provider_admin/install_license.html?ver=20u1 )
  • Log in to Veeam Availability Console as a Portal Administrator.
  • For details, see Accessing Veeam Availability Console.
  • At the top right corner of the Veeam Availability Console window, click Configuration.
  • In the menu on the left, click Licensing.
  • On the License Usage tab, click the license status link.
Veeam Management Pack 8.0 Update 5 for System Center Veeam Backup for Microsoft Office 365 2.0
(User Guide - https://helpcenter.veeam.com/docs/vbo365/guide/vbo_lic_management.html?ver=20 )
  • Go to the main menu > License.

How to get a Support ID - SEE UPDATED KB LINK BELOW

Migrating Veeam ONE Server to Another Machine

$
0
0

Challenge

Migration of Veeam ONE server is needed to install (upgrade) the product on a supported OS.

Cause

The previous version of Veeam ONE was installed on one of the operating systems that is no longer supported by the most recent Veeam ONE version.

Solution

Before you upgrade, be sure to perform a backup of the corresponding SQL database for Veeam ONE, so that you can easily go back to the previous version in case of issues with the upgrade.

NOTE: It is recommended that you have all the recent Windows updates on the Veeam ONE server.

If Veeam ONE is installed on one of the operating systems that is no longer supported by the most recent Veeam ONE version, use procedure provided below:
 
Deployment with a local SQL Server:
 
1.      Stop all Veeam ONE services. 
2.      If there were any changes made to Veeam registry configuration, export these registry hives manually:
[HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam ONE Monitor\Service]  
[HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Reporter Enterprise] 
3.      Backup Veeam ONE database using SQL Management Studio. 
4.      Install all system prerequisites on the new Veeam ONE server. This procedure can be performed by running Veeam ONE setup wizard.  
5.      Download and install SQL Server 2012 R2 or above on the new Veeam ONE server.
6.      Restore the backed up Veeam ONE database (step 3) to the new server via SQL Management Studio.
7.      Run Veeam ONE installation wizard on a supported OS and point to existing SQL Server instance on the database configuration step. Veeam ONE database will be upgraded automatically in case the database version is not higher than the release version of Veeam ONE. If the database version is higher, follow this KB article.
NOTE: Veeam ONE installer performs the release version installation first, the Update file installs later during the installation process.
8.      Launch Veeam ONE Monitor Client and retype connection account settings to all monitored hosts.
9.      Import Veeam ONE configuration registry keys to the new server. This step is not required if Veeam ONE installation is running with the default settings.
10.    Update Veeam ONE Reporter and Business View websites URLs in case the DNS name has changed. For more information see the following guides: Website Settings, Shortcuts.
11.    Restart Veeam ONE services.
 
Deployment with a remote SQL Server:
 
1.      Stop all Veeam ONE services. 
2.      If there were any changes made to Veeam registry configuration, export these registry hives manually:
[HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam ONE Monitor\Service]  
[HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Reporter Enterprise] 
3.      Backup Veeam ONE database using SQL Management Studio to be able to revert to the previous version of the database in case of issues with the upgrade.
4.      Run Veeam ONE installation wizard on a supported OS and point to existing SQL Server instance on the database configuration step. Veeam ONE database will be upgraded automatically in case the database version is not higher than the release version of Veeam ONE. If the database version is higher, follow this KB article.
NOTE: Veeam ONE installer performs the release version installation first, the Update file installs later during the installation process.
5.      Launch Veeam ONE Monitor Client and retype connection account settings to all monitored hosts.
6.      Import Veeam ONE configuration registry keys to the new server. This step is not required if Veeam ONE installation is running with the default settings.
7.      Update Veeam ONE Reporter and Business View websites URLs in case the DNS name has changed. For more information see the following guides: Website Settings, Shortcuts.
8.      Restart Veeam ONE services.
 

More Information

Should you have any questions, please contact Veeam Support.

How to get a Support ID - SEE UPDATED KB LINK BELOW

Release Notes for Veeam Backup & Replication 9.5 Update 3

$
0
0

Challenge

Release Notes for Veeam Backup & Replication 9.5 Update 3

Cause

Please confirm you are running version 9.5.0.580, 9.5.0.711, 9.5.0.802, 9.5.0.823, 9.5.0.1038 or 9.5.0.1335 prior to installing this update. You can check this under Help | About in Veeam Backup & Replication console. After upgrading, your build will be version 9.5.0.1536.
To upgrade from 9.0 or earlier, download the full ISO image and consult the user guide's upgrade section.

If you use Veeam ONE to monitor Veeam Backup & Replication or Veeam Cloud Connect, be sure to install Update 3 for Veeam ONE 9.5 first.
If you are a tenant of a cloud provider, please contact your provider before upgrading to ensure the provider has applied Update 3 on their end.

Providers can be on either 9.5.0.1335 (RTM) or 9.5.0.1536 (GA).

Solution

As a result of on-going R&D effort and in response to customer feedback, Update 3 includes hundreds of enhancements and bug fixes, the most significant of which are listed below.

New features

Built-in agent management. Veeam Agent for Microsoft Windows and Veeam Agent for Linux can now be deployed and managed directly from the Veeam Backup & Replication console, adding support for physical and cloud workloads protection.
  • Maintain complete control of data protection for ALL your virtual, physical and cloud workloads by managing both hypervisor-based and agent-based backups natively through the Veeam Backup & Replication console.
  • Ensure no Windows or Linux computers are left unprotected by centrally deploying Veeam agents with automated host discovery via dynamic protection groups based on Active Directory containers, or CSV files exported from your existing CMDB system.
  • Protect Microsoft Windows Server Failover Clusters, such as SQL Server failover clusters and SQL Server AlwaysOn Availability Groups, with new agent-based failover cluster backup jobs – and transparently restore guest files and application items from cluster backups.
Insider protection for Veeam Cloud Connect. Ensure the ability to recover your data following a cyber-attack by having your Veeam Cloud Connect service provider protect your data against insider attacks. Service providers can now enable protection of your backups against accidental or malicious deletion directly from the Veeam Backup & Replication console. These deletions are often executed either by hackers who have breached the tenant’s network perimeter and obtained powerful credentials with a brute force attack (with the intention of deploying ransomware on the production servers), or by disgruntled employees.

Data location tagging. Ensure data sovereignty compliance required by various regulations, such as the General Data Protection Regulation (GDPR), by tagging production infrastructure and backup infrastructure objects with locations. Location tags are used to prevent accidental errors when configuring backup and replication jobs or performing out-of-place restores, by issuing a warning when an action may result in a data sovereignty violation and producing audit trails whenever such action is confirmed. Additionally, new Veeam ONE reports use location data to help you prove compliance.

IBM Spectrum Virtualize Integration. Reduce the impact on production environments and achieve lower recovery time and point objectives through new storage snapshots integration for IBM Storwize, IBM SAN Volume Controller (SVC) and any other IBM Spectrum Virtualize based storage system, such as Lenovo Storage V series or IBM/Cisco VersaStack.

Universal Storage Integration API. The new storage array integration framework included in Veeam Backup & Replication starting with this update enables select storage partners to build integrations of their primary storage systems with advanced Veeam Backup & Replication functionality that leverages storage snapshots.

Platform support
  • Microsoft Azure. Direct Restore to Microsoft Azure functionality has been updated to support 4TB virtual disks, Azure Germany and Azure China.
  • Microsoft SQL Server 2017 support for application-aware processing on Windows-based virtual machines, including transaction log backup and point-in-time restores; and as a backend configuration database for the Veeam Backup & Replication itself.
  • Microsoft Windows 10 Fall Creators Update support as guest virtual machines, and for installation of Veeam Backup & Replication and all of its components.
  • Microsoft Windows Server 1709 support as guest virtual machines, and for installation of Veeam Backup & Replication remote components.
  • Microsoft Windows Server Hyper-V 1709 support as a hypervisor host, including support for virtual hardware version 8.2 virtual machines.
  • VMware Cloud on Amazon AWS support allows protecting VMs running in the cloud, and migrate or replicate workloads from on-prem vSphere deployment to VMC (and vice versa).
  • VMware vCloud Director 9.0 compatibility.
Storage support
  • Cisco HyperFlex support of deployments with multiple HyperFlex clusters under a single vCenter Server.
  • DELL EMC Data Domain integration now supports Data Domain systems running DD OS 6.1
  • HPE 3PAR StoreServ integration has been extended to include snapshot-only backup jobs; ability to retain primary storage snapshots created by backup jobs with a different retention policy; and ability to perform backup from storage snapshots from secondary 3PAR array running in Peer Persistence mode.
  • Hyperconverged infrastructures (HCI) deployments can now leverage the new option to force the load balancer to use Direct NFS backup proxy located on the same vSphere host with the processed virtual machine, to avoid stressing storage replication network with backup traffic . To enable this functionality, create EnableSameHostDirectNFSMode (DWORD) value under HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication registry key on the backup server. The value is used to controls failover behavior when Direct NFS proxies if the proxy on same host is unavailable: 1 allows failover to other Direct NFS proxies, and 2 restricts failover to NBD only.
  • LTO-8 support for all tape-related functionality.
Backup Copy
  • Backup mapping for agent backup files is now supported to enable scenarios such as backup seeding.
  • Restore from backup copies. When initiating a restore from local user interface, Veeam Agent for Microsoft Windows and Veeam Agent for Linux will now provide the ability to pick a restore point stored in the secondary repository, should backup files in the primary repository be missing.
Hyper-V
  • Hyper-V 2016 VMs with non-snapshottable disk such as disks connected via in-guest iSCSI initiator can now be processed by backup and replication jobs, with unsupported disks skipped and their content not included in a backup or replica. If you’d rather prefer the job to fail on such VMs (legacy behavior), create HyperVIgnoreNonSnapshottableDisks (DWORD) value under HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication registry key on the backup server and set it to 0.
Oracle
  • New Oracle 12.2 account types support includes Microsoft Windows Group Managed Service Accounts (gMSA) and Microsoft Windows Virtual Accounts.
VMware
  • VMDK resize operation will no longer result in resetting CBT data for all virtual machine disks, but rather for the resized disk only.
  • Non-encrypted NBD transport is again available for vSphere 6.5, significantly improving backup and replication performance comparing to previously forced NBDSSL.
Veeam Cloud & Service Provider Partners
9.5 Update 3 includes many new features and enhancements for service providers offering Veeam Cloud Connect services. For the full list of these enhancements and bug fixes, please see this topic on the private VCSP forum. Not a member of the VCSP forum? Click here to join.

This update also resolves the following common support issues:
  • Backup Copy jobs should no longer copy weekly GFS fulls twice under certain circumstances, and should now correctly extend copy interval when processing active full backups.
  • vSphere Web Client plug-in should no longer display "Session expired" errors during its configuration when using vCenter Server Appliance 6.0
  • Linux-based backup repository registered under root account should no longer crash when Data Mover crashes for whatever reason.
  • Building VM list operation accelerated up to 4 times for Hyper-V jobs configured to use SCVMM tags.
  • Reliability enhancements with Hyper-V backups in off-host backups and guest processing logic.
  • File-level recovery in the Enterprise Manager should now work more reliably from non-Windows virtual machines, and after source Hyper-V VM was migrated to another host within SCVMM.
  • Prefix for temporary storage snapshots created by backup jobs was changed from “Veeam_” to “VeeamAUX_” due to many users using the original prefix in day to day operations, which made Veeam Explorer for Storage Snapshots skip the corresponding snapshots.
  • Direct Restore to Microsoft Azure should now tolerate short term Azure connectivity disruptions, uses more firewall friendly port 443 by default, and supports Azure accounts with multiple directories (use AzureDefaultTenantIdGUID registry value to set GUID of the directory to use).
  • VeeamZIP retention should now work correctly with all system locales.

More Information

Please note that Veeam Backup & Replication 9.5 Update 3a is now available and contains all the features/resolved issues from Update 3. Please click here for more information.

WinRM Service cannot process the Request

$
0
0

Challenge

When adding an On-Prem or Hybrid organization to Veeam Backup for Office 365 we get the following error:
User-added image

Cause

The On-Premises Exchange server does not have Powerhsell authentication enabled. 

Solution

On the On-Premises Exchange server, you need to enable Basic Authentication (See Below)
User-added image
  1. Open the Exchange Admin Center and Click on Servers
  2. Choose the Virtual Directories tab
  3. Click on Powershell (Default Web Site) or Powershell (Exchange Web Services web site)
  4. Choose authentication
  5. Enable “Basic Authentication”

Configure the VeeamPN appliance with a static IP address

$
0
0

Challenge

If DHCP is not available or if you want to assign a static IP address to the on premises VeeamPN appliance.

Cause

If DHCP is not available you will need to manually assign a IP Address. Setting this with ifconfig will lose its configuration on reboot of the appliance

Solution

First, you will need to edit the “interfaces” file

Log on to the network hub appliance using the root (the default password is “VeeamPN”, but you may have changed this) 
#vi /etc/network/interfaces

Add the following to the configuration file:  
auto ens160
iface ens160 inet static
address xxx.xxx.xxx.xxx
netmask xxx.xxx.xxx.xxx
gateway xxx.xxx.xxx.xxx
dns-nameservers xxx.xxx.xxx.xxx
dns-nameservers xxx.xxx.xxx.xxx

Replcaing “xxx.xxx.xxx.xxx” with the ip addresses.  If the section for “auto ens160” already, clear that and replace it with the format above.

Hit “esc” then “:wq” to save the file.  

Then edit the resolve.conf file:
#vi /etc/resolv.conf

And add your dns servers:
nameserver xxx.xxx.xxx.xxx # Replace with your nameserver ip
nameserver xxx.xxx.xxx.xxx # Replace with your nameserver ip

Hit “esc” then “:wq” to save the file.  

Restart the networking on your system with:
# systemctl restart networking

Now the IP address should remain through rebooting the appliance.  
 

vCenter Migration Utility

$
0
0

Challenge

If a Virtual Machines MoRef is changed due to migration to new vCenter / inventory change in vCenter, you would receive the error "Object "vmname" is not found".  Please see KB1299 for more details.

This utility is designed to assist in re-mapping the MoRef ID's of the Virtual Machines you are backing up and/or replicating using Veeam Backup & Replication, so that backup incremental chains remain intact, after an inventory change in VMware vSphere vCenter. Do not run any jobs before using migration tool otherwise migration process won't be possible.

Please note that this utility is provided as a courtesy, and is not officially supported by Veeam Technical Support.  Use at your own risk.
Cloud Connect jobs are not supported, please perform Active Full backup.


Important! If you are migrating to a 6.5U2 VCSA, VMware has a new migration utility, which could preserve existing VM MoRef IDs:
https://blogs.vmware.com/vsphere/2016/09/vcenter-server-migration-tool-vsphere-6-0-update-2m.html

https://blogs.vmware.com/vsphere/2017/01/vcenter-server-appliance-6-5-migration-walkthrough.html
This VMware utility only works for a 5.5 VC to a 6.5U2 VCSA!

Cause

Veeam Backup & Replication tracks Virtual Machines in its jobs by a Managed Object Reference ID (MoRef), which will change when moved to another vCenter, or removed and re-added to inventory.

Solution

Please download this bundle: tool and instructions.  Before using this tool, it is highly recommend to take a configuration backup of your VeeamBackup database
Please note that the utility will work only with a source vCenter migration. If Replication target vCenter is changed, you will need to manually map source VMs to their replicas

If you use the VMware provided VCSA Migration tool, you will need to remove and re-add VMs to jobs manually through the new VCSA after adding it to Veeam. A script may be provided at a later date to assist with this process.

VMware highly recommends migrating to a VCSA, as they are phasing out the Windows based vCenter.
https://blogs.vmware.com/vsphere/2017/08/farewell-vcenter-server-windows.html

 

More Information

MD5 checksum for the archive: 23934878fe5082a0e5f0481e76bfffde

Appliance Mode (Hotadd) Requirements and Troubleshooting

$
0
0

Challenge

Appliance mode (HotAdd) fails or configuration assistance is needed. 
The following is shown in the statistics window while processing a VM or could be found within the logs:
"HotAdd is not supported for this disk, failing over to network mode"

Solution

Requirements:

  1. If the Veeam Proxy being used to process the source VM is on a VMFS 3 datastore it must be formatted with proper block size to be able to mount the largest virtual disk of the hot added VMs:
    • 1MB block size – 256GB maximum file size
    • 2MB block size – 512GB maximum file size
    • 4MB block size – 1024GB maximum file size
    • 8MB block size – 2048GB maximum file size
  2. The Proxy being used to back up the VM must be a Virtual Machine on a host that is able to access the datastore where the source VM’s disks are stored
  3. For vSphere 5.1 the maximum supported VMDK size is 1.98 TB
  4. For vSphere 5.5 and older the maximum supported VMDK size is 62 TB
  5. HotAdd is a SCSI feature and does not work for IDE disks
  6. VMware Tools must be installed and up-to-date on the Veeam server and any Veeam proxies
  7. Datastore needs sufficient space for a VM snapshot
  8. Backup and restore of SATA disks in the Virtual appliance mode is supported if you use VMware vSphere 6.0 and later

Known Issues:

  • If the VM disk resides on a Vvol the Hot Add Proxy VM's configuration files must also be on the same Vvol.
  • Hotadd may fail if any disk was created with a newer hardware version than the VM being backed up. For example, if a disk was moved from a hardware version 8 VM to a hardware version 7 VM. To resolve, upgrade the hardware version of the VM.
  • A single SCSI controller can have a maximum of 15 disks attached. To run multiple concurrent jobs with more than 15 disks, you need to add more SCSI controllers to your Veeam Proxy server that is responsible for hot adding the disks. (kb.vmware.com/kb/1037094)
  • In case of standalone host connection (no vCenter added to the console), you can only hot add disks of VMs which are located on the same host as the proxy server.  This may require additional proxy servers to be configured on each host in the environment.
  • Hotadd may fail if you are trying to back up the VM through the host added as a standalone server into Veeam Backup Infrastructure but actually being managed by vCenter. The following error message can be found in the source agent log:
    "Reconfigure attempt failed for VM "" with Vmomi::MethodFault::Exception ("vim.fault.HostAccessRestrictedToManagementServer")"
  • If you plan to process VMs that store disks on the NFS datastore, you must deploy the backup proxy on the same ESX(i) host where these VMs reside.
  • Virtual Appliance backup job fails after you’ve cloned or restored your VBR server. The reason for that is incorrect UUID reference for Veeam Backup VM which can be found in the following registry key of the Veeam server. Please see http://www.veeam.com/kb1332
  • Hot Add fails if VM disks being backed up don't have unique ddb UUIDs across the Vcenter, for example if such VMs were deployed from a single template to different hosts.  Please refer to this Vmware article for details: http://kb.vmware.com/kb/2006865

Troubleshooting:

More Information

Please contact Veeam Technical Support for further assistance.

Microsoft SQL Server processing with Update 3a

$
0
0

Challenge

After upgrading Veeam Backup & Replication 9.5 to Update 3a, you may notice  warning or failures on the following operations:

  • Back up of SQL Server transaction logs;
  • Truncation of SQL Server transaction logs;
  • Collection of SQL instances metadata for Veeam Explorer for SQL (VESQL)

While the error message varies depending on actual operation, there is a common error thrown in the job sessions:

"Logon failure: the user has not been granted the requested logon type at this computer. Code: 1385"

 

In addition, backup jobs for SQL Servers VM with Backup logs periodically option enabled for transaction log backup may complete with warning message:

Unable to update SQL backupset for instance SQLEXPRESS : Code = 0x80040e09 Code meaning = IDispatch error #3081 Source = Microsoft OLE DB Provider for SQL Server Description = The UPDATE permission was denied on the object 'backupset', database 'msdb', schema 'dbo'.

 

Cause

The first issue is due to a change in the required rights of account used for Application-Aware Processing.

Update 3a requires that this account has the following user right assigned:

  • Logon as a batch job granted.
  • Deny logon as a batch job not set.

Second issue is caused by changes in the permission error handling logic of Veeam Backup & Replication.

Solution

Correct SQL Permissions

The permissions of the account specified for use with Application-Aware Processing need to be adjusted on the SQL server. More information can be found in the updated system requirements.

Note: If the permissions have been updated as documented and the issue persists, please create a support case. https://my.veeam.com/#/open-case/step-1

 

Workaround

If unable to correct the permissions of the account used by Veeam Backup & Replication when interacting with the SQL server, you may install this hotfix which changes the application processing logic for SQL Servers in the following manner:

  1. After failing to logon as a batch job, the job will immediately retry using interactive logon (pre-U3a method) before failing completely.
  2. Warning about backupset update failure was changed to info event which additionally explains the issue in better details:
    Transaction logs backup will not be possible due to insufficient permissions to update backupset for SQL instance: %SQLInstance%

To install the hotfix:

  1. Stop Veeam jobs and Veeam services
  2. Make a backup copy of the following files, from the backup server and all guest interaction proxies:
    • C:\Program Files\Veeam\Backup and Replication\Backup\Veeam.Backup.Core.dll
    • C:\Program Files\Veeam\Backup and Replication\Backup\Veeam.Backup.VssProvider.dll
    • C:\Program Files\Veeam\Backup and Replication\Backup\VSS\sql\VeeamLogShipper_X64.exe
    • C:\Program Files\Veeam\Backup and Replication\Backup\VSS\sql\VeeamLogShipper_X86.exe
    • C:\Program Files (x86)\Veeam\Backup Transport\GuestInteraction\VSS\sql\VeeamLogShipper_X64.exe
    • C:\Program Files (x86)\Veeam\Backup Transport\GuestInteraction\VSS\sql\VeeamLogShipper_X86.exe
    • C:\Program Files\Veeam\Backup and Replication\Backup\VSS\VeeamGuestHelpers\VeeamVssSupport2008R2_X64.dll
    • C:\Program Files\Veeam\Backup and Replication\Backup\VSS\VeeamGuestHelpers\VeeamVssSupport2003_X64.dll
    • C:\Program Files\Veeam\Backup and Replication\Backup\VSS\VeeamGuestHelpers\VeeamVssSupport2003_X86.dll
    • C:\Program Files\Veeam\Backup and Replication\Backup\VSS\VeeamGuestHelpers\VeeamVssSupportXP_X86.dll
    • C:\Program Files (x86)\Veeam\Backup Transport\GuestInteraction\VSS\VeeamGuestHelpers\VeeamVssSupport2008R2_X64.dll
    • C:\Program Files (x86)\Veeam\Backup Transport\GuestInteraction\VSS\VeeamGuestHelpers\VeeamVssSupport2003_X64.dll
    • C:\Program Files (x86)\Veeam\Backup Transport\GuestInteraction\VSS\VeeamGuestHelpers\VeeamVssSupport2003_X86.dll
    • C:\Program Files (x86)\Veeam\Backup Transport\GuestInteraction\VSS\VeeamGuestHelpers\VeeamVssSupportXP_X86.dll
  3. Replace the files listed in the previous step with those found in the hotfix package
  4. Start Veeam services on server
Viewing all 4477 articles
Browse latest View live