![]() Fast forward like an hour later, a different VM went down and won't start for the same exact reason. We managed to free up like 4GB on the ESX and allocated that to the VM that would not start, and BAM, we got it to start. The ESX is essentially completely gone as of yesterday and I think it's being caused by Veeam (9.5) snapshots. vSphere Client essentially is telling me there is not enough space to start the VM (I think). ![]() ![]() I patched 3 of my servers and after rebooting them, they failed to come back up. So they are used still but by very few people. Second: This IS a production environment but luckily it's "legacy" and we're supposed to be getting rid of them soon. Gonna make this short because, well, one of my servers is not starting and backups are not running.įirst: This is a closed network, no connection to the internet.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |