VMware snapshots playing havoc with availability groups – Mark Read. Share with your social network DBA’s, have you ever woken up one morning and found your SQL 2012, 2014 or 2016 Availability Group had mysteriously failed over during the wee hours? Of course there can be several legitimate reasons why it failed over (Windows Cluster or Quorum issue, O/S resources, SQL Server/node rebooted, SQL Services restarted, lost network connectivity, storage went offline, etc), but then there are those weird and seemingly unexplainable events that get you scratching your head after a look in all the obvious places for a smoking-gun.
This occurred with a client a while back with a new virtualised data centre infrastructure build (VMware 6.0). I’d finished the SQL build and test, but the infrastructure team were still completing their configuration tasks. The availability group session timeout (ping connectivity) default setting for SQL 2012, 2014 and 2016 is 10 seconds. I increased this to 30 seconds and the false failover issue caused by the VM snapshot went away. All you need to know about Oracle Database licensing with VMware - Blog dbi services. You are running Oracle on VMware and are not 100% sure that you are compliant with the Oracle licensing rules? This article is for you! As I have been confronted several times with Oracle License reviews with VMware installations, I decided to write this article in order to provide answers to the most frequent questions I have received from customers.
Licensing is not an easy topic to address and this difficulty is not specific to Oracle. Additionally, this difficulty increases with the number of different software editors and the related software policy you have to manage as a License Manager, IT manager or CTO. In this article, I will focus on Oracle licensing and more specifically on a very frequent use case: Oracle Database installed on a VMware ESX infrastructure. Oracle on VMware: supported, but not certified Crash course on Oracle licensing terminology In order to quantify and measure the way customers are using Oracle software, Oracle has introduced the notion of License Metric. Vmware oracle databases on vmware best practices guide. VMware vSphere 6.0 Release Notes. Components of VMware vSphere 6.0, including vCenter Server, ESXi, the vSphere Web Client, and the vSphere Client do not accept non-ASCII input.
The VMware Product Interoperability Matrix provides details about the compatibility of current and earlier versions of VMware vSphere components, including ESXi, VMware vCenter Server, the vSphere Web Client, and optional VMware products. Check the VMware Product Interoperability Matrix also for information about supported management and backup agents before you install ESXi or vCenter Server. The vSphere Web Client is packaged with the vCenter Server. You can install the vSphere Client from the VMware vCenter autorun menu that is part of the modules ISO file. To view a list of processors, storage devices, SAN arrays, and I/O devices that are compatible with vSphere 6.0, use the ESXi 6.0 information in the VMware Compatibility Guide.
Some devices are deprecated and no longer supported on ESXi 6.0. The known issues are grouped as follows.