Unable to attach to \\WORKER\Microsoft Exchange Mailboxes.

[Robbert_Brackel]

Hi,

When doing a full backup with Backup Exec 10 for Windows SBS 2003 I get errors like stated below.

AOFO: Started for resource: "D:". Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS).
The snapshot provider used by VSS for volume D: - Microsoft Software Shadow Copy provider 1.0 (Version 1.0.0.7).
Note: Resource: "\\WORKER\Microsoft Exchange Mailboxes" is not snappable. Attempting to back up directly from the source volume.
Note: Resource: "\\WORKER\Microsoft Exchange Public Folders" is not snappable. Attempting to back up directly from the source volume.

Unable to attach to \\WORKER\Microsoft Exchange Mailboxes.
V-79-57344-33932 - Unable to attach to a resource. Make sure that all selected resources exist and are online, and then try again.


Unable to attach to \\WORKER\Microsoft Exchange Public Folders.
V-79-57344-33932 - Unable to attach to a resource. Make sure that all selected resources exist and are online, and then try again.

I have applied all fixes from Microsoft and Veritas, but nothing helps. This is a brand new server, fresh installed.

How is this possible?

Regards,

Robbert

[Asma_Tamboli]

Hi,

- It is usually recommended that the exchange databases be backed up with the remote agent instead of with AOFO.

Try backing up Exchange without AOFO selected.

- Also ensure that the BESA has the Domain Admin rights, full exchange rights and that the account has a mailbox which is activated and is not hidden from the Global Adress List. You can refer to the following Documents to configure the account in this manner:



http://support.veritas.com/docs/266074


http://support.veritas.com/docs/256537


http://support.veritas.com/docs/243328

Hope it helps!

Note : If we do not receive your reply within two business days, this post would be marked ‘assumed answered’ and would be moved to ‘answered questions’ pool.

[Luis_Sakihama]

Hi,

Yes, it is highly recomendly not to use AOFO in Exchange backups, see the following:

http://seer.support.veritas.com/docs/263784.htm

hope this helps

[Robbert_Brackel]

I'm currently running without the AOFO. I'll post the outcome.

Still it's strange. We just purchased BE 10 SBS with the seperate AOFO. So this was a waste of money?

Robbert

[Robbert_Brackel]

I still have the same problem.

Can anyone give me a good solution / workaround?

Thanks,

Robbert.

[Shilpa_pawar_2]

Hi,

Please refer to the following technote in order to isolate the issue:
- Preliminary Troubleshooting List for Exchange and mailbox backups
http://seer.support.veritas.com/docs/242606.htm

Also try creating a new account in Backup Exec and in active directory. Give this account domain admin and local admin rights. Also give exchange full admin rights and make sure that account is not hidden in GAL. Activate this mailbox and test backup with this new account.



NOTE : If we do not receive your reply within two business days, this post would be marked "assumed answered" and would be moved to "answered questions" pool.