When Acronis Management Server demonstrates symptoms of malfunction it may be useful to check whether its performance is in accordance with expected behavior.
Symptoms
Any of the following symptoms may serve as trigger to apply the proposed solution:
- Inconsistency between Agents and Management Server
- Management Server or SQL Server consuming CPU and network bandwidth
- Poor performance of browsing backup plans and logs on Management Server
- Running out of Disk space on Management Server
- Acronis Management Server service crashed.
Solution
- Download and unpack the troubleshooting script ams.zip on the machine, where Acronis Management Server runs;
- Open command line under user with administrative privileges (Hit Start -> Run -> cmd -> right-click and choose -> Run as administrator);
- Change to the folder where you have saved the troubleshooting script (use cd command);
- Run the script with following syntax: cscript /nologo ams.js
- If everything is ok, the output should look similar to this:
- If issues are found, messages are displayed instead of OK similar to this:
- The script will fix any orphaned machines that it can find. It does not fix any other issues. If a solution for a specific issue is known, the script will just display this as result. For instance corresponding KB article will be displayed. Further improvements will ensure that for some issues the script is even able to apply the fix by itself. In this case the script will ask for permission to apply it. To automatically set the fixing behavior you can provide extra -fix: argument to the script with one of the following values:
- all - automatically apply all the solutions (e.g. to fix all the identified issues: cscript /nologo ams.js -fix:all);
- none - automatically ignore issues (most safe option) (eg. to display all issues without fix them: cscript /nologo ams.js -fix:none) ;
- ask - ask for permission to apply solution (this is the default option).
- If everything is ok, the output should look similar to this: