hussainbte's Posts

Can you share the actual pre-freeze and post-thaw scripts.. the content of the scripts. from some examples I have seen the pre-freeze and post-thaw scripts used for backup are used to quiese a certain application.. like db2, oracle , mysql etc.. I have not used them and cannot guarantee there working coz I did not get them from Vmware documentation. can we install the application and then try to use the scripts for the particular DB.. check below example.. pref-freeze script and post-thatw script..  #!/bin/sh if [ "$(id -u)" -eq "0" ]; then exec su - sdb -c /home/sdb/suspend_logwriter fi #!/bin/sh if [ "$(id -u)" -eq "0" ]; then exec su - sdb -c /home/sdb/resume_logwriter fi

The fact that the scripts are getting executed when you take manual snapshot confirms that the scripts are fine.. as per the documentation quiescing is supported and should work. The guide explicitly mentions that in windows it uses snapshots and nothing about linux based system this makes me think its not using snapshot in linux(we can check that from the logs).. also there is no VSS in SLES... not sure how the scripts are called here. Compatibility Matrices for vSphere Replication 8.1.x Can you share a screen shot of the configuration of SLES machines where the scripts are specified.. including location etc.. also if you can share the scripts please

If you dont have room to freeup some space.. you can reserve the VM memory and avoid the swap file from getting created. this will give you some space if your VM has huge RAM configured.. but the VM is configured withlike 2GB ram then creating 2GB space on datastore might not help. provision the VMs with calculations and avoid thin provisioning if this is production

going back to the KB.. were you able to get into the emergency mode whee you could list the filesystems and devices. Looks like fsck mentioned is the KB is the only option gogin forward.. else yeah.. setup new vCenter appliance

As the above linked KB says.. its something out of the vSphere workloads. It was LUN replication using Recoverpoint when I faced this issue. disable the replication if you have it going and see the events disappear.

It does not look like its a hosprofile issue. rather it is something to do with DVS and vSwitch usage. can you create a dummy DVS and add this host to the DVS.. please keep host profile out of the picture for now. Create a new DVS and add this host ot DVS.. share the uplink configurations of the newly created DVS

there are permissions at ESXi level also. login to the host directly using the web client and go to roles.. you need admin permissions here for the ad users added in exception list.. if that makes sense

I am sure that you have checked the below link.. let us know what is confusing.. Lockdown Mode Behavior If the ESXi Shell or SSH is enabled and the host is placed in lockdown mode, accounts on the Exception Users list who have administrator privileges can use these services. For all other users, ESXi Shell or SSH access is disabled. Starting with vSphere 6.0, ESXi or SSH sessions for users who do not have administrator privileges are closed.

Unless you have an overwriting on the portgroup setting, the VM network and the Mgmt should both be using the 3 nics.. by default. check the attached pic and see if you can go to edit setting of the port group and nic teaming policy

As mentioned, if the disk is thin provisioned, there is no point shrinking it. for think provisioned disks, where the Guest OS is not utilizing the allocated space, one way to shrink is to do V2V. Check below link Shrink a VMware Virtual Machine Disk (VMDK) – virtualman