There was only one virtual machine in this data store. As a result, if one is going to be skipped while migrating, it seems that there was no server in the data store and an error occurred.
But, this server was not in migrating during backup.
And Similar symptoms (migrating and will not be backed up) also occurred in virtual machines in other data stores. The virtual machine was shutting down that did not perform any migration operation.
As a remedy for this problem, we confirm that if we do the operation below, we will make improvements. １．Perform inventory removal and re-registration of virtual machines from vCenter ２．Retrieve one backup from the VSC only on the server where the problem occurred
If anyone knows, please let me know １．Why did this problem occur? ２．Is there any other way than the remedial measure I wrote?
The environment is as follows. ・ONTAP 9.1 ・vSphere 6.5 update 1 ・VSC 6.2.1P1D5
As design of VSC, VSC cannot know that VM migration status even though the VM migration has completed. Thus VSC check the status of VM migration to vCenter depends on interval of 'vmware.query.events.time.span.hours' value. That default value is 24, that means VSC will check status per 24hours.
You can change the vaule in“smvi.override” file is in the VSC installation path (by default is c:\Program Files\Netapp\Virtual Storage Console\smvi\server\etc) to 24 to 1, this means VSC will check the status per 1hour.