Suggested Feature SNAPSHOT styled BACKUP for Undisrupted Backup of Running VMs

This post was originally published on this site

I am aware that the higher end products of vmware like vsphere etc have backup features or even there seems to be 3rd party products for such functions. I am however just a vmware workstation pro user user, only familiar with workstation & player, but I had been using these wonderful products for more than a decade since version 4 days.


My suggestion arose from my own needs, I run NAS & email servers in VMs, in a small business office, very reliable for many years.


My host machine is Linux, and I have crontab jobs, running every night to backup my servers. My scripts put each VM 1 by 1 to suspend mode, copy the whole folder to a backup volume and then restore it, before proceeding to the next VM. It is working fine for me especially the NAS has no user at the night time.


There is however a slight problem for the email server, obviously, during my backup period (few minutes), the server is down, and incoming emails are receiving no respond error from my server which got put in suspend mode for backup.


Hence, I am suggesting, a new feature for backup purpose, to allow VM to be continuously running non-stop, no disruption to their functions during their backup. In concept, alike a temporary snapshot being taken, and wholly duplicated to another folder location, just only without the new delta vmdk files containing changes after the snapshot point, and after duplication, this temporary snapshot is deleted, and the VM continues to function undisrupted.


In the duplicated folder, there should be a content of a full VM, in a snapshot state, still snapshot in power ON state. Freezing the state exactly at the moment of the backup time.


My suggestion is to have this feature added into the snapshot manager area, as a new option, call it SNAPSHOT-BACKUP or any more appropriate name anyone else better than me can think of. The UI need to prompt for user to specify a destination folder which backup will duplicate VM into.


At the same time, append a new command into the VMRUN command line utility, calling it by this same new name, so that e.g. we issue command to “vmrun snapshot-backup /home/vm/email/email.vmx /mnt/backup_vm/email” the last part specifies the destination folder for this backup VM to be copied into.


With this feature, I hope VMware Workstation Pro users can easily carryout UNDISRUPTED BACKUP of running VMs.


If this feature could be provided in new version Workstation Pro, it will be beneficial and meaningful, and what the users will get is very similar to what I am doing for the time being – got a duplicated VM in suspended power state, but during the time of backing up my VMs are temporary off-line, disrupting their users.


Thanks & regards.



Idea / Feature Suggestion: Useful to have vmdk disks, usually SCSI / SATA / IDE, make possible for mounting as USB disk as well

This post was originally published on this site

Re: Idea / Feature Suggestion: Useful to have vmdk disks, usually SCSI / SATA / IDE, make possible for mounting as USB disk as well


I thought it would be more correct if I create this posting above as an idea here, pardon for the repetition.


I am a happy user of Workstation for over a decade, since days of I think version 4 workstation.


Recently, began to use Tails Linux and of course it works with Workstation 12 pro.


But I had been only booting up Tails using ISO image live CD mode. In this mode it can not create a persistent file to store some info or settings. As result I am using vmware snapshots to store.

Tails only creates persistence file to store info when it boots up using USB thumb drive. Yes, I had been able to use USB thumb drive and booted up in EFI BIOS mode in vmware too. But I have to physically plug in a USB thumb drive too.


It is kind of good if VMware will allow a vmdk file virtual disk – same as those we connected via SATA / SCSI, to be also simulated to be (HOT) plugged into VMs. Then in this case it will become very convenient.


I think for more than just Tails purpose, if VMware could hot-plug VMDK disks as USB device, it serves a whole lot of useful functions for test / development and powerful usages.


There are physical USB HDD SSD and there are physical USB thumb drives. I suppose VMDK files can simulate them, but I can be ignorant or wrong.


My suggestion is to have essentially thumb drives / SDcards / MicroSD cards simulated by VMware using a VMDK like file / files, this will be a new dimension of simulation that is still a lacking now.




Thanks & regards



ERROR: Task failed on server: Module 'CPUID' power on failed.

This post was originally published on this site

Hi vTeam, I hope you’re all doing well.

I’m creating a nested VMware LAB where I have 1 physical server (Dell OptiPlex 790) with 16GB of RAM and 2 Physical Processors. I’ve installed ESXi on this server and inside I’ve created 2 VMs with ESXi installed on each (one with 11GB RAM for vCenter and the other with 5GB RAM for DC & DNS + Windows 7 and OpenFiler). I can easily create VMs on it but when I tried to deploy VCSA 6.5 if fails when it reaches 80% with this error: “Task failed on server: Module ‘CPUID’ power on failed.”, any ideas, could you please help me? Thanks a lot in advance and hope to hear from you all as soon as possible guys, cheers.

Unable to open *.vmdk The system cannot find the file specified

This post was originally published on this site

My vm1 was working just fine and I suspended it to open vm2.  After suspending vm2, I came back to vm1 and I get the error cannot open the vmdk file because the system cannot find it.  The file is there.  I can browse to it and see it.  My vmx file appears to be in good shape.  I am using windows 10.   If someone can help, I would appreciate it

Disks degraded in ESXi

This post was originally published on this site

I have a ESXI v6 u3 installed on a DL380 G9. I have done Raid from the HP provisioning itself. After installing the ESXI and presenting the disks to it. The disks show me as degraded:



   Display Name: HP Serial Attached SCSI Disk (naa.600508b1001ce2641dcf3c827c33d                                                                                     0df)

   Has Settable Display Name: true

   Size: 1144609

   Device Type: Direct-Access

   Multipath Plugin: NMP

   Devfs Path: /vmfs/devices/disks/naa.600508b1001ce2641dcf3c827c33d0df

   Vendor: HP


   Revision: 5.04

   SCSI Level: 5

   Is Pseudo: false

  Status: degraded

   Is RDM Capable: true

   Is Local: false

   Is Removable: false

   Is SSD: false

   Is VVOL PE: false

   Is Offline: false

   Is Perennially Reserved: false

   Queue Full Sample Size: 0

   Queue Full Threshold: 0

   Thin Provisioning Status: unknown

   Attached Filters:

   VAAI Status: unknown

   Other UIDs: vml.0200010000600508b1001ce2641dcf3c827c33d0df4c4f47494341

   Is Shared Clusterwide: true

   Is Local SAS Device: false

   Is SAS: true

   Is USB: false

   Is Boot USB Device: false

   Is Boot Device: true

   Device Max Queue Depth: 1024

   No of outstanding IOs with competing worlds: 32

   Drive Type: logical

   RAID Level: RAID1

   Number of Physical Drives: 2

   Protection Enabled: false

   PI Activated: false

   PI Type: 0

   PI Protection Mask: NO PROTECTION

   Supported Guard Types: NO GUARD SUPPORT

   DIX Enabled: false


   Emulated DIX/DIF Enabled: false



May I know the reason for this and how to fix it.