Forum Discussion

a1expi's avatar
a1expi
Level 3
9 years ago

Exchange DAG restore - cannot find the backup image

-Exchange 2013 DAG on Windows 2012 R2

-Netbackup 7.6.1.1 (Just upgraded to 7.6.1.2)

-VMware backups to tape (no disk)

-VSS provider installed, exchange admin guide followed

 

I'm having a really odd error when trying to do a restore of a database from a DAG backup (I'm aware I can't do GRT as i'm on tape).

The policy is set to backup the DAG exactly as described in the admin guide, the backup (and the ASC part) completes without any issue.

The first oddity is that when I come to do a restore I choose the DAG as the source client, I see the backups listed but I can't preview any media, the box to show the tape numbers is blank.

If I change the source client to be the underlying Exchange VM I can see the same backup points (But with the drives/folders rather than Information Store) and selecting something lets preview media work as normal.

When I come to restore a database the restore starts, it works out which server to restore to and then errors with:

04/02/2016 22:27:46 - Info bprd(pid=5788) Searched ( 14) files of (189) files for Restore Job ID 8214.xxx
04/02/2016 22:27:46 - Info bprd(pid=5788) Restoring from copy 1 of image created 12/25/15 20:00:15 from policy EX-NEW
04/02/2016 22:27:56 - Info tar32(pid=3452) Restore started           
04/02/2016 22:27:57 - Error bpbrm(pid=4332) cannot find the backup image that the view 10680 depends on  
04/02/2016 22:27:57 - Info tar32(pid=3452) done. status: 175: not all requested files were restored    
04/02/2016 22:27:57 - Error bpbrm(pid=4332) client restore EXIT STATUS 175: not all requested files were restored 

I have distributed application restore mapping set for the DAG, both with FQDN and short names for component host.

Does anybody have any idea about what's going on?

It's almost like it's struggling to link the images taken of the VM to the MS-Exchange-Server restore type.

 

 

 

 

 

 

  • Chasing the thread about fs01 being an illegal server I've eventually stumbled on the solution.

    What I eventually did was add the media server (fs02) to both the master and media server additional server list:

    Master server (fs01) additional servers:

    fs02

    All exchange servers

    DAG Name

    Media server (fs02) additional servers:

    fs02 (Itself, if this isn't in the list the backups fail!)

    All exchange servers

    DAG name

     

     

19 Replies