cancel
Showing results for 
Search instead for 
Did you mean: 

VMware Backup host tries to snapshot itself and fails to Status 156

PatS729
Level 5

Hello,

I have created VMware VIP. Query as follows

vCenter Equals "Vcenter_name"

AND Cluster Contains "ESX Cluster name"

AND Powerstate Equals "Poweredon"

AND VMHasRDM Equals "FALSE"

The query seems working fine. but when snapshot starts my vmware backup host (nbu appliance) tries to snapshot itself and fails to status 156. 

I know there would be a parent job associated to backup host, but i see an additional snapshot job showing client name as my "nbu appliance".

Anyone has seen this behaviour yet ?

Please advise.

4 REPLIES 4

quebek
Moderator
Moderator
   VIP    Certified

Hi

If you test this query do you see this client name there too?

Michal_Mikulik1
Moderator
Moderator
Partner    VIP    Accredited Certified

Hello,

I am not sure what you ask for:

- wanna get rid of nbu appliance in your VIP result lists? Simple use "DisplayName NQ" condition or something like that

- wanna get rid of 156 error here? But I think backup of nbu virtual appliance is useless by VMware policy. nbu appliance does not have supprorted method for dedup services quiescing. "backup" its dedup data by backupid replication to another MSDP server

Rgds

Michal

@Michal_Mikulik1 @quebek Ofcourse i do not want to snapshot/backup my vmware backup host. I do not see backup host is in include list but still it try to snapshot itself and then the snapshot job is failing to status 156. 

Please help.

Have you tried excluding the backup host in your VIP query? It's odd that you say it doesn't show up when you run a test query from the clients tab in the policy.

Does your backup host reside on the ESX cluster that you are querying?