Quantcast
Channel: Symantec Connect - Backup and Recovery - Discussions
Viewing all articles
Browse latest Browse all 5847

VMware VIP policies are suddenly case sensitive in 7.6

$
0
0
I do not need a solution (just sharing information)

After yet another sucessful 7.6 upgrade I noticed the following at a customer site. It seems that between 7.5.0.6 and 7.6.0.2, VMware VIP queries are now case sensitive, i.e. if you had a fairly simple query like:
vmware:/?filter=Displayname AnyOf "serverx"

on 7.5.0.x it will include "serverx", "SERVERX" and even "ServerX" (when it actually saves the backup in the image database, it uses the "correct" case as used in VMware.

It seems this changed in 7.6.0.2, now the case must match 100% for the VM(s) to be included. So be aware if you are using this in your environment, I often see a horrible mixture of case in customer VMware environments :-)

I have just tested this behaviour on both Windows/Linux and vSphere 5.1 and 5.5 environments. Obviosly I have not tested all combinations of the query with this, but it seems to be the case with several fields in the query (display name, data store name etc).

I don´t recall having seen this change mentioned anywhere. Not sure if its a bug or per design, but VM Documentation in 7.6 (it wasn´t there in 7.5) does state:

NetBackup does not recognize upper vs. lower case in display names
In VMware vSphere, virtual machine display names are case-sensitive. A virtual machine with the name "vm1" is a different virtual machine from one that is named "VM1." NetBackup however does not recognize case when it selects virtual machines for backup. It considers VM1 and vm1 to be the same virtual machine.
To ensure that all VMs are correctly backed up, avoid the use of VM names that are differentiated only by upper vs. lower case.

so.....a bug?


Viewing all articles
Browse latest Browse all 5847


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