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

Invalid Exchange Server version

$
0
0

Challenge

Backup jobs in Veeam Backup for Microsoft Office 365 fail with the following error:

[Timestamp]   14 (5696)   No folder hierarchy changes
[Timestamp]   14 (5696) Preparing folders for items processing...
[Timestamp]   14 (5696) Error: Invalid Exchange Server version
[Timestamp]   14 (5696) Stack:
[Timestamp]   14 (5696)    at Veeam.Ews.ExServices.GetExchangeServerVersion()
   at Veeam.Ews.ExServices.get_ExchangeServerVersion()
   at Veeam.Archiver.Source.MailboxActivator.PrepareFolders(IMailboxContext bind, ExFolder top, ExcludedFolders excluded, CancellationToken cancel)
   at Veeam.Archiver.Source.MailboxActivator.DoMailboxWork(CancellationToken cancel)
   at Veeam.Archiver.Source.MailboxAction.DoWork(CancellationToken cancel)
[Timestamp]   14 (5696) Mailbox processing failed: user@domain.com


 

Cause

This is a known issue in Veeam Backup for Microsoft Office 365 version 1.0.0.912.

Solution

A hotfix can be obtained from Veeam Support to resolve this issue. Please open a support case and refer to this knowledge base article.

More Information

If you need help opening a support case, please click here.

Unable to collect files information from datastore in a timely manner due to high vCenter server load

$
0
0

Challenge

Veeam ONE Reporter collects data from datastores using “SearchDatastoreSubFolders_Task” tasks that are pre-defined by VMware. Some of the datastores might become unavailable or experience performance issues. Subsequently, Veeam ONE Reporter may be unable to complete data collection tasks against these datastores.


The following error messages appear in the SchedulingService.log file:


XX/XX/XXXX XX:XX:XX [info] : xxxxx.xxxxx.xxxxx: Exporting virtual machine files  
XX/XX/XXXX XX:XX:XX [warning] : xxxxx.xxxxx.xxxxx: Failed to collect VM files: Datastore [**datastore_name**] timeout is exceeded
Unable to collect files information from datastore [**datastore_name**] in a timely manner due to high vCenter server load.
...
Unable to collect files information from datastore [XXXXXX] in a timely manner due to high vCenter server load.

The collection job in Veeam ONE Reporter will finish with a "Warning" status. Additionally, the session log may contain the following entry:
 
XX/XX/XXXX XX:XX:XX [warning]: xxxxx.xxxxx.xxxxx: There were errors while collecting VM files: Failed in retrieve some VM files because of the timeout is exceeded.

Cause

Veeam ONE Reporter uses a 900 secondtimeout in order to wait for 10 datastore search tasks (default number) to complete.

Any performance or access issues affect the entire collection process, and the collection job finishes with a "Warning" status.
 
The error messages above mean that some issues have occurred on datastores. Due to lack of response, we’ve failed datastore scan tasks and are unable to collect data from some of the datastores. Basically, the problem is either on the datastore’s or on VMware’s side, but we may try to find a workaround for this issue and apply changes to the collection process on Veeam ONE Reporter’s side in order to increase the time to wait until all datastore tasks are completed.
 
NOTE: This workaround just lets you run the “SearchDatastoreSubFolders_Task” task with the new timeout specified to make sure the datastore collection process does complete.

Solution

Here is how to tune the product in order to make your datastore search tasks complete successfuly:
   1) Find a suitable timeout value for completing all the “SearchDatastoreSubFolders_Task” tasks.
   2) Apply registry changes and set a proper timeout value.
   3) Decrease the number of datastore search tasks running simultaneously.

STEP 1:
Find a suitable timeout value for completing all the “SearchDatastoreSubFolders_Task” tasks in each particular scenario by running the PowerShell script (available below in "More Information" section) using VMware vSphere PowerCLI. This shows how much time it takes to complete all mentioned datastore tasks. You can download VMware vSphere PowerCLI package for free by the following link:
http://www.vmware.com/support/developer/PowerCLI/index.html
 
Instructions on how to run the script:
   1) Open PowerCLI and connect to your VMware vCenter server using the "connect-viserver" command.
   2) Specify the credentials to connect to VMware vCenter server.
   3) Change the current directory to the directory where the script is located (use "cd" command).
   4) Run the script and wait until it's finished.
 
The following is an example of the output in the same VMware vSphere PowerCLI window. The script will run the task against every datastore that is registered under the VMware vCenter server.
 
Error messages such as the following might appear:
   Trying to collect *.vmdk and *.flat files from **datastore_name** ( **datastore_id** )
   Exception calling "SearchDatastoreSubFolders" with "2" argument(s): "Datastore'
   [**datastore_name**]' is not accessible."
   At {path_to_the_script}:\Veeam_BrowseDatastores.ps1:45 char:41

 
These errors mean that there are some problems with the datastores. But from the output, you should see how much time it takes to complete scanning all datastores.
 
STEP 2:
Increase the timeout Veeam ONE Reporter uses to complete the entire datastore search process:
   1) Log on to the server with Veeam ONE Reporter installed.
       Open Registry Editor and navigate to the Veeam ONE Reporter registry folder:
       For both x86bit and x64bit systems - HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Reporter Enterprise
   2) Create the following registry key:
       Name – GetVmSnapshotTimeout
       Type – DWORD
       Value – XXXXX *.
         * Equal to or more than time it takes to complete scanning all datastores according to script's output.
            The value is calculated in seconds and should be specified in DECIMAL format.
 
STEP 3:
Decrease the number of datastore search tasks running simultaneously:

Note: We would recommend that you try to run one datastore search task at time.
   1) Log on to the server with Veeam ONE Reporter installed.
       Open Registry Editor and navigate to the Veeam ONE Reporter registry folder:
       For both x86bit and x64bit systems - HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Reporter Enterprise
   2) Create the following registry key:
       Name – VIFilesDatastoresCountByTime
       Type – DWORD
       Value – 1

More Information

Here is the script mentioned above:
 
write-host (Get-Date).TimeOfDay Getting datastores...
 
