Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

How to backup and restore exchange DAG 2010 with Netbackup 7.1

Created: 13 Feb 2013 • Updated: 30 Apr 2013 | 10 comments
This issue has been solved. See solution.

Hello i have two nodes cluster for exchange DAG 2010 i would like to make the good backup. Already what file need to backup with exchnage and how can do it when i create the policy especially in the "backup selection"
please could also explain me the GRT (Granular Recovery Technology) what is the advantage to use it.
thx

Discussion Filed Under:

Comments 10 CommentsJump to latest comment

Dyneshia's picture

Please review our how to viedo : http://www.symantec.com/docs/HOWTO41825

Specifcially : Configuring Exchange 2010 Granular Restore Technology (GRT) Backups with NetBackup 7.0

http://www.symantec.com/docs/HOWTO41878

For configuration :

Everything you need to know to get Exchange Granular backups to work.

http://www.symantec.com/docs/HOWTO73076

What are the supported Disk Storage types for NetBackup Granular Restore Technology (GRT) backups?

http://www.symantec.com/docs/TECH187917

The advantage is you can restore just a single piece of mail instead of the whole mailbox or database.

The downfall is you need a lot of storage since you can only back up to Disk.

SOLUTION
Dyneshia's picture

dont forget to mark the solution if you have received the info you were looking for :)

yaosergekouame@yahoo.fr's picture

hello i have follow your instruction now i meet one error snapshot

1: (130) system error occurred

02/28/2013 18:07:55 - end Snapshot: Delete Snapshot On Exit; elapsed time 0:00:15
02/28/2013 18:12:58 - Info bpbrm (pid=436) reading file list from client
02/28/2013 18:12:58 - Info bpbrm (pid=436) start bpfis on client
02/28/2013 18:12:58 - begin Create Snapshot
02/28/2013 18:13:00 - Info bpfis (pid=14388) Backup started
02/28/2013 18:17:45 - Critical bpbrm (pid=436) from client bak-dag01: FTL - snapshot creation failed - SNAPSHOT_NOTIFICATION::PostSnapshot failed., status 130
02/28/2013 18:17:45 - Critical bpbrm (pid=436) from client bak-dag01: FTL - snapshot creation failed, status 130
02/28/2013 18:17:45 - Warning bpbrm (pid=436) from client bak-dag01: WRN - NEW_STREAM0 is not frozen
02/28/2013 18:17:45 - Warning bpbrm (pid=436) from client bak-dag01: WRN - Microsoft Information Store:\DB_ILM1 is not frozen
02/28/2013 18:17:45 - Info bpfis (pid=14388) done. status: 130
02/28/2013 18:17:45 - end Create Snapshot; elapsed time 0:04:47
02/28/2013 18:17:53 - Info bpfis (pid=0) done. status: 130: system error occurred
system error occurred  (130)

may be the snapshot is not well defined i have put

Snapshot Methed VSS on the policy

Provider Type : 0

Snapshot attribute 0

Maximun Snapshots : 1

My MS Exhange DAG run on the Windows Server 2008 R2 Enterprise

captain jack sparrow's picture

Could you revert with writer status requested by dyneshia.. and bpfis log from active mailbox server

 Cheers !!!

CJS

Dyneshia's picture

Please reply back with the following from each server in the dag :

C:\> vssadmin list providers

C:\> vssadmin list writers

All should come back in a stable state.  Example :

Writer name: 'Microsoft Writer (Bootable State)'
Writer Id: {f2436e37-09f5-41af-9b2a-4ca2435dbfd5}
Writer Instance Id: {bf25043e-afce-43ee-8bcb-4a074496fc06}
State: [1] Stable

Writer name: 'MSDEWriter'
Writer Id: {f8544ac1-0611-4fa5-b04b-f7ee00b03277}
Writer Instance Id: {56b4ca59-b2b2-468c-b0f8-92e6f3193f13}
State: [1] Stable

Writer name: 'Microsoft Writer (Service State)'
Writer Id: {e38c2e3c-d4fb-4f4d-9550-fcafda8aae9a}
Writer Instance Id: {f1c8985f-c8ea-4826-90c6-b04ca78e5de6}
State: [1] Stable
 

If anythign is failed or waiting for completion , a quick fix would be to reboot the server to clear out the writer.  If not Micrsoft will need to be conacted.

Last is circular logging enabled ?

Jomy's picture

Hello,

what is the permanent solution ?

circular logging enabled ? is it required to diasable ?

Dyneshia's picture

If circular logging is enabled, you will only be able to do FULLS.  Please see : http://www.symantec.com/docs/TECH11310
 

The only common  reason for a 130 ( snapshot ) is unstable writers or multiple providers.

To verify the writers are stable by running following from a command line on each server in the dag :

C:\> vssadmin list providers

C:\> vssadmin list writers

All should come back in a stable state.  Example :

Writer name: 'Microsoft Writer (Bootable State)'
Writer Id: {f2436e37-09f5-41af-9b2a-4ca2435dbfd5}
Writer Instance Id: {bf25043e-afce-43ee-8bcb-4a074496fc06}
State: [1] Stable

Writer name: 'MSDEWriter'
Writer Id: {f8544ac1-0611-4fa5-b04b-f7ee00b03277}
Writer Instance Id: {56b4ca59-b2b2-468c-b0f8-92e6f3193f13}
State: [1] Stable

Writer name: 'Microsoft Writer (Service State)'
Writer Id: {e38c2e3c-d4fb-4f4d-9550-fcafda8aae9a}
Writer Instance Id: {f1c8985f-c8ea-4826-90c6-b04ca78e5de6}
State: [1] Stable
 

If anythign is failed or waiting for completion , a quick fix would be to reboot the server to clear out the writer.  If not Micrsoft will need to be conacted.

Jomy's picture

after restarting the exchange server replica writer ststus gets reset

but sarting waiting for completion status after snashot...snapshot itself is in hung state not completing ..

Marianne's picture

Jomy, Please start a new discussion for your issue?

Please post all relevant info for your setup.

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links