Exchange 2010 backup with NMM 2.3

Hi Zkk,

That error message is coming from an error in the group configuration. Please note that NMM backups are snapshot based, so you need to select the snapshot option in the group configuration, set snapshot policy and the desired pool to be used.

Also please consider removing the variable NSR_EXCH_RETAIN_SNAPSHOT=yes if the snapshot policy selected is "Serverless backup" to avoid any further issue.

Thank you.

Carlos.

Hi Zkk,

In this case, as explained earlier, the problem is that you did not select snapshot type backup, and that is required for NMM backups (most of them).

For Exchange backup that is indeed required, so please change the group configuration to check the box "Snapshot backup" and select for example Snapshot policy "Serverless Backup".

Then in the client configuration please add the following settings:

Backup command: nsrsnap_vss_save

Application Information:

NSR_SNAP_TYPE=vss

NSR_ALT_PATH=C:\NMMSnapshot (You can set any other path not located in a clustered disk)

NSR_EXCH2010_BACKUP=active (or passive if backing up passive databases)

NSR_EXCH2010_DAG=dag.example.com

That configuration should work, however please remember not to select any pool in the client configuration or backup will also fail, as the pool in this case is set in the Snapshot pool you selected already in the group settings (just below the snapshot policy).

Thank you.

Carlos.

HI thanks for support

the failure requesting

what is this key value

HI

We dont have DAG , so i can omit that line for specifying DAG parameter ,once again thanks i am very new to NW i ahve only experiance in HP DP and Veritas products , i am verymuch confused about this networkser concepts ,

Hi Zkk,

No worries. Basically this is the meaning of each variable. You will only need to set these 2 for NON-DAG backups:

NSR_SNAP_TYPE=vss

NSR_ALT_PATH=C:\NMMSnapshot (You can set any other path not located in a clustered disk)

NSR_SNAP_TYPE=vss is required to instruct NetWorker that this a snapshot type backup is going to use Microsoft VSS to take the snapshot.

NSR_ALT_PATH is required to instruct NMM where to mount the snapshot for consistency check.

These together with the group configuration (setting snapshot group) is what you need in order to have a valid NMM backup for Exchange 2010 stand-alone.

Let us know if this eventually work for you.

Thank you.

Carlos.

Hi Zkk,

I forgot to mention a third variable that could be handy for you, specially for testing purposes:

NSR_EXCH_CHECK=no

This variable will force NMM to skip the consistency check, so for testing purposes backup can take less time skipping the consistency check.

Thank you.

Carlos.

on all groups which was previuusly working i tried this job , all the same result

Deleted all existing ,created a new backup job

in genenral tab

Save set added

APPLICATIONS:\Microsoft Exchange 2010\Mailbox Database 1114983022

APPLICATIONS:\Microsoft Exchange 2010\Public Folder Database 0904658189

this is copied from the nsrsnap_vss_save ? output 

checked schedule  backup

selected a group

in apps and modules tab

backup command added nsrsnap_vss_save

under application information

NSR_SNAP_TYPE=vss

NSR_EXCH2010_BACKUP=active

NSR_ALT_PATH=D:\NMMSnapshot

only these 3 added

seelected servverless snapshot in group proerties

immediately witin a minute

Failed message

here only server name : APPLICATIONS:\Microsoft Exchange 2010\Mailbox Database 1114983022: Backup of [APPLICATIONS:\Microsoft Exchange 2010\Mailbox Database 1114983022] failed

and 2 more which i cant get any details servername.domain name nsrsnap_vss_save

HI

i Applied as you said now i have client and group

if i run the job it says success in a minute but if i go to group property status

Exchangeserver

APPLICATIONS:\Microsoft Exchange 2010\Mailbox Database 1114983022

succeeded:skip:save:nsrsnap_vss_save

Exchangeserver: APPLICATIONS:\Microsoft Exchange 2010\Mailbox Database 1114983022 level=skip,0 KB 00:00:00      0 files

Exchangeserver

APPLICATIONS:\Microsoft Exchange 2010\Public Folder Database 0904658189

succeeded:skip:save:nsrsnap_vss_save

Exchangeserver: APPLICATIONS:\Microsoft Exchange 2010\Public Folder Database 0904658189 level=skip,0 KB 00:00:00      0 files

Exchangeserver

index

succeeded:skip:index

Exchangeserver: index:Exchangeserver      level=skip,      0 KB 00:00:00      0 files

What does this mean

Hey Zkk,

That is because you have either "Force Incremental" set in the group and/or schedule set to Skip for today so please, uncheck the box "Force Incremental" and also ensure the backup schedule or backup level is set to full.

Thank you.

Carlos.

Hi Zkk,

I think we reached the last obstacle

That error message (Error 0x80004005) is caused because of having the Exchange logs and DB in the same path.

Please note that since NMM 2.3 Build 81 it is supported to have DB and logs in same volume, however being in the same path it is not, so you need to manually move the Exchange logs to an alternate location.

After that, and just in case, run these commands:

vssadmin list writers

Check that all writers are in status  [1]

Then run vssadmin list shadows

If any shadow present manually delete it by running diskshadow:

C:>diskshadow

DISKSHADOW>delete shadows all

DISKSHADOW>exit

This last step is not really required, but it worth more to prevent than to troubleshoot

Thank you.

Carlos.

HI

There is progress now

but job failes with

82624:nsrsnap_vss_save:Save set name APPLICATIONS:\Microsoft Exchange 2010\Mailbox Database 1114983022 is valid.

82624:nsrsnap_vss_save:Save set name APPLICATIONS:\Microsoft Exchange 2010\Public Folder Database 0904658189 is valid.

63781:nsrsnap_vss_save:NMM .. attempt to add component of writer Microsoft Exchange Writer returned an error and can not be added. Error = -2147467259.

63783:nsrsnap_vss_save:NMM .. attempt to add components of writer Microsoft Exchange Writer returned an error and were not added. Error = -2147467259.

80826:nsrsnap_vss_save:NMM .. Backup of Exchange 2010 saveset Microsoft Exchange 2010\Public Folder Database 0904658189 failed. Error 0x80004005.

63335:nsrsnap_vss_save:NMM backup failed to complete successfully.

Internal error.

68151 1327911809 2 0 0 5528 2456 0 exchangeserver.domain  nsrsnap_vss_save 39 nsrsnap_vss_save: Exiting with failure. 0

Zkk,

Error message shown above is because of the logs being in same path as the DB.

Anyway yes, you need to ensure that user (the user set for Replication Manager Exchange Interface) has the correct permissions. Anyway a permissions or IIS related issue would return error message like 0x8001015 (if I remember well).

However your best friend should be always NMM Config Checker. This software (available in Powerlink) will check all that for you.

Thank you.

Carlos.

i checked the document ,

This user needs Exchange Organization, the user is having all permissions as mentioned in the below steps

Domain Administrator and "send-as, Receive-as" permissions.

If the user has already those permissions, check in COM+, as described in NMM 2.3 Documentation:

Modifying the Microsoft Exchange 2007 COM+ component’s user account or password
If your user account, your password information, or both change after the COM+ component is registered, use the following procedure to change the user account or password information for the COM+ component:
1. Start component services.
2. Expand Computers > My Computer > DCOM Configuration.
3. Right-click Replication Manager Exchange Interface and select Properties from the context menu.
4. Click the Identity tab.
5. Modify the domain user account or password and click OK.