Hi

I'm confused I have a vcenter virtual appliance (deployed from the 7.0.0. ISO) and two ESXi. vcenter is running on one of those ESXi. Everything is 7.0.0.

If I log in to ESXi and look at any of the Windows VMs I see "Guest OS Version" of "Microsoft Windows Server 2019 (64-bit)", which is correct (and I recall this OS appeared only in 7.0.0). Also, the "upgrade VM Compatibility" is greyed out, whether the VM is running or stopped, so it appears to be the highest compatibility.

However if I login to vcenter the same VM shows as "ESXi 6.7 and later (Version 14)". Above the list of VMs is the wording "UPGRADE TO MATCH HOST   (Version 17).  If I click the VM and choose to upgrade, the popup box lists 0 VMs to upgrade. Similarly, if I click the VM fro within vcenter I see:

VM Hardware Compatibility

Up to Date

On VM:ESXi 6.7 and later (Version 14)

On Host:ESXi 6.7 and later (Version 14)

Can anyone shed light on what may be happening? ESXi thinks my VMs are 17, and vcenter thinks my VMs and host are only 14.

Many thanks

Jim

Hello Community,

we had a server which had only 8 of 10 fans installed what is still ok.

But since we upgraded the host from 5.5 to 6.5 the hardware status triggers an alert for those two missing fans.

Is there a possibility to disable the 2 fans trigger or the completely hardware status?

Thanks for a short response.

Greetings

KKvss

Anyone else running into this with 4.0?  I just installed 4.0 and I'm not able to add my MyVMware credentials.  I've confirmed logging in to My VMware works fine, so this is a SDDC Manager issue.  Also, this environment worked fine before with other versions so I'm curious if maybe something has changed or if this is a bug?

2020-04-18T15:09:16.790+0000 ERROR [bba7b502e7bf4bfa,a2e0] [c.v.e.s.l.a.r.c.d.DepotUserCredentialController,http-nio-127.0.0.1-7400-exec-2] Failed to update User Credential

Running CentOS 8 and tcpdump shows that no outbound connections are attempted when I run Connect-VIServer. Has anyone noticed this?
Also, I can Ctrl+C to stop the Connect-VIserver because it does not appear to timeout. Exiting pwsh requires Ctrl+Z to background it and then kill %1.

Something is definitely broken.

Powershell installed from the official repo and PowerCLI modules unzipped into /opt/microsoft/powershell/7/Modules/VMware.PowerCLI
 

$> dnf info powershell  Name         : powershell Version      : 7.0.0 Release      : 1.rhel.7 Architecture : x86_64 Size         : 151 M Source       : powershell-7.0.0-1.rhel.7.src.rpm Repository   : @System From repo    : packages-microsoft-com-prod Summary      : PowerShell is an automation and configuration management              : platform. URL          : https://microsoft.com/powershell License      : MIT License Description  : PowerShell is an automation and configuration management              : platform. It consists of a cross-platform command-line shell and              : associated scripting language.   PS> Get-Module | ? {$_.Name -like "*vmware*"}| select Version, Name  Version         Name -------         ---- 7.0.0.15939650  VMware.Vim 12.0.0.15939657 VMware.VimAutomation.Cis.Core 12.0.0.15939652 VMware.VimAutomation.Common 12.0.0.15939655 VMware.VimAutomation.Core 12.0.0.15939651 VMware.VimAutomation.Sdk  PS> $PSVersionTable  Name                           Value ----                           ----- PSVersion                      7.0.0 PSEdition                      Core GitCommitId                    7.0.0 OS                             Linux 4.18.0-147.8.1.el8_1.x86_64 #1 SMP Thu Ap… Platform                       Unix PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…} PSRemotingProtocolVersion      2.3 SerializationVersion           1.1.0.1 WSManStackVersion              3.0  PS> $vcenter = "HIDDEN"      PS> Test-Connection -TargetName $vcenter -TcpPort 443 True PS> Connect-VIServer $vcenter  Specify Credential Please specify server credential User: HIDDEN Password for user HIDDEN: **********************  ^C

Hello,

i am begining with iSCSI vSAN to provide some virtual machines with iSCSI LUNs. I have one cluster of 8 ESXi/vSAN hosts. My questions are realted to the configuration of iSCSI multipathing in vSAN:

• How many hosts/paths should I configure in my iSCSI initiator. It is convinient to use the 8 ESXi/vSAN hosts or only a subset of the cluster, for example, 3 ESXi/vSAN hosts? If I only use 3 nodes, perhaps I am loading these 3 hosts?
• I can't find information about the multipath configuration that I should apply in the iSCSI initiator against a vSAN iSCSI target: path_grouping_policy (failover, multibus, prio...), path_selector (round-robin, queue-lenght...), failback (inmediate, ...), prio(const, alua...)... Do you know any recommendation from VMware?

