Different brand? Can be the controller too. But reading what I'm seeing on the screen, it's very likely to be a disk issue.

@dannierothmann indeed, but by definition the xsconsole only seems to state VM data not pool. I was more worried about it not being a full backup. but then in the same take, i like the idea of a VM only meta on XO. I'm going to put this to bed next week. I'm going to export and compare backup files. place bets..

I don't know how it behaves in this case. I think it might stay with the same feature as before removing the older hosts from the pool. You can check the CPU features before and after with: xe pool-param-get uuid=<POOL UUID> param-name=cpu_info Example output: features_hvm_host: 1fcbfbff-f7ba2223-2d93fbff-00000403-00000001-00000281-00000000-00000000-00001000-9c000400-00000000-00000000-00000000-00000000-00000000; features_hvm: 1fcbfbff-f7ba2223-2d93fbff-00000403-00000001-00000281-00000000-00000000-00001000-9c000400-00000000-00000000-00000000-00000000-00000000; features_pv_host: 1fc9cbf5-f6b82203-2991cbf5-00000003-00000001-00000201-00000000-00000000-00001000-8c000400-00000000-00000000-00000000-00000000-00000000; features_pv: 1fc9cbf5-f6b82203-2991cbf5-00000003-00000001-00000201-00000000-00000000-00001000-8c000400-00000000-00000000-00000000-00000000-00000000; socket_count: 4; cpu_count: 80; vendor: GenuineIntel

@olivierlambert i see.., i was seeing them as one install. I have completed actions, thanks

@s-pam i'd say use them, always use the. Only a few KB of space and could be every handy. We have 3 servers in the pool so overlooked requirement for full pool recovery. (p.s we didn't fail, it's during DR testing it was flagged) we had the backups on already and if this had been a real issue, would have saved a lot of bacon!! turn it on ! (and check you can get it without a running XOA for quicker restore in full meltdown.)