• A snapshot should never remain on a system for more than 48 to 72 hours before being
deleted or reverted. Additional information on snapshot removal can be found in
KB1002836
on the VMware Knowledge Base website.
• Third party based snapshots are not supported.
• Best practices for snapshots are documented in the
Deploying Avaya Aura
®
Communication
Manager on VMware
®
in Virtualized Environment
document.
Important:
Snapshots should not be used as a backup and recovery mechanism. They are only intended to
test an action that may result in an unpredictable outcome.
Using vMotion with real time applications can impact service
Condition
Use of vMotion with real time applications such as Avaya Aura
®
Communication Manager can be
service impacting and is not recommended.
Solution
If vMotion is used, it is recommended that manual migrations with vMotion be done only during a
maintenance window since the migration could be service impacting. If vMotion DRS automation is
used, it is recommended that the DRS automation level be set to the most conservative level
possible, such as level 2 or level 1. See
PSN20151u
on the Avaya Support website for more
information.
Related links
Troubleshooting software issues
on page 34
ESXi host alarm after VMware 6.0 Update 3A upgrade
Condition
The alarm message
System logs on host are stored on non-persistent storage
is
displayed after upgrading an ESXi host to VMware 6.0 Update 3A.
Cause
The upgrade changes the System logs location is changed to a location that would not save them if
the server was rebooted. This is a default action of the upgrade process and cannot be changed
before the upgrade begins.
Solution
Use the following procedure to fix this issue:
https://kb.vmware.com/selfservice/microsites/
search.do?language=en_US&cmd=displayKC&externalId=2032823
.
Related links
Troubleshooting software issues
on page 34
Troubleshooting software issues
October 2017
Troubleshooting the Avaya Pod Fx
™
36