Home > Blogs > Support Insider

Windows 2008+ incremental backups become full backups in ESXi 6.0 b3825889

vmware_tools_iconVMware is actively working to address a recently discovered issue wherein an incremental backup becomes a full backup when backing up Windows 2008 (or higher) virtual machines with VSS-based application quiesced snapshot.

This recent CBT (Changed Block Tracking) issue does not cause any data loss or data corruption.

This issue is well understood and VMware engineering is actively working on a fix.

For more details on this issue and latest status on resolution, please refer to KB article: After upgrading to ESXi 6.0 Build 3825889, incremental virtual machine backups effectively run as full backups when application consistent quiescing is enabled (2145895)

Subscribe to the rss feed for the KB article to ensure you do not miss any update by using this link.

New and updated KB articles for NSX for vSphere 6.2.3

NSXWe’ve just released the bits for NSX for vSphere 6.2.3 and thought all of your making the upgrade would want to be on top of all the ins and outs of this release.

Here is a list of new and/or updated articles in our Knowledgebase:
NSX for vSphere 6.2.3   |   Released 09 June 2016   |   Build 3979471

Of course, do not miss the release notes, which can be found here: NSX for vSphere 6.2.3 Release Notes

NSX for vSphere Field Advisory – May 2016 Edition

NSXOur NSX support team would like all of our customers to know about important KB updates for NSX for vSphere issues.

Here’s what’s new and trending-

Important: Upgrades from NSX for vSphere 6.1.6 to 6.2.2 are not supported.
See KB 2145543 NSX Controller upgrade fails with the error: 409 (Conflict); invoking error handler.

vCloud Networking and Security will reach End of Availability and End of General Support on September 19, 2016.

NEW! See our first NSX KBTV YouTube video: https://youtu.be/5pSNfnk1_MA

vShield Endpoint and vCNS End Of Availability (EOA) – See:
KB 2105558 Support for partner integrations with VMware vShield Endpoint and VMware vCloud Networking and Security.
KB 2110078 Implementation of VMware vShield Endpoint beyond vCloud Networking and Security End of Availability (EOA).
Future releases of NSX for vSphere 6.2.x will enable customers to manage vShield Endpoint from NSX Manager. Customers who purchased vSphere with vShield Endpoint will be able to download NSX.

NSX for vSphere 6.1.x will reach End of General Support on October 15, 2016.

​NEW! VMware has extended the End of General Support date to three years after GA for NSX for vSphere 6.2.x only.  The VMware Lifecycle Product Matrix now reflects this change.

New and Important issues:

KB 2144551 Configuring a default gateway on the DLR in NSX fails
KB 2144605 vCenter 6.0 restart/reboot may result in duplicate VTEPs on VXLAN prepared ESX hosts.
KB 2143998 NSX Edge virtual machines do not failover during a vSphere HA event
KB 2145571 NSX Edge fails to power on when logging all ACCEPT firewall rules
KB 2145468 NSX Edge uplink interface does not process any traffic after it is disabled and re-enabled in ECMP environment
KB 2139067 Shutdown/Startup order of the NSX for vSphere 6.x environment after a maintenance window or a power outage.  Please refer to the updated sequence for a cross VC environment.
KB 2145447 NetX/Service Instance filter created in vCNS disappears after upgrading to NSX
KB 2145322 NSX Edge logs show Memory Overloaded warnings
KB 2144901 Unexpected TCP interruption on TCP sessions during Edge High Availability (HA) failover in VMware NSX for vSphere 6.2.x
KB 2145273 Troubleshooting DLR using NSX Central CLI
KB 2145359 Pings fail between two VMs on different hosts across a logical switch

How to track the top field issues:

Top 20 vRealize Operations Manager articles for May 2016

