Current NMM release lists only DPM 2007 as certified (that doesn't imply it does not work per se). So there are two possibilities:
a) the error you see might be cause by certain uncompatibility caused by code change between DPM 2007 vs 2010 thus NMM does not work with it
b) the error you see is not related to DPM 2010
If you have b) in such case there is a chance by addressing the error to get this configuration working. To do that, you will need to share with us configuration details and of course the error message log.
47363:nsrsnap_vss_save: nsrpsd service is running on VTG-HH1-DPM01.VL-GLOBAL.NET.
82624:nsrsnap_vss_save:Save set name APPLICATIONS:\Microsoft DPM is valid.
63352:nsrsnap_vss_save:NMM .. start the creation of a replica. Replica will be of type Default - which is VSS determined Non Transportable.
83164:nsrsnap_vss_save:NMM .. An error was detected during the replica creation. Details in nmm.raw on VTG-HH1-DPM01.VL-GLOBAL.NET and in the Windows Application or System Event Log.
49931:nsrsnap_vss_save:RM .. 027114 ERROR:DPM Writer is stable. The error is VSS_E_WRITERERROR_NONRETRYABLE. The code is: 0x800423f4. Check the application event log for more information.
49931:nsrsnap_vss_save:RM .. 026094 ERROR:Storage Services operation CC_storageServicesInterface::executeReplication failed with an error as follows: DoSnapshotSet failed.
49931:nsrsnap_vss_save:RM .. 026084 ERROR:Storage Services operation processExecute failed with an error as follows: Storage Services has terminated with an error.
49931:nsrsnap_vss_save:RM .. 027114 ERROR:DPM Writer is stable. The error is VSS_E_WRITERERROR_NONRETRYABLE. The code is: 0x800423f4. Check the application event log for more information.
49931:nsrsnap_vss_save:RM .. 027114 ERROR:SQL Server 2008:SQLWriter is stable. The error is VSS_UNKNOWN_ERROR. The code is: 0x00000000. Check the application event log for more information.
63335:nsrsnap_vss_save:NMM backup failed to complete successfully.
WARNING: DisabledComponents value is not found. Please create and set value 0xffffffff(DWORD), which disables all IPv6 components.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Pass
FIREWALL_STATUS
Domain Profile Settings: OFF
Private Profile Settings: OFF
Public Profile Settings: OFF
---------------------------------------
Current profile: Domain, State: OFF
---------------------------------------
Firewall is not enabled.
Warning
SYSTEM_INFO
Host Name: VTG-HH1-DPM01
OS Name: Microsoft Windows Server 2008 R2 Standard
OS Version: 6.1.7601 Service Pack 1 Build 7601
OS Manufacturer: Microsoft Corporation
OS Configuration: Member Server
OS Build Type: Multiprocessor Free
Registered Owner: FII
Registered Organization: VTG AG
Product ID: 00477-001-0000421-84177
Original Install Date: 05.05.2011, 05:32:02
System Boot Time: 19.08.2011, 10:50:19
System Manufacturer: HP
System Model: ProLiant DL380 G7
System Type: x64-based PC
Processor(s): 2 Processor(s) Installed.
[01]: Intel64 Family 6 Model 44 Stepping 2 GenuineIntel ~1599 Mhz
[02]: Intel64 Family 6 Model 44 Stepping 2 GenuineIntel ~1599 Mhz
BIOS Version: HP P67, 30.01.2011
Windows Directory: C:\Windows
System Directory: C:\Windows\system32
System Volume: C: [Capacity = 72.00 GB, Free Space = 23.14 GB]
Boot Device: \Device\HarddiskVolume2
System Locale: de;German (Germany)
Input Locale: de;German (Germany)
Time Zone: (UTC+01:00) Amsterdam, Berlin, Bern, Rome, Stockholm, Vienna
Total Physical Memory: 32.768 MB
Available Physical Memory: 29.908 MB
Virtual Memory: Max Size: 65.534 MB
Virtual Memory: Available: 62.022 MB
Virtual Memory: In Use: 3.512 MB
Page File Location(s): C:\pagefile.sys
Domain: VL-GLOBAL.NET
Logon Server: \\VTG-HH1-NTS20
Hotfix(s): 38 Hotfix(s) Installed.
[01]: KB2425227
[02]: KB2476490
[03]: KB2478662
[04]: KB2484033
[05]: KB2488113
[06]: KB2492386
[07]: KB2503665
[08]: KB2505438
[09]: KB2506014
[10]: KB2506212
[11]: KB2506928
[12]: KB2507618
[13]: KB2507938
[14]: KB2508272
[15]: KB2509553
[16]: KB2510531
[17]: KB2511250
[18]: KB2511455
[19]: KB2515325
[20]: KB2518869
[21]: KB2522422
[22]: KB2524375
[23]: KB2525694
[24]: KB2529073
[25]: KB2530548
[26]: KB2533552
[27]: KB2533623
[28]: KB2534366
[29]: KB2536275
[30]: KB2536276
[31]: KB2541014
[32]: KB2544521
[33]: KB2544893
[34]: KB2545698
[35]: KB2552343
[36]: KB2555917
[37]: KB976902
[38]: KB982018
Network Card(s): 5 NIC(s) Installed.
[01]: HP NC382i DP Multifunction Gigabit Server Adapter
Connection Name: Local Area Connection
Status: Media disconnected
[02]: HP NC382i DP Multifunction Gigabit Server Adapter
Connection Name: NIC1 Team1
DHCP Enabled: Yes
DHCP Server: N/A
IP address(es)
[03]: HP NC382i DP Multifunction Gigabit Server Adapter
Connection Name: Local Area Connection 3
Status: Media disconnected
[04]: HP NC382i DP Multifunction Gigabit Server Adapter
Connection Name: NIC2 Team2
DHCP Enabled: Yes
DHCP Server: N/A
IP address(es)
[05]: HP Network Teaming Virtual Miniport Driver
Connection Name: TEAM Adapter
DHCP Enabled: No
IP address(es)
[01]: 192.168.254.245
*** Current system locale of this machine appears to be Non-English(de;German (Germany)). ***
-----------------------------
See the notes below...
While installing NMM, specify [en-us (English)] character installation path. Non english installation paths are not supported.
Info
CLUSTER_ROLE_STATUS
Cluster service role state : The Cluster service role is not installed on the node.
Info
MULTI_PATH_IO_CHECK
Microsoft Multipath I/O (MPIO) is not enabled on this machine.
Pass
VSS_SERVICE_STATUS
The Volume Shadow Copy service (VSS) is in the "Running" state and set to "Manual" configuration mode.
Info
VSS_WRITER_LIST
Writer name: Task Scheduler Writer is in State: [1] Stable
Writer name: VSS Metadata Store Writer is in State: [1] Stable
Writer name: Performance Counters Writer is in State: [1] Stable
Writer name: DPM Writer is in State: [1] Stable
Writer name: System Writer is in State: [1] Stable
Writer name: SqlServerWriter is in State: [1] Stable
Writer name: ASR Writer is in State: [1] Stable
Writer name: Registry Writer is in State: [1] Stable
Writer name: Shadow Copy Optimization Writer is in State: [1] Stable
Writer name: COM+ REGDB Writer is in State: [1] Stable
Writer name: WMI Writer is in State: [1] Stable
Info
VSS_PROVIDER_LIST
Provider name: Microsoft Software Shadow Copy provider 1.0 of Provider type: System, Version: 1.0.0.7 is available.
Warning
VSS_SHADOWSTORAGE_CHECK
For volume:
.
Used shadow space : 81.775 GB (64%)
Allocated shadow space : 83.528 GB (65%)
Maximum shadow space : UNBOUNDED (100%)
-> Maximum shadow space is set to UNBOUNDED.
Free space available to be used for Shadow Storage on volume
, Shadow Copy Storage volume is:
is 23.141 GB (Out of maximum volume size of 72.000 GB)
Percentage shadow free space available: 51.50%
For volume:
.
Used shadow space : 44.307 GB (21%)
Allocated shadow space : 46.524 GB (22%)
Maximum shadow space : UNBOUNDED (100%)
-> Maximum shadow space is set to UNBOUNDED.
Free space available to be used for Shadow Storage on volume
, Shadow Copy Storage volume is:
is 23.141 GB (Out of maximum volume size of 72.000 GB)
Percentage shadow free space available: 62.80%
For volume:
.
Used shadow space : 15.312 GB (3%)
Allocated shadow space : 17.787 GB (3%)
Maximum shadow space : UNBOUNDED (-543968109%)
-> Maximum shadow space is set to UNBOUNDED.
Free space available to be used for Shadow Storage on volume
, Shadow Copy Storage volume is:
is 23.141 GB (Out of maximum volume size of 72.000 GB)
Percentage shadow free space available: 95.06%
For volume:
.
Used shadow space : 2.016 MB (0%)
Allocated shadow space : 609.766 MB (37%)
Maximum shadow space : UNBOUNDED (100%)
-> Maximum shadow space is set to UNBOUNDED.
Free space available to be used for Shadow Storage on volume
, Shadow Copy Storage volume is:
is 23.141 GB (Out of maximum volume size of 72.000 GB)
Percentage shadow free space available: 93.33%
For volume:
.
Used shadow space : 642.125 MB (6%)
Allocated shadow space : 1.22 GB (11%)
Maximum shadow space : UNBOUNDED (100%)
-> Maximum shadow space is set to UNBOUNDED.
Free space available to be used for Shadow Storage on volume
, Shadow Copy Storage volume is:
is 23696.559 MB (Out of maximum volume size of 73727.996 MB)
New volumes are not mounted automatically when added to the system. To mount a
volume, you must create a volume mount point.
Info
SERVER_ROLES_FEATURES
The following roles and features are enabled on this machine:
----- Roles -----
File Services [File-Services]
File Server [FS-FileServer]
----- Features -----
.NET Framework 3.5.1 Features [NET-Framework]
.NET Framework 3.5.1 [NET-Framework-Core]
SNMP Services [SNMP-Services]
SNMP Service [SNMP-Service]
SNMP WMI Provider [SNMP-WMI-Provider]
Windows Server Backup Features [Backup-Features]
Windows Server Backup [Backup]
Command-line Tools [Backup-Tools]
Checking NMM Software Components... [POST INSTALL MODE = NMM version choosen to check against is equal or lesser than the NMM version already installed]
Pass
NMM_INSTALL_CHECK
Product: NetWorker Module for Microsoft Applications, Version: 2.3 is installed.
Pass
POWERSNAP_INSTALL_CHECK
Product: PowerSnap, Version: 2.5.1 is installed.
Pass
RMAGENT_INSTALL_CHECK
Product: RMAgentPS, Version: 5.3.0.1 is installed.
Pass
NSRPSD_SERVICE_STATUS
The NetWorker PowerSnap Service service (nsrpsd) is in the "Running" state and set to "Auto" configuration mode.
Pass
RMAGENTPS_SERVICE_STATUS
The Replication Manager Client for RMAgentPS service (RMAgentPS) is in the "Running" state and set to "Auto" configuration mode.
Pass
NETWORKER_INSTALL_CHECK
Product: NetWorker (Client), Version: 7.6.1 is installed.
Pass
NSREXECD_SERVICE_STATUS
The NetWorker Remote Exec Service service (nsrexecd) is in the "Running" state and set to "Auto" configuration mode.
Application Host Configuration items you should check manually...
Manual
NETWORKER_SOFTWARE
NetWorker Software Checklist
-> NMM 2.3 can be installed on NetWorker Client or Storage Node : version
* 7.5.3 and later
* 7.6.1 and later
-> For DataDomain Support :
* Server version 7.6.1 and later with NMM 2.3 installed on NetWorker Client or Storage Node version 7.6.1 and later
-> For Offline System State Restore Support :
* Server version 7.6.2 and later with NMM 2.3 installed on NetWorker Client or Storage Node version 7.6.2 and later
Bottom line : NetWorker Server and storage node version 7.6.2 and later will support all features
Manual
NETWORKER_LICENSES
NetWorker Licenses
-> NMM Client License
-> NW Client License
Manual
NETWORKER_DSN_IN_CLUSTER_CONFIGURATIONS
** Dedicated Storage Node(DSN) configuration on Cluster **
For Microsoft SQL:
-> On the NetWorker server, create one DSN using Active node name.[say rd=joy-flora.joy.com:c:\dev]
-> Create another DSN using passive node name [say rd=joy-fauna.joy.com:c:\dev]
-> In the Virtual SQL NetWorker client resource, select Globals (2 of 2) > Storage Node column, specify "curphyhost" (with out quotes)
-> Make sure you have a local device in the configured storage pool for bootstrap and index backups.
For Exchange 2007 CCR:
-> Configure CCR setup with two mailbox servers.
-> Create two nodes, for example Node1 and Node2, and virtual client resources by using NMC.
-> Create a DSN device for Node1. e.g.: rd=Node1[FQDN]:C:\Device1
-> Create a DSN device for Node2. e.g.: rd=Node2[FQDN]:C:\Device2
-> Under Node1 client properties, select Globals (2 of 2) > Storage Node column, specify "Node1" (with out quotes).
-> Under Node2 client properties, select Globals (2 of 2) > Storage Node column, specify "Node2" (with out quotes).
-> Now under virtual client properties, select Globals (2 of 2) > Storage Node column, specify "curphyhost" (with out quotes).
-> Make sure you have a local device in the configured storage pool for bootstrap and index backups.
Manual
BACKUP_PRODUCT_CHECK
Check if any other backup product installed on same machine
-> If Microsoft DPM 2007 SP1 software is installed, there is no user action required.
Manual
BITLOCKER_ENC_SUPPORT
Bitlocker encryption is not supported.
Manual
NW_GROUP_INACTIVITY
NetWorker Group inactivity timeout should be set to 0.
Manual
SW_HW_BACKUPS_SUPPORT
Mixing Software and H/W provider will cause backups to fail.
Manual
UNSUPPORTED_CHARACTERS_IN_SAVESETS
NMM savesets containing one or more special characters from the list below are not supported.
<
>
$
'
"
&
/
\
Note: The backups will fail if any of the specified special characters are present in the savesets.
Manual
INSTALL_PATH_LANG
NMM supports English only installation paths. Do not install NMM in non-english directory path.
Manual
MSDTC_SERVICE_DEPENDENCIES
Microsoft Distributed Transaction Coordinator Service Dependencies for cluster setups
-> For EMC Hardware VSS backups, EMC Solution Enabler(SE) Installation requires MSDTC service to be running on the cluster node.
There is no support for DPM 2010 in the NMM 2.3 release and there are no current plans to add support in 2011 or 2012. The Microsoft DPM team has confirmed there are significant changes in DPM 2010 and existing data protection products that support DPM 2007 will not work with DPM 2010.
The number of NetWorker customers using NMM to backup DPM 2007 is small and there are enough higher priority projects to justify deferring support for DPM 2010.
There are currently no workarounds available.
So, EMC products cannot be used to backup or restore DPM 2010 server.
ble1
4 Operator
•
14.4K Posts
0
August 18th, 2011 13:00
Current NMM release lists only DPM 2007 as certified (that doesn't imply it does not work per se). So there are two possibilities:
a) the error you see might be cause by certain uncompatibility caused by code change between DPM 2007 vs 2010 thus NMM does not work with it
b) the error you see is not related to DPM 2010
If you have b) in such case there is a chance by addressing the error to get this configuration working. To do that, you will need to share with us configuration details and of course the error message log.
36115_carloscor
217 Posts
0
August 19th, 2011 00:00
Hello Andreas,
It is true that NMM 2.3 doesn't officially support DPM 2010, however I've been doing tests in my lab and for me worked perfectly.
As Hrvoje said please share with us some more information such as error messages, configuration etc, so we can look into it.
As usual, my first recommendation if to run NMM Config Checker and check out the results.
Thank you.
Carlos.
andreasschulz1
1 Rookie
•
11 Posts
0
August 19th, 2011 02:00
for the first, I would thank for your support !
folowing savesets ran sucessfully D:\, SYSTEM COMPONENTS, APPLICATIONS: SqlServerWriter
But when I try APPLICATIONS:\Microsoft DPM the backup failed, but the backup job will not end !
-----------------------------------------------------------------------------------------------------
47363:nsrsnap_vss_save: nsrpsd service is running on VTG-HH1-DPM01.VL-GLOBAL.NET.
82624:nsrsnap_vss_save:Save set name APPLICATIONS:\Microsoft DPM is valid.
63352:nsrsnap_vss_save:NMM .. start the creation of a replica. Replica will be of type Default - which is VSS determined Non Transportable.
83164:nsrsnap_vss_save:NMM .. An error was detected during the replica creation. Details in nmm.raw on VTG-HH1-DPM01.VL-GLOBAL.NET and in the Windows Application or System Event Log.
49931:nsrsnap_vss_save:RM .. 027114 ERROR:DPM Writer is stable. The error is VSS_E_WRITERERROR_NONRETRYABLE. The code is: 0x800423f4. Check the application event log for more information.
49931:nsrsnap_vss_save:RM .. 026094 ERROR:Storage Services operation CC_storageServicesInterface::executeReplication failed with an error as follows: DoSnapshotSet failed.
49931:nsrsnap_vss_save:RM .. 026084 ERROR:Storage Services operation processExecute failed with an error as follows: Storage Services has terminated with an error.
49931:nsrsnap_vss_save:RM .. 027114 ERROR:DPM Writer is stable. The error is VSS_E_WRITERERROR_NONRETRYABLE. The code is: 0x800423f4. Check the application event log for more information.
49931:nsrsnap_vss_save:RM .. 027114 ERROR:SQL Server 2008:SQLWriter is stable. The error is VSS_UNKNOWN_ERROR. The code is: 0x00000000. Check the application event log for more information.
63335:nsrsnap_vss_save:NMM backup failed to complete successfully.
nsrsnap_vss_save: APPLICATIONS:\Microsoft DPM: failed
68151 1313738007 2 0 0 7232 4916 0 vtg-hh1-dpm01.vl-global.net nsrsnap_vss_save 39 nsrsnap_vss_save: Exiting with failure. 0
APPLICATIONS:\Microsoft DPM: Backup of [APPLICATIONS:\Microsoft DPM] failed
-----------------------------------------------------------------------------------------------------------------
the configuration is simple:
Backup Server NetWorker 7.6.1.1.Build.422 Power Edition/102
Networker Client 7.6.1.7 NMM 2.3.0.79
DPM 2010 internal SQL DB on W2k8R2
Application Settingf
NSR_SNAP_TYPE=vss
NSR_PS_SINGLE_SAVE_PER_SAVESET=yes
NSR_PS_FIRST_SAVESET_SAVE=APPLICATIONS:\Microsoft DPM\DPM Database
NSR_DPM_RETRY_WAIT=5
NSR_DPM_RETRY_MAXIMUM=3
EMC Config Checker
36115_carloscor
217 Posts
0
August 19th, 2011 03:00
Hi Andreas,
These would me my suggestions:
Set the following save sets:
APPLICATIONS:\Microsoft DPM
APPLICATIONS:\SqlServerWriter
C:\
SYSTEM COMPONENTS:\
Remove any Application Information variables and leave only this one (for testing purposes):
NSR_SNAP_TYPE=vss
Do you have VSS provider other than VSS (Microsoft's)? Check it by running
vssadmin list providers
Based on the output of NMM Config Checker I would say that all writers are stable, so no need to check that one.
Please ensure that the group has the following values set to "0":
Inactivity time out
Client retires
Savegrp paralellism.
Also check the VSS (Shadow Copy) configuration:
andreasschulz1
1 Rookie
•
11 Posts
0
August 19th, 2011 06:00
Hello Carlos,
When I omitted this parameter or set this to no, failed the backup shortly
NSR_PS_SINGLE_SAVE_PER_SAVESET=yes
It looks like that way that the regutry keys for debugging vss doesen't work on w2k8r2
I will try vsstrace tool
Thanks
Best Regards
Andreas
andreasschulz1
1 Rookie
•
11 Posts
0
August 22nd, 2011 04:00
Hello Carlos,
The answer from product management of EMC:
There is no support for DPM 2010 in the NMM 2.3 release and there are no current plans to add support in 2011 or 2012. The Microsoft DPM team has confirmed there are significant changes in DPM 2010 and existing data protection products that support DPM 2007 will not work with DPM 2010.
The number of NetWorker customers using NMM to backup DPM 2007 is small and there are enough higher priority projects to justify deferring support for DPM 2010.
There are currently no workarounds available.
So, EMC products cannot be used to backup or restore DPM 2010 server.
Thanks alot for your help
Best Regards
Andreas