This post is more than 5 years old
37 Posts
0
4333
NMM for Exchange 2010 fails after upgrade from 8.1.xx to 9.0.0.6
Hi there,
after upgrading NetWorker and NMM to V9.0.0.6 Exchange backup fails. nsrnmmsv.raw shows this errors:
This post is more than 5 years old
37 Posts
0
4333
Hi there,
after upgrading NetWorker and NMM to V9.0.0.6 Exchange backup fails. nsrnmmsv.raw shows this errors:
Top
Vakil
35 Posts
0
June 27th, 2016 16:00
Have you open a case with Support on this, this looks like a small issue, something somewhere missing.
Could you kindly paste NMM.raw for analysis. Please note NMM 9 does support only AFTD and DDBOOST as the backups are BBB (Block Based Backups).
Setup the AFTD (non-DD) for client direct using the share and remote username/password fields of the device and try your backup.
Elviz42
37 Posts
0
June 22nd, 2016 02:00
...
nsrnmmsv NSR critical Client Direct to the device is not enabled for the Client. Verify that the Data Domain is accessible via DNS or the AFTD configurations are correct.
...
We do our backup to a AFTD, JBOD, locally attached to NetWorker.
bingo.1
2.4K Posts
0
June 22nd, 2016 03:00
Then deselect the 'client direct' option in the General tab which has obviously been enabled.
Elviz42
37 Posts
0
June 22nd, 2016 08:00
I tried both: With "Client Direct" enabled and without, but same result.
bbeckers1
1 Rookie
1 Rookie
•
102 Posts
0
June 22nd, 2016 08:00
as you did not specify if you updated to NW9 version only on the client or also for the backup server nor the setup for the AFTD device and what has been defined to make client direct possible, it is difficult to a get an idea what might be the matter, but I'd guess it might have to do with the defined "device access information" of the AFTD and the client no being able to resolve that name correctly. This is a feature introduced in NW8.0, so I'm curious what you have defined as device access information or if you intended to use client direct functionality at all?
Remote client backup fails with local AFTD
NW149725
While creating a local Advanced File Type Device (AFTD) device, if you do not specify the Uniform Naming Convention (UNC) path, the AFTD device is Client Direct disabled. If you try to perform a backup to this AFTD device from a remote block based backup client, the backup fails.
Workaround
1. Right-click the AFTD device that you created.
2. Select Modify device properties.
3. Under the General tab, in the Device access information field, specify the UNC path.
The AFTD device is Client Direct enabled.
4. Perform the backup.
Elviz42
37 Posts
0
June 23rd, 2016 10:00
Hi Barry, thanx for your help :-) . I updated Server and Client to NM9 (9.0.0.6) .
I shared the backup to disk folder so that I can use UNC paths and added them to the device access information. This looks like this now:
\\ \backup2disk\
E:\backup2disk\
On the client side I switched nsrexecd service from "local System" to our backup user with Domain admin rights. I also removed all application Information that were left overs from the update. Now application Information Looks like this:
NSR_EXCH_CHECK=no
Backup command is nsrnmmsv.exe
Unfortunatly the backup still Fails with the same error.
Do you have any more suggestions?
Kind regards
Heiko
bbeckers1
1 Rookie
1 Rookie
•
102 Posts
0
June 23rd, 2016 15:00
Did you run the "system configuration checker" part of the NMM installation? See also: https://support.emc.com/kb/334399
Run "Config Checker" link or directly "C:\Program Files\EMC NetWorker\nsr\support\config checker\cfgchkui.exe". No issues/warnings reported by config checker wrg to exchange backup requirements? Always good to check.
with nw8.x and earlier one would use NMM "nsrsnap_vss_save -?" command to list which DB's would be back upped on a node. With NW9 it is "nsrnmmsv.exe -?". Does that report the DB's nicely? Are we dealing with a single exchange node here or rather a DAG setup?
Does the filesystem backup work using the same AFTD?
nw9.0.0.7 and corresponding nmm9.0.0.7 has just been released a week or so ago, so you might look into that combination possibly? But fixes stated are not always very descriptive and sometimes even broken links... see further below.
https://support.emc.com/docu66746_NetWorker_Module_for_Microsoft_9.0.0_and_Data_Protection_Add-in_for_SCVMM_9.0.0_Cumula…
ftp://ftp.legato.com/pub/NetWorker/NMM/Cumulative_Hotfixes/9.0.0/9.0.0.7
It was released on June 13, 2016.
NMM & SCVMM 9.0.0.7 Build 515
Publication Date: June 13, 2016
This package contains the following cumulative fixes:
258308 26005 Mailbox Export to PST fails if user has explicit 'Mailbox Import Export' Role assignment. Works if user is a member of Organization management Role group
258183 26206 Exchange backups fail if database is specified in the saveset list
258173 [SP] Pause Search while doing backup
257222 [Regress] NMM is crashing when we select required volumes option
257078 NMM 901 earlier builds gets installed in the setup where NMM 901 Build 540 is already installed.
256846 26051 SQL Incremental backup fails and gets promoted to FULL for a Cross domain Mirroring setup.
256836 26018 Mailbox restore does not restore 'recoverable items' aka dumpster
256024 [Config Wizard] AG and non-AG level savesets getting created in windows cluster and AG listener resources respectively.
255477 AD Scheduled backups are failed due to recent policy changes.
255361 SCVMM add in: Special character VM is not showing under recover page for recovery
254885 25779 SQL Recovery fails with "Error failed to obtained tape session" error when NMM resolves the hostname to a different canonical name than NW's canonical name (FQDN vs shortname)
253335 All special characters are not browsable in NMM gui
251723 Hyper-V CSV backup pass but NMC shows failed for some savesets
248155 Backup fails on SQL machines when client is configured with IP instead of host name
243348 NMM GLR mailbox browsing. Check the status of user during mailbox browse, to improve GUI response for deleted mailbox restore
bbeckers1
1 Rookie
1 Rookie
•
102 Posts
0
June 23rd, 2016 16:00
to report the available DB's for backup with nw9/nmm9 it is for a single node:
nsrnmmsv -P
and for a node in a DAG env:
nsrnmmsv -A NSR_FEDERATED_BACKUP=yes -A NSR_EXCH_DAG= -P
so "-P" and not with an "-?" like with the older nsrsnap_vss_save.
bbeckers1
1 Rookie
1 Rookie
•
102 Posts
0
June 23rd, 2016 17:00
but nmm9 manual also still states to be able to use:
nsrnmmsv -v -?
Elviz42
37 Posts
0
February 28th, 2017 08:00
Hi Vakil,
reconfiguring the AFTD did not work, but unmounting the volume from the old AFTD and Setting up a new AFTD to the same folder in UNC-Syntax:
Before:
AFTD Path: E:\backup2disk\1Month
After:
ATFD Path: \\SERVER\backup2disk\1Month
Client direct Path: \\SERVER\backup2disk\1Month
Remote User: \
Thanx a lot :-)