Backup Exec 2010 R2/R3 Active Directory Restore Access Denied

[Monkay]

Hello,

I've successfully backed up Active Directory via the system state but when I go into do a restore I get the following error when I try to expand the Active Directory node:

[SYMANTEC][Backup Exec Catalog Driver] (Access is denied.)

The account used to perform the backup is a domain admin as is the account being used do the restore.

I can't seem to find any information on this error, so hopefully somebody else has come accross this problem before.

[ZeRoC00L]

Do you have the Backup Exec Active Directory agent installed ?

Or are you trying to restore the complete active directory ?

[Monkay]

We have the Active Directory Recovery agent and I have been able to restore objects in the past - not sure what has changed as the message doesn't really give me much to go on.

[shaganasty]

I also just tried and got the exact error dialog.

we are running windows 2008 R2 with backup exec 2010 r2 and do have the license for the active directory recovery agent. all agents are up to date.

service pack 1
hotfix 150096
hotfix 144101
hotfix 148347
hotfix 153090
hotfix 147674
hotfix 155520

this is our first time trying to recover a deleted user.

we do our backups to disk using the domain admin and they are successful with no errors.

hope there is a fix for this

[RadioBavaria]

Hello,

we had the same problem with both versions, 2010 R2 SP1 and also with R3.

Very interesting that we have the problem only if we make the (recommended) backup to disk.

If we backup to tape, we then can open the AD part in restore selections without error.

So we opened a call and today I got feedback that this is an acknowledged and know problem and that they will work on a hotfix.

Here the proof:

http://www.symantec.com/business/support/index?page=content&id=TECH159962

So as workaround I can only recommend a backup to tape until then. Dramatically increases backup time (40 compared to 6 minutes in our case), but at least you can use your backup then ... ;)

[Monkay]

Thanks for the information and the workaround.

I'll look forward to the hotfix!

[RadioBavaria · Accepted solution]

After around 2 month the problem is solved

http://www.symantec.com/docs/TECH159962

and a hotfix is available, but unfortunately only for BE 2010 R3, and not for the R2 build:

http://www.symantec.com/docs/TECH161270