$dss = get-datastore
write-host (Get-Date).TimeOfDay $dss.Count datastores found
 
$fqf = New-Object VMware.Vim.FileQueryFlags
$fqf.FileSize = $true
$fqf.FileType = $true
$fqf.Modification = $true
$fqf.FileOwner = $true
 
$fq1 = New-Object VMware.Vim.FileQuery
 
$ss1 = New-Object VMware.Vim.HostDatastoreBrowserSearchSpec
$ss1.details = $fqf
$ss1.sortFoldersFirst = $true
$ss1.MatchPattern += "*.*"
 
 
$ss2 = New-Object VMware.Vim.HostDatastoreBrowserSearchSpec
$ss2.details = $fqf
$ss2.sortFoldersFirst = $true
$ss2.MatchPattern += "*delta.vmdk"
$ss2.MatchPattern += "*flat.vmdk"
 
 
$ss1.Query = $fq1
 
foreach($ds in $dss)
{
 $dsv = $ds | get-view
 
 if($ds.Accessible -ne $true)
 {
   write-host (Get-Date).TimeOfDay Skip files collecting because $dsv.Summary.Name"("$dsv.Summary.Datastore.Value")" is not accessible.
 }
 
 else
 {
   $dsb = get-view $dsv.browser
   $rp = "["+$dsv.summary.Name+"]"
 
   write-host (Get-Date).TimeOfDay Trying to collect *.vmdk and *.flat files from $dsv.Summary.Name"("$dsv.Summary.Datastore.Value")"
   $sr2 = $dsb.SearchDatastoreSubFolders($rp, $ss2) 
   write-host (Get-Date).TimeOfDay Completed. $sr2.Count files found on $dsv.Summary.Name"("$dsv.Summary.Datastore.Value")"
 
   write-host (Get-Date).TimeOfDay Trying to collect other files from $dsv.Summary.Name"("$dsv.Summary.Datastore.Value")"
   $sr1 = $dsb.SearchDatastoreSubFolders($rp, $ss1) 
   write-host (Get-Date).TimeOfDay Completed. $sr1.Count files found on $dsv.Summary.Name"("$dsv.Summary.Datastore.Value")"
 }
}
 

An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full

$
0
0

Challenge

After installing Windows April update KB4015553 Veeam jobs and services fail at different operations with:
 
"An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full"

Cause

This particular update (and all consequent rollups that include it) causes the system to run out of free RPC ports when there are failed iSCSI connections.

Solution

Repairing or removing unsuccessful iSCSI connections, followed by the server reboot, was found to fix the issue. Additionally, remove any unused targets from the ‘Favorite Targets’ tab that are associated with these connections as they may be reconnected after reboot.

This issue has been addressed by Microsoft. Apply the appropriate update below to resolve the issue

For 2016:           https://support.microsoft.com/en-us/help/4025334
For 2012 R2:      https://support.microsoft.com/en-us/help/4025335

-------------------------------------------------------------------------------------------------------------------------------------------------

The update that resolved the above Buffer Space iSCSI issue (KB4025335) has caused another iSCSI issue that only affects Backup from Storage Snapshots using an iSCSI connection.
 
After installing Windows Update KB4025335, KB4034681, KB4025333, or KB4025336, Veeam jobs utilizing Backup from Storage Snapshots using an iSCSI connection fail with the following errors:
 
“Error: Cannot retrieve physical extents for connecting iSCSI target IQN iqn.2007-11.com.nimblestorage:lun-nim-oracle-veeam-lun-nim-oracle-v069a713ff86811d1.000000d1.fef260ee.s069a713ff86811d1.000000de.0000b1cb on proxy IQN iqn.1991-05.com.microsoft:mtl-s-fs0005.solotech.local”
 
In the logs, it can be seen with this error:
 
Task Log:
“[25.07.2017 09:44:54] <61> Error Failed to find physical drive for LUN with lun Id 'WwnOrIqn: 'iqn.1992-04.com.emc:cx.apm00140946425.a1', LunId: '10',
 
[25.07.2017 09:44:54] <61> Error Unable to retrieve devices for iSCSI session. number of retry attempts: '20'. Interval: '100'. (Veeam.Backup.Common.CCppComponentException)
[25.07.2017 09:44:54] <61> Error in c++: void __thiscall disklib::vmfs_san::iscsi_api::iscsi_discovery::GetDevicesForSessionWithRetry(struct _ISCSI_UNIQUE_SESSION_ID &,class std::vector<struct ISCSI_DEVICE_ON_SESSIONW,class std::allocator<struct ISCSI_DEVICE_ON_SESSIONW> > &,int,int) failed.
[25.07.2017 09:44:54] <61> Error in c++: void __thiscall disklib::vmfs_san::iscsi_api::iscsi_discovery::LoginTarget(const class std::basic_string<wchar_t,struct std::char_traits<wchar_t>,class std::allocator<wchar_t> > &,class std::vector<struct disklib::vmfs_san::iscsi_api::IscsiDriveInfo,class std::allocator<struct disklib::vmfs_san::iscsi_api::IscsiDriveInfo> > &) failed.”

 
 
Proxy Resources Log:
 “[04.08.2017 13:50:55] < 4016> cli| VMFSSAN.ConnectISCSITarget
[04.08.2017 13:50:55] < 4016> cli| (EString) TargetName = iqn.1992-04.com.emc:cx.apm00140946425.a1
[04.08.2017 13:50:55] < 4016> cli| - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
[04.08.2017 13:50:55] < 4016> dsk| Retrieving devices for target 'iqn.1992-04.com.emc:cx.apm00140946425.a1'.
[04.08.2017 13:50:55] < 4016> dsk| WARN|The data area passed to a system call is too small.”

 
The above issue is resolved by installing Windows Update KB4034663, which can be found here:
 
https://support.microsoft.com/en-us/help/4034663/windows-8-1-windows-server-2012-r2-update-kb4034663
 

More Information

https://social.technet.microsoft.com/Forums/SharePoint/en-US/492f62ce-aec8-4777-98f0-0c9dbf302954/problem-with-kb4015553?forum=winserverwsus