Thanks in advance.

Christian

Hi all,

We have a VDI environment running on two vCenter Server.

One is running as the vCenter Server Role of Horizon environment (VC1), and the other is created by VxRail Manager(VC2) which provide the vSAN datastore to VDI virtual machines.

We create a vRealize Operation Manager to collect the information of Horizon environment and vSAN datastore recently.

The vSphere adapter could collect both two vCenter server information and horizon adapter can collect the information from connection server.

However, the status of vSAN adapter shows "Collection Failed".

I tried reboot the vRealize Operation Manager Appliance, but when I saved the vSAN adapter settings, we get the below error message.

We are sure the credential of vSAN Adapter is correct and we can see the certificate information of the vCenter server.

Does anyone know how to solve the problem?

Thanks a lot!

Version:

vRealize Operation Manager 7.5

vRealize Operation Manager for Horizon 6.6.1

vCenter Server 6.5u2 (VC1)

(VxRail)
vCenter Server Appliance U2C (VC2)ESXi 6.5 EP11

Hello,

I have an automatic backup scheduled of a vCenter appliance (version 6.7.0.21000).  I'm using the FTPS protocol.  The backups seem to start fine and run for about seven or eight minutes, transferring roughly 3 GB of data to the FTP server, but something must be happening at that point, because the automated job goes in to a holding pattern, and times out twenty hours later.  The message in the backup log is:

Timeout! Failed to complete in 72000 seconds.

There is no other indicator of what exactly caused the timeout.  I can see the files on the FTP server, so it doesn't appear to be a permissions issue.

The error occurs each time the scheduled job runs (weekly).  I'm wondering if anyone has experienced this, and has a possible suggestion on how to resolve it.  Below is the most recent error text from the backup log.  Thanks in advance for any assistance with this!

2019-09-02T04:59:14.303 [MainProcess:PID-45427] INFO: The location provided: ftp://10.1.250.249/VCenter_Server_Backups/vCenter/sn_dcnvcsvr.dcn-nd.com/S_6.7.0.21000_20190902-045913_

2019-09-02T04:59:14.340 [MainProcess:PID-45427] INFO: Starting backup job...

2019-09-02T04:59:14.616 [MainProcess:PID-45427] INFO: Estimating full VCDB size.

2019-09-02T04:59:14.616 [MainProcess:PID-45427] INFO: Estimating /storage/db/vpostgres compressed size.

2019-09-02T04:59:14.656 [MainProcess:PID-45427] INFO: original size: 673987241, compressed size: 121385102.1041, compression ratio: 0.1801

2019-09-02T04:59:14.656 [MainProcess:PID-45427] INFO: Estimating /storage/seat/vpostgres compressed size.

2019-09-02T04:59:14.719 [MainProcess:PID-45427] INFO: original size: 2922135552, compressed size: 420787519.488, compression ratio: 0.144

2019-09-02T04:59:14.719 [MainProcess:PID-45427] INFO: Estimating /root/.pgpass compressed size.

2019-09-02T04:59:14.719 [MainProcess:PID-45427] INFO: original size: 0, compressed size: 0.0, compression ratio: 0.1055

2019-09-02T04:59:14.719 [MainProcess:PID-45427] INFO: Estimating /var/log/vmware/vpostgres compressed size.

2019-09-02T04:59:14.720 [MainProcess:PID-45427] INFO: original size: 30756678, compressed size: 3244829.529, compression ratio: 0.1055

2019-09-02T04:59:14.720 [MainProcess:PID-45427] INFO: Estimating /etc/vmware/vm-support/vpostgres-support-noarch.mfx compressed size.

2019-09-02T04:59:14.720 [MainProcess:PID-45427] INFO: original size: 0, compressed size: 0.0, compression ratio: 0.1055

2019-09-02T04:59:14.720 [MainProcess:PID-45427] INFO: Estimating /storage/db/vpostgres_ssl compressed size.

2019-09-02T04:59:14.721 [MainProcess:PID-45427] INFO: original size: 15107, compressed size: 1593.7884999999999, compression ratio: 0.1055

2019-09-02T04:59:14.721 [MainProcess:PID-45427] INFO: Estimating /storage/dblog/vpostgres/pg_xlog compressed size.

2019-09-02T04:59:14.721 [MainProcess:PID-45427] INFO: original size: 436207616, compressed size: 99847923.3024, compression ratio: 0.2289

