Skip to main content

B & R Management Console often painfully slow

Thread needs solution

Is it just me/my machine or is the Management Console often painfully slow when doing simple tasks like displaying the running tasks: (loading .....), bringing up a plan details for editing or saving an updated plan: (Processing, please wait ...)?

Why? Can it be fixed? (In my case everything is being done on a single machine.)

0 Users found this helpful

Hi Alan. My Management COnsole is painfully slow too but I think it is more the SBS 2008 then the Management Console. What OS are you running it on?

Here it's the same. To display the content of a depot when creating a new bachup plan takes often 1 minute and more.

Mine is slow but not near that slow. My overall opinion of SBS 2008 is that it is slow in general. I am running a Quad Core Xeon 3360, 8GB memory and a good Adaptec 5405 Raid 5 controller and I just have 3 workstations on the network. My jaw dropped when I saw how slow it ran. Put that same hardware on a SBS 2003 OS and it would flat out rock. Are you anything close to those specs?

My AMS is a virtual machine on a ESXi running Win XP. The machines I back up are Win XP and SBS 2003, all virtual machines on ESXi. The depot is on a Win XP, not a virtual machine, connected via 1 GB to the VMs.

Hello all,

Thank you all for your posts and I am very sorry for not replying earlier. I will definitely try to answer your questions.

Alan Wilkinson, Jim Becher and Peter Müller,

There are a few reasons why the management console is slow. The delay could be caused by the management console's interaction with the SQL database. We are currently working on optimizing these interactions, so that the management console works faster.

After installing the program, have you rebooted the machines at some point in time? I understand how important production servers are, and it is sometimes very difficult to reboot them, but the slowness could be caused by this as well.

A lot of logs can be causing a slowdown. If you have trouble accessing the logs, you can either delete them or specify Log Cleanup Rules.

Please let me know if you have additional questions.

I had the same problem. Looking through running processes I noticed that the arsm.exe took 30% of CPU (however the removable storage was already removed - so not really an activity expected). After waiting for some hours, I killed the process. - after this the IDE is now reacting to all actions directly with no waiting at all ... I don't know what arsm.exe was doing to the database ... however my data catalog was empty anyway for some reason.