https://support.microsoft.com/en-us/help/4015550
This security update introduced an issue in which, if an iSCSI target becomes unavailable, attempts to reconnect will cause a leak. Initiating a new connection to an available target will work as expected

Veeam Backup for Microsoft Office 365 1.0 Update 1 Release Notes

$
0
0

Challenge

Veeam Backup for Microsoft Office 365 1.0 Update 1 Release Notes

Cause

NoteAfter installing Update 1, please install a new update. Click here for more details.

The package contains two files: Veeam.Backup365.msi and VeeamExplorerForExchange.msi.

Prior to installing this update please reboot the Veeam Backup for Microsoft Office 365 server to clear any locks on the Veeam services; when the reboot is done, please stop all Veeam services before applying the update.

VeeamBackup365.msi can be used:
  • As an update over version 1.0.0.860 (You can check this, selecting About from the main menu in the Veeam Backup for Microsoft Office 365 interface.)
  • As a new installation without a previous version
After upgrading, Veeam For Office 365 build version will be 1.0.0.912. The new version of the Veeam Explorer for Microsoft Exchange will be 9.5.0.912

Solution

As a result of on-going R&D effort and in response to customer feedback, Update 1 includes many enhancements and bug fixes listed below.

General
  • Added a warning when a mailbox is selected which has an invalid Office 365 license.
  • The backup fails with the error JET_errTempPathInUse.
  • After a restore job, the iSCSI connection to a repository fails with JET_errInstanceUnavailable. The repository now reopens the database correctly.
  • After the first of January, 2017, some mailboxes fail to backup with Object reference not set to an instance of an object error. The update also corrects the content of the existing repository databases.
  • The configuration database consumes a lot of disk space: Circular logging is now used by default. The Veeam Backup for Microsoft Office 365 service will clear the old non-circular logs on the first start after the update.
  • The support ID is now visible in the license information.
  • The options dialog is shown incorrectly when a contrast theme is used.
  • The System Menu appears at a random place when a non-default DPI is used.
  • The headers on dialogs and wizards are too big because you use high DPI.
Restore
  • When you want to restore items with Veeam Explorer for Microsoft Exchange, the Conversation History folder isn’t visible for restore.

More Information