2019-09-02T04:59:14.721 [MainProcess:PID-45427] INFO: Estimated size:

original_size=4063102194,

compressed_size=645266968.212,

encrypted_size=709793665.0332

2019-09-02T04:59:14.721 [MainProcess:PID-45427] INFO: Calculate size for components

2019-09-02T04:59:14.942 [MainProcess:PID-45427] INFO: Archive size for component vum: 2560294666

2019-09-02T04:59:15.236 [MainProcess:PID-45427] INFO: Archive size for component rbd: 141405104

2019-09-02T04:59:15.807 [MainProcess:PID-45427] INFO: Archive size for component imagebuilder: 9175

2019-09-02T04:59:15.808 [MainProcess:PID-45427] INFO: Appliance Stats Monitor database file path: /var/vmware/applmgmt/appliance_stats.sqlite

2019-09-02T04:59:52.477 [MainProcess:PID-45427] INFO: The backup dir does not exist

2019-09-02T04:59:52.705 [MainProcess:PID-45427] INFO: Started to backup VC components at UTC: 2019-09-02 04:59:52.705612

2019-09-02T04:59:52.726 [LotusBackup:PID-45645] INFO: Starting backup Lotus.

2019-09-02T04:59:52.726 [LotusBackup:PID-45645] INFO: BackupLotus: Running /usr/lib/vmware-vmdir/bin/vdcbackup /storage/db/vmware-vmdir/ /tmp/backup_lotus/

2019-09-02T04:59:52.728 [ConfigFilesBackup:PID-45646] INFO: Started with configuration files backup.

2019-09-02T04:59:52.731 [VCDBBackup:PID-45647] INFO: Retrieving postgres server listening port

2019-09-02T04:59:52.732 [VCDBBackup:PID-45647] INFO: Executing command: netstat -plnt.

2019-09-02T04:59:52.738 [StatsMonitorDBBackup:PID-45649] INFO: Starting backup appliance monitor SQLite DB.

2019-09-02T04:59:52.739 [StatsMonitorDBBackup:PID-45649] INFO: Appliance Stats Monitor database file path: /var/vmware/applmgmt/appliance_stats.sqlite

2019-09-02T04:59:52.739 [StatsMonitorDBBackup:PID-45649] INFO: Executing command sqlite3 /var/vmware/applmgmt/appliance_stats.sqlite .dump.

2019-09-02T04:59:52.740 [ComponentScriptsBackup:PID-45648] INFO: Starting backup component: vum

2019-09-02T04:59:52.740 [ComponentScriptsBackup:PID-45648] INFO: Execute vum script: /etc/vmware/backup/component-scripts/vum/backup_restore.py --startBackup

2019-09-02T04:59:52.748 [ComponentScriptsBackup:PID-45648] INFO: Dispatching stream.

2019-09-02T04:59:52.801 [VCDBBackup:PID-45647] INFO: Starting VCDB full database backup

2019-09-02T04:59:52.801 [VCDBBackup:PID-45647] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', "select pg_xlogfile_name(pg_start_backup('backup_20190902_045913_11726888'));"].

2019-09-02T04:59:52.865 [ConfigFilesBackup:PID-45646] INFO: incl: /var/log/vmware/applmgmt/cfg_incl_l9z9zvsi.lst excl: /var/log/vmware/applmgmt/cfg_excl_5mm952rc.lst

2019-09-02T04:59:52.865 [ConfigFilesBackup:PID-45646] INFO: tarCmd = ['/usr/bin/tar', '-cz', '-C', '/', '--ignore-failed-read', '-T', '/var/log/vmware/applmgmt/cfg_incl_l9z9zvsi.lst', '-X', '/var/log/vmware/applmgmt/cfg_excl_5mm952rc.lst', '--warning', 'no-file-ignored']

2019-09-02T04:59:53.888 [LotusBackup:PID-45645] INFO: stdout: VdcBackupDB: Setting vmdir state to VMDIRD_READ_ONLY

VdcBackupDB: Backing up: /storage/db/vmware-vmdir//data.mdb

VdcBackupDB: Backing up: /storage/db/vmware-vmdir//lock.mdb

VdcBackupDB: Setting vmdir state to (3)

2019-09-02T04:59:53.889 [LotusBackup:PID-45645] INFO: BackupLotus: Dispatching files ['lock.mdb', 'data.mdb']

2019-09-02T04:59:53.889 [LotusBackup:PID-45645] INFO: tarCmd = ['/usr/bin/tar', '-cz', '-C', '/tmp/backup_lotus/', '--ignore-failed-read', '--warning', 'no-file-ignored', 'lock.mdb', 'data.mdb']

