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

Web plugin troubleshooting guide

$
0
0

Challenge

Web plugin is a new feature, which has little in common with other features and it may seem to be difficult to troubleshoot. It is suggested to follow this guide rather than trying to analyze error message, as it is not very informative and almost always misleading.

 

Solution

Known issues and solutions

Unable to connect Enterprise Manager
Make sure that Enterprise Manager and RestAPI services are running. Please disable proxy in Internet Explorer on vCenter and EM servers, disable firewalls.
If it doesn't help, then review plugin log on vCenter, if you see something like "Certificate error: Remote servers certificate thumbprint does not match the thumbprint stored in the application settings" then
1. Perform plugin uninstall with cleanup(see section below)
2. Reinstall Enterprise Manager and select required certificate during installation

Invalid SSO Token
Steps to resolve:
1. Make sure, that EM and RestAPI services are running under domain account with local administrator priveleges.
2. Add user(that is used to log on to vSphere web client) in EM Roles explicitly.
If it doesn't help, then analyze SSO token.

Server error: null
Plugin files are not completely installed, corrupted or 2 versions of plugin are installed. If you have vShpere 5.5 then plugin might have old version.
Steps to resolve:
1. Verify plugin version installed in EM(Configuration - vCenter Servers) and EM version(EM - configuration - about - Veeam Backup Enterprise Manager Service). For vSphere 5.5 it should be not lower than 7.0.0.764. If needed, apply the latest patch once again. If Enterprise Manager and Veeam B&R are installed on different servers, make sure that the latest patch is installed on both servers.

2. Perform Plugin uninstall with cleanup
3. Install plugin

Installation fails with message in EM "Check if there is an existing one already installed" and null reference exception in EM log
In IIS on EM make sure that SSL certificate is assigned to Veeam site.


Generic troubleshooting guide

If the issue is not listed in known issues section or it didn't help, then follow this guide before escalating a ticket.
1. Disable proxy in IE and firewall both on EM and VC
2. Verify that EM version is current (EM - configuration - about - Veeam Backup Enterprise Manager Service) and install latest patch if needed. In case of upgrade, uninstall plugin from EM, restart vSphere web client service and install it again.
3. Add user(used to log on to VC) to EM roles explicitly
4. Make sure that RestAPI and EM services are running under domain account with local admin priveleges

Check if RestAPI service is available and responding:
1. Login to EM server and open in browser https://<em-server>:9398/web. You should receive an XML. Username and password may need to be entered. You can safely ignore untrusted certificate warning.
2. If this page doesn't open, check if RestApi service is started
3. If service is started, run netstat -abn from command line to check if port 9398 is listened by Veeam.Backup.EnterpriseService.exe
4. Try to open "http://<em-server>:9399/web", if this page opens while "https://<em-server>:9398/web" doesn't - you need to re-install SSL certificate for RestAPI (see corresponding chapter below - RestAPI certificate change)

If nothing, listed above helps:
1. Perform plugin uninstall with cleanup(see section below)
2. Reinstall EM
3. Install plugin
If the above steps do not resolve the issue, please contact Veeam Support.


Thoubleshooting steps

Plugin uninstall with cleanup
1. Uninstall plugin from EM
2. Restart vCenter Web Client Service. On windows server from services.msc console, on VC appliance from Vcenter Management web page
3. Remove all pieces of web plugin, that were not removed. Open SSH session to VC appliance and remove all enties that are returned by find / -name '*veeam*'. On windows server remove all files and folders containing veeam in %programdata%\vmware and %programfiles%\VMware

SSO token analyze
1. Open Svc.VeeamRestAPI.log
2. SSO token is Base64 encoded. Copy encoded text between "Failed to authorize user. SSO token: [" and closing "]" into notepad and remove all occurrences of "\n" (replace to empty string)
3. Decode resulting Base64 string. You can use http://www.base64decode.org/ for that.
4. In the resulting xml look for tag "saml2:Issuer". There is a URL to the VC SSO service. Verify if the URL points to the VC. Try opening it from Veeam server. Response file in XML format should be opened or downloaded, depending on browser settings. Certificate not trusted error can be safely ignored. If the URL is wrong, then customer should reconfigure SSO.

RestAPI certificate change
To view all SSL certificates assigned on different ports, run command prompt on EM server "netsh http show sslcert".
Locate 2 records:
0.0.0.0:9443 (stands for Enterprise Manager)
0.0.0.0:9398 (RestAPI service)
1. Copy "Application ID" value from the 0.0.0.0:9398 section
2. Copy "Certificate Hash" value from 0.0.0.0:9443 section
3. Execute "netsh http delete sslcert ipport=0.0.0.0:9398" to delete existing cert
4. Execute "netsh http add sslcert ipport=0.0.0.0:9398 certhash=<hash> appid=<id>"(where <id> and <hash> are values, gathered before) to set new certificate

More Information