[[DOWNLOAD|DOWNLOAD UPDATE|https://www.veeam.com/download_add_packs/vmware-esx-backup/kb2224/]]

Veeam.Backup365.msi MD5 Checksum: 87ea25d92920cb009a500399cdd71abe
VeeamExplorerForExchange.msi MD5 Checksum: 258a892ff4b9f096aa93696f29edd657

Case administrators management: Guide for users

$
0
0

Challenge

Starting in Mar. 2017, only case administrators and license administrators will be able to submit support cases. Please make sure to define valid case administrators for your Veeam licenses.  This change only affects cases submitted via the customer portal.  If you need immediate support, feel free to call in to the support line: https://my.veeam.com/#/support/phone-support


Customers are now able to list people who can manage support tickets on behalf of their company – case administrators. By adding a case administrator, you invite an employee of your company, a reseller or a third-party contractor to join you in managing your cases with the Veeam® Support Team. Please note that case administrators can open cases, but they cannot manage your existing licenses.

Please also note Veeam Support is not able to change the case administrator for an account. This action can only be performed by license administrators (primary or secondary) for a given account.

To view your Production Licenses or discover what email is assigned as the License Administrator please click here: https://my.veeam.com/#/licenses/production
 
If you are a primary or a secondary license administrator, you already have access to case administrators management on My Account or by going here https://my.veeam.com/#/case-administrators-management. Here you can manage case administrators for all your licenses (Support IDs). Note: If the link for this pages does not load, this means you are not presently a license administrator for any contracts.

If you have lost access to the license administrator account or would like it to be changed, please create a licensing case.

User-added image

Solution

How do you assign case administrators to a license? 

Click Create case administrator to invite someone to manage your support cases. A case administrator can be an employee of your company, a reseller or a third-party contractor. On the next page you will need to provide their e-mail address.

If the person to whom you would like to give case administrator rights does not have a profile on veeam.com, you may be asked to specify their name and company. If your case administrator's company is not yet registered on veeam.com some additional info may be requested. 

User-added image
User-added image


Once all the necessary details are provided you will need to select Support ID(s) to which the newly created case administrator will be associated. By doing so you give them the right to use the Support ID(s) when opening cases on behalf of your company. 

User-added image


When the changes are saved, the new case administrator will be created and associated with the selected Support ID(s). Please note that if the specified user is not yet registered on veeam.com, they will have to complete the registration by following the corresponding link that they will receive by email. Should this be the case, the newly added case administrator will be able to access My Account and open cases only after confirming the registration.

If you would like to share a Support ID with one or several existing case administrators at the same time, please use the button Add administrator in the License view. Then, select administrators for this Support ID. Please note that the number of case administrators is limited – there can be no more than 10 case administrators per Support ID.  

User-added image


You can also assign several Support IDs at a time to one of your case administrators. For this please click Add Support ID in the Case administrator view.

User-added image


How do you remove case administrators from licenses? 

A case administrator can be removed from a license. Once this is done they will no longer be able to manage support cases for this Support ID (pic.1). Please note that you cannot remove other license administrators marked with a lock sign (pic.2).

User-added image


You can also remove a case administrator from all your licenses at once by following the link Delete administrator in the Case administrator view. Please note that you will not see this link if the user is a license administrator. 

User-added image


What rights do case administrators have? 

  • Case administrators can open, update and close support cases for the licenses assigned to them
  • Case administrators can also manage cases created by other case and license administrators 
  • Case administrators belonging to the same account can view your licenses but cannot manage them 
  • Case administrators cannot view and manage other case administrators

More Information

Starting in Mar. 2017, only case administrators and license administrators will be able to submit support cases. Please make sure to define valid case administrators for your Veeam licenses.

Configuring Veeam Agent for Microsoft Windows on servers with Microsoft DirectAccess enabled

$
0
0

Challenge

The backup job ​on Microsoft Windows Server OS with DirectAccess server enabled fails with the following error message:
 
Error: The remote procedure call failed and did not execute RPC function call failed. Function name: [GetSvcVersion]. Target machine: [xxx.xxx.xxx.xxx]

Cause

Microsoft DirectAccess locks ports 6000-47000. You can use the following PowerShell command to verify this:
 
Get-NetNatTransitionConfiguration

Solution

Change the custom port for RPC_transport to any idle port, which is outside the 6000-47000 range by editing the following registry key:
 
HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Endpoint Backup\EndPoint_Rpc_Transport_Port

Hyper-V Guest processing skipped (check guest OS VSS state and integration components version)

$
0
0

Challenge

Guest VMs will fail to engage VSS when application-aware image processing is enabled generating an error:

 Error    Guest processing skipped (check guest OS VSS state and integration components version) (System.Exception)

Cause

This issue has multiple potential causes, usually related to the Integration Services version of the failing guest server. This issue occurs when Application-Aware image processing is utilized in the Backup or Replication job settings for transactional quiescence using Microsoft VSS

Solution

Please Note:
 
  • A list of supported Guest OSes for each version of Hyper-V can be found here. 
  • Important! Server 2012 R2 and higher guests are not supported for VSS-enabled (AAIP) backups on 2008 R2 hosts due to integration components incompatibility.
  • If the VM Guest OS is 2012 and the Host is 2008R2:
    • View the Guest OS Application Event logs for errors with source: vmicvss and Event ID: 13.
    • If this error is present, open the Registry Editor (regedit) and navigate to:
      HKLM\SOFTWARE\Microsoft\WindowsNT\CurrentVersion\SystemRestore\
      Within that key create a new DWORD
      Name: ScopeSnapshots
      Value: 0
      Note: If the SystemRestore key is not present, you will have to create it.
 
--------------------------------------------------------------------------------------------------------- 

The solution section of this knowledge base article has been split into 3 different sections. Please go over each step in each of the 3 sections.

 
1. Integration Services
2. Within the Guest

3. VM Configuration

 
--------------------------------------------------------------------------------------------------------- 
 

1. Integration Services

Click here for a list of Hyper-V Integration Services and their corresponding build numbers.

How to identify…

Using Event Viewer

 
This section will provide directions on ensuring the Hyper-V Integration Services are up to date within the Guest OS of the VM that is failing to backup.
 
If Hyper-V Integration Services are out of date you will find Event ID 4000 within the Hyper-V-Integration section of the Event Viewer on the Hyper-V host where the VM is located.
 
User-added image
 

Using PowerShell (Server 2012 or newer)

 
Run the follow command in an Administrative PowerShell prompt on the host where the VM that fails to backup resides.
 
Get-VM | select VMName, IntegrationServicesState
 
The results of which will list out each present VM, and the state of its integration services.

 
User-added image
 
How to correct
Note: A reboot will most likely be required to complete the Integration Services update.
The following information is from the Microsoft page found
here.
 
Install or update integration services
For hosts earlier than Windows Server 2016 you'll need to manually perform install the update from within the guest operating system. These steps can't be automated or done within a Windows PowerShell session.
  1. Open Hyper-V Manager. From the Tools menu of Server Manager, click Hyper-V Manager.
  2. Connect to the virtual machine. Right-click the virtual machine and click Connect.
    User-added image
  3. From the Action menu of Virtual Machine Connection, click Insert Integration Services Setup Disk. This action loads the setup disk in the virtual DVD drive.
     User-added image

    Depending on the guest operating system, you may need to start the installation manually.

    User-added image
  4. After the installation finishes, you may be prompted to restart.
    User-added image
 
 

2. Within the Guest

The following steps and checks are to be performed within the Guest OS of the VM that is failing to backup.

A.Make sure Windows is running the most recent service pack.

B.Ensure that the VSS Storage Area and Volume Match

  1. From an Administrative Command Prompt, run the command ‘VSSUIRUN.exe”
    User-added image
  2. Check the [Settings] for each Volume and ensure that the Volume and the Storage area match.
    User-added image

C.Ensure there are no Dynamic disk or FAT\FAT32 volumes

Note: The VHD(X) that the VM runs off can be dynamic. The volume within the Guest OS cannot.
  1. Open Disk Management (diskmgmt.msc)
  2. Review the Type and File System columns
  3. VSS is not compatible with Dynamic disks or FAT\FAT32
    User-added image
    All volumes must be NTFS or ReFS

D.Check System Reserved partition free space.

  1. System Reserved partition must have more than 42MB of space free.
  2. If less than 42MB is free, try creating a shadow copy for the volume.
    User-added image
    Remember to delete the Shadow Copy if it is successful.

E.Start\Restart the “Hyper-V Volume Shadow Copy Requestor”

 

  1. Open Services (services.msc)

  2. Find the “Hyper-V Volume Shadow Copy Requestor” service.

  3. If it is ‘Stopped’, Start it.

  4. If it is ‘Running’, restart it.

 

3. VM Configuration

The following steps and checks are to be performed from the Hyper-V host level.
 
  1. Make sure the VM has a SCSI controller. One must be present, even if there are no devices to use the SCSI controller.

    The error will present itself in the Hyper-V VMMS > Admin Event log. Example:
    User-added image
    “The virtual machine ' Vm-Name' cannot be hot backed up since it has no SCSI controllers attached. Please add one or more SCSI controllers to the virtual machine before performing a backup. (Virtual   machine ID).”
  2. Within the Virtual Machine settings verify that the “Backup (Volume Snapshot)” option is enabled. 
    User-added imageUser-added image
  3. Make sure that the virtual machine files (VHD files) are not sitting in the root folder of the CSV, as this may prevent correct snapshot creation due to permission restrictions. We strongly recommend keeping virtual machine files in separate folder. More information regarding this can be found here.
    User-added image
 

 
Verification
Performing the following will you to determine if the steps performed about have corrected the issue without need to run the Veeam Backup & Replication job again.
Perform the following steps on the Hyper-V host that the VM is running on.
 
  1. Open an Administrator Command Prompt.
  2. Run the command:
    Diskshadow /L C:\writers.txt

    User-added image
  3. Run the command:
    list writers

    User-added image
 
Open the file that was created and and locate the VM name in the section for the Hyper-V writer. For each VM there's a "Caption" entry. The caption should read "online" or "child partition", and not "offline" or "saved state".
 

More Information

PowerShell script to tell you if you need to update your Integration Services
https://blogs.msdn.microsoft.com/virtual_pc_guy/2013/04/29/powershell-script-to-tell-you-if-you-need-to-update-your-integration-services/

Recommended hotfixes for Hyper-V servers:
 

Oracle error has occurred. ORA-01031: insufficient privileges

$
0
0

Challenge

VSS operations fails for Oracle with:

Oracle error has occurred. ORA-01031: insufficient privileges

Cause

This error is caused by an incorrect configuration for the service account leveraged for VSS operations when processing Oracle databases

Solution

The service account leveraged for Application Aware Image Processing needs to be included in the group:

ORA_DBA

Addition steps may be needed to allow authentication via the sqlnet.ora file for the failing database(s). Please open the sqlnet.ora file via text editor and save with the NTS setting as shown below for Windows native operating system authentication:

SQLNET.AUTHENTICATION_SERVICES= (NTS)

More Information

The sqlnet.ora file is typically found in the ORACLE_HOME\Network\Admin folder directory but may change based on Oracle installation parameters when deployed.

Using the Diskshadow Utility to manually test VSS operations

$
0
0

Challenge

This article describes the steps needed to manually create a volume shadow copy using the Diskshadow command line utility in Windows.

Cause

Veeam products use the Microsoft Volume Shadow Copy Service (VSS) for a variety of tasks:
  • In VMware environments, VSS ensures transaction consistency when backing up Windows VMs.
  • In Hyper-V on Windows Server 2008R2, 2012, and 2012R2, VSS is the primary component of the backup API.
  • Veeam Agent for Windows (formerly Veeam Endpoint Backup) uses VSS to help make sure data is consistent.
  • VSS is used to trigger transaction log truncation for Microsoft Exchange.
When troubleshooting, it is sometimes necessary to test if the Volume Shadow Copy Service is operating correctly. A quick test for a single volume can be performed using the Shadow Copies utility (see KB1794). Windows Server Backup is generally sufficient for isolation tests (and may be preferred by Microsoft Support), but it does not support all possible configurations.

The Diskshadow command line utility provides a greater degree of support, and is a better match for how Veeam products use the VSS API. However, it is only available on Windows Server 2008 or newer; it is not available for client versions of Windows.

Solution

Test shadow copy creation, then review Interpreting the Results (below).  


VMware Environments or Agent Backups


Copy-Only Mode


Use this method when transaction log truncation is not relevant. For best comparison, specify copy-only in the Veeam job settings.
From an administrator command prompt run the following commands:
 
​diskshadow/l <output path for log file> (the /l parameter is optional)
set verbose on
set context volatile

Next, add each volume that will be part of the backup set. Typically, this will be all volumes, including the system reserved partition.

Examples:
 
add volume \\?\Volume{xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxx}\
add volume X:
add volume C:\ClusterStorage\Volume1

See Finding Volume GUIDs at the end of this article for more information. Once all volumes have been added, start shadow copy creation:

create

Normally, shadow copies created this way will be automatically deleted when Diskshadow exits or is reset, but the delete shadows command is available if needed.

Note: Some issues may be isolated to a single volume. To identify which volume is responsible for an error, add only one volume to the backup set, create the shadow copy, then exit or reset Diskshadow before starting over with the next volume.
 

Full Mode


Full mode is the default setting for Veeam jobs. This method will notify VSS writers that a backup has occurred. Some applications, including Microsoft Exchange, will truncate transaction logs automatically in response to this notification. Other applications, such as Microsoft SQL Server, record that a backup has been taken but do not truncate transaction logs.

To test log truncation along with the creation of the shadow, run the following commands from an administrator command prompt:

diskshadow /l <output path for log file> (the /l parameter is optional)
set verbose on
set context volatile

Next, add each volume that will be part of the backup set. Typically, this will be all volumes, including the system reserved partition.

Examples:

add volume \\?\Volume{3c8d1bcb-9d95-11e5-80b0-806e6f6e6963}\
add volume X:
add volume C:\ClusterStorage\Volume1

See Finding Volume GUIDs at the end of this article for more information. Once all volumes have been added, start shadow copy creation:

begin backup
create
 
Once the shadow copy is created, inform the VSS writers that the backup has completed. For some writers, this will trigger transaction log truncation:
 
end backup
 
Normally, shadow copies created this way will be automatically deleted when the end backup command is completed, but the delete shadows command is available if needed.
 

Hyper-V Environments


Note: The following information is applicable to Server 2008R2, 2012, and 2012R2.

Veeam Backup & Replication creates shadow copies of volumes containing virtual machines. For transactionally-consistent backups (Application-Aware Image Processing or Hyper-V Quiescence), the Hyper-V VSS Writer triggers the Hyper-V Volume Shadow Copy Requestor service in each VM to create shadow copies of volumes within the VM. Error messages generated by shadow copy creation failure generally do not indicate whether the problem is isolated to a hypervisor volume or an in-guest volume.

Start by isolating whether the failure occurs only when using Application-Aware Image Processing or Hyper-V Quiescence. If the problem does not occur when both options are disabled, test shadow copy creation from within the virtual machine as described in the VMware Environments or Agent Backups section, above.

If snapshot creation is failing for crash-consistent backups, or if in-guest shadow copy creation does not result in any errors, it may be necessary to test shadow copy creation on the Hyper-V host. Because Hyper-V backup can be complex, a scripted approach is recommended. Veeam Support can run a scripted test that also collects a significant amount of useful logging. Contact support to schedule a remote session, and ask about hv_mkshadow.

Warning: Attempting to perform a shadow copy of a volume containing virtual machines will trigger in-guest shadow copy creation on all VMs on that volume unless specifically excluded. This may have negative effects on performance or responsiveness of these VMs and the Hyper-V host. Veeam Backup and the hv_mkshadow script exclude unnecessary VSS writer components from the shadow copy.
 

 

Finding Volume GUIDs


To add volumes that lack a mount point (such as the System Reserved Partition), use the volume GUID obtained through either the mountvol command-line tool, or the Shadow Copies utility.

To access the Shadow Copies utility, right click any volume and choose Configure Shadow Copies. On older operating systems, this may instead be a tab in Properties. In the Shadow Copies utility:
  1. Select the volume displayed as a GUID;
  2. Click Settings…
  3. Copy the volume GUID from the settings window and paste it into DiskShadow.
User-added image
Alternatively, run “mountvol” from a command prompt; below the usage information will be a list of GUIDs and their associated mount points, if any.

 

More Information

Interpreting the Results
 
Typically, if shadow copy creation fails via both Diskshadow and Veeam products, that indicates that the Veeam application is functioning correctly, and the problem is isolated to shadow copy creation. Troubleshoot the errors reported by Diskshadow and any events appearing in Event Viewer.
 
Two examples of failures reported directly by Diskshadow are as below. The first is an instance where the Volume Shadow Copy service fails, hangs, or is shut down midway through the creation process. The “RPC server” error can be a bit misleading; in this case a call was sent to the Volume Shadow Copy service and it was not there to receive it.
 
COM call "m_pVssBackup->StartSnapshotSet" failed.
 
The last operation failed.
                - Returned HRESULT: 800706ba
                - Error text: The RPC server is unavailable.
 
Another example shows a more common issue, that of the volume having insufficient free storage for the shadow copy creation.
 
The last operation failed.
                - Returned HRESULT: 8004231f
                - Error text: VSS_E_INSUFFICIENT_STORAGE
 
These messages will usually immediately follow the list of included writers, and should be the last output returned in the Diskshadow process.
 
In some cases, shadow copy creation will succeed via Diskshadow, but error or warning events will be generated in the event log. If similar errors are generated when Veeam backup or replication jobs fail to create a shadow copy, that usually indicates that the Veeam application is aborting the shadow copy in response to the errors. In this situation, the Veeam application can usually be assumed to be functioning correctly, so it is best to focus troubleshooting on any events appearing in Event Viewer.
 
Troubleshooting shadow copy creation or transaction log truncation may require the assistance of Microsoft technical support. The error
“COM call "lvssObject4->GetRootAndLogicalPrefixPaths" failed”
can be ignored. For more information, see Microsoft KB3025158.
 

Veeam Backup & Replication Upgrade Paths

$
0
0

Challenge

This article documents the path to be taken to get to the most recent version.

Solution

Important Note Regarding Performance
Veeam Backup & Replication provides an option during installation to create a local SQL Express instance. This option is often taken and as such older versions of Veeam that are then updated may be running on old SQL Express instances. This can affect performance. It may be advised to upgrade the local SQL instance to the most current supported version after first upgrading Veeam to the latest version and update. All versions of Veeam Backup & Replication after 8.0.0.917 (Patch 1) support SQL 2014.
 
Note: Versions 9.0 and higher require a 64 bit OS for installation.
 
Please refer to the following links for steps and more information on upgrading to 9.0 or 9.5:
 
Upgrade to 9.0: https://helpcenter.veeam.com/archive/backup/90/vsphere/upgrade_vbr.html
 
Upgrade to 9.5:  https://helpcenter.veeam.com/docs/backup/vsphere/upgrade_vbr.html?ver=95
 
9.5 Update 2:  https://www.veeam.com/kb2283
 
 
7.0.0.x
7.0.0.871 -> 9.0.0.x -> 9.5.0.x
To upgrade from 7.0 to 9.0, you must have 7.0 Patch 4 installed (7.0.0.871).
Link to 7.0 Patch 4:  https://www.veeam.com/kb1891
 
Refer to above links for steps to upgrade.
 
8.0.0.x
8.0.0.x -> 9.0.0.x -> 9.5.0.x
8.0.0.2084 -> 9.5.0.x
To upgrade from 8.0 to 9.5, you must have 8.0 Update 3 installed (8.0.0.2084).
Link to 8.0 Update 3:  https://www.veeam.com/kb2068
 
Refer to above links for steps to upgrade.
 
9.0.0.x
9.0.0.x -> 9.5.0.x
Any version of 9.0.0.x can upgrade directly to 9.5.
 
Refer to the above links for steps to upgrade.


 

More Information

Veeam Version 9.0 Supported Versions: 
 
vSphere Supported Versions: 4.1, 5.x, 6.0
 
Hyper-V Supported Versions: 2008 R2 SP1, 2012, 2012 R2
 
Veeam Database SQL Versions: SQL 2005, 2008, 2008 R2, 2012, 2014
 
 
Veeam Version 9.5 Supported Versions:
 
vSphere Supported Versions: 4.1, 5.x, 6.x (6.5 Supported with 9.5 Update 1 – 9.5.0.823)
 
Hyper-V Supported Versions: 2008 R2 SP1, 2012, 2012 R2, 2016, Nano
 
Veeam Database SQL Versions: SQL 2008, 2008 R2, 2012, 2014, 2016

 

LVMDriver : Failed to create LVM Instance

$
0
0

Challenge

In RHEL 7.4, Veeam Agent for Linux operations such as job runs or job creation are failing with the following error:
LVMDriver : Failed to create LVM Instance

Cause

With RHEL 7.4, the default global unit setting in the /etc/lvm/lvm.conf changed from 

units = "h"

to

units = "r"

This value option is not recognized by some distributions and programs. It interferes with the operations of Veeam Agent for Linux.

Solution

Before implementing this change, please check with your Linux Administrator that they approve of updating the global unit setting from “r” to another value. You can find a full list of available unit options at this RHEL link.

More Information

If the lvm.conf file doesn’t show a units value of “r”, please open a support case for further investigation. 

How to Re-create the Database of Veeam Agent for Microsoft Windows

$
0
0

Challenge

Veeam Support is instruction you to re-create the database of Veeam Agent for Microsoft Windows.

Cause

The Veeam Agent for Microsoft Windows database files have been corrupted.

Solution

Perform the following actions:

1. Run regedit.exe and locate the HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Endpoint Backup key. Create the following value under this key:
Name = Recreatedatabase 
Type = DWORD 
Value =

2. Go to Control panel > Administrative Tools and run Services. Restart the Veeam Agent for Microsoft Windows service.

A new database instance will be created (this usually happens within 5 minutes).

Veeam Backup & Replication - SQL Backup Guide: Using Microsoft SQL Server Agent With Application - Aware Image Processing

$
0
0

Challenge

This guide was created to assist you with successfully backing up, and restoring, Microsoft SQL databases.

Cause

Some highlights from this guide:

• Veeam Backup v7 most commonly used restore options for SQL
• Veeam Backup Job Configuration when backing up SQL
• Log Truncation, when and when not to use it
• Excluding the .bak and .trn Files
• Many more technical considerations included

Solution

Direct link for Veeam Backup & Replication 9.0:
Veeam Backup & Replication SQL Backup Guide

Direct link for Veeam Backup & Replication 9.5:
Veeam Backup & Replication SQL Backup Guide
 

Install or Upgrade fails with “Error occurred during certificate processing. Error 6”

$
0
0

Challenge

An upgrade operation from Veeam 8 to Veeam 9 (or from Veeam 9 to Veeam 9.5) fails with the error message „Error occurred during certificate processing”.
The following lines can be found in BackupSrvLog.log located in C:\ProgramData\Veeam\Setup\Temp :

 
***Veeam*** Binding certificate to port...
***Veeam*** VmWinError has been occurred. Error: 6.
Error occurred during certificate processing.

The below commands in CMD produce an error “The handle is invalid”:
 
C:\>netsh http show urlacl
URL Reservations: 
----------------- 

The handle is invalid.
C:\>net start http 
The service name is invalid.

Cause

This is caused by an HTTP service issue.
Either the service is not started or it is disabled in registry and cannot be started.

User-added image
(HKLM\SYSTEM\CurrentControlSet\services\HTTP, Start)

Solution

a) Change the start type of the service in registry from 4 to 3:

User-added image
Refference: https://technet.microsoft.com/en-us/library/cc959920.aspx

b) Reboot the server.
c) Verify that the service was started by running "net start http" command in CMD.
d) Start Veeam installation/upgrade again.

