Solved!
Go to SolutionL
Lars_Stottmeist
9 Posts
0
10745
January 27th, 2014 07:00
NMM 3.0 and Exchange 2010 (DAG)
Hi all,
I'm struffling a bit to implement Exchange 2010 backup.
NMM3.0, NW8.1 client (win2k8r2), Server: NW 7.6.5.7
What I have is a DAG Exchange 2010 environment:
Node1:
C:\Users\BackupInst>nsrsnap_vss_save.exe -v -?
NMM .. changing backup name xxxMM3-SIR to primary name xxxmm3-sir.corpxxxxx.local for multi NIC client.
List of valid saveset entries for APPLICATIONS on client xxxmm3-sir.corpxxxxx.local ...
Initializing data to display...
NMM ... Using client name XXXEMM3-SIR, the version of the Exchange server is Exchange 2010.
96585:nsrsnap_vss_save:NMM .. Initialization success -- Exchange shell successfu
lly initialized. Required for Exchange 2010 or Exchange 2013.
96585:nsrsnap_vss_save:NMM .. Initialization success -- Exchange shell successfu
lly initialized. Required for Exchange 2010 or Exchange 2013.
"APPLICATIONS:\Microsoft Exchange 2010"
"APPLICATIONS:\Microsoft Exchange 2010\DAG100_MBDB00002 -- Passive"
"APPLICATIONS:\Microsoft Exchange 2010\DAG100_MBDB00004 -- Passive"
"APPLICATIONS:\Microsoft Exchange 2010\DAG100_MBDB00006 -- Passive"
"APPLICATIONS:\Microsoft Exchange 2010\DAG100_PUBDB03 -- Standalone"
"APPLICATIONS:\Microsoft Exchange 2010\DAG100_MBDB00003 -- Active"
"APPLICATIONS:\Microsoft Exchange 2010\DAG100_MBDB00005 -- Active"
"APPLICATIONS:\Microsoft Exchange 2010\DAG100_MBDB00001 -- Active"
68150:nsrsnap_vss_save:nsrsnap_vss_save: Exiting with success.
Node 2:
C:\Users\BackupInst>nsrsnap_vss_save.exe -v -?
NMM .. changing backup name XXXMM4-SIR to primary name xxxmm4-sir.xxx.
local for multi NIC client.
List of valid saveset entries for APPLICATIONS on client xxxmm4-sir.corpxxx.local ...
Initializing data to display...
NMM ... Using client name XXXMM4-SIR, the version of the Exchange server is Exchange 2010.
96585:nsrsnap_vss_save:NMM .. Initialization success -- Exchange shell successfu
lly initialized. Required for Exchange 2010 or Exchange 2013.
96585:nsrsnap_vss_save:NMM .. Initialization success -- Exchange shell successfu
lly initialized. Required for Exchange 2010 or Exchange 2013.
"APPLICATIONS:\Microsoft Exchange 2010"
"APPLICATIONS:\Microsoft Exchange 2010\DAG100_MBDB00001 -- Passive"
"APPLICATIONS:\Microsoft Exchange 2010\DAG100_MBDB00003 -- Passive"
"APPLICATIONS:\Microsoft Exchange 2010\DAG100_MBDB00005 -- Passive"
"APPLICATIONS:\Microsoft Exchange 2010\DAG100_MBDB00006 -- Active"
"APPLICATIONS:\Microsoft Exchange 2010\DAG100_MBDB00002 -- Active"
"APPLICATIONS:\Microsoft Exchange 2010\DAG100_PUBDB04 -- Standalone"
"APPLICATIONS:\Microsoft Exchange 2010\DAG100_MBDB00004 -- Active"
68150:nsrsnap_vss_save:nsrsnap_vss_save: Exiting with success.
I want to backup the passive Databases.
I created 3 clients:
1. XXXMMDAG100.corpxxx.local (deactivated dummy client):
NSR_SNAP_TYPE=vss
NSR_ALT_PATH=F:\mount_dir
2. xxxMM3-SIR:
NSR_SNAP_TYPE=vss
NSR_EXCH2010_DAG=XXXMMDAG100.corpxxx.local
NSR_ALT_PATH=F:\mount_dir
NSR_EXCH2010_BACKUP=passive
NSR_EXCH_CHECK=no
NSR_CHECK_JET_ERRORS=no
3. xxxMM4-SIR:
same as node 1
SaveSet for all is: APPLICATIONS:\Microsoft Exchange 2010
Group settings:
Snapshot=enabled
Snapshot Policy is set
Snapshot Pool is set
Error Msg:
...
NMM .. Starting Backup. This operation may take a long time depending on the size of the data requested.
82296:nsrsnap_vss_save:NMM .. Operation unit failed with error 'Backup failed while creating coversave. Failed to fetch cover save record before proceeding. saveset name = APPLICATIONS:\Microsoft Exchange 2010 savetime = Mon Jan 27 15:51:02 2014 . Please make sure you have configured at least one NetWorker Device and client resources are configured for the application host[xxxmmDAG100.corpxxx.local] and the proxy client[xxxmm4-sir.corpxxx.local] on NetWorker Server [7.101.2.10]'.Possible cause: 1)Unsupported file system or 2)write-protected disc or 3)No space on disc or 4)Drive not found
NMM .. Error backing up one or more of the file system savesets: NMM .. Operation unit failed with error Backup failed while creating coversave. Failed to fetch cover save record before proceeding. saveset name = APPLICATIONS:\Microsoft Exchange 2010 savetime = Mon Jan 27 15:51:02 2014 . Please make sure you have configured at least one NetWorker Device and client resources are configured for the application host[xxxmmDAG100.corpxxx.local] and the proxy client[xxxmm4-sir.corpxxx.local] on NetWorker Server [7.101.2.10].
64038:nsrsnap_vss_save:NMM .. Error creating NetWorker backup of snapshot: NMM .. Operation unit failed with error Backup failed while creating coversave. Failed to fetch cover save record before proceeding. saveset name = APPLICATIONS:\Microsoft Exchange 2010 savetime = Mon Jan 27 15:51:02 2014 . Please make sure you have configured at least one NetWorker Device and client resources are configured for the application host[xxxmmDAG100.corpxxx.local] and the proxy client[xxxmm4-sir.corpxxx.local] on NetWorker Server [7.101.2.10].
63372:nsrsnap_vss_save:NMM .. Registration of snapshot set failed -- NMM .. Operation unit failed with error Backup failed while creating coversave. Failed to fetch cover save record before proceeding. saveset name = APPLICATIONS:\Microsoft Exchange 2010 savetime = Mon Jan 27 15:51:02 2014 . Please make sure you have configured at least one NetWorker Device and client resources are configured for the application host[xxxmmDAG100.corpxxx.local] and the proxy client[xxxmm4-sir.corpxxx.local] on NetWorker Server [7.101.2.10]
76960:nsrsnap_vss_save:NMM .. error caught calling RM to commit the replica.
49931:nsrsnap_vss_save:RM .. 027114 ERROR:Exchange Replication Service is stable. The error is VSS_E_WRITERERROR_RETRYABLE. The code is: 0x800423f3. Check the application event log for more information.
49931:nsrsnap_vss_save:RM .. 027114 ERROR:Exchange Replication Service is stable. The error is VSS_E_WRITERERROR_RETRYABLE. The code is: 0x800423f3. Check the application event log for more information.
49931:nsrsnap_vss_save:RM .. 027114 ERROR:Exchange Replication Service is stable. The error is VSS_E_WRITERERROR_RETRYABLE. The code is: 0x800423f3. Check the application event log for more information.
49931:nsrsnap_vss_save:RM .. 024168 ERROR:The VSS shadow copy for Exchange Replication Service was not successful because of an error that occurred earlier.
83394:nsrsnap_vss_save:NMM .. cluster failover or application role change after a replica created may have caused snapshot creation failure, try to restart the backup.
Microsoft DiskPart version 6.1.7601
Copyright (C) 1999-2008 Microsoft Corporation.
On computer: xxxmm4-SIR
Automatic mounting of new volumes enabled.
37959:nsrsnap_vss_save:The group or resource is not in the correct state to perform the requested operation.
.
63335:nsrsnap_vss_save:NMM backup failed to complete successfully.
Internal error.
68151 1390834517 2 0 0 4768 16580 0 xxxmm4-sir.corpxxx.local nsrsnap_vss_save NSR warning 39 nsrsnap_vss_save: Exiting with failure. 0
APPLICATIONS:\Microsoft Exchange 2010: Backup of [APPLICATIONS:\Microsoft Exchange 2010] failed
Any ideas what I missed out here?
CarlosRojas
1 Rookie
•
1693 Posts
2849
0
Posted January 27th, 2014 08:00
Hi Lars,
Regardless of the new IP for the DAG, you need to address the name resolution issue, as otherwise backup will never work.
You can first try by using hosts file in server and clients to make sure IP can resolve backup server name and backup server can resolve physical nodes and DAG.
My advise though is to use DNS and configure forward and reverse lookup.
Thank you,
Carlos
Lars_Stottmeist
9 Posts
2849
0
Posted January 27th, 2014 08:00
Hi Carlos,
thanks for your response.
The servers file is empty.
The ip you mentionend belongs to the backupserver.
Do I need a dedicated ip address for the client that is named like the DAG FQDN?
At the moment I added the DAG FQDN to node1 in /etc/hosts on the backupserver.
Both nodes have only one ip address to use for backup at the moment.
We have no DNS in our backup lan. So any client name must exist in backupservers hosts file:
7.x.x.x xxxmm3-sirbk XXXMMDAG100.corpxxx.local
Thanks for any hints.
Lars
CarlosRojas
1 Rookie
•
1693 Posts
2849
0
Posted January 27th, 2014 08:00
Hi Lars,
I'm first looking at where the IP 7.101.2.10 comes from?
Please checlk the servers file in the /nsr/res folder of the client and let us know what is in there.
If anything please stop NW services on the client, comment any entries in that file, rename/delete /nsr/tmpo in the client and try again.
This message usually indicates a wrong configuration of the pool, no devices available for the pool selected or a name resolution or wrong configuration.
Thank you,
Carlos
Lars_Stottmeist
9 Posts
2849
0
Posted January 27th, 2014 08:00
Backupserver and client alias is configured properly in hosts file of the client.
Filesystem backup works and exchange backups stores some savesets on the server before it fails.
Nslookup does not work for backupserver name or ip.
But ping to backupserver name or ip is OK:
C:\Users\BackupInst>nslookup 7.101.2.10
Server: xxxmd3-sir.corpxxx.local
Address: 10.xx.xx.xxDNS request timed out.
timeout was 2 seconds.
*** Request to xxxmd3-sir.corpxxx.local timed-outC:\Users\BackupInst>nslookup qxxx01
Server: xxxmd3-sir.corpxxx.local
Address: 10.xx.xx.xx*** xxxmd3-sir.corpxxx.local can't find qxxx01: Non-existent domainC:\Users\BackupInst>ping 7.101.2.10
Pinging 7.101.2.10 with 32 bytes of data:
Reply from 7.101.2.10: bytes=32 time<1ms TTL=254
Reply from 7.101.2.10: bytes=32 time<1ms TTL=254
Reply from 7.101.2.10: bytes=32 time<1ms TTL=254Ping statistics for 7.101.2.10:
Packets: Sent = 3, Received = 3, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0msC:\Users\BackupInst>ping qxxx01
Pinging qxxx01 [7.101.2.10] with 32 bytes of data:
Reply from 7.101.2.10: bytes=32 time<1ms TTL=254
Reply from 7.101.2.10: bytes=32 time<1ms TTL=254
Reply from 7.101.2.10: bytes=32 time<1ms TTL=254
Reply from 7.101.2.10: bytes=32 time<1ms TTL=254Ping statistics for 7.101.2.10:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0msI will ask for a dedicated ip address.
Regards
Lars
... and besides all Carlos mentioned already two things come to my mind in Exchange environment:
a) all NetWorker client resources have to be created using the FQDN. Make sure this is true.
Otherwise the results (meaning errors) are not predictable.
b) the mount point (here: NSR_ALT_PATH=F:\mount_dir) should not be located on any volume keeping Exchange databases or log files.
Otherwise it might block snapshot creation even option "NSR_EXCH_CHECK=no" is used.
There is absolutely no real reason not to locate this on drive C: for this folder is used for temporary snapshot mounting only and not real data is stored there; except a few small temporary files. Using drive C: you are always on the save side.
Lars_Stottmeist
9 Posts
2849
0
Posted February 4th, 2014 05:00
Thank you both for the useful hints.
With a dedicated ip backuplan address for the dag and fqdn as client names the backup is working fine now.
Now I have trouble with the restore.
Monitor.xml shows:
...
***** Error Detected during validaiton of file 'R:\RDB\_restoredLogs\E00000002F0.log', error '2'. Will try recovering from this error.
***** Error Detected during validaiton of file 'R:\RDB\_restoredLogs\E00000002F1.log', error '2'. Will try recovering from this error.
***** Error Detected during validaiton of file 'R:\RDB\_restoredLogs\E00000002F2.log', error '2'. Will try recovering from this error.
...
nmm.raw shows the same.
nwsnap.raw:
...
NSR warning Duplicate entry for /M:\DAG100_MBDB00003_DB/DAG100_MBDB00002_LOG @ 1/1/1970 1:00:00 AM
NSR warning Duplicate entry for /M:\DAG100_MBDB00003_DB/DAG100_MBDB00002_LOG @ 1/1/1970 1:00:00 AM
NSR warning Duplicate entry for /M:\DAG100_MBDB00003_DB/DAG100_MBDB00002_LOG @ 1/1/1970 1:00:00 AM
...
NSR info Didn't recover requested file R:\RDB_MM4_3\_restoredLogs\E00000002F0.log
NSR info Didn't recover requested file R:\RDB_MM4_3\_restoredLogs\E00000002F1.log
NSR warning Could not send indication to jobd.
JOBS critical Too many indications attempted - discarding one
NSR info Didn't recover requested file R:\RDB_MM4_3\_restoredLogs\E00000002F2.log
NSR warning Could not send indication to jobd.
JOBS critical Too many indications attempted - discarding one
...
Any ideas about this?
Thank you,
Lars
CarlosRojas
1 Rookie
•
1693 Posts
2849
0
Posted February 7th, 2014 03:00
Hi Lars,
I would rather mark this post as answered and raise a new one for the restore, but anyway, can you please let us know the restore procedure you are carrying out, and also provide some more info, such as the monitor output (from NMM GUI9 and NMM logs?
Thank you,
Carlos
CarlosRojas
1 Rookie
•
1693 Posts
2849
0
Posted January 27th, 2014 08:00
Hi Lars,
Yes, DAG should have it's own IP, in fact I believe that is also required for Exchange DAG to be configured properly, same as any other cluster.
What I meant is why there is an IP and not a name in the error message, so error message should be something like:
Please make sure you have configured at least one NetWorker Device and client resources are configured for the application host[xxxmmDAG100.corpxxx.local] and the proxy client[xxxmm4-sir.corpxxx.local] on NetWorker Server [xxxmmNetWorjer_Server.corpxxx.local]. instead of the IP of the NW server.
Is name resolution working fine for forward and reverse lookups?
Also it0's failing to fetch the coverset, so I would work on the name resolution before looking into anything else.
Thank you,
Carlos