2019-09-02T04:59:59.597 [LotusBackup:PID-45645] INFO: Lotus backup finished successfully.

2019-09-02T04:59:59.606 [LotusBackup:PID-45645] INFO: Successfully completed Lotus cleanup.

2019-09-02T04:59:59.606 [LotusBackup:PID-45645] INFO: Successfully completed Lotus cleanup.

2019-09-02T05:00:26.734 [ConfigFilesBackup:PID-45646] ERROR: rc: 0, stderr: /usr/bin/tar: etc/krb5.lotus.conf: Warning: Cannot stat: No such file or directory

/usr/bin/tar: etc/vmware-vcha/vmware-vmon.service.bak: Warning: Cannot stat: No such file or directory

/usr/bin/tar: etc/vmware-vsm/logging.properties: Warning: Cannot stat: No such file or directory

/usr/bin/tar: etc/vmware-vsm/wrapper/wrapper.conf: Warning: Cannot stat: No such file or directory

/usr/bin/tar: etc/vmware/appliance/firewall.conf: Warning: Cannot stat: No such file or directory

/usr/bin/tar: etc/vmware/appliance/firewall/ccm-firewall.conf: Warning: Cannot stat: No such file or directory

/usr/bin/tar: usr/lib/vmware-cm/wrapper/conf/wrapper.conf: Warning: Cannot stat: No such file or directory

/usr/bin/tar: usr/lib/vmware-vcha/data/pg-firewall-block.conf: Warning: Cannot stat: No such file or directory

/usr/bin/tar: usr/lib/vmware-vcha/data/pg_hba_block.conf: Warning: Cannot stat: No such file or directory

2019-09-02T05:00:26.735 [ConfigFilesBackup:PID-45646] INFO: Successfully finished configuration files backup.

2019-09-02T05:00:27.350 [StatsMonitorDBBackup:PID-45649] INFO: Completed backup appliance stats monitor SQLite DB.

2019-09-02T05:02:02.759 [ComponentScriptsBackup:PID-45648] INFO: Component vum backup successful.

2019-09-02T05:02:02.763 [ComponentScriptsBackup:PID-45648] INFO: Starting backup component: rbd

2019-09-02T05:02:02.763 [ComponentScriptsBackup:PID-45648] INFO: Execute rbd script: /etc/vmware/backup/component-scripts/rbd/rbd-backup-restore --startBackup

2019-09-02T05:02:02.773 [ComponentScriptsBackup:PID-45648] INFO: Dispatching stream.

2019-09-02T05:05:40.272 [VCDBBackup:PID-45647] INFO: Successfully start Postgres on-line backup window.

2019-09-02T05:05:40.273 [VCDBBackup:PID-45647] INFO: Backup start WAL file is 00000001000000630000002B.

2019-09-02T05:05:40.282 [VCDBBackup:PID-45647] INFO: tarCmd = ['/usr/bin/tar', '-cz', '-C', '/', '--ignore-failed-read', '--warning', 'no-file-ignored', '--warning', 'no-file-changed', '--warning', 'no-file-removed', 'storage/db/vpostgres', 'storage/seat/vpostgres', 'root/.pgpass', 'var/log/vmware/vpostgres', 'etc/vmware/vm-support/vpostgres-support-noarch.mfx', 'storage/db/vpostgres_ssl']

2019-09-02T05:05:40.283 [VCDB-WAL-Backup:PID-47925] INFO: Starting backup WAL files.

2019-09-02T05:05:40.284 [VCDB-WAL-Backup:PID-47925] INFO: VCDB backup start at WAL file 00000001000000630000002B.

2019-09-02T05:05:40.284 [VCDB-WAL-Backup:PID-47925] INFO: Each WAL backup image contains 5 WAL files.

