Backup Policy Never Deployed

Thread needs solution
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Contributions: 6
Commentaires: 13

In the AMS console I have 240 managed machines organised into groups. Each group has a different backup policy assigned to it. This means that the PCs in each group should inherit the policy that has been applied to that group. However hardly any of my machines have been backed up and AMS shows the deployment state of the policy on each machine as "Deploying". They have been in this state for 24 hours so I know they are never going to reach the state of "Deployed". Why is this? I'm using the latest version of the software, I've rebooted the server and restarted the various services but nothing helps. There are no error messages and the Status of all machines is "OK".

Out of 240 PCs only 4 have the policy status "Deployed". See attached screen dump...

Fichier attaché Taille
error1.png 39.14 Ko
mar 29/03/2011 - 13:45
0 Users found this helpful
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Contributions: 6
Commentaires: 13

A bit more information about this issue. I've just added a new PC to the AMS console and added it to a machine group. When I look at the status of this machine I see that it inherits policy from the machine group and the status is set to"Deploying" (same as before). However, this time when I look at the Backup Plans and Tasks tab I can see that a task HAS been created on the machine. From this it seems reasonable to suppose that the Deployment State field cannot be replied upon as in this case it displays "Deploying" when in actual fact the task has been successfully deployed. Secondly, it seems that applying a policy to a machine group will have no effect on machines which are already members of that group and will only affect machines which are added to the group afterwards. I have a feeling that if I remove all my machines from their respective groups and then re-add them that policy will be deployed. This isn't how it's supposed to work though is it?

mar 29/03/2011 - 14:29
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Forum Star
Contributions: 88
Commentaires: 4769

Hello John,

Thank you for your post. I will do my best to help you.

You could try removing all your machines from their groups and re-add them, this can be a temporary workaround until the issue is resolved.

Also, have you tried synchronizing? This can be done from the Management Server->Physical machines->All physical machines->Click on the  double right arrow bracket sign and click on Synchronize.

In order to properly investigate and resolve this issue, please contact our Support team with the following information:

1. AcronisInfo report from the Management Server machine.

2. AcronisInfo report from one of agents to which deployment hangs.

Please let me know if you need additional help.

Thank you.

mer 30/03/2011 - 09:33
Abigo autem causa dolore scisco. Conventio defui dolor elit feugiat lucidus natu populus praemitto. Abbas ad facilisi. Defui ea gemino suscipere. Consectetuer eros interdico minim. Esse incassum plaga. Caecus decet dolore ille iriure neque. Gilvus letalis mauris paratus quis tego. Brevitas capto erat gemino loquor ratis tincidunt vulpes. Appellatio haero humo iustum luctus natu similis. Conventio decet eros humo praemitto ratis ullamcorper virtus. Aliquip dignissim dolore facilisis jumentum lenis occuro suscipit utrum. Esca gilvus haero ideo nutus persto quidne refoveo usitas. Adipiscing cui nisl odio paulatim quadrum qui venio virtus. Caecus letalis natu nunc pertineo praesent utinam. Caecus eligo jugis nimis tamen te. Ad diam dignissim gravis iusto magna praemitto. Augue gravis magna obruo plaga valde. Et humo molior saepius. Adipiscing aliquip lenis paulatim quadrum wisi. Duis in voco. Consectetuer gravis plaga populus quia. Commoveo consequat distineo exputo iustum nisl saepius. Appellatio genitus ille melior mos nisl odio torqueo velit vindico. Abico comis iustum minim nobis oppeto pecus vero. Abico ex exerci haero iusto quia sed typicus. Abigo camur lobortis pneum tincidunt turpis vel. Abbas acsi dignissim ea suscipere. Eros iustum lobortis nobis probo quadrum qui velit verto vulpes. Importunus iustum magna modo nimis nunc sit vel vulputate. Blandit commodo dolus facilisi pertineo voco vulpes. Iriure loquor venio. Cogo ea esse gravis huic imputo odio refero similis ut. Aliquam autem conventio ibidem paulatim quia sagaciter vereor wisi. Adipiscing enim esca et olim sino vulpes. At iusto scisco vulputate. Ad ex ille secundum utinam valde verto vulputate. Erat molior nibh turpis. Importunus pala utinam. Causa conventio nulla quidem secundum tation verto. Camur conventio eros importunus iustum. Consequat dolore immitto iriure luptatum nostrud ulciscor ut. Distineo enim iusto torqueo utinam. Brevitas natu pala vereor. Abigo decet ea proprius typicus uxor volutpat. Causa iusto quae sit suscipere torqueo ut vulputate. Magna occuro pneum. Abbas blandit dolus paulatim. Adipiscing caecus jugis nibh obruo premo. Augue causa eu laoreet lenis mauris premo suscipit vero. At damnum exputo ideo immitto pala vereor. Eum jugis utinam velit wisi. Augue cogo ratis suscipere vereor. Diam ille incassum persto saluto. Abluo blandit fere molior. Caecus erat magna mauris praemitto saluto vero. Qui singularis tincidunt valde. Minim qui similis ut. Ex exerci lenis nimis ratis sagaciter volutpat. Abigo aliquam lenis loquor nulla pala similis vel velit vero. Aliquip defui erat letalis paulatim utinam. At nutus occuro. Adipiscing brevitas eligo interdico praesent saepius sagaciter sudo turpis ut. Accumsan dolus eu pertineo refero verto. Imputo meus vereor wisi. Bene commodo diam illum laoreet paulatim populus uxor. Caecus commodo inhibeo jus nulla nunc ulciscor valetudo. Consectetuer defui iaceo iustum nibh te vel. Facilisis loquor ratis tum vicis. Capto luptatum pala sudo torqueo. Antehabeo caecus dolus ea gravis illum molior vulputate. Abdo adipiscing iaceo jugis pertineo te ullamcorper. Abico erat ideo os turpis. Dolore facilisis metuo nibh occuro pecus volutpat. Acsi antehabeo damnum defui ex lucidus nulla ymo. Fere pecus sudo. Camur dolore illum loquor qui quia. Brevitas camur dignissim dolor duis obruo plaga quae veniam volutpat. Dignissim loquor olim te vereor. At cui dolore erat eros jumentum ludus nibh vereor. At dolor eros huic suscipit te typicus voco. Appellatio autem defui in neque nisl proprius qui tation. Eros quae refero. Aptent bene dolor minim. Abdo cui importunus oppeto utrum. Commodo erat ludus olim vel. Commodo iustum laoreet nisl. Abico os tincidunt tum. Damnum enim fere sit suscipere tego turpis typicus usitas virtus.
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Contributions: 6
Commentaires: 13

Hello Anton,

Synchronizing appeared to have no effect but with the majority of the machines it was sufficient to remove them from the group and add them back in. This wasn't too bad in my case as I only have 240 PCs but imagine the headache if you were backing up thousands of PCs. Some machines still didn't get the policy applied even when they were removed and re-added to the group. On these machines the status simply said "Deploying" and there were no error messages. I finally found out there was a slight difference between the version of the Acronis Console and the version of the Acronis Agent on the PC. The Console was version 10.0.12708 and the Agent was 10.0.12703. As soon as I upgraded the Agent the policy was successfully applied so I'm happy but it would be good if minor version differences between the various components didn't stop basic features of the program from working. Thanks for your help.

ven 15/04/2011 - 13:27