Hi,
I received the below error message when trying to take a backup of my server.
Error code: [91:479]
Description: There are no virtual machines in the subclient content. Finishing the job in the discovery phase.
May I know what exactly here the issue is?
This means that your vmgroup/subclient rule is not discovering any vm’s for that particular vmgroup/subclient.
If you look at the content of the rule, you can see which rules applies to that vmgroup, and see a preview of the content.
I make it a habit that all vmgroups i configure should have some content. In addition to userdefined vmgroups you have the vmgroup that contains \
This means it will protect all VM’s not defined in any other vmgroup.
To confirm, you may review the vsdisc.log from the VSA proxy used by the job.
This means that your vmgroup/subclient rule is not discovering any vm’s for that particular vmgroup/subclient.
If you look at the content of the rule, you can see which rules applies to that vmgroup, and see a preview of the content.
I make it a habit that all vmgroups i configure should have some content. In addition to userdefined vmgroups you have the vmgroup that contains \
This means it will protect all VM’s not defined in any other vmgroup.
I have investigated and came to know that this VM is defined to single vmgroup.
What does the preview of the Vmgroup show?It should show which VMs it discover and will run backup for. Does it show the VM that is specifically defined?
if you define a vmgroup to contain specific VM’s they are added to the content of the group using the vm uuid. Has this VM been recreated or gotten its uuid reset in vmware for any reason it will no longer be discovered. Then you would need to select it again in content.
What does the preview of the Vmgroup show?It should show which VMs it discover and will run backup for. Does it show the VM that is specifically defined?
if you define a vmgroup to contain specific VM’s they are added to the content of the group using the vm uuid. Has this VM been recreated or gotten its uuid reset in vmware for any reason it will no longer be discovered. Then you would need to select it again in content.
Yes, I can see my VM in the content. Now, I received a new error on it.
Error summary
Description: Insufficient free space available to create a snapshot of virtual machine cASSINGFP2]. Please check the available free space on the virtual machine's datastores, and verify that the subclient option 'Perform datastore free space check' has the desired setting. tiH1_VOL2_RAID5_Replication] 9.4%]
Source: cm0002ue2v, Process: JobManager
This above error is clear enough to understand that the datastore is running out of space which need to be cleanup and claim some free space.
By default settings each VMgroup is configured to check that there is 10% freespace, before allowing a backupsnapshot to be taken.
However this can be configured to be less, if needed. Be aware that if you are running thin provisioned vm’s and the datastore gets filled 100% then you will get write errors in your production vm as they have nowhere to write the data.
So I would try to do some clean up or migrate workloads away from that datastore, so you have at least 10% free space.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.