strange issues with scheduler
sometimes some backup tasks wern't executed (please check immagine2.png).
and sometimes some backup tasks start but then disappear without errors or warnings (please check immagine3.png)
of course in both cases backup archives doesn't contains the last backup, and in both cases there aren't errors or warnings. how can be possible? thank you in advice
Fichier attaché | Taille |
---|---|
immagine3.png | 48.68 Ko |
immagine2.png | 48.19 Ko |

- Se connecter pour poster des commentaires

ok, about this specified problem I opened a case this mornng, the number is 02969117
about our general issues openend and not resolved since lot of time please check the attachment thank you in advice
Fichier attaché | Taille |
---|---|
410321-138238.png | 44.61 Ko |
- Se connecter pour poster des commentaires

Thank you for the info. I've forwarded these details to our support managers to check what's going wrong.
- Se connecter pour poster des commentaires

We have same issues with scheduler ... in our case i guess the problem is related to the fact that when VM is deleted and not removed from backup prios deletion the job the job itself became unmanageable (can't add new VMs ....) and sometimes scheduler is not working. The only option is to create new job, apply to all existing VMs and remove the old one.
- Se connecter pour poster des commentaires

Lubos Oravec wrote:We have same issues with scheduler ... in our case i guess the problem is related to the fact that when VM is deleted and not removed from backup prios deletion the job the job itself became unmanageable (can't add new VMs ....) and sometimes scheduler is not working. The only option is to create new job, apply to all existing VMs and remove the old one.
Confirmed bug - Observed the same issue as Lubos. VM was deleted from ESX server, but not removed from Management console. The job that was attached to the deleted VM becomes unmanageable (e.g. job cannot be run on existing VM's) and the ESX server as a whole becomes in the Management console becomes unmanageable (e.g. no new VM's on that ESX server can be added to management console). Additionally if you attempt to apply the job to an existing VM, the management console sits at "Applying" and does nothing.
As Lubos eluded, the only way to currently fix the issue is to delete the job entirely, and recreate the job
- Se connecter pour poster des commentaires

Hi,
Just want to confirm this issue too. Should be solved ASAP imo! And... When is expected the new update? We're already 3 months later.
Thanks,
- Se connecter pour poster des commentaires

Hi,
The behavior of web console after VM deletion from vSphere is not normal and such problems may occur only if there are some issues with connection between the Acronis Management Server and one of the registered Agents for VMware (appliances or Windows Agents). For example if one of these agents is disconnected then the list of VMs reported by this agent is not updated and thus the changes made in vSphere (even if there are other agents connected to the same ESXi host/vCenter registered in AMS) are not reflected properly. If this is not the case then such issues should be investigated separately with our support team involved.
P.S. Currently we're working on Acronis Backup 12 Advanced release and along with it there will be Update 4 released for Acronis Backup 12 where most of the product infrastructure-related issues are already addressed (there was reworked the flows of VMs discovery by the agents for example and many other things). This is all planned to happen within approximately 1 month from now.
Thank you.
- Se connecter pour poster des commentaires

Thanks to Lubos for the tip.
it's evident that this product should be engineered in a different way, and the support too.
when I hear phrases like "The behavior of web console after VM deletion from vSphere is not normal and such problems may occur only if there are some issues with connection between the Acronis Management Server and one of the registered Agents for VMware (appliances or Windows Agents)" I think that is only a personal supposition, and is not enforced by a serious log analysis. Of course maybe it's right or maybe not, but there isn't any true evidence because the product logs are unusefol or sometimes simply there arn't logs (how can a task disappear without giving warnings in a product done for enterprise environments??) and in this condition I cannot understand how the support analysis is done, and I cannot understand how they can give this expletations. I say this because I get a lot of reply of this kind both from forum and also when opening tickets. Those type of suppositions are totally unuseful, sounds like a bluff and we need an in-depth analysis based on domonstrably fact; it isn't acceptable that in mounths of utilization of this product all the problems we have sbmitted are without a working solution...
- Se connecter pour poster des commentaires
