Video Screencast Help

BAR GUI and BPLIST COMPARISON.

Created: 25 Jul 2013 • Updated: 26 Jul 2013 | 4 comments
This issue has been solved. See solution.

Hi Guys,

Master : Linux , 7,.5.0.4

Media servers on same vesrion.

Master and media servers are on appliance 5220.

Client : Windows 2008, MS Exchange 2007.

Type Of Backup MS-Exchange.

Problem :

We have the restore request for restoring individual mailbox.

We have GOOD backup. No when we go to BAR GUI and BROWSE for "Top Of Information Store" and furher folders.....

BAR GUI displays as "No Entity Was Found".

Here is the question : I checked with Symantec regarding browing the images ;

Answer : When we click the ANY FOLDER (consider top of information store) there will be job populated in Activity Monitor with Type Restore.

I agree, It connects with MS EXCHNG via API...but what it checks for on client server coz when that compltes we can browse the folder ahead.

when there was issue going on BAR GUI NO ENTITY WAS FOUND...i tried for BPLIST which was listing the mailbox items successfully.

Again the question is BAR GUI and BPLIST accessing the data from different location...from my point imgdb on master...it should be.

And if we consider bplist genreates the o/p differnly than BAR GUI for EXCHNAGE...then bpretsore option ruled out for EXCAHNGE?? coz we will not be able to find the img files without bplist 

 

 

Operating Systems:

Comments 4 CommentsJump to latest comment

Mark_Solutions's picture

When you browse an Exchange GRT image in the BAR GUI it mounts the image (via the Exchnage Server by default or on the Media Server if you have set that as the GRT Proxy Restore Host in the exchange servers client host properties)

It then reads that to extract the information

As a result it is usually quicker if you use a proxy restore host set to be your media sever

Also bear in mind that this only works at all whilst the backup image is held on disk, even if you have duplicated GRT information to tape.

You will see a blank restore job run every time you browse mailboxes in the BAR GUI - this is the image mount and read process running

It also helps to have a reasonable size disk storage unit fragment size as this makes reading the image quicker (I like to use 5000MB as a disk storage unit fragemtn size when using GRT)

Hope this helps

Authorised Symantec Consultant

Don't forget to "Mark as Solution" if someones advice has solved your issue - and please bring back the Thumbs Up!!.

Giri_S's picture

You will see a blank restore job run every time you browse mailboxes in the BAR GUI - this is the image mount and read process running -> Is there a way to go on media server and chk for that images whether its mounted or not and the location too (i know tht when restore chkin job compltes it mounts tht).

Can u please help me to understand second part to : means for bplist....

Netbackup Admin (Unix)

Mark_Solutions's picture

It mounts the image using NFS - you may see an additional drive letter appear on the Exchange or Media Server when this happens - until it is mounted it cannot start to read it - this can take a while

Not sure if there is a problem doing a GRT restore using the bprestore command but the manual does make a note of:

If you start an Exchange mailbox restore operation with the bprestore command
and encounter a status 5 error, check that the path is correct. The bplist command
does not properly escape the “[” and “]” characters.
For example, bplist returns the following path for a mailbox:
/Microsoft Information Store/SG1/Mailbox1/backrest100 [backrest100]/
Instead, edit the path so it appears as follows:
/Microsoft Information Store/SG1/Mailbox1/backrest100 \[backrest100\]/

Authorised Symantec Consultant

Don't forget to "Mark as Solution" if someones advice has solved your issue - and please bring back the Thumbs Up!!.

SOLUTION
Giri_S's picture

to verify whether its mounted...i think /usr/openv/netbackup/bin/net use could be good idea?

isn't it ? I ll log seperate case with symantec for HOWTO restore from cmd for exch.

Netbackup Admin (Unix)