Volumes are not displayed from AMS in Backup and Recovery 11

The suggestion is that user that AMS uses to connect to agent has no privileges of 'backup operator' and can't browse disks. (Does it allow you to browse to C:\users\administrator folder in 'files' mode of the tree?) Were you able to set up disk backup if you connect directly to the machine with agent?

The Machine with the AMS an the Management Console installed on is a Window 7 Prof.

What was the reason to set up the server function on a desktop machine (I suppose that it is a desktop machine, not another de-factor server with desktop os)?

Dear dev-anon,

thanks for your reply!
If I try to C:\Documents and Settings\administrator (the C:\users\administrator is not present because of it´s an 2003 SBS Server) I see all files.
If I connect directly to the machine with the agent over the AMS it´s excactly the same issue: Volumes are not displayed, Files are ok.

If also tried to connect with the admin-account of the 2003 SBS Server via AMS. Exactly the same result.
I don´t think that it is an privileges problem, because of in Backup and Recovery 10 it worked perfect with the same accounts in the same constellation.
If I install the Management Console directly on the machine with the agent, everything is allright and I see the volumens and can create a backup job.

Someone has an idea what to do? Maybe a bug in the new B&R11?

Thanks a lot!

Best regards

If I connect directly to the machine with the agent over the AMS it´s excactly the same issue: Volumes are not displayed, Files are ok.

If even the direct connection doesn't work, (too straightforward to be such a glaring bug) it's either privilege problem or something else with the machine. Maybe there is something interesting in "C:\Documents and Settings\All Users\Application Data\Acronis\BackupAndRecovery\MMS\LogEvents" Overalll it looks like if the user (even if it's administartor) (rather, groups it belongs to) has no "backup files and directories" privilege ( run gpedit.msc -> computer configuration->windows settings ->security setting->local policies->user rights assignments).
ps - did you already contact the support?

pps - http://kb.acronis.com/content/6069 it's about ABR10 but effect is the same

Hello!

Thanks for all the infos. I have tried everything (user rights, snap api driver version 585 and 600, etc.). Always the same issue.
Then I have contaced the acronis support and opend an case. They where going to the 3rd-Level Support and are actually trying to fix it. It looks like it is an incompatibility or a problem with the hard drive / raid conroller we have in the server.

I´d made an downgrade to ABR10 for the time acronis will take to fix it.

Thank you for your help and good bye!

Best regards

Hi Moebeer

Thanks for the update and for letting us know all is in hand with Acronis support... Out of interest would you beable to let us know what the RAID controller is you are running in your server?

Hi all!

Sorry, I don´t know the exact model. But it is an Adaptec.

Thank´s all and best regards!

moebeer,

I am also running SBS 2003 domain. While the ABR ran great on SBS machine, other machines were having issues connecting with agent and MC. I was able to fix by changing the logon acct for the service on local machine to a domain user acct (Account created by software when installed).

When software was installed (on SBS 2003 DC), it created a different acct for each service (Acronis Managed Machine Service, Acronis Management Server Service, and Acronis Storage Node Service). The acct created for AMSS is member of the Domain User and DC Name $ Acronis Centralized Admins. The accts created for the AMMS and ASNS are members of Domain Users and Backup Users. I would check and see if the WIN 7 machine is using local or domain accts for the logon name for the services on the WIN 7 machine. I would also check to see if those accts for the services on WIN 7 machine are part of the "AcronisBackupServerUsers", "DC Name $ Acronis Centralized Admins", "DC Name $ Acronis Remote Users" security groups, which were created on SBS DC during install

Also check ISA for the SBS Protected Networks Access Rule, and make sure that Enforce Strict RPC compliance is not checked (it will block some DCOM components).

The only question is why create the AMS on a workstation in domain and not the SBS machine? You should still be able to add MC to workstation, but because it is SBS, it is more complicated with domain permissions and authentication then a normal DC. Putting AMS on SBS DC will save many headaches in the end.

moebeer wrote:

If I install the Management Console directly on the machine with the agent, everything is allright and I see the volumens and can create a backup job.

I was seeing something similar, which was how I was able to determine it was a local vs. domain permission issue.