08-28-2018 04:33 AM
Can anyone share the process flow from exchange perspective
Solved! Go to Solution.
08-28-2018 04:45 AM
It connects the the DAG and then it finds out where the databases are hosted (active/passive) so it can connect to those hosts to get the data.
08-28-2018 07:57 AM - edited 08-28-2018 07:57 AM
The NetBackup for Exchange admin guide explains in detail how Exchange servers are selected for backup. Bpresolver is just the process that makes the selection.
Bpresolver also...
- Determines whether an Exchange server is part of a DAG the first time the server is used for a backup. You can see the call in the bpbrm log.
- Selects one or more Exchange servers for a database restore. It selects the active server for each database being restored. In this case, you can see the call in bprd, and then you can see one or more child bprd processes for the actual restores.
- Selects an Exchange mailbox server for GRT restore. Before NetBackup 7.6.0.3 (meaning Exchange 2010 only), bpresolver selected a CAS. From 7.6.0.3 forward, this call is a no-op. Bpresolver runs on the destination client, and selects that client so long as it's an Exchange mailbox server.
I don't think we have documented the flow within bpresolver. That's an internal detail, subject to change as changes in Exchange force changes. At a gross level, bpresolver invokes something called BEDS, which is a library shared with Backup Exec, to find out about the Exchange environment. Within BEDS, a process called monad makes any PowerShell calls that may be necessary.
08-28-2018 04:45 AM
It connects the the DAG and then it finds out where the databases are hosted (active/passive) so it can connect to those hosts to get the data.
08-28-2018 04:58 AM
Thank you..
If you have documents regarining the process flow of exchange backup included both netbackup and exchange processes, pls share
08-28-2018 07:09 AM
And how the BPRESOLVER will behave when the exchange node is added to the preffered server list
08-28-2018 07:57 AM - edited 08-28-2018 07:57 AM
The NetBackup for Exchange admin guide explains in detail how Exchange servers are selected for backup. Bpresolver is just the process that makes the selection.
Bpresolver also...
- Determines whether an Exchange server is part of a DAG the first time the server is used for a backup. You can see the call in the bpbrm log.
- Selects one or more Exchange servers for a database restore. It selects the active server for each database being restored. In this case, you can see the call in bprd, and then you can see one or more child bprd processes for the actual restores.
- Selects an Exchange mailbox server for GRT restore. Before NetBackup 7.6.0.3 (meaning Exchange 2010 only), bpresolver selected a CAS. From 7.6.0.3 forward, this call is a no-op. Bpresolver runs on the destination client, and selects that client so long as it's an Exchange mailbox server.
I don't think we have documented the flow within bpresolver. That's an internal detail, subject to change as changes in Exchange force changes. At a gross level, bpresolver invokes something called BEDS, which is a library shared with Backup Exec, to find out about the Exchange environment. Within BEDS, a process called monad makes any PowerShell calls that may be necessary.