Required logs
1. (From EM) Svc.VeeamBES.log
2. (From EM) Svc.VeeamRestAPI.log
3. (From VC) VMWare web client log(logs location on VC - http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2004090
4. (From VC) For vSphere 5.1 or older, web plugin logs from VC. Should be located in the same folder, where VMWare Web Client logs are. For vSphere 5.5 there is no dedicated Veeam Plugin log, info is written in Web Client log instead

5. (From VC) For vSphere 6 please see - https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2110014


 

The tasks array included at least one null element

$
0
0

Challenge

You are missing a segment of topology or a certain piece of performance information. The vmspi.log (default location: C:\Program Files\Veeam\Veeam Virtualization Extensions for System Center\Collector\Log) contains the following entries:

+** [VP038] buildInventory failed [***], The tasks array included at least one null element.
+** [VP050] performanceDaemon The tasks array included at least one null element.

Cause

In complex and highly distributed environments collector threads are stalled.

Solution

The hotfix ensures that stalled threads are processed properly. Download the hotfix here.

Follow these steps to apply the fix.
  1. Stop Veeam VMware Collector service.
  2. Make a backup of VeeamCollector.exe (default path: C:\Program Files\Veeam\Veeam Virtualization Extensions for System Center\Collector).
  3. Unpack the downloaded .zip and replace VeeamCollector.exe with the executable from the archive.
  4. Start Veeam VMware Collector service.

 

More Information

If you have any questions, contact Veeam Support.

Domain Controller starts up in Safe Mode

$
0
0

Challenge

After doing a full Virtual Machine restore, Instant Recovery, or testing of a Replica, you will find that the Virtual Machine boots up in what appears to be safe mode. 

When the Domain Controller boots for the first time it is actually in Active Directory services restore mode.

Cause

This is normal for this to happen as we're booting from a backup file, however it should reboot automatically.

Solution

Login with the Directory services restore mode account (typically .\administrator) and open a command prompt and run the following:
bcdedit /deletevalue safeboot
shutdown -t 01 -r
Afterwards it should reboot in normal mode.

 
 

More Information

Please reference the Microsoft Knowledge Base Article below for further details:

http://technet.microsoft.com/en-us/library/cc816897(WS.10).aspx

For a complete guide of how to restore a Domain Controller from a Veeam Backup please see this KB:

https://www.veeam.com/kb2119

How to migrate a SQL database

$
0
0

Challenge

This step-by-step article describes how to move Microsoft SQL Server user databases and the most common SQL Server components between computers that are running SQL Server.
 
The steps that are described in this article assume that you will not move the master, model, tempdb or msdb system databases. The steps provide different options for you to transfer logins and the most common components contained in the master and msdb databases.
 
For information about the specific items not transferred when you follow the steps in this article, see the "More information" section.
 
Note: For Microsoft SQL Server 2008, refer to the "Managing Metadata When Making a Database Available on Another Server Instance" topic at the following in SQL Server 2008 Books on Line Web site:  http://msdn.microsoft.com/en-us/library/ms187580.aspx
 
Note: Data migration from SQL Server 2000 to Microsoft SQL Server 2000 (64-bit) is supported. You can attach a 32-bit database to a 64-bit database by using the sp_attach_db system stored procedure or the sp_attach_single_file_db system stored procedure, or by using backup and restore in the 32-bit Enterprise Manager. You can move databases back and forth between the 32-bit and the 64-bit versions of SQL Server. You can also migrate data from SQL Server 7.0 by using the same methods. However, downgrading data to SQL Server 7.0 from SQL Server 2000 (64-bit) is not supported. A description of each method follows.

Solution

In Veeam Backup & Replication v8 and higher the DBConfig Utility can be used to change the DB that Veeam is attempting to connect to, rather than editing the registry. http://helpcenter.veeam.com/backup/80/vsphere/index.html?dbconfig_utility.html

If SQL instance that Veeam Backup & Replication will connect to uses SA authentication, the DBConfig utility must be used.

Here is the Microsoft KB describing the procedure: http://support.microsoft.com/kb/314546

Please ensure that the account you are installing Veeam Backup on has at least db_owner rights on this database after it is moved.
 
After your database is moved successfully, install Veeam Backup & Replication on the desired machine and point it to the database that you have just moved.

If Veeam Backup & Replication is already installed, please change the following registry keys:

HKEY_LOCAL_MACHINE\SOFTWARE\VeeaM\Veeam Backup and Replication\SqlDatabaseName
HKEY_LOCAL_MACHINE\SOFTWARE\VeeaM\Veeam Backup and Replication\SqlInstanceName
HKEY_LOCAL_MACHINE\SOFTWARE\VeeaM\Veeam Backup and Replication\SqlServerName

 
HKEY_LOCAL_MACHINE\SOFTWARE\ Wow6432Node\VeeaM\Veeam Backup and Replication\SqlDatabaseName
HKEY_LOCAL_MACHINE\SOFTWARE\ Wow6432Node\VeeaM\Veeam Backup and Replication\SqlInstanceName
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\VeeaM\Veeam Backup and Replication\SqlServerName
 

Task fails with error: Application is Shutting Down

$
0
0

Challenge

Jobs of any type fail with the error, “Application is shutting down.” For example:
 
Application is shutting down. Failed to download disk. Shared memory connection was closed. Failed to upload disk. Agent failed to process method {DataTransfer.SyncDisk}
 
BackupSynthesizedStorageToTape failed Application is shutting down. Unable to receive file. Application is shutting down.
 
In Event Viewer on the Veeam Backup & Replication server, a time change of several minutes is recorded in the System log a few minutes before the error occurs:
 
SEVERITY:Informational
SOURCE:Microsoft-Windows-Kernel-General
EVENT ID:1
DESCRIPTION:System time changed from 2016-03-31T12:06:22.375327200Z to 2016-03-31T12:12:23.623952000Z.

 

Cause

The Veeam Backup Service uses a system of timed leases as part of monitoring the many processes it manages. Usually this error involves a five minute lease for the VeeamAgent processes (Data Movers). When the Veeam Backup Service is operating normally, this lease is continually renewed. If the lease expires, the associated process is shut down.
 
Typically the lease will expire either because the system time has changed by several minutes, or because a problem communicating with the Veeam Backup Configuration Database has prevented the Veeam Backup Service from renewing the lease.

Solution

On VMware virtual machines, VMware Tools will periodically synchronize the system time with the ESXi host. If the time on the host differs from the NTP server used by Windows, the system time will repeatedly shift between the two different times. The best solution is to synchronize the time on the ESXi host, the Veeam Backup & Replication server and/or the domain controllers to the same source. If this is not possible, you should disable VMware Tools time synchronization for the Veeam Backup & Replication server.
 
As a quick but incomplete workaround, you can run the following from the command line on the Veeam Backup & Replication server:
"c:\Program Files\VMware\VMware Tools\VMwareToolboxcmd.exe" timesync disable
 
If time synchronization does not appear to be the problem, please contact Veeam Support.

 

More Information

VMware KB: Timekeeping best practices for Windows, including NTP
 

Backup to Data Domain fails with “Error: calling system(), returns nonzero. Err: 5040 Failed to connect to storage.”

$
0
0

Challenge

When preparing storage for backup you receive the following error message: "Error: calling system(), returns nonzero. Err: 5040 Failed to connect to storage"

Cause

The Data Domain chooses to use a different NIC than configured. Veeam is unable to communicate with the appliance as a result.
 
This is visible in the job logs:
 
Info     Preparing storage '[REDACTED].vbk' for write. Is optimized for de-duplication media 'False'.
Info     [AP] (9150) command: 'prepStorageForWriteEx\nddboost://[REDACTED].vbk\n8192\n0\n'
Info     [AP] (9150) error: calling system(), returns nonzero. Err: 5040

Solution

Re-add the repository to Veeam Backup and Replication with the production network IP address.

More Information

EMC has documentation on this error message, though it does not pertain directly to Veeam; see below. For more in-depth assistance when troubleshooting this issue, it is recommended to contact EMC support.
 
https://community.emc.com/docs/DOC-26481

Veeam Explorer for Exchange (VEX) Restore Failure - HTTP Error 501 – Load Balancer

$
0
0

Challenge

The following KB is only relevant if a Load Balancer is being used.
 
When attempting to use the “Restore to <email>” function the restore fails with “HTTP Error 501”.
 
The following will be found in the logs:

 
Item restore failed: The request failed with HTTP status 501: Invalid Request.
Error: ExplorerManagementService: Failed to handle OnFinishItemRestore event (sessionId = ‘Unique_Identifier’)
Restored item with the specified identifier does not exist
Error: Restored item with the specified identifier does not exist

Cause

This happens because when VEX detects the CAS server it sees the load balancer instead of the actual CAS.

Solution

Instead of restoring to the original location, select “Restore to” and then manually change the CAS server to the FQDN of the Exchange CAS server.
 
Alternatively you can point the load balancer hostname/FQDN to the IP of the exchange with a hosts entry. 


 

Topology construction failing due to a NullReferenceException

$
0
0

Challenge

Management Pack fails to build the environmental topology. The vmspi.log (default location: C:\Program Files\Veeam\Veeam Virtualization Extensions for System Center\Collector\Log) contains the following entries:
 
+** System.NullReferenceException: Object reference not set to an instance of an object. at nworksCore.TopologyNode.Clone()

Cause

Some host hardware objects may fail to return mandatory properties, such as NIC MAC address or NIC name. In this case Veeam Colelctor would fail to process such objects.
 

Solution

The hotfix prevents Veeam Collector from crashing and provides additional output about the object with missing properties. Download the hotfix here.

Follow these steps to apply the fix.

  1. Stop Veeam VMware Collector service.
  2. Make a backup of VeeamCollector.Core.dll (default path: C:\Program Files\Veeam\Veeam Virtualization Extensions for System Center\Collector).
  3. Unpack the downloaded .zip and replace VeeamCollector.Core.dll with the executable from the archive.
  4. Start Veeam VMware Collector service.

More Information

If you have any questions, contact Veeam Support.

VDDK error: 13 - Troubleshooting

$
0
0

Challenge

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

Solution

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

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

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

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

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

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

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

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

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

 

More Information

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

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

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

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

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

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

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

 

SQL VSS Writer is missing: databases will be backed up in crash-consistent state and transaction log processing will be skipped

$
0
0

Challenge

Job reports warning "SQL VSS Writer is missing: databases will be backed up in crash-consistent state and transaction log processing will be skipped"
Running vssadmin list writers shows that SqlServerWriter in not in the list.

Cause

There are different causes of the issue:
  • the SQL instance have databases with names ending in a space character. 
  • the account under which SQL VSS Writer service is running doesn't have sysadmin role on a SQL server
  • SQL VSS Writer service stuck in an invalid state

Solution

Depending on a particular cause:
  • Please rename the database to a new name (without a space in it)
  • Grant the SQL VSS Writer service user a sysadmin role (Instructions in KB here here: https://www.veeam.com/kb1978)
  • Restart SQL VSS Writer service (Instructions in KB here herehttps://www.veeam.com/kb2041)
  • In the case of SBS machines that are also Domain Controllers, ensure that the SQL Writer is running as a domain administrator and not local system
  • Allow the SQL Writer service account access to the Volume Shadow Copy service via the registry:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VSS\VssAccessControl
    If the DWORD value “NT SERVICE\SQLWriter” is present in this key, it must be set to 1.
    If the Volume Shadow Copy service is running, stop it after changing this registry value. Do not disable it.
     

VMware CBT Data Corruption

$
0
0

Challenge

Possible data corruption in backups after extending disk size past a 128GB boundary on VMWare.

Cause

According to VMWare KB kb.vmware.com/kb/2090639, CBT may return an incorrect list of VM disk sectors when a software runs QueryChangedDiskAreas("*").

This issue occurs when expanding a virtual disk (vmdk) file with Change Block Tracking (CBT) enabled. This may cause CBT to incorrectly calculate the in-use blocks in the vmdk file.
 
Note: The amount of space the virtual disk is extended is not relevant, the increment of space by which a virtual disk is extended is not relevant. The virtual machine has this issue when its disk is grown past any 128GB boundary in absolute size. The issue is triggered at other sizes which are a power of 2 from 128GB up. For example: 256GB, 512GB, and 1024GB.

Solution

VMware has released patches for ESXi 5.0,5.1, and 5.5 to fix this issue, please see VMware KB article kb.vmware.com/kb/2090639. Their patch is NOT retroactive and CBT must still be reset, their patch will only prevent it from occurring moving forward after applying the Patch/Update.
 
The solution implemented in to Veeam Backup & Replication v8 and the hotfix for Veeam Backup & Replication v7 are only workarounds. They function by detecting if a VM’s disk size has changed between job runs. This means if the VM is already affected by this CBT corruption issue it will not be corrected automatically.
 
Note: Remember that regardless of your Veeam Backup & Replication version, we can only addresses CBT corruption for new virtual disk extensions that occur after a VM was been backed up or replicated by Veeam at least once. It is therefore advised that you should reset CBT manually for all VMs that may have been impacted. Below is a script to do this with the VMs powered on.
 
 ──────────────────────────────────────────────────────────
Veeam Backup & Replication v7
──────────────────────────────────────────────────────────
 
Apply the following hotfix to protect your backups.
 
1. Make sure you are running Veeam Backup and Replication 7.0.0.871 (patch 4) otherwise obtain a patch vee.am/kb1891
2. Stop all Veeam services
3. Replace DLL's in ‘C:\Program Files\Veeam\Backup and Replication’ with DLL's from the hotfix package
4. Start Veeam services
 
──────────────────────────────────────────────────────────
Veeam Backup & Replication v8 and Later
──────────────────────────────────────────────────────────
 
Veeam Backup and Replication 8 has a built-in solution for this issue. Veeam Backup & Replication resets CBT for any resized VMware disk to prevent corruption. If ESXi hosts are patched against this issue, this behavior may no longer be desirable.  To disable automatic CBT reset upon virtual disk size change, create the following registry value on the Veeam Backup Server (requires v8 Update 2 or later):

Key: HKLM\SOFTWARE\Veeam\Veeam Backup and Replication
Type: REG_DWORD
Value name: ResetCBTOnDiskResize

Set this DWORD value to 0. To apply the registry change, make sure no jobs or restores are running, then restart the Veeam Backup Service.


──────────────────────────────────────────────────────────
Reset all VMs with CBT Enabled
──────────────────────────────────────────────────────────
The following script has been created to expedite the process of Resetting CBT on all VMs that presently have CBT enabled.
This script will only run against VMs that are powered on and have no snapshots on them.
This script is provided as is, and may cause disruption within the virtual environment as it performs a snapshot creation and deletion.
This script may require you to alter the current PowerShell execution policy.
www.veeam.com/download_add_packs/vmware-esx-backup/kb1940/


The following commands can be used to reset CBT for all VMs where it is presently enabled.
(Run these one line at a time after connecting to the vCenter Server via VMware PowerCLI.)
 
Get the VMs with CBT enabled:
    $vms=get-vm | ?{$_.ExtensionData.Config.ChangeTrackingEnabled -eq $true}
 
Create a VM Specification to apply with the desired setting:
   $spec = New-Object VMware.Vim.VirtualMachineConfigSpec
   $spec.ChangeTrackingEnabled = $false
 
Apply the specification to each VM, then create and remove a snapshot:
   foreach($vm in $vms){
   $vm.ExtensionData.ReconfigVM($spec)
   $snap=$vm | New-Snapshot -Name 'Disable CBT'
   $snap | Remove-Snapshot -confirm:$false}
 
Check for success:
   get-vm | ?{$_.ExtensionData.Config.ChangeTrackingEnabled -eq $true}
 
Note: After CBT reset the following job run will take longer to complete.

 

More Information

The following is from VMware’s KB article:

Frequently Asked Questions:
 
Is there a way to determine if a virtual disk has been expanded?
Customers should rely on their own change control records to determine if a virtual disk has been expanded. This information is not tracked in the virtual machine.
 
Are virtual machines grown in smaller increments affected?
The amount of space the virtual disk is extended is not relevant, the increment of space by which a virtual disk is extended is not relevant. The virtual machine has this issue when its disk is grown past any 128GB boundary in absolute size. The issue is triggered at other sizes which are a power of 2 from 128GB up. For example: 256GB, 512GB, and 1024GB.
 
Checking if CBT is enabled:
•In the home directory of the virtual machine, verify if there is a vmname-ctk.vmdk file for one or more virtual hard disks.
•To Query the advanced configuration parameters for the Virtual Machine:
  1. Right-click the virtual machine and click Edit Settings.
  2. Click the Options tab.
  3. Click General under the Advanced section and then click Configuration Parameters. The Configuration Parameters dialog opens.
  4. Search for the ctkEnabled parameter entry for each disk and note if it is enabled or not.
 Note: The VDDK API call configSpec.changeTrackingEnabled = new Boolean(true); can enable/disable CBT on the fly. In this case, it is not required to power off the virtual machine to change the CBT configuration as taking and deleting a snapshot can apply these settings.
 

SureBackup Fails After MS Update KB3139914

$
0
0

Challenge

SureBackup script tests fail as seen below:
 

Info     [SureBackup] [VMNAME] [ScriptTests] Begin 'Predefined script 1: name DNS Server, starting...'
Error    Failed to create proces
s with net logon (ERROR_ENVVAR_NOT_FOUND) (System.Exception)
 
This is the DNS Script test specifically. The various script tests will have different names, however the error will remain constant.

Cause

Microsoft KB3139914 has been installed; it pertains to the secondary logon service.

Solution

There are three possible solutions:
  1. Uninstall the update if possible.
  2. Leave credentials blank as a workaround. This entails a recreation of the Application Group or Linked Jobs as at present there is no way to remove credentials from the VM options in either of these, once they have been set.
  3. Support has a hotfix that can be implemented to address this issue without removing credentials or the update. Note that this update can only be applied if you are running Veeam v9 update 1 (9.0.0.1491)

More Information

https://support.microsoft.com/en-us/kb/3139914

Installation Fails with Patched Database

$
0
0

Challenge

When installing Veeam Backup & Replication, selecting an existing configuration database fails due to the following error message:
 

Unable to use database VeeamBackup, because it was created with a later version of Veeam Backup and Replication.
 
OR
 
The Configuration Database Connection Settings utility is unable to select a database due to the following error message:
 

Unable to use database VeeamBackup, because it was not created with current version of Veeam Backup and Replication.
 
In older versions of the software, or if the configuration database location is changed via the registry, no error message appears, but the Veeam Backup Service fails to start.

Cause

When Veeam Backup & Replication is updated, the configuration database is upgraded and its version number is changed. The updated database is not compatible with the Generally Available version of the software.
 
For example, Veeam Backup & Replication v9 GA (9.0.0.902) is upgraded to v9 Update 1 (9.0.0.1491), and then uninstalled. In this scenario, attempting to reinstall from the v9 ISO using the existing configuration database will fail. This is because the database version is greater than the latest version supported by the software.

Solution

Recommended Method:
 
If Veeam Backup & Replication is already installed, apply the latest update.
 
If it is not installed:

  1. Choose a new database name during installation. An empty database will be created with this name.
  2. Once installation has completed, apply the latest update.
  3. Switch from the empty database to the original configuration database using the Configuration Database Connection Settings utility.
 
To delete the empty database after installation, use SQL Server Management Studio.
  1. In Object Explorer, connect to the instance containing the empty database (such as localhost\VEEAMSQL2012).
  2. Expand Databases, right-click the empty database, and then click Delete.
  3. Confirm the correct database is selected, and then click OK.
 
 

Legacy Method:
 
The version number of the configuration database can be reverted with the following query:
 
Use VeeamBackup
UPDATE [Version] SET current_version = <see table below>
 
Build numbercurrent_version
6.5.0.109633
7.0.0.6901179
8.0.0.8171870
9.0.0.9022754
 
Once the version number is reverted, it is possible to install using the existing database. However, the software cannot be used in this configuration: it must immediately be updated to the same or later version that was previously installed. Otherwise, data corruption or unexpected behavior may occur.
 
Certain updates alter the database schema in a way that requires an additional change to the Version table before the update can be installed:
 
Updatecurrent_version
v7 Patch 4 (7.0.0.871)1200
v8 Update 3 (8.0.0.2084)2022

 
Do not attempt to revert to a previous release of the software (such as to v8 from v9).

More Information

How to apply a SQL script 
 
If there may be other problems with the configuration database, try restoring from configuration backup. It is recommended to create a configuration backup prior to updating the software.
 
ISOs containing updated versions of the software (maintenance releases) are not available. For more information on this topic, consult the Community Forum.


 

Backup Copy – Animation of Retention

$
0
0

Challenge

This article is intended to document how Backup Copy’s retention is enforced.

Solution

──────────────────────────────────────────────────────────
Backup Copy Retention – Simple Retention Policy
──────────────────────────────────────────────────────────
To maintain the desired number of restore points, Veeam Backup & Replication uses the following rotation scheme:
 
1. At the first synchronization interval, Veeam Backup & Replication copies the first restore point — full backup — to the target backup repository.
 
2. At every next synchronization interval, Veeam Backup & Replication adds a new restore point — incremental backup — to the chain on the target backup repository. This happens until the number of restore points in the backup chain reaches the number specified in the retention policy settings.
 
3. After the new restore point is added, the allowed number of restore point is exceeded. Veeam Backup & Replication transforms the backup chain to make room for the most recent restore point.
 
The backup chain transformation is performed in the following way:
 
1. Veeam Backup & Replication re-builds the full backup file to include changes of the incremental backup following the full backup. More specifically, it injects data blocks from the first incremental backup in the chain into the full backup. This way, a full backup ‘moves’ one step forward in the backup chain.
 
2. The first incremental backup is removed from the chain as redundant: its data has already been injected into the full backup and so the full backup file contains the same data as this incremental restore point.
 
User-added image
 

Within this animation the lettered squares represent blocks on a disk.
 
──────────────────────────────────────────────────────────
Backup Copy Retention – “GFS” Retention Policy
──────────────────────────────────────────────────────────
 
GFS restore points are not created in a separate task. Veeam Backup & Replication re-uses a full backup created in the regular backup cycle and propagates it to the appropriate tier.
 
For an in-depth explanation of this please see:

https://helpcenter.veeam.com/backup/vsphere/backup_copy_gfs_weekly_cycle.html
 
For example below the following settings are used:
 
User-added image
 


Within this animation the lettered squares represent blocks on a disk.
User-added image


 

Enterprise Manager Install fails with Patched Database Error

$
0
0

Challenge

If the Veeam Backup Enterprise Manager software is moved, or needs to be reinstalled and it was previously patched it errors out with the following error:

User-added image

Cause

The SQL database that is being reused contains table entries that mark it as having been used with a newer version the version of BEM that is being installed.

Solution

 If you wish to start with a clean installation:
•Remove the existing VeeamBackupReporting DB to allow a fresh DB to be created.

──────────
 
If you wish to preserve existing historical information within BEM:
• Modify the existing VeeamBackupReporting DB to be seen as an earlier version, using SQL queries below.
 
Note: We recommend backing up your database prior to making any changes. To change the version number:

 
1. From SQL Management Studio, connect to the instance containing the Veeam configuration database (default name is VeeamBackupReporting)
2.  Expand “Databases”
3.  Right-click “VeeamBackupReporting” > New query.
4.  Paste the appropriate query (below) and press “execute” or F5.
 
# Veeam Backup & Replication v7
Use VeeamBackupReporting
UPDATE [Version] SET current_version = 568
UPDATE [Version] SET Fill_version = 341

 
# Veeam Backup & Replication v8
Use VeeamBackupReporting
UPDATE [Version] SET current_version = 670
UPDATE [Version] SET Fill_version = 568


# Veeam Backup & Replication v9
Use VeeamBackupReporting
UPDATE [Version] SET current_version = 849
UPDATE [Version] SET Fill_version = 713

 
After install completes be sure to run the most recent patch. This can be found at: http://www.veeam.com/patches.html.
 

Deduplication Appliance Best Practices

$
0
0

Challenge

Performance or deduplication ratio is low when backing up to a deduplication enabled storage appliance from Veeam Backup & Replication. 
Please note that following article does not pertain to ExaGrid Storage or EMC DataDomain. If you use either of these please see the corresponding articles:
If you are using ExaGrid Storage, please see https://www.veeam.com/kb2056
If you are using EMC DataDomain, please see https://www.veeam.com/kb1956

Cause

The default options within Veeam Backup & Replication are intended for non-deduplication storage.

Solution

It is advised to configure the job as following when backing up to a deduplication appliance:

  • Use “Incremental”
  • Uncheck “Enable synthetic fulls” 
  • Check “Perform active full backups periodically”
  • Uncheck “Enable inline  data deduplication”
  • Change the Compression Level to “Dedupe-friendly”
  • Change Optimize for to “Local target (16TB+ backup files)”
Veeam Backup & Replication v8

User-added image
User-added image



 

More Information

  Forever Forward Incremental, Synthetic Full, and Reversed Incremental operations will perform poorly with deduplication devices because the backup files that have been written to the storage previously must be interacted with during these operations. The act of reading existing data on deduplication  device is slow because each block requested must be rehydrated and uncompressed to be read. With DataDomain deduplication appliances, however, it is possible to leverage DataDomain's own mechanism of updating file blocks' metadata internally, and consequently achieve greater performance with Synthetic Full. New full backup files can then be created without physically moving data into the file, but rather by synthesizing them from the existing data.
 
The process of rehydration and uncompressing during read operations from the deduplication storage will also impact the performance of all restore operations.
 

Contact your storage vendor to inquire about further specific details to optimize Veeam Backup & Replication to work with their storage solution.
 
 

EMC Data Domain Storage with Veeam Backup & Replication: Configuration Best Practices and Performance Expectations

$
0
0

Challenge

This article documents general performance expectations, best practices, and configuration advice, when using an EMC Data Domain appliance with deduplication as a repository for Veeam Backup & Replication.

Solution

For further information regarding how Veeam Backup & Replication works with EMC Data Domain DDBoost please review:
http://helpcenter.veeam.com/backup/80/vsphere/deduplicating_appliance_emc.html
 
Performance Expectations
 
EMC Data Domain Deduplication Storage Systems provide both high compression and deduplication ratios so that data can be kept for extended periods.  When a Data Domain is configured as a repository for Veeam Backup & Replication, write performance may vary depending upon the particular EMC Data Domain Deduplication System model, protocol, and backup infrastructure architecture.
 
When attempting to read data from a Data Domain it must rehydrate and decompress each block, for this reason operations which read from the Data Domain will perform slower than non-dedupilcated storage, this is more noticeable with operations which use random I/O. All restores will occur as fast as the environment can accept new information, and as fast as the Data Domain can decompress and rehydrate the blocks.
 
For quick recovery you may consider using fast primary storage and keeping a several restore points (3-7) for quick restore operations such as Instant Recovery, SureBackup, Windows or Other-OS File restores since they generate the highest amount of random reads. Then use the DataDomain as a secondary storage to store files for long term retention. If an EMC Data Domain Deduplication System will be used as primary storage, it is strongly suggested to leverage alternative restore capabilities within Veeam Backup & Replication such as Entire VM restore and VM files restore. This may result in faster recovery capabilities when used with EMC Data Domain Deduplication Systems than Instant Recovery and File Level Restore operations.
 
Instant Recovery
  • This type of restore can be effected adversely by the aforementioned limitations of a Data Domain appliance, and also the type of VM being restored. Highly transactional VMs will require more IOPS from the Data Domain during the Instant Recovery than others. With this in mind you can expect to only be capable of running only a few Instant Recoveries simultaneously. Instant Recovered VMs that are started from a backup file stored on a Data Domain may react or start slowly as the majority of their read operations will be hindered by the Data Domain.
  • For VMware users it is highly advised when performing an IR that the user select to have virtual disk updates redirected to a high performance Datastore. This will improve performance by caching written blocks to low latency storage.
  • It is advised that if the VM is intended to be made permanent that the VM be migrated to production storage as soon as possible after the Instant Recovery has begun.

File Level Restores
When performing Veeam Backup & Replication File Level Restore (FLR) capabilities slow recovery times may be experienced.  During Veeam FLR recovery capabilities, a significant amount of read activity occurs when accessing the Veeam “service data” metadata for each individual file as the Veeam backup files are not arranged in sequence.  This read activity must be performed to determine the location of the data block(s) associated with each file during granular restore sessions.  This significant level of random access is not recommended with archive tier storage devices because they are designed for optimal performance with sequential read operations.  Veeam recommends implementing EMC Data Domain Deduplication Storage Systems as a secondary target for these use cases as the more random read operations, the slower the restore will be with EMC Data Domain Deduplication Systems.
  • The backup browser may take longer than usual to open if an increment is selected and furthermore by that increments distance from the full restore point.
  • Navigating between folders within the Backup Browser may take additional time as each folder’s content must retrieved from the backup file to display it.

Backup
  • Reverse Incremental performance will be very poor due to its highly random I/O.
    Note: When the Backup Job is configured with a DDBoost repository, Veeam Backup & Replication will prevent Reversed Incremental from being selected by the user.
  • Synthetic Full creation will be very slow to a Data Domain, unless using DDBoost.
  • Synthetic Full with Transforms are not advised.

Backup Copy
  • A retention longer than 30 is not advisable as restore operations will diminish in performance.
  • The Health Check option may take a very long time as it is performing a read operation.

Replication
  • Using the Datadomain to store Replica metadata is not advisable.
    Note: Veeam Backup & Replication will prevent the user from selecting a DDBoost repository.
 
Veeam Backup & Replication Configuration

Parallel processing (global option):
This option significantly accelerates the backup process and decreases the backup window since virtual disk data is gathered simultaneously.  It also dramatically increases fragmentation in the backup files causing high random read for any restore operation. The greater volume of VMs or disks processed simultaneously will increase fragmentation and result in slow restore times. You may consider disabling Parallel Processing, this will decrease backup performance, but increase restore performance.

Storage optimization (job option):
Setting the storage optimization to Local 8TB+ has been shown to improve the effectiveness of Data Domain’s deduplication. The larger this value is, the smaller the preparation phase will be for a backup task and less memory will be used to keep storage metadata in memory.  However, the larger value may cause slowness in aforementioned restore operations due to the fact that Veeam will need to read entire blocks (ex. 8MB, the largest block size available in Veeam Backup & Replication v8) even for requests kilobytes in size. This results in redundant portions of data being read but not needed for restore.

Inline-deduplication (job option):  
​Since EMC Data Domain Deduplication Systems have excellent hardware deduplication and compression capabilities, it is highly advised that Veeam built-in deduplication be disabled to decrease load on the backup proxy.

Decompress backup block before storing(repository option):
Veeam strongly recommends enabling this option so that raw data is sent to the EMC Data Domain Deduplication System, leveraging its global deduplication and compression capabilities. Leaving Veeam compression enabled may significantly impact EMC Data Domain deduplication capabilities resulting in high load and slow backup jobs.
 
Backup Mode
  • For CIFS/NFS presented repositories Forward incremental mode with periodic Active full backups is recommended to avoid the rehydration penalty during synthetic operations.
  • For DDboost enabled repositories Forward incremental mode with either Active full or Synthetic full backups is recommended. Synthetically produced full backups will generally have the best restore performance and reduce the time VM is run off of a snapshot during the backup job run. However in some environments an Active Full job may run faster.
  • Transforming previous backup chains into rollbacks is not advisable for both repository types.
  • For forever forward incremental backup and backup copy on DDboost enabled repositories, the option “Defragment and compact full backup file” should be enabled if available. In most cases a weekly schedule is appropriate. This helps to avoid excessive growth of pre-compression data size for the full backup file.
 
Repository Performance Expectations and Configuration
 
If DDBoost is not licensed on the Data Domain system it must be added as a CIFS type or Linux type repository. It is advised to use a Linux server with the volume mounted via NFS as a relay server to help improve performance. Under some circumstances CIFS or NFS communication may perform better than DDBoost with Veeam Backup & Replication v8 because of the limitation of a single thread per backup job when using DDBoost. DDBoost has been shown to improve performance when performing Synthetic Fulls.
 
With Veeam Backup & Replication v9, support for EMC Data Domain Boost is enhanced with the introduction of the following capabilities:
  • Support EMC Data Domain Boost 3.0
  • Reduced impact of storage fragmentation during restore operations even with enabled parallel processing. This feature allows Veeam to store the VM backup in the dedicated backup chain so that fragmentation ratio will be minimum.
  • Reduce the impact of the block size so you may define any block size without impact on the restore process. Veeam will be able to read data granularly so amount of the redundant will be minimum.
 
With DDBoost
 
If the Data Domain System is licensed for DDBoost please proceed to configure it using the following steps.
 
  1. Launch the creation of a new Repository, on the Type tab select Deduplication storage appliance.
    http://helpcenter.veeam.com/backup/80/vsphere/repository_launch.html
    http://helpcenter.veeam.com/backup/80/vsphere/repository_type.html
  2. Select the deduplication storage as EMC Data Domain.
  3. On the next tab configure the information to for connecting to the Data Domain appliance.
    Very bottom on this page:
    http://helpcenter.veeam.com/backup/80/vsphere/repository_server.html
  4. On the Repository tab click Browse and select the necessary location from the list of available paths. http://helpcenter.veeam.com/backup/80/vsphere/repository_repository.html
  5. The default settings can be taken for the last steps in repository configuration.
    Unless your environment requires you to specify a different vPower NFS Server.
 
Without DDBoost

I. CIFS
  1. Launch the creation of a new Repository, on the Type tab select CIFS
    http://helpcenter.veeam.com/backup/80/vsphere/repository_launch.html
    http://helpcenter.veeam.com/backup/80/vsphere/repository_type.html
  2. On the next tab configure the path to which the Repository will write to, and set credentials to access that share.
    Second section named Shared Folder on this page:
    http://helpcenter.veeam.com/backup/80/vsphere/repository_server.html
  3. On the Repository tab within the advanced section, enable “Decompress backup data blocks before storing”
  4. The default settings can be taken for the last steps in repository configuration.
    Unless your environment requires you to specify a different vPower NFS Server.
 
II. NFS
The Data Domain will need to be configured for NFS access, and configure a Linux server to mount the volumes from the Data Domain via NFS. Please refer to the following links for further information regarding connecting Linux to the Data Domain via NFS:
http://forums.veeam.com/veeam-backup-replication-f2/veeam-datadomain-and-linux-nfs-share-t8916.html
http://tsmith.co/2014/veeam-and-datadomain/
 
  1. Launch the creation of a new Repository, on the Type tab select Linux
    http://helpcenter.veeam.com/backup/80/vsphere/repository_launch.html
    http://helpcenter.veeam.com/backup/80/vsphere/repository_type.html
  2. On the next tab select the Linux server that we be connected to. If it is not present in the list select “Add New…”
  3. On the Repository tab specify the path on the Linux server that leads to where you mounted the Data Domain via NFS. On this tab in the advanced section enabled “Decompress backup data blocks before storing.
    http://helpcenter.veeam.com/backup/80/vsphere/repository_repository.html
  4. The default settings can be taken for the last steps in repository configuration.
    Unless your environment requires you to specify a different vPower NFS Server.
 
 

Network adapter driver is not loaded when booting from recovery media

$
0
0

Challenge

When booting from Veeam Recovery Media, the network driver fails to boot. Manual driver injection returns "NO DEVICE ID" error and also fails.

Cause

The drivers required for Intel 219 series network adapter do not work in WinRE environment.

Solution

As a workaround, you can restore from backups on a local storage or, alternatively, try using a different network adapter.

More Information

To open a support case, go to Veeam Endpoint Backup Control Panel > Support > Technical Support.

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:

 
Hot add is not supported for this disk, failing over to network mode...

The following can be found within the logs:
 
“output: --wn:Hot add is not supported for this disk, failing over to network mode...\n”

Solution

Requirements: 
  • 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.
o    1MB block size – 256GB maximum file size
o    2MB block size – 512GB maximum file size
o    4MB block size – 1024GB maximum file size
o    8MB block size – 2048GB maximum file size
  • 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.
  • In versions 5.1 and older of vSphere, the maximum supported VMDK size is 1.98 TB.
  • The disks that are to be hotadd must be SCSI. IDE and pvscsi drives are not compatible with hotadd.
  • VMware Tools must be installed and up-to-date on the Veeam server and any Veeam proxies
  • Datastore needs sufficient space for a VM snapshot
 
 
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")
  • Hot Add may fail if the VM you are trying to back up and the proxy server are in different clusters.
  • 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 Support for further assistance: http://www.veeam.com/support.html
 

No updates from gateway servers

$
0
0

Challenge

No data come from the gateway servers. The Svc.VeeamGateSvc.log on the Gateway server (default path C:\ProgramData\Veeam\Backup) contains the following entry:
 
Failed to establish target connection to endpoint: [xxx.xxx.xxx.xxx:9999]

where xxx.xxx.xxx.xxx points to the Veeam Managed Backup Portal server.

Cause

The gateway server is unable to reach Veeam Managed Backup Portal server.

Solution

Verify the following:
  • ​port TCP:9999 is open on the Veeam Managed Backup Portal server;
  • you are able to telnet to TCP:9999 on the Veeam Managed Backup Portal server.
If you are unable to telnet to TCP:9999 on the VMBP server from the Gateway, follow these steps to re-create the firewall rule.
  1. Open Windows Firewall advanced settings on the Veeam Managed Backup Portal server.
  2. Open Inbound Rules and locate rule named Veeam Management Agent port (In). Disable or delete it.
  3. Choose to create New Rule > Custom on the Rule Type page.
  4. On the Program page, select This program path and specify the location of Veeam Management Agent (the default path is C:\Program Files\Veeam\Managed Backup Portal\CommunicationAgent\Veeam.MBP.Agent.exe).
  5. On the Protocols and Ports page, select Protocol type = TCP, Local port = Specific ports, 9999.
  6. On the Scope, Action and Profile pages the defaults can be accepted.
  7. Provide a descriptive name for the new rule and click Finish.
There is also another (less secure) approach to the rule creation.
  1. Open Windows Firewall advanced settings on the Veeam Managed Backup Portal server.
  2. Open Inbound Rules and locate rule named Veeam Management Agent port (In). Disable or delete it.
  3. Choose to create New Rule > Port on the Rule Type page.
  4. On the Protocols and Ports page, select Protocol type = TCP, Specific local ports = 9999.
  5. On the Action and Profile pages the defaults can be accepted.
  6. Provide a descriptive name for the new rule and click Finish.

More Information

If you have any questions, contact Veeam Support.
Viewing all 4483 articles
Browse latest View live


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