2019-09-02T05:05:41.286 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:05:42.315 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:05:43.348 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:05:44.385 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:05:45.419 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:05:46.455 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:05:47.488 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:05:48.552 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:05:49.580 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:05:50.619 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:05:51.658 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:05:52.684 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:05:53.708 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:05:54.732 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:05:55.751 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:05:56.785 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:05:57.819 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:05:58.859 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:05:59.903 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:06:00.934 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:06:01.958 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:06:02.991 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:06:04.28 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:06:05.51 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:06:06.80 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:06:07.111 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:06:08.143 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:06:09.175 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:06:10.201 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:06:11.237 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:06:12.268 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:06:13.303 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:06:14.338 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:06:15.373 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:06:16.406 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:06:17.429 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:06:18.455 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:06:19.485 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:06:20.517 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:06:21.549 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:06:22.585 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:06:23.618 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:06:24.648 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:06:25.685 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:06:26.716 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:06:27.752 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:06:28.779 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:06:29.806 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:06:30.845 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:06:31.885 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:06:32.918 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:06:33.955 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:06:34.994 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:06:36.36 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:06:37.77 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:06:38.121 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:06:39.148 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:06:40.179 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:06:41.218 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:06:42.258 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:06:43.285 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:06:44.308 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:06:45.333 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:06:46.372 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:06:47.402 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:06:48.430 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:06:49.451 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:06:50.468 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:06:51.495 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:06:52.538 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:06:53.556 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:06:54.586 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:06:55.617 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:06:56.648 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:06:57.680 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:06:58.707 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:06:59.735 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:07:00.767 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:07:01.804 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:07:02.822 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:07:03.860 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:07:04.892 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:07:05.914 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:07:06.945 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:07:07.980 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:07:09.17 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:07:10.51 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:07:11.82 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:07:12.119 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:07:13.156 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:07:14.198 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:07:15.233 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:07:16.268 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:07:17.304 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:07:18.334 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:07:19.370 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:07:20.403 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:07:21.439 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:07:22.471 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:07:23.507 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:07:24.540 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:07:25.573 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:07:26.607 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:07:27.638 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:07:28.665 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:07:29.702 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:07:30.744 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:07:31.772 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:07:32.806 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:07:33.839 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:07:34.863 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:07:35.894 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:07:36.928 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:07:37.980 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:07:39.20 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:07:40.48 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:07:41.74 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:07:42.105 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:07:43.140 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:07:44.171 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:07:45.208 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:07:46.249 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:07:47.285 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:07:48.317 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:07:49.345 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:07:50.379 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:07:51.406 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:07:52.442 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:07:53.481 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:07:54.514 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:07:55.553 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:07:56.592 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:07:57.633 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:07:58.668 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:07:59.700 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:08:00.736 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:08:01.763 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:08:02.787 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:08:03.824 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:08:04.856 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:08:05.898 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:08:06.934 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:08:07.972 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:08:09.9 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:08:10.35 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:08:11.61 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:08:12.95 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:08:13.122 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:08:14.149 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:08:15.183 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:08:16.224 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:08:17.249 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:08:18.269 [VCDB-WAL-Backup:PID-47925] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'SELECT pg_xlogfile_name(pg_current_xlog_location());'].

2019-09-02T05:08:18.867 [VCDBBackup:PID-45647] INFO: tarCmd = ['/usr/bin/tar', '-cz', '-C', '/', '--ignore-failed-read', '--no-recursion', '--warning', 'no-file-ignored', 'storage/dblog/vpostgres/pg_xlog', 'storage/dblog/vpostgres/pg_xlog/archive_status']

2019-09-02T05:08:19.153 [VCDBBackup:PID-45647] INFO: Stopping Postgres full database backup.

2019-09-02T05:08:19.154 [VCDBBackup:PID-45647] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', 'select pg_xlogfile_name(pg_stop_backup());'].

2019-09-02T05:08:19.306 [VCDB-WAL-Backup:PID-47925] INFO: VCDB backup stop at WAL file 00000001000000630000002B.

2019-09-02T05:08:19.309 [VCDB-WAL-Backup:PID-47925] INFO: Dispatching 1 WAL files into backup archive: wal_backup_1.tar.gz

2019-09-02T05:08:19.313 [VCDB-WAL-Backup:PID-47925] INFO: tarCmd = ['/usr/bin/tar', '-cz', '-C', '/', '--ignore-failed-read', '-T', '/var/log/vmware/applmgmt/wal_files_q5uw5oyp.lst', '--warning', 'no-file-ignored', '--warning', 'no-file-changed', '--warning', 'no-file-removed']

2019-09-02T05:08:20.234 [VCDB-WAL-Backup:PID-47925] INFO: No WAL files got rotated during backup.

2019-09-02T05:08:20.234 [VCDB-WAL-Backup:PID-47925] INFO: WAL files from 00000001000000630000002B to 00000001000000630000002B were backed up into wal_backup_1.tar.gz successfully.

2019-09-02T05:08:20.238 [VCDB-WAL-Backup:PID-47925] INFO: tarCmd = ['/usr/bin/tar', '-cz', '-C', '/', '--ignore-failed-read', '--warning', 'no-file-ignored', 'dev/shm/all_wal_meta.json']

2019-09-02T05:08:20.512 [VCDB-WAL-Backup:PID-47925] INFO: Verifying all new WAL were backed up.

2019-09-02T05:08:20.513 [VCDB-WAL-Backup:PID-47925] INFO: Completed backup all 1 WAL files from (VCDB backup start)00000001000000630000002B to (VCDB backup stop)00000001000000630000002B.

