![]() I'm also using separate LUN's for ISO files as well as another for templates. This does mean that I have one more LUN than I might have otherwise (three iSCSI LUN's for VM's to use) but that's ok. Using that model/method, I'm keeping over 50% free space on the LUN's, even though I've provisioned up to that 20% mark. Especially when you have both thick and thin VMDK files on the LUN/datastore. ![]() Keep ~20% free from the provisioned space standpoint and you should be safe. I've gotten into the model of looking at the 'provisioned space' numbers instead of the space used. Take the recommended and Double it.ħ5% is the recommended. These days I am almost figuring that the Datastore Remaining Space/Available Space Best Practice - is a moving target. Then VM Convert the ESXi (Lab) Host Server VM Guest back to my ESXi 4.0 production host. Then Remove from Inventory and Delete the ESXi (Production) Server Guest VM. Used VMConverter to convert the server VM to a 2nd ESXi 4.0 (LAB) host. vmdk files (30GB) from Datastore2 to the 'datastore1. I was able to move one of the other guest VM. Now the Snapshot(s) was in an 'orphaned' state. The process used up 'ALL' the datastore space. Rather than deleting the earliest snapshot and then the later - I chose 'Delete All' There was near 80GB free (77GB) on this datastore: Datastore2. Guess what? This created some snapshot delta work. We noticed this process when the Windows Shared Drive space neared 10GB free. PST to the server each week, without deleting the old one first or overwriting the previous one. Turns out a user had been copying their Outlook. Then to my lacking, forgot to remove the snapshot in a 'very short period of time'.Ī few months later - it hit me - I need to remove that snapshot. Took 2 snapshots of a 'Windows f/s' server VM. We had a 450GB datastore for VM Storage and a 74GB Datastore for ISO Images, etc. I have been bitten by the 'Snapshot Delta-Delete' datastore free space constaint. What are others leaving for free space?Īny assistance anyone could provide would be greatly appreciated! So my question: am I flawed in my thinking? Am I missing something that could come back to bite me if I simply fill up my datastore's to make the best use of them? Is there a best practice for free space (I'm assuming the 75% and 85% thresholds aren't a best practice, simply a guideline well more like a arbitrary number VMWare threw in w/o much thought behind it). I'm willing to accept any risk that I wouldn't have time to do a cold migration to a new LUN should the need arise, I simply don't see any situations where I wouldn't be able to accommodate a cold migration to a datastore with sufficient free space. My philosophy to this point has been to us up as much as I can as to not "waste" knowing I can simply migrate the VM to a new LUN should the need arise to either expand a vdisk or allocate more memory. I realize this may be subjective given you can't always predict growth needs for a guest VM nor can you predict memory requirements. This got me to thinking, how much should I really be leaving free on my datastore's. I see they were set to 75% and 85% as it relates to warning and error thresholds. I recently upgraded to vCenter and with that came along some datastore usage alarm definitions. I have a question relating to the amount of free space to leave on a datastore.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |