When reviewing a support bundle from vmPRO, you can derive information about the environment’s datastores from the datastore_cache.
 
The log files path you would reference is similar to:
 

    \pancetera-support.tar.bz2\pancetera-support.tar\var\pancetera\datastore_cache\
 
Here is a Windows Explorer view of the datastore_cache:
 

 
 

This information is collected by the pansupport.sh as triggered manually or from the Web UI.  This portion of the script collects the meta data infor with the intent of elimenating name collisions.

//Excerpt from the pansupport.sh//

# include datastore fs json meta data file and symlinks to detect name collisions
find /var/pancetera/datastore_cache -type f -maxdepth 2 -path "/var/pancetera/datastore_cache/*/.*.json.content" >> $filelist

Here is what a list of the /var/pancetera/datastore_cache looks like live on the system.

bash-4.1# pwd
/var/pancetera/datastore_cache
 

bash-4.1# ls -alh
total 60K
drwxrwxrwx 15 root root 4.0K Oct  4 08:44 .
drwxrwxrwx  6 root root 4.0K Oct  5 01:36 ..
drwxrwxrwx  3 root root 4.0K Oct  9 08:50 4b03813a-80a54654-a217-0030483450b1
drwxrwxrwx  4 root root 4.0K Oct  9 08:50 4b1d74d6-eee84f06-fe5f-0030483450b0
drwxrwxrwx  4 root root 4.0K Oct  9 08:50 4b1d7a3b-d37ae471-f8f1-0030483450b0
drwxrwxrwx  3 root root 4.0K Oct  9 08:50 4b1d7a53-1202fbc3-b7dd-0030483450b0
drwxrwxrwx  7 root root 4.0K Oct  9 08:50 4b5df85e-b23819c3-2025-0030483450b0
drwxrwxrwx  8 root root 4.0K Oct  9 08:50 4b5e21a8-d949a3dc-7743-0030483450b0
drwxrwxrwx  3 root root 4.0K Oct  9 08:50 4b636dd4-cd678a07-419b-0030483450b0
drwxrwxrwx  4 root root 4.0K Oct  9 08:50 4d265379-c3a6d073-c3a2-0030483450b0
drwxrwxrwx  8 root root 4.0K Oct  9 08:50 4d274a30-26e61fe9-c06f-0030483450b0
drwxrwxrwx  8 root root 4.0K Oct  9 08:50 4d374ebe-aba17cba-86ff-0030483450b0
drwxrwxrwx  7 root root 4.0K Oct  9 08:50 5aff0913-024b17eb
drwxrwxrwx  3 root root 4.0K Oct  9 08:50 d8ef66a4-7d1b4a2b
drwxrwxrwx  2 root root 4.0K Oct  9 08:50 f42f0c6c-d3ccc3ca

Live on a vmpro appliance there will a directory for every VM within a datastore.  The vmpro support bundle will only collect .json.content file.

bash-4.1# ls -alh /var/pancetera/datastore_cache/5aff0913-024b17eb
total 32K
drwxrwxrwx  7 root root 4.0K Oct  9 10:29 .
drwxrwxrwx 15 root root 4.0K Oct  4 08:44 ..
-rwxr-xr-x  1 root root  430 Oct  9 10:29 .ff6a2cffff08ffffff29ff7866ffff3b36ff3068.json.content
drwxrwxrwx  2 root root 4.0K Oct  9 09:37 DXi V1000 2.2
drwxrwxrwx  2 root root 4.0K Oct  5 08:49 Jon - DXi V1000 256block pool
drwxrwxrwx  2 root root 4.0K Oct  5 10:23 Mint Cin Linux
drwxrwxrwx  2 root root 4.0K Oct  9 10:30 Mint Cin Linux - Restore
drwxrwxrwx  2 root root 4.0K Oct  5 08:49 eye-DXiV1000-03
 

bash-4.1# ls -alh  /vmfs/volumes/5aff0913-024b17eb/
total 421M
drwx------ 13 root root  440 Oct  9 10:31 .
drwxr-xr-x 15 root root  560 Oct  8 08:29 ..
-rwxrwxrwx  1 root root  430 Oct  9 10:29 .ff6a2cffff08ffffff29ff7866ffff3b36ff3068.json
drwxr-xr-x  2 root root  180 Oct  9 10:31 ASPS-RA-Massive(2)
drwxr-xr-x  3 root root 1.4K Oct  9 10:31 DXi V1000 2.2
drwxr-xr-x  3 root root  380 Oct  9 10:31 Jon - DXi V1000 256block pool
drwxr-xr-x  2 root root   80 Oct  9 10:31 Mint Cin Linux
drwxr-xr-x  3 root root  200 Oct  9 10:31 Mint Cin Linux - Restore
drwxr-xr-x  2 root root  100 Oct  9 10:31 RHEL
-rwxrwxrwx  1 root root 2.8G Oct 11  2012 en_windows_server_2008_r2_x64_dvd_x15-50365.iso
drwxr-xr-x  2 root root  100 Oct  9 10:31 eye-DXiV1000-02
drwxr-xr-x  3 root root  620 Oct  9 10:31 eye-DXiV1000-03
drwxr-xr-x  2 root root   80 Oct  9 10:31 eye-DXiV1000-04
drwxr-xr-x  3 root root  100 Oct  9 10:31 logs
-rwxrwxrwx  1 root root  67K Mar 27  2013 smartmotion.mysqldump
-rwxrwxrwx  1 root root  81K Mar 18  2013 smartmotion.psqldump
-rwxrwxrwx  1 root root   32 Mar 18  2013 smartmotion.uuid
-rwxrwxrwx  1 root root 503M Sep 11 16:46 test.txt
-rwxrwxrwx  1 root root    0 Mar 27  2013 testfile
drwxr-xr-x  5 root root  540 Oct  9 10:31 vmware-ovftool
 

Each datastore make a directory in the support bundle.  If a datastore has multiple vmpro nodes moving data spanning across its VM's you will see multiple .jason.content files reporting as such.  The major difference in the json file will be the 'Paths' list the VM moved by that UUID of the vmpro node.
 

You can manually make reference to the UUID of a datastore you are interested in using for log analysis by reviewing the symbolic links in the datastore_fs as mounted on /vmfs/volumes.
 
Example of a .json file:
 

 
Text Contents of a .json file:
    { "name": "Storage1", "uuid": "4b03813a-80a54654-a217-0030483450b1", "url": "\/vmfs\/volumes\/4b03813a-80a54654-a217-0030483450b1", "hv": "10.20.230.15", "hostsystem":     "aspsesx.quantum.com", "type": "VMFS", "dc": "ha-datacenter", "timestamp": 1362368559, "accessible": 1, "capacity": 248571232256, "freeSpace": 175294644224, "is_local_dc": 1, "paths":     [ ".", "ASPS-RA-Elbert" ] }
 
Without having direct access to the vmpro appliance while doing log analysis, we can determine from the .json file that the datastore Storage1 is UUID '4b03813a-80a54654-a217-0030483450b1'.  Its path is /vmfs/volumes/4b03813a-80a54654-a217-0030483450b1. The host (ESX) is 10.20.230.15 and is named aspsesx.quantum.com. This is a VMFS file system, and the datacenter is aspsesx.quantum.com. Capacity and free space are given.  The VM 'ASPS-RA-Elbert' string indicates there is a .vmx file for this VM stored in the 'Storage1' datastore.  This doesnt mean the VM is set for export implicitly. 

What's Next?

Working with Log Rotate in vmPRO >

Typical Issues that Lead to Log Analysis within a Support Package >