Connection errors with version 9, Exchange and SharePoint 2

[PHead2]

I upgraded to version 9 this week and now I have problems backing up my Exchange and Sharepoint Portal servers. There wasn't any problem when I was using 8.6. Data does get backed up (about 12GB worth) but the job fails.

Here's what's returned in the Job Log:

Job Completion Status
Job ended: Friday, February 14, 2003 at 2:10:23 AM
Completed status: Failed
Final error code: a000fe30 HEX
Final error description: A communications failure has occurred.

Final error category: Server Errors



Errors
The connection to target system has been lost. Backup set canceled.


This has happened three nights in a row.

Anyone have any experience with this?

 

[Qdog]

Did you fix this? Let me know, got a similiar issue with Sharepoint....

 

[rasworld]

Hi Guys,

Did either of you get to the bottom of the error, i am having the same problem on a Dell box with SBS 2k on it...

Any help appreciated

Ryan
Sydney Australia

 

[BENHIL]

I upgraded also to version 9 and now I have the same problems backing up my Exchange.

I get following error message:

a000fe30 HEX
A communications failure has occurred

At least I have installed the newest servicepack, but the error appears every night.
If I look in the restore-list I see all mailboxes.
So ... can I ignore this error-message or knows someone a
solution for my problem ????

I found nothing about this error on the website of veritas ...

 

[kempis555]

I'm having the exact same problem, and this is after finally getting Exchange to backup only after setting the backup user to be an administrator, and then allowing all administrators to read any mailbox. Bleah that sucks security-wise, now any junior admin can read the CEO's mail.

This just happened on Friday after the exchange server went down temporarily and scared me into getting this veritas thing working. ^_^

I also noticed in the first posting that my exchange mailboxes are backing up around 12 GBs as well... I wonder if a limit or something has been reached at 12. The exact number is: 12,361,245,486 bytes.

If you find any answers please post them, thanks.

-k

 

[PHead2]

I solved the Exchange problem be deleting a recreating the service account's (the one that Veritas uses to access Exchange) mailbox. Give it a try.

 

[PHead2]

For the last poster having to set the backup user as admin and granting all admins mailbox access, how do you have your Veritas service account setup?

You should create on account that is a Domain Admin and Exchange Full Admin and set its' password to never exprire. You should then configure Vertias to use this account and have the Backup Exec Remote Agent run under this account name as well (as well as all Veritas services on the Backup Exec server). If you do all this the user account will already be an Admin on the server and have access to backup all of the mailboxes. Other users do not need to know the password for this account, they can still use Veritas as long as they have rights on the server it is running on.

I was never able to solve the Sharepoint problem, we stopped using it anyway since it was really unreliable...

 

[kempis555]

Thanks PHead, I was reading other posts apparently other people have been using the re-made job trick to solve the exchange problem.

I'll try that to see if the error goes away for me. The odd thing is that BE doesn't say that Exchange is the problem, it's just giving that error with no details.

-k

 

[PHead2]

Just to be clear, I deleted and recreated the mailbox, not the backup job...

Good luck.

-P

 

[BENHIL]

Hmmh .....

PHead2 (TechnicalUser) Jul 14, 2003
Just to be clear, I deleted and recreated the mailbox, not the backup job...

I cannont find any mailbox on our exchange server, which
is created form veritas.
Can You help me to find this mailbox.

... or .... must we create a special mailbox ???

Thaks ... for Your help !!!

GM

 

[kempis555]

Ditto what Benhil asked.

I never set up a mailbox for the backup user either. Is that something we overlooked in the documentation? Why would he (she?) need a mailbox?

-k

 

[PHead2]

I started with 8.6 and one of the requirements for backing up Exchange mailboxes was to create an Exchange mailbox which was associated with the account Veritas uses. You could only backup the Information Store as a whole wihtout the mailbox. I do not know if this requirement went away with version 9 but I do know that deleting and recreating this account solved my connection problems when trying to backup the individual mailboxes. If the account was never created than maybe that's what the problem is, although I know I read somewhere that version 9 did not have all of the requirements for exchange earlier versions did. I cannot remember what the differences were though.

I am sure that the mailboxes were not getting backed up until I fixed this (only the entire Information Store was) based on the size of the backups.

 

[PaulAckerman]

The error: "The connection to target system has been lost. Backup set canceled" is caused by veritas attempting to backup the Exchange virtual directory (M by default). Exchange creates this drive to interact with other apps and it is not to be backed up under any circumstances according to Veritas as it can corrupt the information store. Removing the M drive from the selections will resolve the situation and you will no longer get this error.