I recently reinstalled my VMware servers using USB sticks. After the first reboot I noticed an yellow warning. When highlighting the different servers I noticed the “System logs are stored on non-persistent storage” warning.
This is how you can fix that :
Select a persistent (SAN?) storage that you can use and go to Browse Datastore.
Create a new folder
Give it a name..
After that go to advanced settings bij the configuration tab of your ESX server.
Go to the Syslog tab.
Give the name of the datastore between brackets and the name of the folder you just created. Hit ok and you notice that the warning is gone :
Do you want to demonstrate or test Veeam Backup and Recovery V7?
When you are holding the vExpert/VCP/MCP/MCTS or MVP status then you’re entitled for a free 180-day NFR license for Veeam Backup & Recovery for the new 7 version.
Check it out here.
This is how you easily can kill an running VM :
- Login to your VMware server
- Start esxtop
- Press c to show CPU resource screen
- Press Shift-V to show only virtual machines
- Press f to add a column (Leader World ID)
- Identify the machine you wish to kill (LWID)
- Press K and enter the ID
- Wait for a couple of seconds
The following describes how to connect your Synology NAS to your ESXi host using NFS :
First make sure NFS is enabled :
NFS has to be enabled ofcourse
Then create an shared folder (or use an existing one)
Add NFS rights, specify the host (ESXi server) and read/write access :
Now goto your ESXi server, configuration –> storage :
Now Add Storage..
Choose Network File System :
Specify you folder (go back 4 screenshots for the information you specified)
Click next and you have an extra NFS datastore!
Many times people asked me how to extend a disk or I see them running Gpart or CLI tools while it’s not necessary. For those people I decided to write this blogpost.
Step 1 : Extend your disk in VMware settings
Go to you vCenter server and extend the disk. Simply go to the server you wish to edit, choose edit settings and click on the hard drive you wish to extend. Make sure you select the right drive!
Now just fill in the amount of disk space you want for this drive. In mine example (I took this picture after resizing the disk) it was 30 GB and I added 20 Gb so the total is 50 Gb of storage.
Step 2 : Check your drive and extend it
Before I extended the drive it was 30 Gb, check this picture :
Now we are going to extend this drive. Go to server manager/storage.
Click rescan disks, because Windows doesn’t see the extra available space right yet. After the rescan you must see extra unallocated space. Now select the volume (partition) you wish the extend. See below :
Just go through these simple steps :
Et voila, the disk is extended :
Today a customer wanted SSH by default on for specific reasons and didn’t like the yellow warning on their ESXi servers. This is how you disable this :
First enable SSH :
Go to Security Profile –> SSH –> options and enable it.
Notice that now you have a yellow warning neir your hosts :
Now this is how you can disable the warning :
Go through Advanced Settings –> UsersVars –> SuppressShellWarning and change the value from 0 to 1
Notice the warning sign is gone :
You can also use the CLI :
esxcli system settings advanced set -o /UserVars /SuppressShellWarning -i 1
Are you an vExpert, VCP, VCI, MVP, MCP or MCTS? Then you get here your free NFR license for Veeam Backup & Replication v6.5 (for example your home or work lab).
I’m running Veeam Backup & Replication for several years now and couldn’t do without.
After installing CentOs you might notice that the eth0 network card interface isn’t working in some cases. Here is how to fix this :
You need to edit (nano) two files :
- /etc/sysconfig/network (check networking=0)
- /etc/sysconfig/network-scripts/ifcfg-eth0 (set IP address and boot=on)
After this you can install VMware tools also. (Check my other post)
This is how you install VMware Tools on CentOs :
mkdir /media/cdrom mount /dev/cdrom /media/cdrom cd /tmp tar –xf /media/cdrom/VM* cd vm* ./vmware-install.pl
Now reboot your system
rm -r /tmp/vmware-tools-distrib
While upgrading to the latest version everything seemed to be working fine, but when I started Veeam B&R for the first time it wanted to upgrade some components and while upgrading one component it stalled with the error “no access”.
This is how I fixed this problem. Go to your installation directory, (in my case D:\Program Files\Veeam\Backup and Replication\Packages) and right click the packages you wish to upgrade and click install.
In my case the upgrade went perfectly and Veeam noticed the upgrade and everything was fine.