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

Backup job fails with “VIX Error Code: 13” or “Access is denied. Code: 5”

November 16, 2016, 11:39 am
$
0
0

Challenge

The backup or replication job fails with the following error message:
 
VIX Error: You do not have access rights to this file Code: 13
 
OR
 
RPC function call failed. Function name: [IsSnapshotInProgress].RPC error: Access is denied. Code: 5
 

Cause

The issue occurs when Veeam is unable to start the agent that triggers Microsoft VSS on the guest machine because of insufficient privileges. It may also be related to VMware Tools malfunction.

Solution

To resolve:

1. Ensure that the account being used by Veeam is a member of the Local Administrators group on the VM that is to be backed up.
2. If the account being used is not named “Administrator”, you must disable UAC on the Guest OS of the VM to be backed up.
 
a.  For 2008/2008 R2, in the “Change User Account Control Settings”, move slider to Never Notify
b.  For 2012/2012 R2, you must change the “EnableLUA” DWORD to 0 in HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\policies\system

3.  Uninstall VMware Tools, and Reinstall VMware Tools. (Please see https://kb.vmware.com/kb/2010137 for more information). If you are unable to upgrade existing VMware tools see https://kb.vmware.com/kb/1001354

 

More Information

For more information regarding disabling UAC under 2012 and 2012 R2, please review the following: http://social.technet.microsoft.com/Forums/windowsserver/en-US/0aeac9d8-3591-4294-b13e-825705b27730/how-to-disable-uac?forum=winserversecurity

While most service accounts created have the ability to manage files, folders, and services, many may not have the rights to execute VSS tasks. This is why a user that is in the Administrator group should be specified for application-aware image processing and guest filesystem indexing.
 
By default in a VMware vSphere environment if Veeam Backup & Replication is not able to reach the <ip>\Admin$ share of the Guest VM, it will failover to a network-less protocol called VIX.
 
In situations where UAC must remain enabled, named Administrator accounts must be used for this process. Only administrative accounts with SID-500 access will be able to execute remote administration commands with this Windows feature enabled. These will be the local “Administrator” account made locally when installing windows, or the “Administrator” account used with the domain. Created domain administrator accounts have a default SID-512 and may not be sufficient for remote administration.
 
↧
Search

How to forcibly stop jobs that are stuck in ‘stopping’ status

November 16, 2016, 12:33 pm
$
0
0

Challenge

This KB documents the process for forcibly terminating all jobs for a given Veeam Backup & Replication installation. The steps outlined in this KB will terminate all jobs.
 
Note: Some jobs may take some time to stop, please allow up to 60 minutes for a jobs to stop on their own before forcibly terminating them.

Solution

The problem may occur because a process or task that the job is waiting for has not been completed. Such a task can be snapshot removal. Therefore, as the first step it is recommended to check the vSphere Client to see if there is a snapshot removal process pending/working on the vSphere side.
 
The following steps will forcibly terminate ALL jobs/restores.
 
  1. Close the Veeam Backup & Replication console.
  2. Stop all service that begin with Veeam.
  3. Open the Task Manager on the Veeam Server and kill all VeeamAgent.exe processes.
    Note: Some VeeamAgent.exe process will be located on Source Proxies and Windows Repositories that are not the Veeam Server.
  4. Wait 5-10 minutes for the tasks to timeout and fail. 
  5. Remove snapshots from VM(s) that part of the stuck jobs. (If they have not been already removed).
  6. Start the services that were stopped in step 2.
***Repeat Steps 2 –4 on each Proxy and Repository used by the Job.

Note. If you use the Virtual Appliance (HOTADD) mode, before removing the snapshots make sure there are no stuck disks on the Veeam Backup server or one of the backup proxies. Otherwise, the snapshots can be orphaned. https://www.veeam.com/kb1775 
 
─────────────────────────
 
If the jobs are still listed as “Stopping” after performing the steps outlined above please proceed through the following steps.

For information on how to apply SQL scripts please review https://www.veeam.com/kb1443.
  1. Back up the Veeam database. (http://www.veeam.com/kb1471)
  2. Run the following query against the VeeamBackup database:
UPDATE [Backup.Model.JobSessions]
SET [state] = '-1'
WHERE [state] != '-1'
 
↧
↧

Microsoft Exchange logs are not being truncated in Veeam Backup and Replication 9.5

November 16, 2016, 1:31 pm
$
0
0

Challenge

After upgrade to version 9.5.0.711 Microsoft Exchange logs no longer get truncated. In the Windows Application event logs you might get an error with an event ID 2034.

Cause

This is a known issue in build 9.5.0.711. If you disable Microsoft SQL logs truncation in Job properties then Microsoft Exchange logs truncation will be disabled too.
Exchange logs truncation is regulated by a single boolean when you call SetBackupSucceeded() WinAPI with Exchange VSS writer writerID.
When that boolean is set to true Exchange VSS writer goes ahead and truncates the logs, and v9.5.0.711 sets this boolean to false based on SQL configuration in Job properties.

Solution

Enable SQL log truncation in Job properties and this will allow Exchange logs to be truncated.
↧

HCL - StoreOnce with Catalyst

November 17, 2016, 4:09 am
$
0
0

Challenge

Product Information:

Product Family: HPE StoreOnce w/Catalyst
Status: Veeam Ready - Integrated
Classification Description: Integrated storage where joint development activities between the manufacturer and Veeam have occurred to create advanced backup or restore functionalities.

Solution

Product Details:

Model number: All StoreOnce Models
Firmware version: 3.13.1-1546.2
General product family overview: From ROBO to the entire enterprise, HPE StoreOnce System with HPE StoreOnce Catalyst is a single and agile backup and recovery solution. Reduce costs and keep pace with rapid data growth, confident that your SLAs are securely met.


Veeam Details:

Veeam Build Number: 9.0.0.902
Veeam Settings:

  • Repository Type: Deduplicating Storage Appliance
  • Deduplication: OFF
  • Compression: Optimal
  • Storage Optimization: Local target (16TB+ backup files)
  • Per-VM Backup Files: ON
  • Decompress before storing: ON
  • Align backup file blocks: OFF

More Information

Special Considerations:

HPE StoreOnce with Catalyst is recommended as a secondary backup target for long-term retention of Veeam backup files.

Company Information:

Company name: Hewlett Packard Enterprise
Company overview: HPE delivers high-quality, high-value products, consulting, and support services in a single package. That’s one of their principal differentiators. They have industry-leading positions in servers, storage, wired and wireless networking, converged systems, software, services and cloud.

↧

"Use Windows Session Credentials" options does not work for Veeam One Reporter and Business View websites

November 17, 2016, 7:51 am
$
0
0

Challenge

When using Internet Explorer, Veeam ONE Reporter and Business View websites keep asking for Windows credentials at logon despite enabling the “Use Windows session credentials” option.

Cause

By default the "Automatic Logon" feature is turned off in Internet Explorer.

Solution

Make sure that both sites are added to Trusted Sites and enable the "Automatic logon" feature at Tools > Internet Options > Security tab > Trusted sites icon > Custom level button > User Authentication > Logon > Automatic logon with current user name and password.
 
↧
↧

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

November 18, 2016, 1:14 am
$
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. 

 
↧

SureBackup: A connection attempt failed

November 18, 2016, 1:15 am
$
0
0

Challenge

The following error message can be seen in the SureBackup log:

[timestamp] <01> Error    A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond xxx.xxx.xxx.xxx:443 (System.Net.Sockets.SocketException)

Cause

Veeam Backup & Replication is not able to connect to the Virtual Lab and grab network settings from the web server.

Solution

If you assign a proxy appliance an IP address from the same network where the Veeam B&R server is located, Veeam B&R will automatically add a new route to the routing table on the Veeam Backup server, so please make sure that the 443 port is not blocked.

If you assign a proxy appliance an IP address from a network other than that where the Veeam B&R server is located, you will have to manually add a new route to the routing table on the router in the production network. Otherwise, you will not be able to access virtual machines in isolated networks.

Ensure that the specified network settings on the "Proxy" step of the Virtual Lab wizard corresponds to the production settings.

↧

Fault tolerant VMs

November 18, 2016, 8:00 am
$
0
0

Challenge

Veeam Backup & Replication does not allow you to add a Fault-Tolerant (FT) VM to a backup job even if FT is temporarily disabled.

Cause

Processing of vSphere FT VMs is not supported in conjunction with vSphere 4.x or 5.x. With vSphere 6.x and Veeam Backup & Replication 8 u2, FT VMs are supported.

Please see the following article for more details: https://www.veeam.com/blog/veeam-availability-suite-update-2-vsphere-6-support-endpoint-and-more.html.

Solution

Update to both Veeam Backup & Replication 8 u2 and vSphere 6.x to enable support for FT VMs.

More Information

VMware Fault Tolerance & Snapshots: https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1016619

VMware vSphere 6.0 Platform White Paper: http://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/whitepaper/vsphere/vmw-white-paper-vsphr-whats-new-6-0-pltfrm.pdf

↧
Search

Veeam Backup & Replication 9.5 Day 0 Update

November 18, 2016, 8:29 am
$
0
0

Challenge

This update is provided to enable upgrading existing installations of Veeam Backup & Replication 9.5 RTM partner preview (build 9.5.0.580) to generally available version of Veeam Backup & Replication 9.5 GA (build 9.5.0.711). This update addresses a number of issues reported by our partners on the preview build.

All new installations should be performed using Veeam Backup & Replication 9.5.0.711 ISO that is available for download starting November 16th, 2016. Please, delete the partner preview build ISO to ensure you don't accidentally use it in the future.

Solution

Please confirm you are running version 9.5.0.580 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.711.

Prior to installing this update please reboot the Veeam server to clear any locks on the Veeam services and when the reboot is done, please stop all the Veeam services and apply the update. After installing the update, please start the Veeam services, open the console and allow Veeam B&R to update its components.

To obtain this update, please click here (you need to be logged in to download the update).
MD5 checksum: df474686aae3f0ce3830e446d98e150f

More Information

"Add or Remove Programs" will still show version 9.5.0.580 after Veeam Backup & Replication 9.5 Day 0 Update is installed. This is normal behavior. The actual version can be looked up in Help | About dialog of Veeam Backup & Replication console.
↧
↧

Understanding Veeam ONE 9.5 Deployment Types

November 21, 2016, 2:43 am
$
0
0

Challenge

Understanding the difference between Optimized for Typical Deployment, Optimized for Advanced Scalability Deployment and Backup Data Only data collection modes.

Cause

Data collection mode determines what metrics Veeam ONE will collect, and specifies the product configuration in a number of areas. Choosing an appropriate data collection mode allows you to optimize monitoring and reporting performance and improve user experience in Veeam ONE.
You can choose of the following Veeam ONE data collection modes:
  • Optimized for Typical Deployment mode is recommended for small to medium environments up to 100 hosts and 1500 VMs. In this mode, Veeam ONE collects all inventory, configuration and performance metrics, and makes collected data available in dashboards, reports and alarms. This mode provides the greatest data granularity level, but results in a greater load on the Veeam ONE server and a larger size of Veeam ONE database.
  • Optimized for Advanced Scalability Deployment mode is recommended for large environments with more than 100 hosts and 1500 VMs. In this mode, Veeam ONE collects all metrics required for alarms and reports. This mode provides a lesser data granularity level than the Typical Deployment mode, and results in a lower load on the Veeam ONE server and a smaller size of the Veeam ONE database.
  • Backup Data Only mode is recommended for users who want to focus on Veeam Backup & Replication monitoring and reporting, and do not need a deep visibility of the virtual infrastructure. In this mode, Veeam ONE collects all inventory, configuration and performance metrics from Veeam Backup & Replication servers. It also collects inventory and configuration metrics from virtual infrastructure servers, but skips virtual infrastructure performance metrics. As a result, Veeam ONE dashboards, reports and alarms display backup-related data only; for VMware vSphere and Microsoft Hyper-V objects, performance data is not available. This mode results in the least possible size of the Veeam ONE database and the lowest load on the Veeam ONE server.

Solution

To switch between the modes:
  1. Open Veeam ONE Monitor.
  2. On the toolbar, click Options and select Server Settings. Alternatively, you can press [CTRL+S] on the keyboard.
  3. Open the Other Settings tab.
  4. In the Support utility section, click Launch.
  5. In the Veeam ONE Settings menu, select Scalability.
  6. Choose the necessary data collection mode and click Save.
  7. Restart Veeam ONE Monitor Server and Veeam ONE Reporter Server services.

NOTE that the previously collected data will not be revisited.

More Information

For the list of settings and metrics affected by the deployment mode change, please refer to this document.

If you have any questions, contact Veeam Support.
↧

Veeam Backup update fails with "This Veeam Backup & Replication installation cannot be updated automatically"

November 23, 2016, 2:09 pm
$
0
0

Challenge

When attempting to update the Veeam Backup & Replication software, an error is encountered:
This Veeam Backup & Replication installation cannot be updated automatically. Please contact Veeam customer support for assistance with manual update.
 

Cause

Update setup program checks the digital signature of the existing files to ensure their integrity before updating them. All product files are signed using Global Sign certificates. Some Windows installations do not contain Global Sign's root certificates authority as trusted root certificates, or have non-current certificates. This issue is typically observed on servers with locked down security settings, or servers with no internet access or latest updates installed.

Solution

To resolve this issue, please install the below four certificates manually on the system:
https://www.digicert.com/CACerts/DigiCertAssuredIDRootCA.crt (DigiCert Assured ID Root CA)
https://secure.globalsign.com/cacert/gscodesigng2.crt (GlobalSign CodeSigning CA - G2)
https://www.digicert.com/CACerts/DigiCertHighAssuranceEVRootCA.crt (DigiCert High Assurance EV Root CA)
https://www.digicert.com/CACerts/DigiCertEVCodeSigningCA-SHA2.crt (DigiCert EV Code Signing CA - SHA2)
https://support.globalsign.com/customer/portal/articles/1426602-globalsign-root-certificates (install R1, R2, and R3 certificates)
If your backup server does not have internet access, please download certificate files from another computer.

More Information

To install a certificate:
Right-click on the certificate file in Windows, select "Install Certificate", install on "Local Machine", and select the store "Trusted Root Certification Authorities". When installed properly, "GlobalSign" and "GlobalSign Root CA" should show under Console root -> Certificates -> Trusted Root Certification Authorities -> Certificates.

User Added Image
↧

Licenses shortage results in Reporter collection job to finish with Warning status.

November 25, 2016, 4:37 am
$
0
0

Challenge

The Reporter collection job finishes with the Warning status due to sockets number exceeded. To make sure this is the case, open the Reporter web page and navigate to Configuration > Sessions node and double-click the corresponding session, scroll to the bottom of the job log and find the [warning]: Sockets number exceeded line.

Cause

Behavior by design.

Solution

The data in the reports will only be available for the hosts included in data collection on Veeam One Monitor side (Monitor UI -> Options -> Server Settings -> Monitored Objects\Hosts\VMs (depending on Veeam One version)). 

More Information

If you have any questions, contact Veeam Support.
↧

License cannot be installed in Veeam ONE 9.5

November 25, 2016, 6:22 am
$
0
0

Challenge

When installing the license file, the following error message may occur: License signature is invalid

Cause

Sometimes the license check module is unable to process the license key correctly.

Solution

To resolve the issue follow these steps:
  1. Stop Veeam ONE Monitor Server service.
  2. Back up the original VeeamNet.dll file at C:\Program Files\Veeam\Veeam ONE\Veeam ONE Monitor Server\
  3. Download the new VeeamNet.dll here and replace the original file with it.
  4. Start Veeam ONE Monitor Server service.
We have also replaced the Veeam ONE distribution downloadable from veeam.com
It no longer contains the issue described in the present article, so downloading the current ISO file and installing Veeam ONE from it will resolve the license installation issue.

More Information

If you have any questions, contact Veeam Support.
↧
↧

Release Notes for Veeam Backup & Replication 8.0 Update 3

November 29, 2016, 1:01 am
$
0
0

Challenge

Release Notes for Veeam Backup & Replication 8.0 Update 3

Cause

Please confirm you are running version 8.0.0.807, 8.0.0.817, 8.0.0.831, 8.0.0.917, 8.0.0.2018, 8.0.0.2021, 8.0.0.2029 or 8.0.0.2030 prior to installing this update. You can check this under Help | About in Veeam Backup & Replication console. After upgrading, your build will be version 8.0.0.2084

Prior to installing this update please reboot the Veeam server to clear any locks on the Veeam services and when the reboot is done, please stop all the Veeam services before applying the update.

After installing the update, during the first start of the Veeam Backup Service, required modifications will be made to the configuration database automatically to optimize its performance. These modifications may take up to 10 minutes to complete. Please do not reboot the Veeam server, or attempt to stop the service during this operation. If there is concern regarding the time that the Veeam Backup Service takes to start after upgrade, please contact Veeam Customer Support.

Once Veeam Backup Service starts, please open the console and allow Veeam Backup & Replication to update its remote components.

 

Solution

New Features and Enhancements

Microsoft
  • Support for Windows 10 as guest virtual machines (VMs), including application-aware processing.
  • Support for installation of Veeam Backup & Replication and all of its components on Windows 10.

VMware
  • Support for vSphere 6.0 Update 1.
  • Added ability to convert "VMware Tools not found" job warning to informational event. To enable this behavior, set DisableVMwareToolsNotFoundWarning (REG_DWORD) registry value to 1.

Linux
  • Support for the following additional SSH ciphers: aes128-ctr, aes192-ctr, aes256-ctr, aes192-cbc and aes256-cbc.

Veeam Explorer for Microsoft SQL Server
  • Log truncation is automatically skipped for stopped and unsupported SQL Server instances to prevent errors from being logged.
  • Preferred network settings will now also apply to transaction log backup jobs.
  • Support for SQL Servers using non-standard port number.

Veeam Explorer for SharePoint
  • Support for ADFS authentication.
  • Support for UPN credentials.

SureBackup
  • Proxy appliance will now respond to ping from within Virtual Lab to prevent firewalls automatically blocking its network as public.

Other
  • Removed weakly encrypted username and password logging from guest processing components using networkless (VIX) guest interaction mode. Veeam thanks Pasquale Fiorillo and Francesco Ongaro of ISGroup for vulnerability discovery.
  • Improved performance of certain user interface operations, such as opening Backups node in large environments.
  • Reduced load on SQL Server hosting product configuration database, while improving SQL interaction reliability in large environments.
  • Improved performance of configuration backup in large environments.
  • Minor enhancements and bug fixes in various product areas.

More Information

Due to an update and internal change in behavior of CTP driver on Hyper-V hosts, each first run of each job after the update will perform a full scan of disks on the source side, which may extend backup times significantly. It is recommended to plan accordingly prior to installing the update.

Note: This version has not been tested against with vSphere builds beyond 6.0 Update 1. If you are using a later vSphere version, please upgrade to Veeam Backup & Replication 9.0

[[DOWNLOAD|DOWNLOAD UPDATE|https://download2.veeam.com/VeeamBackup&Replication_8.0.0.2084_Update3.zip]]
↧

ConfigStoreRootPath cluster parameter is not defined

December 1, 2016, 2:44 am
$
0
0

Challenge

This article describes how to fix the warning/error “ConfigStoreRootPath cluster parameter is not defined” appearing in the following situations:
  • When you add a Windows Server 2016 Hyper-V cluster to Veeam console.
  • When you take a backup of a VM with a shared virtual disk located on the Windows Server 2016 Hyper-V cluster

Cause

In Hyper-V 2016 Microsoft implemented a possibility to share a virtual hard disk (in .vhdx or .vhds format only) between two or more VMs and use that virtual hard disk as a shared storage when building guest clusters.
 
When you decide to add a Windows Server 2016 Hyper-V cluster to Veeam console, you must decide where to store meta files created during the backup process of the VMs from the shared virtual hard disk (i.e. information about snapshot groups etc.).
 
By default, meta files location is not defined, so you need to define it manually.

Solution

1. To check the existing configuration run the following PS command on any node of the cluster:
  
Get-ClusterResource "Virtual Machine Cluster WMI" | Get-ClusterParameter ConfigStoreRootPath

By default, “value” points to a cluster volume (e.g. C:\ClusterStorage\Volume1).

2. Create a folder on that volume, and this folder will act as the meta files location. The folder should be available to all members of the cluster. (e.g. C:\Clusterstorage\Volume1\Hyper-V\Shared)

3. Specify the path to the newly created folder with the following commands:
  
$path = C:\ClusterStorage\Volume1\Hyper-V\Shared
Get-ClusterResource "Virtual Machine Cluster WMI" | Set-ClusterParameter -Name ConfigStoreRootPath -Value $path

The cluster now can be added to Veeam. If the cluster had already been added and the backup failed with the error in question, re-run the backup after setting the value.
↧
Search

Backup Job or Backup Proxy rescan fails with “Failed to create processing task for VM Error: Disk 'GUID' not found”

December 1, 2016, 9:41 pm
$
0
0

Challenge

After installing patch 1 for Veeam Backup & Replication 8, jobs may start to fail with the following error message:
[Error] Failed to create processing task for VM Error: Disk '<GUID>' not found.
 

Cause

The error is caused by the wrong disk IDs that were added to the database when the Veeam Backup & Replication 8 was running. This issue has been solved in patch 1, but wrong IDs still remain in the database and, in some cases of processing VMs in Direct SAN or Hot-Add mode, can affect the jobs.

Solution

To solve the issue, the wrong disk ID should be removed from the used Veeam database. We recommend backing up your database prior to making any changes. To apply the query, follow the next steps:
 
1.  From SQL Management Studio, connect to the instance containing the Veeam configuration database (default names are VEEAM, VEEAMSQL2008R2 or VEEAMSQL2012);
2.  Expand “Databases”;
3.  Right-click  “VeeamBackup” > New query;
4.  Paste the appropriate query (below) and press “execute” or F5
DELETE FROM Physhost_disk WHERE disk_id = ‘GUID’

You will need to paste the GUID from the error message in the job to the query. For example, if the error message looks like:
Failed to create processing task for VM Error: Disk '3f8688c2-d5ae-4ac8-be11-2257097f8eb9' not found.

The query should look like:
DELETE FROM Physhost_disk WHERE disk_id = '3f8688c2-d5ae-4ac8-be11-2257097f8eb9'

5. Close the Veeam GUI and run Veeam again to force the GUI to update.

NOTE:  This is an operation that Veeam Support is happy to walk through with you and this KB is provided mostly as a convenience for customers wishing to perform the above operations themselves. If you would like to walk through this process with a representative of Veeam Customer Support, please do not hesitate to open a case with us via the Customer Portal.

In some circumstances there may be multiple orphaned disk references in the database, the error shown in the GUI will only display the first problematic GUID the software comes across. With this in mind it is advised to run a test job after running the above query, if the test jobs fails with another GUID error run the query again for that GUID. Repeat the test process till no errors occur.
 

More Information

How to find used SQL server name and Backup Your Veeam SQL DB
Installing Microsoft SQL Management Studio
How to apply a SQL script
↧

Create VSS processing exclusion for vCenter Database

December 7, 2016, 11:27 am
$
0
0

Challenge

The vCenter database in most cases will be automatically excluded from the Application-Aware Image Processing process, preventing the database from being frozen or quiesced. If this does not happen automatically backing up the VM where the vCenter database is stored may fail with the following error.
 
" VSSControl: Failed to prepare guest for freeze, wait timeout 900 sec."
 
More information regarding this error can be found in http://www.veeam.com/KB1377

Solution

The solution below will instruct you on how to enable and use the DBExclusion menu that is built-in to Veeam Backup & Replication v7 and higher.
 

1. Close the Veeam Backup & Replication console.

2. Open Regedit.exe

3. Navigate to the key HKLM

4. Add a new DWORD ‘EnableDBExclusions’>

5. Set the Value to 1

User-added image


6. Close the Registry Editor and open Veeam Backup & Replication

7. Open “Database Exclusions” from the Main Menu
User-added image

8. In the window that pops up, click Add.

9. Specify the DNS name (case sensitive) or IP address, and Database Name (case sensitive) that you wish to exclude from VSS Freezing and being Quiesced. 10. Specify the Database name (case sensitive) that you wish to exclude from application-aware image processing.

User-added image

10. Allow the writer service account access to the Volume Shadow Copy service via the registry:
On the VM you are backing up, open regedit.exe and navigate to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VSS\VssAccessControl
If a DWORD value for the account assigned to the writer service is present in this key, it must be set to 1. In most cases, the relevant service account appears in services.msc as the log-on account for the service listed in KB2041. However, some writers have special accounts. For example, in MS SQL Server 2012 and later, if the DWORD value “NT SERVICE\SQLWriter” is present in the VssAccessControl key, it must be set to 1.

 

On next job run the specified database will be excluded from the Application-Aware Image Processing freeze task.

*Note - If you are using a default or unnamed SQL instance (example: MSSQLSERVER) then only the server name (or IP address) should be added in the "Add Database" screen.

↧
↧

Veeam licensing

December 7, 2016, 11:34 am
$
0
0

Challenge

How is Veeam Backup & Replication licensed?

Solution

Veeam licensing for all products is described here: http://veeam.com/faq.html
 

You can verify your license key by logging in to www.Veeam.com with your credentials: http://www.veeam.com/manage_licenses.html. An updated key will be available for all customers with valid and active support contracts.

If you have difficulties retrieving your license file, go to cp.veeam.com, click "Open Case", and be sure to select "Licensing" to receive assistance from Veeam licensing. 

To download Veeam products for trial license, go to http://www.veeam.com/downloads/. The trial license key is sent to you in email after registering. The trial license is valid for 30 days from the moment of  registration.

To obtain a full license key for the desired number of sockets, refer to http://www.veeam.com/buy-end-user.html. The full license includes a one-year maintenance plan.

More Information

To check check what version your license key is for, open the *.lic file in Notepad/Word and locate the section listed as "Version"

For example if your "Version" is listed as 9.x you are able to install any patch for Veeam Backup and Replication 9.0 or Veeam Backup and Replication 9.5
↧

Notification emails are not sent for backup jobs

December 7, 2016, 11:58 am
$
0
0

Challenge

Notification emails are not sent for backup jobs

Cause

The Veeam Backup service account is not a member of the Backup Administrators group in Veeam

Solution

Emails are not being sent for backup jobs and there are no errors or warnings in the console.  Emails for backup configuration Likely do work.
 
 
The Job is successful in the console, but in the “Job.<job name>. log” you will see:
 
Info     Job has been stopped with failures. Name: [<job_name>], JobId: [<guid>]
Error    Access denied. (System.Security.SecurityException)
 
This is due to the service trying to update the veeambackup.manager.exe and is not a backup administrator in Veeam roles.
 
Add the service account to the role backup administrator, in the Veeam roles. These are accessed in Main Menu > Users and Roles

User-added image

User-added image
 
↧

NetApp hardware VSS provider limitation

December 7, 2016, 12:08 pm
$
0
0

Challenge

Hyper-V Backup/Replication Job utilizing NetApp Data ONTAP VSS Hardware Provider reports warning or error message:
"Another shadow copy creation is already in progress. Please wait a few moments and try again"
 

Cause

NetApp hardware VSS provider doesn't allow concurrent snapshot creation within cluster, even when snapshots are initiated on different hosts and for different CSVs.
With NetApp hardware VSS provider you can have only one snapshot creation running within cluster at once - there is no concurrency.

Microsoft software VSS provider (Microsoft CSV shadow copy provider) has no such limitation.

Solution

You can switch to Microsoft software VSS provider:
https://helpcenter.veeam.com/backup/hyperv/hv_server_volumes.html#volume

Or disable concurrent shadow copy snapshot creation within cluster for all providers:
Create HyperVRestrictConcurrentSnapshotCreation (DWORD) registry value under HKLM\SOFTWARE\Veeam\Veeam Backup and Replication key on the Veeam backup server.
And set it to 1.
Then stop all Jobs and restart Veeam Backup service.

 
↧
Viewing all 4469 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>