Exchange 2010 backup with NMM 2.3

Hi Pratik,

If you are running the backup against the node hosting the passive DB's it will be backing up only the passive DB's, I suggested to set "all", just to see what happens with the stand alone DB. Is that one in use?

Anyway, if you prefer just render the nmm.raw from the last backup and I'll take a look.

Thank you.

Carlos.

Hi Pratik,

Let's focus first in the backup and we'll look afterwards in the log truncation.

In this case it's normal that your backup is failing.

It's very important to understand this variable:

NSR_EXCH2010_BACKUP=passive

You are instruction NMM to backup only passive DB's, however APPLICATIONS:\Microsoft Exchange 2010\Mailbox Database 1127528913 is Standalone.

I understand you have set the saveset APPLICATIONS:\Microsoft Exchange 2010\ROLE 1, correct?

Please try to run a backup again setting this variable:

NSR_EXCH2010_BACKUP=all

Anyway, at this stage you should know that the error messages we are interested in are located in the nmm.raw file, and you should render it and paste the full output to have a better understanding of the failure.

Please run the backup again with the "all" value instead and let us know the results. If it fails please paste in here the rendered nmm.raw for the last 2 backup operations (passive and all)

Thank you.

Carlos

Microsoft Exchange Server 2010 SP1 14.1.218.15          Dated  8/24/2010   no rollups installed

Hi Carlos,

As you said, i made the change NSR_EXCH2010_BACKUP=all and started the backup. The backup had started and the snapshot were rolled over to the tape but the backup failed with following errors:

savegrp: suppressed 9 lines of verbose output

71639:nsrsnap_vss_save:NMM .. Failed to create passive node saveset. client `MAHA-MUM-MB01.MAHAGOV.LOCAL' is not properly configured on the NetWorker Server

or `MAHA-MUM-MB01.MAHAGOV.LOCAL'(if not a virtual host) is not in the aliases list for client `maha-mum-mb02.MAHAGOV.LOCAL' (15013).

82958:nsrsnap_vss_save:NMM .. creation of dummy saveset failed. Calling CommitReplica with FALSE.

77175:nsrsnap_vss_save:NMM ..  completed commit replica with status of false.

63335:nsrsnap_vss_save:NMM backup failed to complete successfully.

Internal error.

68151 1329908120 2 0 0 8744 1436 0 maha-mum-mb02 nsrsnap_vss_save 39 nsrsnap_vss_save: Exiting with failure. 0

objects to the NetWorker saveset 'VSS:/'.

NMM .. Delete the temporary snapshot as part of deport

76958:nsrsnap_vss_save:NMM .. successfully

Also i am attaching the error file & the backup details snapshot  for your reference.

Regards,

Pratik.

Hi Pratik,

Any luck with the backups? Did it finally work?

Thank you.

Carlos.

Hi Carlos,

Sorry for the late response. Yes, the backup has finally worked successfully. The issue was because of the default database that is created. I excluded that database and configured the backup and the backup went on smoothly.

Anyways, thanks a lot for your help.

Regards,

Pratik.

Any sort of netwoker related backup will run succesfully if carlos is with us ,ask him the way how to restore it also

if i can value carlos , i would have give him 1000 points ,

Thanks for the feedback. Could you please mark the question as answered?

Thank you.

Carlos.

Hi Pratik,

I would suggest to create a new threat for this, however before going ahead I would need to know:

1.- Is this stand alone or DAG environment?

2.- Have you checked the documentation? if so, did you follow the steps suggested? If so, and filed, what error message are you getting?

The most common issues are related to permissions at Exchange level, of even that NMM GUI is not open with elevated privileges in Windows 2008 or 2008 R2.

Thank you.

Carlos.

Thanks Carlos.

Will try this out and let you know.

@Zkk: I hope this might have answered your queries also.

Regards,

Pratik

Hi Carlos,

This is a DAG environment.

Regards,

Pratik U Vengurlekar

(System Integration - Services)

(+91 9769114223)

Hi Pratik,

The first step is to open NMM GUI with elevated rights (Open as administrator).

Then you need to ensure that the client name that you see on the top right area of NMM GUI is the DAG client name with FQDN. To change it (by default will appear the name of the physical node) you need to click in options, configure options. Then on the right of the client name you will see the "Refresh" button (2 green arrows). Click there and from the left pane select the DAG name with FADN, and click on "Add". Once displayed on the right pane then click OK. Back to the configure options window, click on the drop down menu and select the DAG name instead of the physical name. Then click OK.

Now you should see the DAG client name, and the DB's backed up. Then please read the "copy and paste" from NMM Application Guide documentation (you definitely should take a look, it's a step-by-step which includes screenshots):

To perform recovery of a DAG database:

1. Open the NMM client GUI.
2. Select the NetWorker Server on which the NMM client software was configured for backup.
3. Select the DAG client name on the top right area of NMM GUI
4. In the Exchange 2010 Recover Session toolbar, click the Advanced Recover Option.

The Advanced Recover dialog box appears. This dialog box lists the three steps for recovery:

• Select Recovery

• Select DB & Server

• Summary

Note: Click Recover Options to skip the steps for Advanced Recovery and perform full recovery of the database listed in Database (Source).

1.- In Select Recovery Type, under Recovery Type, select one of the following:

• Recovery Database (RDB) Recovery

Recovery to Recovery Database (RDB)

To perform recoveries to RDB for Exchange 2010:

2.- In the Advanced Recovery window, select Recovery Database (RDB) Recovery and click Next.

The Manage RDB window appears.

3.- You can create a new RDB or select a RDB from the Recovery Database (RDB) List.

To create a new RDB, click Create.

The Create_DB window appears.

In the Create_DB window:

1. In the RDB Name field, type a name for the new RDB.
2. In the EBD File Path field, browse and select the file path location for the new RDB.
3. In the Log File Path field, browse and select the location for the log file.

Note: Backup fails if the logs path and Mailbox database path are in the same path.

Ensure that the logs path and Mailbox database path are not in the same path, even if the logs and database reside on mount point or normal path.

1. Click Create.

The new RDB is created and appears in the Recovery Database (RDB) List.

• Mount a RDB — Select a RDB from the Recovery Database (RDB) List and click Mount. Only one RDB can be mounted at a time.

Ensure that the RDB is mounted on the current node of the NMM client for successful recovery. If the database being recovered is not mounted on the current node or if replication is on, then the recovery will fail.

Ensure that the RDB is mounted before proceeding to the next step.

4.- Select the created RDB and click Next.

Exchange Server recovery options and the NetWorker recovery options and allows you to review the details before proceeding with recovery.

Note: Click Back to make changes to the recovery options that were previously selected by you.

5.- To proceed with recovery, click Start Recovery.

Let me know how it goes.

Thank you.

Carlos.

Hello,

I have the same issue after the config checker  :

NETWORK_ADAPTER_STATUS

ERROR: Network adapters which can be used for NMM backup operations, are not detected.

Check if any network adapters are [installed | media-connected | not-disabled].

Can you please tell me what you've done to solve this issue ?

Many thanks.

CatalinM

I'm having the same problem you had, what is the "default database"? DB of Networker? Of Exchange? Can you help me? Thanks in advance...Andre