More Information

If the installation fails with Error 5 instad of Error 6, please check the following KB article:
https://www.veeam.com/kb2137

Replication job to VMware Virtual Volumes (VVols) fails with VDDK error: 7 (A file access error occurred on the host or guest operating system)

$
0
0

Challenge

Replication job to a VVOL target will fail with the error below:

User-added image

Task.<VM name>.vm-<vm-ref> will contain following error:
[TIMESTAMP] <21> Info             [AP] (5e06) disconnecting
[TIMESTAMP] <55> Error                  [AP] (5e06) error: VDDK error: 7 (A file access error occurred on the host or guest operating system). Value: 0x0000000000000007
[TIMESTAMP] <55> Error          Failed to write to a virtual disk

 

Cause

Due to a change in VMware vSphere 6.0 Update 1, replication to VVol datastores is no longer possible with Veeam. This article will be updated in case more recent VMware vSphere updates fix this newly introduced issue.

Here is an official statement from VMware VDDK release notes:
Avoid creating snapshots for restore on VVol datastores. Due to Virtual Volume (VVol) implementation in the vSphere 6.0 release, VMware recommends against creating a snapshot (then reverting and deleting it) when restoring files on a VVol datastore. This is because writing to a non-leaf disk (such as a snapshot backing file) is considered a layering violation and throws an error on many VVol storage devices. Writing to the leaf disk of the snapshot is not a layering violation. The restore snapshot remains mandatory for SAN transport, which is not supported on VVol datastores anyway.

