Video Screencast Help
Search Video Help Close Back
to help
Not able to make it to Vision this year? Get a sampling in the Best of Vision on Demand group.

Exchange 2007, Status 1

Updated: 16 Sep 2010 | 14 comments
Roobix.Cube's picture
0 0 Votes
Login to vote

Hi all,

Trying to set up Exchange backup of two storage groups, but both streams fail with a Status 1, and both report:

ERR - failure reading file: Microsoft Information Store:\Second Storage Group\Log files (BEDS 0xE0008488: Access is denied.)



The event log on the Exchange server reports:

Event ID 215: MSExchangeIS (1800) Second Storage Group: The backup has been stopped because it was halted by the client or the connection with the client failed.

 

 

Any thoughts?  It should be noted that regular file system backups from this server work fine.

 

 

 

Environment:
Master/Media server: Netbackup 6.5.1, Windows 2003
Exchange Server: Netbackup 6.5.1, Exchange 2007 on Windows 2003


Message Edited by Roobix.Cube on 07-01-2008 06:55 PM

Comments

Roobix.Cube's picture
01
Jul
2008
0 Votes 0
Login to vote

Still no luck....

 

1. have upgraded by master/media server and the Exchange server to Netbackup 6.5.2

 

2. tried starting the Exchange server's Netbackup client service as both  Local System Account and new Netbackup account in Domain Admins group.

J.Hinchcliffe's picture
02
Jul
2008
0 Votes 0
Login to vote

Hint - ( I am not a windows or exchange person).

 

When I first went to setup the exchange 2007 I also got these errors.

the windows/exchange person found that some security setting was not set in exchange 2007 to allow netbackup to the backups.

 

but I have no clue as to what they changed that made it work, but I do know that it was something about the admins not haveing rights to exchange 2007.

 

not sure if that helps or not.

I don't have to know how to spell....I work on Unix.
NetBackup 7.0.1 - AIX & Windows

Roobix.Cube's picture
07
Jul
2008
0 Votes 0
Login to vote

Hrmph.  I've upgraded the Exchange server to Windows 2003 SP2 and Exchange 2007 SP1, but still getting the same errors.  Following both Netbackup 6.5 Exchange pdf doco's (290211 and 292587) to configure permissions, as well.

 

Any other thoughts?  Any other tests I can run?

 

Roobix.Cube's picture
12
Aug
2008
0 Votes 0
Login to vote

Update:

 

I can successfully backup and restore /Microsoft Exchange Mailboxes/ and /Microsoft Exchange Public Folders/

 

For some reason I still can't backup Microsoft Information Store:\* or any variations thereof.  I have the NBU account as a member of (yes, I've gone overboard to get this working):

 

   Domain Admins
   Enterprise Admins
   Exchange Organization Admins
   Exchange Public Folder Admins
   Exchange Recipient Admins
   Exchange Servers
   Exchange View-Only Admins

 

Any other thoughts?  Very frustrating...  :smileymad:

sdw303's picture
13
Aug
2008
0 Votes 0
Login to vote

Is the same username specified in the "Exchange" tab of the client host properties?

Clustered Exchange?  Are you specifying the Exchange cluster name as the client name in the policy?

Roobix.Cube's picture
13
Aug
2008
0 Votes 0
Login to vote

Yep, the account name is there (MSITEAM\NBU), as below.  This is not clustered environment...

 

NBU_TSE's picture
16
Sep
2008
0 Votes 0
Login to vote

Hi Roobix,

 

First check that Client can enumerate the Information Store:

 

1. Logon to the Exchange Client (Active node if CCR) with the Exchange Admin account.

 

2. Open the Backup Archive and Restore Gui, select File... from the menu bar > Specify NetBackup Machines and Policy Type > Make sure the source/desntination is set to the Exchange Server name (as it appears in Exchange) and the Policy Type is set to MS-Exchange.

 

3. Now choose Select for Backup and check if Microsoft Information Store is visible and can be enumerated by expanding the folder (if possible)

 

At this stage if the Client is able to expand and see the Storage Groups, then we know NetBackup is communicating with Exchange via the BEDS interface, and we should be able to back this up ok.

 

If this cannot enumerate Information then there is either a configuration issue, possibly client name is not specified correctly, note: need to specify the EVS (Exchange Virtual Server) name if Exchange CCR. Or this could be a binary problem.

 

If NetBackup cannot see the Information Store, check if NTBackup can (if Win2003).

 

Please also confirm if Exchange and Windows is 32-bit or 64-bit. NetBackup does not work with Exchange 2007 in 32-bit environment.

 

Hope this helps

 

Gary (NetBackup Database Support Engineer)

Message Edited by NBU_TSE on 09-16-2008 02:46 AM

Snr Tech Support Engineer
NetBackup Database Team
Symantec

Roobix.Cube's picture
08
Oct
2008
0 Votes 0
Login to vote

Argh!  Perhaps that's the problem....we're running Exchange 2007 on Windows 2003, x86.  Seems like a lame way to end this.  Anyone have a work around here? 

Hyzer's picture
19
Oct
2008
0 Votes 0
Login to vote

First of all, I’m not an expert…

Try at your own risk :-)

 

 The Local system account should be fine when backing up information stores…

 

Have you tried backing up each information store independently?

(i.e. “Microsoft Information Store\SG1\Store1”)

I ran into something similar; part of exchange crashed… After getting exchange back up I kept getting code 1 when backing up that storage group.

Try backing up each information store independently, one by one. (Once the first store is backed up with a code “0”, start the next one. Don’t run them at the same time.) Exchange will not purge the transaction logs until the last store, in the group, has been backed up with a code “0.”

Once all stores are backed up and the transaction logs have been purged by exchange run a normal backup to see if Exchange and NBU are now in sync.

 

Good luck

sdw303's picture
19
Oct
2008
0 Votes 0
Login to vote

It does work, we successfully backup several info stores on MS Exch 2007 SP1 using NBU v6.5.2 - and restored each ok to an RSG - no problems.

 

I can add that using NetBackup to secure MS Exchange 2007 is only supported using the 64 bit client, and when MS Exchange 2007 and NetBackup v6.5.2 are running on 64 bit Windows (and I assume only Windows 2003 64bit is supported - I don't know about Win2008).

 

The account that is used to perform the backups:

1) Must be specified in the "Exchange" tab of the client properties.  (You've said this is done)

2) Must be the account that the "NetBackup Client Service" logs in as.  (You say you've followed the docs - so I assume you've done this)

3) Must be an MS Exchange Admin.   (I think you've got this covered).

4) Must have it own mailbox (I only read the post quickly and didn't see this mentioned).

 

HTH.

Roobix.Cube's picture
13
Nov
2008
0 Votes 0
Login to vote

 

Yeah, I'm pretty certain we've covered that all off, as per the screenshots below.  Same error occurs.

 

AD User

 

 


Exchange Mailbox 

 

Client Service

Client Properties 

 

 

Any other thoughts?

Roobix.Cube's picture
13
Nov
2008
0 Votes 0
Login to vote

In regards to a previous question, "Now choose Select for Backup and check if Microsoft Information Store is visible and can be enumerated by expanding the folder (if possible).   At this stage if the Client is able to expand and see the Storage Groups, then we know NetBackup is communicating with Exchange via the BEDS interface, and we should be able to back this up ok", I can indeed confirm that the BAR GUI can enumerate the Information Stores...

 

Backup, Archive and Restore GUI 

 

 

I can also confirm that NTBACKUP works...

 

NTBACKUP 

 

 

But still no Netbackup love :smileysad:

Message Edited by Roobix.Cube on 11-13-2008 05:42 PM
m3lyan's picture
14
Mar
2010
0 Votes 0
Login to vote

I have same problem in

I have same problem
in BAR GUI i can enumerate information store and First Storage Group
when i highlight storage group i got in the left pane that its contain mailbox database but nothing about the log
HELP

jpriddy's picture
15
Mar
2010
1 Vote -1
Login to vote

You're running Exchange 2007

You're running Exchange 2007 32-bit in production?  That is not in any way supported by Microsoft.  I didn't think that you could even get a key that would activate it for longer that 180 days... which would account for why Symantec would not support it either.