Category Archives: Uncategorized

SharePoint Explorer is unable to find content database

Ran into this Veeam error today when demonstrating Veeams Explorer for SharePoint to a customer.

The customer was using a supported version of SharePoint and Veeam was configured to use a licensed version SQL 2014. After checking over the backup job settings and ensuring no errors or warnings were being thrown I hit the Veeam forums. Fortunately, someone else had seen the same problem which you can find here.

“The Application-aware logic uses NetBIOS names to locate corresponding SQL servers during backup and in some cases (where SQL server for the site collection is specified using IP address or SQL Server alias, for example), Veeam B&R still does not have the required information, even provided that application-aware backup was successful. If this is your case (I believe support will be able to verify that), you can configure SQL server mapping manually via the registry, as far as I know, there’s an ability to do that.”

Big props to ‘ jtroobfor detailing the steps on how to configure the SQL server mappings which are detailed below,

Step 1. Create HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\SPSToSQLMap\ key. It should be a sibling to the Veeam Backup and Replication key, not its child.

Step 2. Add a string, where ‘value name’ is the SharePoint server FQDN (if FQDN doesn’t work, try NetBIOS), and ‘value data’ = “<SQL_SERVER>\<SQL_INSTANCE>”.

E.g. Each value should be named by the SharePoint server FQDN and contain ‘SQL_Server\Instance’ as value data. So create a string, enter the value name of Sharepoint-01.domain.local (or e.g. Sharepoint-01), then value data = sql01\SP2013. If using the default unnamed instance, value data would just be “sql01”.

Step 3. If you have multiple SQL servers for a single SharePoint, separate instance names by; e.g. SQL01\SP2013; SQL02\SP2013. Add as many as needed if there are multiple Sharepoint servers.

Step 4. Close and re-open Veeam Backup Console  & test.

After modifying the registry on the Veeam B&R server, the next issue we encountered was a database upgrade warning. Again, Veeam forums to the rescue,

Essentially, by selecting ‘Yes’ the database from the mounted backup file (under C:\VeeamFLR folder) will be upgraded, the backup file itself and the production database will be left intact.

After clicking yes we could restore items from SharePoint successfully.

Failed to create database VeeamBackup. Create failed for database VeeamBackup.

Recently encountered this issue after attempting to install Veeam B&R v9 on a server that at one stage in the servers life had an instance of Veeam B&R  installed then uninstalled.

I cannot comment on how it was uninstalled but my very first installation of Veeam B&R went smoothly, I utilised the existing Veeam DB and ran up a couple backup jobs. Unfortunately after a couple days, several issues started to happen. Essentially the existing DB was no good and I needed to wipe the slate clean.

Unfortunately, several unsuccessful installations later, Veeam was now having a problem when creating the database during installation.

The exact error was ‘Failed to create database VeeamBackup.Create failed for database VeeamBackup’

What finally fixed the problem was to uninstall all Veeam B&R & SQL components then  manually delete the left-over Microsoft SQL folder in the program files to resolve the issue.


Instant VM Recovery Lease Timeout

Have you ever tried to perform an instant VM recovery and the VM just refused to publish yet when you try smaller VMs it is successful?

The problem may be the Instant VM recovery lease is timing out which can be caused by a number of factors.

  • VM with large disks attached
  • Large backup chain
  • Slow storage
  • Deduplication on the storage

To increase the lease timeout, you need to create two registry entries which go under ‘HKLM\SOFTWARE\Veeam\Veeam Backup and Replication’

IrMountLeaseTimeOut (REG_DWORD) value (default one is 30 minutes).
IrVcdMountLeaseTimeOut (REG_DWORD)

VM Instant Recovery Reg

To take effect, you must restart the Veeam Backup & Replication service.

Attaching tape to virtual Veeam

So it turns out there is a free tool that allows you to expose physically connected tape devices via ISCSI protocol. This could be really good news for those forced to use a physical Veeam server to attach to your tape library.

IBM Storwize IP replication

I was recently working on a VMware SRM solution utilising an IBM Storwize v3700 SAN at each site with remote mirror. I had configured a global mirror with change volume relationship over IP which works beautifully when both source and target SANs were in the same subnet/building. Once the target SAN was moved out of the building to the DR site, the IP SAN traffic went through the gateway across the WAN to the other site. The performance for the IP replication was pretty average, to say the least,  out of a 100Mbps link, I could only achieve 1MBps, even though windows file copy would easily saturate the link providing 10MBps consistently.

Windows File Copy


We ended up testing the link for packet loss and while it did show some packet loss, I had assumed that given that Windows file copy could achieve 10MBps then the Storwize SAN from IBM should be able to achieve similar results.
Well, it turns out that’s incorrect. As per the below snippet from the IBM System Storage SAN Volume Controller and Storwize V7000 Replication Family Services Redbook.

packet loss results in sever performance degradation well out of proportion to the number of packets actually lost. A link that is considered “high quality” for most TCP/IP applications might be completely unsuitable for the remote mirror.

IBM Storwize Packet Loss


Now, this helped explained why Veeam could perform Backup Copy to the DR site at a consistently fast 10MBps without any problems yet the remote mirror performed so badly.

After resolving the packet loss problem which was dodgy SFP+ fibre adapters and a couple cables, the remote mirror performance jumped straight to 10MBps and has stayed there consistently ever since.

Configuring VMware Capacity Planner for IP subnet discovery (2014366)

I had trouble discovering servers on a different subnet so after a little digging, I found the below which did the trick.


After installing the VMware Capacity Planner Datamanager and configuring the system to receive new systems, you can perform these steps to discover systems on an IP subnet:

  1. Open Capacity Planner Data Manager.
  2. Navigate to Admin > Options.
  3. Go to Modules > Discover > Settings.
  4. Deselect the Discover Groups / Domains option.
  5. Under the Node Discovery tab, deselect Lan Manager Systems and Active Directory Systems.
  6. Select DNS Names and IP Address.
  7. Under the System Discovery tab, select the Test Connection to system during discovery option.
  8. Under the IP Subnets tab, click Add.
  9. Add the appropriate Subnet Range by Class or CIDR Notation.
  10. Click Apply.
  11. Click Tasks > Run Manual Tasks > Run Discover Task.The IP subnet that has been configured are pinged and systems are discovered.

Performance of vSphere Flash Read Cache in VMware vSphere 5.5


VMware vSphere® 5.5 introduces new functionality to leverage flash storage devices on a VMware ESXi™ host. The vSphere Flash Infrastructure layer is part of the ESXi storage stack for managing flash storage devices that are locally connected to the server. These devices can be of multiple types (primarily PCIe flash cards and SAS/SATA SSD drives) and the vSphere Flash Infrastructure layer is used to aggregate these flash devices into a unified flash resource. You can choose whether or not to add a flash device to this unified resource, so that if some devices need to be made available to the virtual machine directly, this can be done. The flash resource created by the vSphere Flash Infrastructure layer can be used for two purposes: (1) read caching of virtual machine I/O requests (vSphere Flash Read Cache) and (2) storing the host swap file.

VMware Hybrid Cloud: What is it?

VMware Hybrid Cloud, allows you to migrate your workload from your own vSphere infrastructure onto another vSphere cloud which is maintained and operated by an external party. Another example is; in some situations, you may need both a local server running specific applications and a cloud service that hosts additional applications, files, or databases.  In such a situation, the two are often configured for interoperability.