Solution

Replication job to VMware Virtual Volumes (VVols) is no longer supported.

More Information

For more information please review http://pubs.vmware.com/Release_Notes/en/developer/vddk/65/vsphere-vddk-65-release-notes.html

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

$
0
0

Challenge

When attempting to update the Veeam Backup & Replication or Veeam ONE software, an error is encountered:
This Veeam Backup & Replication/Veeam ONE 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 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

HCL - Infinidat Backup Appliance B-Series

$
0
0

Challenge

Product Information

Product Family: Infinidat Backup Appliance 
Status: Veeam Ready - Archive 
Classification Description: Verified disk archive storage that can be used as a Backup Copy target.  Synthetic full backups, granular restores, and vPower features may not provide sufficient performance or be supported.   

Solution

Product Details

Model number: IBA B-series 
Number of Drives: 15/240 
Drive type: SSD/NL-SAS 
Firmware version: 1.3.3.1 
Additional support: Any hardware configuration with an equal or greater hardware configuration 
General product family overview: The INFINIDAT Backup Appliance (IBA) is an enterprise grade, high performance, high capacity and highly available backup appliance. 
The IBA maximizes deduplication efficiency through using an innovative inline & variable block size deduplication technology. 
The IBA supports the NFS, CIFS, VTL and OST protocols. 
The IBA support deep integration with VEEAM Backup & Replication software by creating a VEEAM repository on the IBA system and a VEEAM agent that runs inside the IBA process space achieving better backup performance. 

 