Top 20Here is our Top 20 vRealize Operations Manager articles list for May 2016. This list is ranked by the number of times a VMware Support Request was resolved by following the steps in a published Knowledge Base article.

  1. vRealize Operations Manager 6.1, 6.2, and 6.2.1 Sizing Guidelines
  2. Update sequence for vSphere 6.0 and its compatible VMware products
  3. Resetting the Administrator password in VMware vRealize Operations Manager appliance
  4. Important information before upgrading to vSphere 6.0
  5. High garbage collection occurs on the VMware vRealize Operations Manager (vROps) Master node
  6. Adding additional storage to the VMware vRealize Operations Manager Analytics or UI virtual machine
  7. Using custom email templates in VMware vRealize Operations Manager 6.x
  8. VMware vRealize Operations Manager for Horizon 6.2 Broker Agent fails to pair with the Horizon adapter
  9. After upgrading to VMware vRealize Operations 6.2.0a, vCenter adapters remain in Starting state
  10. vRealize Operations Manager 6.x is inaccessible, status of all nodes is Waiting for Analytics to Start
  11. VMware vRealize Operations Manager 6.x displays the critical alert: FSDB file corrupted for resourceInternalId
  12. Ensuring adequate free disk space is available on VMware vRealize Operations Manager 6.x nodes
  13. Uninstalling a Solution or Management Pack from VMware vRealize Operations Manager
  14. End Point Operations Agent is not collecting data in vRealize Operations Manager 6.2.0a or 6.2.1
  15. Cluster Status is stuck at Going Online in VMware vRealize Operations Manager 6.0.x
  16. Creating low disk space alerts for the virtual machine guest file systems in VMware vRealize Operations Manager 6.0.x
  17. Understanding Feature Accommodation between VMware vSphere 6.0 and vRealize Operations 5.8.x and 6.0.1 Feature Accommodation
  18. VMware Horizon View topology information is not present in vRealize Operations Manager for Horizon View 6.x
  19. Restarting VMware vRealize Operations Manager 6.0.x fails with a Waiting for Analytics message in the Admin UI
  20. After cancelling the selected alerts in VMware vRealize Operations Manager 6.0.x, one or more of the selected alerts remain

Top 20 vRealize Automation articles for May 2016

Top 20Here is our Top 20 vRealize Automation (vRA) articles list for May 2016. This list is ranked by the number of times a VMware Support Request was resolved by following the steps in a published Knowledge Base article.

  1. Update sequence for vSphere 6.0 and its compatible VMware products
  2. Repairing or updating the trust between all components within a VMware vRealize Automation 6.x environment
  3. Removing a virtual machine from Management in VMware vRealize Automation 7 using Cloud Client
  4. Important information before upgrading to vSphere 6.0
  5. VMware vCloud Suite 7 Fulfillment
  6. Removing a virtual machine from Management in VMware vRealize Automation or VMware vCloud Automation
  7. Requests get stuck at In Progress or Pending Approval status in VMware vRealize Automation
  8. Various tasks fail after upgrading or migrating to VMware vRealize Automation 6.1.x or 6.2
  9. Deleting an endpoint in vRealize Automation fails with the error: This endpoint is being used by # compute resources and # storage paths and cannot be deleted
  10. Logging in to a tenant with verified administrator credentials or user credentials fails in VMware vRealize Automation 6.2.x
  11. Installing or configuring VMware vRealize Automation fails with the error: This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms
  12. Certificate troubleshooting, supportability, and trust requirements for vRealize Automation 6.2
  13. Connecting to a resource using the Remote Console (VMRC) option in VMware vRealize Automation 6.2.1 fails with the error: Cannot establish a remote console connection
  14. Provisioning fails after creating a new blueprint from VMware vRealize Automation 7.0.1
  15. Signing VMware vRealize Automation certificates using an internal Microsoft CA signing authority
  16. Configuring appliance database server for replication in VMware vRealize Automation Center virtual appliance
  17. Unable to add Active Directory users or groups to vCenter Server Appliance or vRealize Automation permissions
  18. Provisioning virtual machines using VMware vRealize Automation workflows fails to progress through the expected lifecycle
  19. Logging in to tenant fails after adding authenticated proxy config in VAMI in VMware vRealize Automation 7.0.x
  20. VMware vRealize Automation 7.0 patch to prevent potential data loss when using bulk import

