AMS so SLOOOWWW to log into after services restarted!
WHY WHY WHY, does it take almost a freakin HOUR to be able to connect to the AMS once I restart the Acronis and SQL Services on the AMS Host?
Restarted the services a long time ago and I still get this message:
Code: 11,337,731(0xAD0003)
LineInfo: 0x90FB8A255B1DF677;
Module: trueimg_remote_full_vs
Message: Failed to establish the local connection with Acronis Management Server Service. Make sure that the service is installed and its status is Started.
Code: 196,610(0x30002)
LineInfo: 0x37819FD1E1F7A62A;
Module: trueimg_remote_full_vs
Module: trueimg_remote_full_vs
Code: 65,520(0xFFF0)
LineInfo: 0xBD28FDBD64EDB8E0;
Module: trueimg_remote_full_vs
Message: The system cannot find the file specified
----
COME ON! That just shouldn't happen and I'm frustrated as hell?
Also, if often takes 20 MINUTES just to display the backup jobs and task list!!!??? takes FOREVER to try and load a freaking LOG FILE!
This just should not happen! Is it due to the SQLLITE instance or something?
I see 11.5 is now released and I really hope these performance issues are addressed.
Same issue here, if i want to do anything with acronis, i have to start it up, and do something else for an hour or two before i can actually check anything. In the program options, there are built in database cleanup tools, are these ineffective? Why do we have to manually run this if it is supposed to be built into the program?
@Carl, if you have done this, does it actually help to speed up starting the service?
Guys, this is well known issue and we have addressed it in updates. The reason of this slow startup for AMS is that it runs time consuming consistency check on startup and when there are many objects accumulated during its lifetime, the checks take just too long. I'll request a KB article to be created in order to work around this issue. I'll keep you posted on that KB article in here.
Some things are slow due to the fact that the dml_objects.db3 file is now almost 7GB in size. There is an ams_cleanup tool, but it does take forever to run on such a large file. I haven't tried the built in database cleanup utilities.
Wow, 7GB is just too much. You definitely need to clean it up. What do you mean by ams_cleanup tool? There is something like this that on fast enough disks should do the job in an hour or two: http://kb.acronis.com/content/31547. But you will definitely have a performance boost after it. BTW, this is exactly the KB article I am going to update.
Sorry, I do mean remove_history. I had it running for at least an hour or more and it barely touched the dml_ojbects.db3 file at all. Do I'm not sure what is up with that.
I will probably be installing 11.5 from scratch, and recreate all the backup plans next week. But there has to be a more efficient database storage method than that. And even though I have "max log size 1GB" set, this file is huge. Is there another setting that helps keep that file size down to a managable size?
I'm trying this again while I wait to upgrade to 11.5 (we've had various other priorities to deal with before I can upgrade).
Well, I started this process at 10am this morning. It's not 1:20pm and it's still not finished!! The file is now 8GB and takes forever to do anything useful. I did a remove_history.bat 2012-09-16 just to keep some recent history, but for crying out loud, this is ridiculous!
It's now 3:30pm and the stupid thing is STILL GOING!
I'm going to have to cancel it as backups start at 5pm.