2019-09-02T05:08:20.516 [VCDBBackup:PID-45647] INFO: WAL backup process completed successfully.

2019-09-02T05:08:20.520 [VCDBBackup:PID-45647] INFO: WAL backup process exited.

2019-09-02T05:08:20.523 [VCDBBackup:PID-45647] INFO: Finishing full database backup

2019-09-02T05:08:20.523 [VCDBBackup:PID-45647] INFO: Retrieving postgres server listening port

2019-09-02T05:08:20.523 [VCDBBackup:PID-45647] INFO: Executing command: netstat -plnt.

2019-09-02T05:08:20.590 [VCDBBackup:PID-45647] INFO: Canceling running pg_start_backup() process.

2019-09-02T05:08:20.591 [VCDBBackup:PID-45647] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', "SELECT pg_cancel_backend(pid) FROM pg_stat_activity WHERE pid <> pg_backend_pid()  and query ~ '^select\\ pg_xlogfile_name\\(pg_start_backup\\(.*\\)\\)\\;' "].

2019-09-02T05:08:20.638 [VCDBBackup:PID-45647] INFO: No pg_start_backup() process is running.

2019-09-02T05:08:20.639 [VCDBBackup:PID-45647] INFO: Checking whether Postgres online backup still in progress

2019-09-02T05:08:20.639 [VCDBBackup:PID-45647] INFO: Executing command: /opt/vmware/vpostgres/current/bin/psql -U postgres -p 5432 -t -c "select pg_is_in_backup();".

2019-09-02T05:08:20.664 [VCDBBackup:PID-45647] INFO: Postgres on-line backup already finished. Skip stopping backup operation

2019-09-02T05:08:20.665 [VCDBBackup:PID-45647] INFO: Successfully cleaned up for VCDB backup.

2019-09-03T00:59:52.578 [MainProcess:PID-45427] ERROR: Timeout! Failed to complete in 72000 seconds

2019-09-03T00:59:52.578 [MainProcess:PID-45427] ERROR: BackupManager encountered an exception: Timeout! Failed to complete in 72000 seconds.

2019-09-03T00:59:52.583 [MainProcess:PID-45427] INFO: Cleaning up the backup job.

2019-09-03T00:59:52.583 [MainProcess:PID-45427] INFO: Cleaning up all running backup child processes.

2019-09-03T00:59:52.616 [MainProcess:PID-45427] INFO: Cleaning up all sizeFiles.

2019-09-03T00:59:52.616 [MainProcess:PID-45427] INFO: Cleaning up Lotus.

2019-09-03T00:59:52.616 [MainProcess:PID-45427] INFO: Successfully completed Lotus cleanup.

2019-09-03T00:59:52.616 [MainProcess:PID-45427] INFO: Cleaning up ConfigFiles.

2019-09-03T00:59:52.616 [MainProcess:PID-45427] INFO: Cleaning up VCDB.

2019-09-03T00:59:52.616 [MainProcess:PID-45427] INFO: Finishing full database backup

2019-09-03T00:59:52.616 [MainProcess:PID-45427] INFO: Retrieving postgres server listening port

2019-09-03T00:59:52.616 [MainProcess:PID-45427] INFO: Executing command: netstat -plnt.

2019-09-03T00:59:52.667 [MainProcess:PID-45427] INFO: Canceling running pg_start_backup() process.

2019-09-03T00:59:52.667 [MainProcess:PID-45427] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', "SELECT pg_cancel_backend(pid) FROM pg_stat_activity WHERE pid <> pg_backend_pid()  and query ~ '^select\\ pg_xlogfile_name\\(pg_start_backup\\(.*\\)\\)\\;' "].

2019-09-03T00:59:52.700 [MainProcess:PID-45427] INFO: No pg_start_backup() process is running.

2019-09-03T00:59:52.701 [MainProcess:PID-45427] INFO: Checking whether Postgres online backup still in progress

2019-09-03T00:59:52.701 [MainProcess:PID-45427] INFO: Executing command: /opt/vmware/vpostgres/current/bin/psql -U postgres -p 5432 -t -c "select pg_is_in_backup();".

2019-09-03T00:59:52.728 [MainProcess:PID-45427] INFO: Postgres on-line backup already finished. Skip stopping backup operation

2019-09-03T00:59:52.728 [MainProcess:PID-45427] INFO: Successfully cleaned up for VCDB backup.

2019-09-03T00:59:52.729 [MainProcess:PID-45427] INFO: Cleaning up ComponentScripts.