Top 20 vSAN articles for May 2016

Top 20Here is our Top 20 vSAN articles list for May 2016. This list is ranked by the number of times a VMware Support Request was resolved by following the steps in a published Knowledge Base article.

  1. Best practices for Virtual SAN implementations using Dell PERC H730 or FD332-PERC storage controllers
  2. VMware Virtual SAN 6.2 on disk upgrade fails at 10%
  3. Required VSAN and ESXi configuration for controllers based on the LSI 3108 chipset
  4. vCenter Server 6.0 Update 2 displays on non-Virtual SAN enabled ESXi hosts displays the message: Retrieve a ticket to register the Virtual SAN VASA Provider
  5. VMware Virtual SAN 6.1 or 5.5 Update 3 Disk Groups show as Unmounted in the vSphere Web Client (DDH)
  6. VMware Virtual SAN 6.2 on disk upgrade fails due to CBT enabled virtual disks
  7. Troubleshooting VSAN SSD congestion on vSphere 5.5
  8. Following maintenance, hosts in a Virtual SAN cluster may erroneously report the error: Host cannot communicate with all other nodes in virtual SAN enabled cluster
  9. vSphere 5.5 Virtual SAN requirements
  10. Support statement for 512e and 4K Native drives for VMware vSphere and VSAN
  11. VMware Virtual SAN 6.0 Requirements
  12. Replacing VMware vCenter Server Certificates with SSL Certificate Automation Tool causes the vSAN health check plugin to stop functioning with the error: Error HTTP status 503
  13. Adding existing Virtual SAN hosts to a new Virtual SAN cluster after rebuilding vCenter Server
  14. Consolidating disks in VMware Virtual SAN fails with the error: An error occurred while consolidating disks: msg.disklib.NOSPACE
  15. VMware Virtual SAN 6.2 fulfillment
  16. VSAN performance object missing after upgrading to VSAN 6.2
  17. Enabling or disabling a Virtual SAN cluster
  18. Requirements and considerations for the deployment of VMware Virtual SAN (VSAN)
  19. Virtual SAN Health Service – Network Health – Hosts disconnected from vCenter
  20. Virtual SAN Health Service – Physical Disk Health – Component Metadata Health

Top 20 NSX articles for May 2016

Top 20Here is our Top 20 NSX articles list for May 2016. This list is ranked by the number of times a VMware Support Request was resolved by following the steps in a published Knowledge Base article.

  1. Update sequence for vSphere 6.0 and its compatible VMware products
  2. Downloading and enabling VMware vShield Endpoint 5.x on supported VMware vSphere platforms
  3. Important information before upgrading to vSphere 6.0
  4. vCenter 6.0 restart/reboot may result in duplicate VTEPs on VXLAN prepared ESX hosts
  5. Windows virtual machines using the vShield Endpoint TDI Manager or NSX Network Introspection Driver (vnetflt.sys) driver fails with a blue diagnostic screen
  6. Slow VMs after upgrading VMware tools in NSX / vCloud Networking and Security
  7. vCenter Server or Platform Services Controller certificate validation error for external VMware Solutions in vSphere 6.0
  8. Changing the VMware NSX for vSphere 6.x License from virtual machine to CPU
  9. Fixing NSX for vSphere IPSEC VPN disconnects
  10. Migration of Service VM (SVM) may cause ESXi host issues in VMware NSX for vSphere 6.x
  11. Connectivity issues on secondary UDLR in Cross-vCenter with NSX
  12. NSX Service Deployment fails with the error: Error while doing IP configuration
  13. Registering NSX Manager to Lookup Service with External Platform Service Controller (PSC) fails with the error: server certificate chain not verified
  14. NSX is unavailable from the vSphere Web Client Plug-in after taking a backup of NSX Manager with quiesced snapshot
  15. ESXi 5.5.x/6.0.x host in a VMware NSX for vSphere 6.2.1 environment fails with a purple diagnostic screen and reports the backtrace: PFFilterPacket and VSIPDVFProcessSlowPathPackets
  16. Configuring transport zone in VMware NSX for vSphere fails with the error: invalid control plane mode
  17. VMware NSX controller deployment fails with the error Timeout on waiting for controller ready
  18. After upgrading vShield Manager to NSX for vSphere Manager, traffic loss is seen on the ESXi cluster
  19. Collecting controller snapshot via the NSX-MH Manager API Inspector fails and return no data on VMware NSX for Multi-Hypervisor 4.2.x
  20. Support for partner integrations with VMware vShield Endpoint and VMware vCloud Networking and Security

