Highlighted
2 Bronze

Issues creating Exchange 2010 DAG Backup

Jump to solution

Hello

I am new to the forum and would appreciate any help.

I am looking for help or step by step instructions for creating a new networker backup for Exchange 2010 DAG.

I trying to do this with networker 8.2.0.5 and NMM 8.2

I think I may have something wrong with the settings I have on my clients?

I have six servers in the DAG.

I have two entries for each server (one for OS and one for exchange) and one for the DAG name.

The OS Client

Save Set : ALL  

Backup Commands and Application Info are blank.

The Exchange Client Entries

Save Set : APPLICATIONS:\Microsoft Exchange 2010   

Backup Commands and Application Info are blank.

EXCDAG

Save Set : APPLICATIONS:\Microsoft Exchange 2010 


Backup Command: nsrsnap_vss_save


Application Information:


NSR_SNAP_TYPE=vss

CIRCULAR_PROMOTION_POLICY=Promote

NSR_FEDERATED_BACKUP=yes

NSR_FEDERATED_PSOL=EXCCLIENT01,EXCCLIENT02,EXCCLIENT03,EXCCLIENT04,EXCCLIENT05,EXCCLIENT06

NSR_EXCH_INCL_SA=TRUE

NSR_ALT_PATH=c:\nw_mount

NSR_EXCH2010_DAG=ExcDAG

NSR_EXCH2010_BACKUP=preferred

NSR_EXCH_CHECK=no

The Exchange Group Has only the EXCDAG in it and the properties are:

Snapshot, policy and pool are all selected.

Configuration ... Retries to runtime limit are all set to 0

I am trying to run the group that has just the DAG as a client and it does not backup any data and fails.

I get one of these for each member of the DAG.

EXCDAG:APPLICATIONS:\Microsoft Exchange 2010 85940:nsrsnap_vss_save:Slave backup with job id (1885684) failed on host


Also get one of these in each of the servers event log:

The group or resource is not in the correct state to perform the requested operation. .


Any help or ideas is much appreciated. Thank you

0 Kudos
1 Solution

Accepted Solutions
Highlighted
4 Germanium

Re: Issues creating Exchange 2010 DAG Backup

Jump to solution

Hi ttobey

Can you please check the nmm.raw file (render it so it's readable) ?

Maybe you would like to attach it here?

Thank you,

Carlos

View solution in original post

0 Kudos
7 Replies
Highlighted
4 Germanium

Re: Issues creating Exchange 2010 DAG Backup

Jump to solution

Hi ttobey

Can you please check the nmm.raw file (render it so it's readable) ?

Maybe you would like to attach it here?

Thank you,

Carlos

View solution in original post

0 Kudos
Highlighted
2 Bronze

Re: Re: Issues creating Exchange 2010 DAG Backup

Jump to solution

Here is the latest try in nmm.log from one of the servers.

Thanks for looking Carlos Rojas

0 Kudos
Highlighted
2 Bronze

Re: Issues creating Exchange 2010 DAG Backup

Jump to solution

A small update.........

I am right now trying again after changing the DAG to backup ACTIVE instead of PREFERRED and it seems to be making better progress. (Maybe its bypassing the non-healthy copies?) I will post results and if needed new nmm in a bit.

Thanks

0 Kudos
Highlighted
2 Bronze

Re: Re: Issues creating Exchange 2010 DAG Backup

Jump to solution

As I mentioned here is the latest.

Thanks again

0 Kudos
Highlighted
4 Germanium

Re: Issues creating Exchange 2010 DAG Backup

Jump to solution

Hi,

The error message:

The database state for saveset Microsoft Exchange 2010\DB10 doesn't match the NSR_EXCH2010_BACKUP or NSR_EXCH_BACKUP value  and will not be backed up

Means that doesn't like the value NSR_EXCH2010_BACKUP=ACTIVE

Have you tried to use "Preferred passive" instead? Or even passive? You can try to make sure this is the only configuration issue, and if it works we take it from there.

Thank you,

Carlos

Highlighted
2 Bronze

Re: Issues creating Exchange 2010 DAG Backup

Jump to solution

I did.

When I set it to active I get the error you see.

When set to passive or preferred I get that the (clones) DB are not healthy.

I have the exchange guy rebooting the seemed problem server and I will try again with preferred and passive and post back. Thanks

0 Kudos
Highlighted
2 Bronze

Re: Re: Issues creating Exchange 2010 DAG Backup

Jump to solution

I do believe I am all set.

After the replication of the non healthy server it seems to be OK.

I hit a few other minor self explanatory snags that I worked out.

The backup was successful and we will soon test a restore to make sure we are good.

Thanks Carlos Rojas for willingness to help me out.

0 Kudos