Veeam Details

Veeam Build Number: 9.5.0.1038 
Veeam Settings:  

  • Repository Type: Linux 
  • Deduplication: OFF 
  • Compression: Optimal 
  • Storage Optimization: Local Target 
  • Per-VM Backup Files: ON 
  • Decompress before storing: ON 
  • Align backup file blocks: OFF 

More Information

Company Information

Company name: Infinidat
Company overview: INFINIDAT was founded in 2011 by a team of storage industry experts focused on helping customers to eliminate compromises between cost, capacity, functionality and performance when it comes to their storage and backup infrastructure, enabling them to focus more on what makes them competitive. 

HCL - Promise VTrak

$
0
0

Challenge

Product Information

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

Solution

Product Details

Model number: VTrak E5300f, E5302f, E5600f, E5800f
Number of Drives: 24 
Drive type: 9 Disks Seagate ST3000NM00 SAS, 3 Disks ST6000NM00 SAS, 4 Disks ST4000NM01 SAS, and 8 Disks HUS7260 SAS 
Firmware version: 11.04.0000.00 
Veeam Build Number: 9.5 
Additional support: Any hardware configuration with an equal or greater hardware configuration  
General product family overview: Storage subsystem with two storage controllers with 4 FC ports on each storage controller 

 

Veeam Details

