Forum Discussion

mnakhan's avatar
mnakhan
Level 5
12 years ago

MS-Exchange 2010 DAG (GRT) restoration of individual mailbox to different location failed

hi,

in my environment MS-Exchange Server 2010SP2 MS-Windows2008R2 2servers in DAG,

CAS servers 2010SP2 MS-Windows2008R2  2 servers,

Appliance5220 2.5.2

when we restore the backup of individual mailbox on same database location its functional. when we tried to restore the individual mailbox on different database location under the same dag its failed.

10/04/2013 03:09:08 - begin Restore
10/04/2013 03:09:09 - restoring from image dag.com_1379696765
10/04/2013 03:09:09 - Info bprd (pid=21428) Restoring from copy 1 of image created Fri Sep 20 12:06:05 2013
10/04/2013 03:09:09 - requesting resource @aaaac
10/04/2013 03:09:09 - granted resource  MediaID=@aaaac;DiskVolume=PureDiskVolume;DiskPool=dp_disk_tnb-appliance;Path=PureDiskVolume;StorageServer=tnb-appliance;MediaServer=tnb-appliance
10/04/2013 03:09:11 - Info bpbrm (pid=21464) MSMPCH1 is the host to restore to
10/04/2013 03:09:11 - Info bpbrm (pid=21464) reading file list from client
10/04/2013 03:09:11 - connecting
10/04/2013 03:09:11 - Info bpbrm (pid=21464) start nbfsd on client
10/04/2013 03:09:13 - Info bpbrm (pid=21464) start nbgre on client
10/04/2013 03:09:15 - Info tar (pid=0) Restore started
10/04/2013 03:09:15 - connected; connect time: 0:00:00
10/04/2013 03:09:47 - Error bpbrm (pid=21464) from client MPCH1: ERR - unable to create object for restore: \\dag\Microsoft Information Store\Database1\Database\Production [ramahmud], rai error = 17
10/04/2013 03:09:47 - Error bpbrm (pid=21464) from client MPCH1: ERR - unable to create object for restore: \\dag\Microsoft Information Store\Database1\Database\ [_mahmud]\Top of Information Store, rai error = 17
4/2013 05:23:24 - Error bpbrm (pid=17731) from client MSMPCH1: ERR - unable to create object for restore: \\dag\Microsoft Information Store\dbx01\Database\bkuptest [bkuptest]\Top of Information Store\Tasks, rai error = 17
10/04/2013 05:23:24 - Info tar (pid=0) done. status 0
10/04/2013 05:23:24 - Info tar (pid=0) done. status: 5
10/04/2013 05:23:24 - Info tar (pid=0) done. status: 5: the restore failed to recover the requested files
10/04/2013 05:23:24 - Error bpbrm (pid=17731) client restore EXIT STATUS 5: the restore failed to recover the requested files
10/04/2013 05:23:24 - restored from image dag.com_1380843563; restore time: 0:00:38
10/04/2013 05:23:25 - end Restore; elapsed time 0:00:45
MS-Exchange policy restore error  (2810)


 

kindly help me for its resolution

 

regards

Backup and Recovery
Linux
NetBackup Appliance

9 Replies

  • Mark_Solutions's avatar
    Mark_Solutions
    Level 6
    12 years ago

    Have you completed the Distributed Application Mappings on the Master Servers Host Properties?

    Have you tried running the restore from the alternate client itself - it should be run from there or the Master only.

    The No.Restrictions file is also useful here.

    Other than that the bpresolver log file from the CAS / Mailbox servers and the tar log from the destination client would be useful

  • mnakhan's avatar
    mnakhan
    Level 5
    12 years ago

    HI Mark all entries present in the master server properties->Distributed Application Mapping along FQN and without FQN .

    No.Restriction file is also present 777 permission of altnames/No.Restrictions

    but no luck.

  • Anuj_Kr's avatar
    Anuj_Kr
    Level 4
    12 years ago

    Is that 2 Exchange database are on different Exchange active node?

    Check out with your exchange admin if they are able to move any mailbox between from DB 1 to DB 2 without any error. If they are able to do so then we should check netbackup logs of client for further investigation.

  • Marianne's avatar
    Marianne
    Level 6
    12 years ago

    ... we tried to restore the individual mailbox on different database location ....

    Have you created a mailbox on the 'different' database?

    One of the basic mailbox restore requirements is that the destination mailbox must exist.

    See Prerequisites and operational notes for restoring Exchange individual mailboxes ...  in NetBackup for Microsoft Exchange Server Administrator's Guide  http://www.symantec.com/docs/DOC5172

  • Mark_Solutions's avatar
    Mark_Solutions
    Level 6
    12 years ago

    Not only must it exist on the target location but as mailbixes tie into AD as well as exchange i would imagine that it cannot exist in the original location as well - otherwise the user would have 2 mailboxes on 2 different databases

    You need to run this against a test mailbox - run the backup, delete the test mailbox, create an empty new mailbox on the destination and then try the restore - i cannot see how else this could work as exchange would just not allow it

    Hope this helps

  • mnakhan's avatar
    mnakhan
    Level 5
    12 years ago

    hi Marianne,

    yes we created a mailbox on different database using command

    CMD ….1:

    Get-Mailbox abc |set-mailbox -Database dbx01

    Press “Y”

    CMD…2:

    Set-mailbox abc –applymandatoryproperties

    For verification:

    Get-mailbox –database dbx01

     

    then we use Netbackup BAR / CAS-server BAR for restoration to different location

    it fails

     

  • mnakhan's avatar
    mnakhan
    Level 5
    12 years ago

    Hi Mark,

    same location its restoration is working but we want to estore the entire mail box to different location menad from datbase to dbx01

     

  • mnakhan's avatar
    mnakhan
    Level 5
    12 years ago

    hi all,

    any solution for MS-exchange backup restore to different location?

    is any bug in NB 7.5.0.5 that create a hardle for restoration to different location?

    when i tried to restore MS-Exchange backup same location its working fine. i also check to restore FS backup to differnt location it's working.

     

     

     

  • nathanmike's avatar
    nathanmike
    Level 4
    12 years ago
    @noman, i had the sale problem. I opened a critical case at Symantec and they recommend me to patch to 7.5.0.6 because it has a lot of etrack about get (see 7.5.0.6 release notes) we did patch to 7.5.0.6 and we don't have problems anymore.