2019-09-03T00:59:52.729 [MainProcess:PID-45427] INFO: Cleaning up StatsMonitorDB.

2019-09-03T00:59:52.729 [MainProcess:PID-45427] INFO: Cleaning up failed backup files.

2019-09-03T00:59:53.682 [MainProcess:PID-45427] INFO: Cleaned up the backup job.

2019-09-03T00:59:54.129 [MainProcess:PID-45427] INFO: Event com.vmware.applmgmt.backup.job.start.failed.event successfully posted to http://localhost:8085/sdk

2019-09-03T00:59:54.136 [MainProcess:PID-45427] INFO: Backup job failed.

VCSA 6.7.0.42200 with 50+ hosts 6.7U3

Yesterday i uploaded the april-patches (ESXi670-202004001) into the software depot for autodeploy

this morning the vami reports "Imagebuilder service health with warnings" - running out of available disk space

looking on space utililization of the vcsa it reports :

Filesystem                                Size  Used Avail Use% Mounted on

/dev/mapper/imagebuilder_vg-imagebuilder  9.8G  2.9G  6.3G  32% /storage/imagebuilder

/dev/mapper/autodeploy_vg-autodeploy      9.8G  3.8G  5.5G  41% /storage/autodeploy

why is the warning threshold so low? theres enough storage available

As title says

I've tried linked clone floating Pool , linked clone with  Persistent disk, Linked clone app volume over a couple of years now and there is always some kind of problem ,

Apparently there is an App volume update coming soon to fix this

Does it work well for anyone here at the moment and if so what is your setup?

Hello Everyone!

I am enrolling Samsung Android devices with Android Enterprise in COPE mode, using the QRcode method and preparing the devices with a staging user.

• First problem, I set an Application Control profile to blacklist apps in my personal profile, unfortunately it seems that the profile is not respected at the first installation, to make it is I have to go on the profile itself and force the installation on a given device. The assignment seems to be correct, unfortunately in the production phase the thing would become annoying if it remained so.
• Second problem, when the employee enters his AD credentials for the final registration, I set that two apps are downloaded for the management of e-mail with parameters taken from the employee's personal data. Also in this case the apps are not downloaded automatically as they should and if the downloads from the company store don't have the preset parameters. If I force the installation again then everything works. But as before it becomes annoying during production with hundreds of devices.

Do things like this happen to you? I have to use staging because the customer wants the devices with the apps already downloaded, but I wonder if it's not the staging itself that creates these problems?

Thanks and regards,

Gianmarco

Hi All,

I am trying to gather the vnic interface details of all NSX edge, DLR in my environment.

I am using foreach loop twice to gather the information. But , i need to format the output like in CSV as below.

Expected Output:

DLR/ESG  Name               Interface Name      Interface connection status          IP address          Mask

ESG 1                                   vnic2                    Connected                                    10.10.10.1           255.255.255.0

ESG 1                                   vnic3                    Connected                                    10.10.10.2           255.255.255.0                             

=================================================================================================================================

$edgelist = get-nsxedge | select name

Write-Host "NIC Information of each DLR/ESG"

Write-Host "-------------------------------"

foreach ($edge in $edgelist)

{

Write-Host "$edge.name"

$interfacelist = Get-nsxedge -name $edge.name | get-nsxedgeinterface

Write-Host "Interface Count:" $interfacelist.count

    foreach ( $interface in $interfacelist)

    {

        Write-Host "Interface Name :" $interface.name

        Write-Host "Interface Type :" $interface.type

        Write-Host "Interface Connection status :" $interface.isconnected

        $priaddress =  $interface | Get-nsxedgeinterfaceaddress | Select PrimaryAddress

$netmask =  $interface | Get-nsxedgeinterfaceaddress | Select subnetMask

Write-Host "IP Address :"  $priaddress

Write-Host "SubnetMask :"  $netmask

Write-Host "----------------------------------------------------------------------------"

    }

   Write-Host "----------------------------------------------------------------------------"

  }

We're handing out iPads to patients to keep them entertained while they aren't allowed to have visitors. I'm trying to prevent people from taking them home with them. Before I get started with anything, yes they're setup in DEP. What do you think would be the best way to either prevent people from taking them home or would encourage them to be returned? Physically locking them down isn't really feasible.

I thought setting up a geofence with the iPads would be the best thing to encourage them to be returned. I tried to setup a single app profile to install once they left our main campus, but it doesnt seem to do anything.

• I enabled collection of location data
• I configured an area
• I installed Hub on all of the devices
• I created a profile that puts the ipad in single app mode if it's in the area (I realize this is backwards)