Top 20 vCenter articles for May 2016

Top 20Here is our Top 20 vCenter articles list for May 2016. This list is ranked by the number of times a VMware Support Request was resolved by following the steps in a published Knowledge Base article.

  1. Purging old data from the database used by VMware vCenter Server
  2. ESXi 5.5 Update 3b and later hosts are no longer manageable after upgrade
  3. Permanent Device Loss (PDL) and All-Paths-Down (APD) in vSphere 5.x and 6.x
  4. Upgrading to vCenter Server 6.0 best practices
  5. ESX/ESXi host keeps disconnecting and reconnecting when heartbeats are not received by vCenter Server
  6. Unlocking and resetting the VMware vCenter Single Sign-On administrator password
  7. Consolidating snapshots in vSphere 5.x/6.0
  8. Powering on a virtual machine fails after a storage outage with the error: could not open/create change tracking file
  9. Diagnosing an ESXi/ESX host that is disconnected or not responding in VMware vCenter Server
  10. VMware vSphere Web Client displays the error: Failed to verify the SSL certificate for one or more vCenter Server Systems
  11. Deprecated VMFS volume warning reported by ESXi hosts
  12. Resetting the VMware vCenter Server and vCenter Server Appliance 6.0 Inventory Service database
  13. Cannot take a quiesced snapshot of Windows 2008 R2 virtual machine
  14. vCenter Server 5.5 fails to start after reboot with the error: Unable to create SSO facade: Invalid response code: 404 Not Found
  15. Update sequence for vSphere 6.0 and its compatible VMware products
  16. Registering or adding a virtual machine to the Inventory in vCenter Server or in an ESX/ESXi host
  17. Back up and restore vCenter Server Appliance/vCenter Server 6.0 vPostgres database
  18. Updating rollup jobs after the error: Performance data is currently not available for this entity
  19. Configuring VMware vCenter Server to send alarms when virtual machines are running from snapshots
  20. Determining where growth is occurring in the VMware vCenter Server database

Top 20 ESXi articles for May 2016

Top 20Here is our Top 20 ESXi articles list for May 2016. This list is ranked by the number of times a VMware Support Request was resolved by following the steps in a published Knowledge Base article.

  1. VMware ESXi 5.x host experiences a purple diagnostic screen mentioning E1000PollRxRing and E1000DevRx
  2. ESXi 5.5 Update 3b and later hosts are no longer manageable after upgrade
  3. Commands to monitor snapshot deletion in VMware ESXi/ESX
  4. Recreating a missing virtual machine disk descriptor file
  5. Determining Network/Storage firmware and driver version in ESXi/ESX 4.x, ESXi 5.x, and ESXi 6.x
  6. Permanent Device Loss (PDL) and All-Paths-Down (APD) in vSphere 5.x and 6.x
  7. Installing patches on an ESXi 5.x/6.x host from the command line
  8. Identifying and addressing Non-Maskable Interrupt events on an ESX/ESXi host
  9. Restarting the Management agents on an ESXi or ESX host
  10. Downloading and installing async drivers in VMware ESXi 5.x and ESXi 6.0.x
  11. Enabling or disabling VAAI ATS heartbeat
  12. ESXi 5.5 or 6.0 host disconnects from vCenter Server with the syslog.log error: Unable to allocate memory
  13. Powering off a virtual machine on an ESXi host
  14. Consolidating snapshots in vSphere 5.x/6.0
  15. Powering on a virtual machine fails after a storage outage with the error: could not open/create change tracking file
  16. Snapshot consolidation in VMware ESXi 5.5.x and ESXi 6.0.x fails with the error: maximum consolidate retries was exceeded for scsix:x
  17. Reverting to a previous version of ESXi
  18. Configuring a diagnostic coredump partition on an ESXi 5.x/6.0 host
  19. Diagnosing an ESXi/ESX host that is disconnected or not responding in VMware vCenter Server
  20. Enabling or disabling simultaneous write protection provided by VMFS using the multi-writer flag