Veeam Build Number: 9.5
Veeam Settings:  

  • Repository Type: Windows 
  • Deduplication: Yes
  • Compression: Optimal
  • Storage Optimization: Local Target 
  • Per-VM Backup Files: No 
  • Decompress before storing: No 
  • Align backup file blocks: No 

More Information

Company Information

Company name: Promise Technology Inc. 
Company overview: Promise Technology Inc. is a recognized global leader in the storage industry and the leading developer of high-performance storage solutions, designed for the data center, surveillance, cloud and rich media markets. Always striving to meet the rigorous demands of our customers, Promise has earned a reputation for developing innovative storage solutions for vertical markets which deliver practical answers to the business challenges facing large enterprise corporations, small to medium businesses, security integrators and creative professionals. 

Promise is focusing on opening up new data storage markets, redefining storage possibilities and seeking opportunities for integrated development. This passion for innovation has kept us at the forefront of the storage industry and led us to form strategic alliances with leading storage-related companies worldwide. Promise has quietly become the preferred storage provider for the world’s top resellers and integrators, who are proud to sell our technology and products through their vertical markets and channels. 

Veeam ONE installation fails with "Couldn't create crypto provider" message

$
0
0

Challenge

Veeam ONE installation fails with "Couldn't create crypto provider" message.

Cause

One of the known issues with Microsoft update 3000850 as per this MS KB article is the following: Opening Credential Manager fails with error 0x80090345", that also affects creating crypto provider.

Solution

To work around this problem, set the value of the ProtectionPolicy registry entry to 1 to enable local backup of the MasterKey instead of requiring a RWDC in the following registry subkey: HKEY_LOCAL_MACHINE\Software\Microsoft\Cryptography\Protect\Providers\df9d8cd0-1501-11d1-8c7a-00c04fc297eb
 

More Information

If you have any questions, contact Veeam Support.

Moving Veeam ONE database to a different SQL Server

$
0
0

Challenge

You need to move the Veeam ONE database from the original SQL Server to a different SQL Server and change Veeam ONE Server configuration settings.

Solution

To change SQL Server or database connection settings for Veeam ONE Server, you can use the Veeam ONE Settings utility.

To modify connection settings, follow the instructions below.

Provision a domain account for Veeam ONE Monitor and Veeam ONE Reporter on the new SQL Server. This can be one account or two different accounts. Move the database to the new SQL Server. Depending on Veeam One version, grant the account(s) appropriate permissions:

 
Veeam One 6.xdb_owner 
Veeam One 7.xSystem Administrator
Veeam One 8.xSystem Administrator
Veeam One 9.0System Administrator
Veeam One 9.5Public role (default permissions)
CREATE ANY DATABASE permissions
db_owner role on the Veeam ONE database
public, db_datareader, SQLAgentUserRole permissions on the msdb database
[For Always-On Availability Groups] VIEW SERVER STATE permissions 
  

Next, modify the accounts that are used by monitoring and reporting components of Veeam ONE.

First, modify connection settings for Veeam ONE Monitor. To accomplish this, perform the following steps:
  1. Launch the Veeam ONE Settings utility available under the following path:

    C:\Program Files\Common Files\Veeam\Veeam ONE Settings\VeeamOneSettings.exe

  2. In the menu on the left, select General, open the Database tab and make the necessary changes in the SQL Server section.
    User-added image

  3. Make sure this account has sufficient privileges on the Veeam ONE database on the SQL Server side, as it will be used for performance data collection.

  4. Click the Test Connection button to check whether new configuration settings are correct.

  5. Save changes.

  6. Restart Veeam ONE Monitor Server service.

Then modify connection settings for Veeam ONE Reporter and Business View. To accomplish that, follow the next steps:

  1. In the list of services, locate Veeam ONE Reporter Server service and choose to modify its properties. Open the Log On tab and specify the necessary account for the service in the Log on as section.

  2. Make sure this account has sufficient privileges on the Veeam ONE database on the SQL Server side, as it will be used for data collection.

  3. Launch the Veeam ONE Settings utility available under the following path:

    C:\Program Files\Common Files\Veeam\Veeam ONE Settings\VeeamOneSettings.exe

  4. In the menu on the left, select General, open the Web Identity tab and make the necessary changes in the Web identity section.
    User-added image

  5. Make sure this account has sufficient privileges on the Veeam ONE database on the SQL Server side, as it will be used for overall Web UI operation and reports creation.

  6. Save changes.

  7. Restart Veeam ONE Reporter Server service.

 

IMPORTANT!

  • Should the database be connected to a different Veeam One installation, make sure there is no version\build mismatch. Otherwise, the application will fail.
  • Starting with Veeam One v8, database partitioning became an option. If this option has been in place on the previously used SQL server, follow the steps described in this KB article to implement it on the new SQL server. 
  • Starting with Veeam One v9.5, index defragmentation maintenance job for Veeam One database has been implemented. To create this job on the new SQL server download and run this script.

NOTE
Veeam One database partitioning jobs (VeeamOneSqlMaintenance_Med and VeeamOneSqlMaintenance_Med) and index defragmentation maintenance job (VeeamOne Maintenance Job) will remain intact on the old SQL server under SQL Server Agent > Jobs node and need to be removed manually.

More Information

If you have any questions or problems, please contact Veeam Support at http://www.veeam.com/support.html
Viewing all 4469 articles
Browse latest View live


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