The iPad won't install or uninstall the profile, I put it in my car and drove it home a few times and nothing changes. I've had an open ticket for a week or two, but they can't even tell me if this is possible.

Em uma VM estou recebendo a seguinte mensagem de erro no processo de replicação ...

"unable to perform parallel vm disk processing"

Os demais processos de replicação estão OK, somente de uma das maquinas virtuais ...

Ainda efetivando as buscas para entender o problema e vou postar aqui, mas se alguém já passou por isso e puder dar um norte, seria de grande valia, vou também levantar as informações de versão do sistema entre outras para alimentar mais detalhes e auxiliar ...

Desde já agradeço ...

We are running on Horizon 7.9 with persistent linked clone desktops without user data disk. We use Persona at the moment and has vGPU on desktops as they are used for highly intensive graphics workload. Majority of our desktops are Windows 7 and we are piloting Windows 10, but as everyone knows Persona doesn't work well with Windows 10. So we are planning to integrate DEM. But since DEM takes care of only Profile settings and not actual profile data, we are thinking of using DEM with FSLogix.

A couple of questions:

1) Is DEM + FSLogix a good solution for Persistent Desktops? I see many people mention them for Non-persistent desktop.

2) Has anyone tried integrating DEM and FSLogix and if yes, how does it look performance, functionality and stability wise?

3) How easy is it to configure?

4) Anything we will have to consider when we are using it on vGPU environment?

5) Is there a way to migrate existing profiles once we move to DEM + FSLogix?

DEMdevsjessevExpert: Pim van de Vis

Hello all,

Hope i find all of you well. I’m newbie on NSX. First of all, sorry about my poor english writing skill.

I’m in a project for a customer that pretends to implement NSX-T. Can anyone give me a help with the design for this project?

The hardware that I will have available to start, are 4 hosts, with four 10Gb NIC and two 25Gb NIC, each.

The 4 servers will work as a hyper-converged solution. I will have to install vSphere 6.7, vSAN, VCSA 6.7 and NSX-T 2.5, plus all the customer workloads will be created on them, in at least two tenants. I will also have to separate the DMZ traffic from the other customer traffic. DMZ on a N-VDS and the other on another N-VDS (make sense?).

I need a suggestion, to know what the is best solution design due the conditions that I have available.

I was thinking:

- Use 2x 25Gbit pnics for ESXi management network + vcenter + vMotion + VSAN (vDS)

- Use 2x10Gbit pnics for NSX-T (customer DMZ) (N-VDS)

- Use 2x10Gbit pnics for NSX-T (other customer traffic) (N-VDS)

Is that a simple away, or there is other way more simple?

Other questions:

-    About the tenants, each one will have a T1-router but only one T0 for both?

-    The TEP ip pool, I will have two (Two overlay TZ, one for DMZ and other for the other traffic), right? One for DMZ and other for other customer traffic?

-    The Edge cluster will have two Edge appliances for both DMZ and the other traffic, or should I have an edge cluster for DMZ and other cluster for the other traffic?

Many thanks.

Pedro Santos

Hi All,

In my lab I have been running VCSA 6.7 which has been updated to version 6.7.0.42300 which is update 3e.

I now need to restore my VCSA and it appears that I need the ISO for the same version as the file level backup was created with.

In my case that is version 6.7.0u3e, however update 3e is a patch version and I am unable to find an iso for version 6.7.0u3e. The documentation stats that you need to use the ISO of the particular patch for the version you are restoring. How do I deploy a VCSA from the patch iso in order to restore my backup?

Has anyone a working procedure for this?

Any help or suggestions is greatly appreciated.

DJ

Hello,

have anyone encounter an issue with running chrome browser in horizon? I have had multiple employees stat that sometimes chrome will take 2 to 3 min to load and sometimes they have to double click on it to open chrome browser.

Buenas a todos

Tengo un problema con mi maquina virtual. Intento hacerle ping a un plc desde la maquina virtual y teniendo la ip en rango y la maquina en "bridged" no consigo hacerle ping. He hecho la prueba con el router de casa y si que he podido hacerle ping.

Para comprobar si el problema estaba en el ordenador, he probado a hacer ping desde el host y si lo he conseguido. He probado a copiar esta maquina virtual en otro ordenador y también he podido comunicarme con el plc.

Es decir que desde el host consigo comunicarme pero desde dentro de la maquina virtual no. Me han dicho que podría ser un problema de permisos, pero lo he revisado y creo que están bien, aunque no podría asegurarlo ¿Alguien podría ayudarme?

Muchas gracias de antemano

Un saludo

i recently upgraded v Center appliance from v sphere 6 .x to vCenter 6.7 . i am facing below issue while login from web client :