Hello all,
I am new to snapshots and have been looking to resolve this issue since setting up my snapshots. I assumed that when pointing the snapshots to a separate datastore that I could save space. I was unaware that it still created a additional drive in the original datastore. Right now my problem is this. I got the warning that I needed to consolidate a couple of the servers, but I did not act immediately like I should have. Now I have a much more important issue of space.
I have successfully run the disk consolidation on both of the servers that were in need. But all the disks created by the snapshots are still there. I need to get rid of these, but am not sure the best path to take in this. I checked and both of the servers are showing as running off the last numbered .vmdk i.e. disk-000015.vmdk. Could someone instruct me on the best practice to for lack of a better work, consolidate the disks or delete the ones I should no longer need after the consolidation process?
Thank you in advance.
Since the snapshot files are still there, it looks like the consolidation die not succeed, and you'll need a plan B.
To find out what can be don, please provide some information:
For the file lists, please run the command ls -lisa > VM#.txt (replace # with another character for each VM) in each of the affected VM's folders. Then download the listings, and attach them to a reply post.
André
Unfortunately I am a Vmware novice. I have enabled TSM-SSH, but when launching putty, it just flashes the console and is closed in half a second. I am not sure what else needs to be done to get SSH working.
Enabling TSM-SSH is actually all that needs to be done to be able to access a host through SSH.
Just to clarify, you start putty, make sure that the SSH protocol is selected, enter the host's IP address, and then the putty console opens, and closes without a warning/error?
André
Yes. I believe I have figured out why, now searching for a way around.
I had an old version of putty. ver 5.3
I just got version 7.0 and it does give an error.
"ssh protocol version 1 required by our configuration but not provided by server"
Please start putty, and click SSH in the left pane to see what protocol option is selected. Putting the radio button to "2" should work for both version.
André
I am in. I do not usually use the console. I ran the command, but do not know where to find the file I just created. lol
You've been talking about 2 VMs if I understood you correctly.
So please run the command in each of the two VMs' folders (i.e. on the datastore). From the command line the VM's' files are located in /vmfs/volumes/<datastorename>/<vmname>
After running the command in both folders, you'll be able to download the VM#.txt files from the datastore browser within the vSphere Client.
Please don't forget to mention the free disk space on the datastore.
André
Discussion moved from Product & Feature Suggestions to ESXi
I will have to update this tomorrow. I have been entering the path wrong and now I have to finish another project before time runs out.
I do know this. There are multiple vmdk files varying in size from 18 MB to 452.6 GB, totaling to over 2.6 TB. The available space on the Datastore is 555 GB. I would assume that space is the issue. I have another datastore with with 5.48 TB of free space. I can maneuver some of the VMs to get the appropriate space needed to get this resolved.
Thank you.
I can maneuver some of the VMs to get the appropriate space needed to get this resolved.
If space is the issue, then freeing up additional space will certainly help. Anyway, I'd suggest we first fry to find out the reason, and then proceed with steps to resolve the issue, even if it's just to find out how much additional free disk space is required.
André