vCenter appliance is a vm and most of the time we are running it on the same ESXi cluster.
In some cases we may need to increase the disk capacity of some partition(most of the time its log file path).If our vCenter is running out of disk space, vCenter related services may not tart as expected. To resolve this issue we need to increase the free space capacity of the vCenter appliance.
How to do this
Using below bash script we can register all the vms in datastores with ESXi host.This has tested in vSphere 6.5 & 6.7 Hol
for myvm in $(find / -name *.vmx);
vim-cmd solo/registervm $myvm
if we want we can find on specific datastore. please refer the below example
find /vmfs/voluems/datastore10R10/ -name *.vmx
(datastore10R10 is my datatore name)
VMware vSAN -Video training-part 03
This is a very useful feature when its working with changes.This is the easiest way to restore our vCenter.
As a destination backup media we need to have http,https,ftp or ftps server. Since I had windows server. Just I add web roles with ffp feature sfrom server manager.
Once I completed that process. I have to do the following configuration on windows server.
Open Internet information service manager
Telnet is the command which we can easily use to check the service status of the remote system.
Ex if we can telnet to vCenter server from our desktop using port 443, we can say that web services of the vCenter is up
But when we use vCenter shell or ESXi shell, we cannot use telnet command.
As an alternative option, we can use curl command. Please refer the below screen capture
curl -v telent://vcsa-01a:443
Sometimes we may need to take snapshot of the vm but we don’t have enough space in our datastore.In that case we can change the snapshot directory by editing vmx file.
Shell.log is the one of the log file which helps us to resolve problems and in some scenarios it will help us to do the audit process.
- With the below example we can see that per-worker-01a vm is runnin on esx-01a.
In few hours later we can notified that vm has powered off. We could nt find any logs in vCenter or in the os level.
What we can do is we can check the shell.log file. If someone has powered off the vm using command line on the ESXi , we can find the details.
In the above shell.log file we can see that someone has tried to power off this vm.