Solved

Help! ArcServe Backup fails with Exchange Document Level Backup after upgrade

Posted on 2010-09-01
5
7,133 Views
Last Modified: 2012-08-14
Hi there
I upgraded ArcServe Backup to the latest version and all the settings seem to come across ok except for Exchange. The Backup ran as normal after the upgrade and all sql dbs etc backed up fine but Exchange document level failed with errors below.
Active Directory is 2003 level, Server is windows 2003. Exchange is 2003 also.
Any idea how to troubleshoot and fix this?
many thanks

AE9603 Agent is not able to enumerate the storage group,  database or mailbox
AW9627 No item was backed up.
AE9603 Agent is not able to enumerate the storage group,  database or mailbox
AW9627 No item was backed up.
0
Comment
Question by:stack888
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
5 Comments
 
LVL 11

Accepted Solution

by:
Coast-IT earned 167 total points
ID: 33584430
Guy with the same problem here decided to reinstall...  Can't find any answers for you on this one.

https://communities.ca.com/web/ca-recovery-management-storage-global-user-community/message-board/-/message_boards/message/5060760
0
 
LVL 4

Assisted Solution

by:kenycl
kenycl earned 167 total points
ID: 33586129
check the job password for the particular node is correct and run a pre-run test on the job and check again.

this person seems to have similar system running as yours and had it sorted
https://communities.ca.com/web/ca-recovery-management-storage-global-user-community/message-board/-/message_boards/message/2251759
0
 
LVL 6

Assisted Solution

by:dax_bad
dax_bad earned 166 total points
ID: 33591305
Hey,

Check that the accounts you provided in the job containing the Exchange server has the correct exchange permissions. If that's not it, can you try to backup an exchange server on db level?

/Daniel
0
 
LVL 2

Author Closing Comment

by:stack888
ID: 33592219
hey guys, i got it resolved. Bit of a weird one.
I'll split the points between everyone.
Turned out to be around permissions. Had tried creating another User with enough permissions but turns out because the AD alias name began with the same few characters then it doesn’t work. Huh. Created another account with totally different name/alias etc and gave it backup permissions, exchange enterprise permissions etc and connected to the Exch Agent using this and it works now.
0
 
LVL 1

Expert Comment

by:partymarty84
ID: 33858048
I just had this same problem, however it was due to me hiding the exchange agent user from the global address list.
0

Featured Post

Ransomware-A Revenue Bonanza for Service Providers

Ransomware – malware that gets on your customers’ computers, encrypts their data, and extorts a hefty ransom for the decryption keys – is a surging new threat.  The purpose of this eBook is to educate the reader about ransomware attacks.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

How to resolve IMCEAEX NDRs in Exchange or Exchange Online related to invalid X500 addresses.
In this article we will learn how to backup a VMware farm using Nakivo Backup & Replication. In this tutorial we will install the software on a Windows 2012 R2 Server.
This tutorial will walk an individual through the process of installing the necessary services and then configuring a Windows Server 2012 system as an iSCSI target. To install the necessary roles, go to Server Manager, and select Add Roles and Featu…
The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager

740 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question