Discussions about this online appear to follow the “Can I automate?” question with a familiar and unuseful “Use the SDK” answer. This will automate the process, but force you to manage space in the location you store the output.Įven worse, the lack of a command-line option forces the use of an SDK that may (or may not) provide the required utility. For our purposes, we’ll have to take the lesser of two evils and modify the VM name on the fly. This will either fill your disk space fast creating new copies, or it will stop the process. One of the bigger ways is not allowing you to overwrite an existing VM (that you might have created previously). The key thing to understand is that VMware is doing a number of things to try and stop you from automating this process. In this article, I’m going to go over a means of automating Converter so you can again use it for a backup. This has many confused, who used the tool as something of a “poor man’s disaster recovery tool”. This used to be possible in earlier versions of Converter but was unceremoniously removed from version 5.0 and up. Perhaps a daft move, but VMware Converter (sometimes called P2V or vCenter Converter) no longer allows you to script the creation of a machine image by way of the command line.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |