I have followed this guide
https://support.symantec.com/en_US/article.TECH153...
to remove old backup destinations.
Unfortunately I didn't read the note at the end:
NOTE: Please be aware of the following side effects of using the above steps:
- Client machines may lose their association with the backup policy
- Client machines may go into a 'Not Installed' state (seen via 'Manage Tasks' / 'Computers' view)
Despite the above side effects, over a period of time (impossible to say how long as it depends on size of environment and what the Symantec Management Agent 'configuration' interval is set to), the client machines will regain their association to the backup policy and also regain their correct status (when the policy 'cleanup' is complete).
It happened that 4 clients have undergon exactly the issues cited here. Even more, they completely disappeared from the management solution, like they had been deleted (but I didn't delete them, I just followed the guide and deleted their old backup destinations associations). After clicking "update" in the managament agent settings tab, they appeared again in the management solution, going to "not installed state". After rebooting them one time, they changed their state to SAFE/AT RISK depending on what was their state before. BUT! They have lost their associtation with all client polices, included backup policies.
What should I do? I have waited 24 h and reboteed them 5 times. Should I wait even more? or should I start to add them back manually to the policies? Why this happened? My suspect is that the policies have not been restore because in the above procedure not only their backup destinations, but also their records had been deleted from the database...