Top 40 Horizon View articles for April 2016

Here is an update for the top Horizon View articles list for April 2016. This list is ranked by the number of times a VMware Support Request was resolved by following the steps in a published Knowledge Base article.

  1. Manually deleting linked clones or stale virtual desktop entries from the View Composer database in VMware View Manager and VMware Horizon View
  2. Using Microsoft Certreq to generate signed SSL certificates in VMware Horizon View
  3. VMware View ports and network connectivity requirements
  4. Removing invalid linked clone entries automatically using the ViewDBChk tool in VMware Horizon View 5.3 and later versions
  5. Provisioning View desktops fails due to customization timeout errors
  6. Linked Clone pool creation and recomposition fails with VMware Horizon View 6.1.x and older releases
  7. Finding and removing unused replica virtual machines in the VMware Horizon View
  8. Configure security protocols for PCoIP for Horizon 6 version 6.2 and later, and Horizon Client 3.5 and later
  9. Removing a standard (replica) connection server or a security server from a cluster of connection/security servers
  10. Restart order of the View environment to clear ADLDS (ADAM) synchronization in View 4.5, 4.6, 5.0, 5.1, 5.2, 5.3, 6.0, and 6.1
  11. Recommended restart cycle of the VMware Horizon View environment
  12. Troubleshooting SSL certificate issues in VMware Horizon View 5.1 and later
  13. Manually deleting replica virtual machines in VMware Horizon View 5.x
  14. Provisioning VMware Horizon View desktops fails with error: View Composer Agent initialization error (16): Failed to activate software license
  15. Black screen when logging in to a Horizon View virtual desktop
  16. Generating a Horizon View SSL certificate request using the Microsoft Management Console (MMC) Certificates snap-in
  17. Recompute virtual disk digest tasks storm in vCenter Server
  18. Performing an end-to-end backup and restore for VMware View Manager
  19. Forcing replication between ADAM databases
  20. View Connection Server fails to replicate
  21. The View virtual machine is not accessible and the View Administration console shows the virtual machine status as Already Used
  22. Configuring USB device filters and redirecting Human Interface Devices (HIDs) in View Client
  23. Poor virtual machine application performance may be caused by processor power management settings
  24. Network adapter disappears from a Windows virtual machine
  25. Changing the log file behavior in the VMware View components
  26. Troubleshooting USB redirection problems in VMware View Manager
  27. Administration dashboard in VMware Horizon View reports the error: Server’s certificate cannot be checked
  28. Connecting to the View ADAM Database
  29. View Manager Admin console displays the error: Error during provisioning: Unexpected VC fault from View Composer (Unknown)
  30. Troubleshooting and Frequently Asked Questions for space reclamation in VMware Horizon View 5.2.x and 5.3.x
  31. Troubleshooting VMware Horizon View HTML Access
  32. VMware View SVGA driver reports newer version than the installed View Agent version
  33. Troubleshooting Agent Unreachable status in VMware Horizon View
  34. Intermittent provisioning issues and generic errors when Composer and vCenter Server are co-installed
  35. Disabling the HotAdd/HotPlug capability in ESXi 5.x and ESXi/ESX 4.x virtual machines
  36. Troubleshooting frequent PCoIP disconnects in a VMware View environment
  37. Increasing the video memory on VMware View desktops
  38. Determining which replica disk is used for a linked clone virtual machine
  39. VMware View Administrator shows the virtual machine status error: Configuration Error
  40. View Connection Server reports the error: [ws_TomcatService] STDOUT: java.lang.OutOfMemoryError: Java heap space