Unsolved
This post is more than 5 years old
16 Posts
0
3758
July 24th, 2012 11:00
Exchange 2010 DAG, NMM 2.3, active DB backup works, passive backup fails
Hi folks,
We just stood up a new 2010 environment and I've had a few issues setting up NetWorkler (7.6.3) to back it up, and I think I'm nearly there. I'd like to back up the passive DB copies as our environment, while relatively small, handles a tremendous amount of email. So like the description says, when I set NSR_EXCH2010_BACKUP to active, the backup completes fine. When I set it to passive, it fails.
Here is the Application information (same for both nodes of the DAG):
NSR_SNAP_TYPE=vss
NSR_EXCH2010_DAG=DAG1.00000.com (edited)
NSR_EXCH2010_BACKUP=active
NSR_EXCH_RETAIN_SNAPSHOTS=yes
NSR_ALT_PATH=C:\vss_backup
And here is the error I get after the passive backup:
1 retry attempted
52051:nsrsnap:Printing savecmd=nsrsnap_vss_save.exe after parsing 79549:nsrsnap:[nsrsnap.c 1891] Invoking command: "nsrsnap_vss_save.exe -A optype=conventional -A "NSR_SNAP_TYPE=vss" -A "NSR_EXCH2010_DAG=DAG1.00000.com" -A "NSR_EXCH2010_BACKUP=passive" -A "NSR_EXCH_RETAIN_SNAPSHOTS=yes" -A "NSR_ALT_PATH=C:\vss_backup" -A "NSR_CHECK_JET_ERRORS=all" -A NSR_PARENT_JOBID=225295 -b Exchange -c bevexmb02.00000.com -f "C:\Program Files\Legato\nsr\tmp\sd000001" -g "Exchange" -LL -m bevexmb02.00000.com -s bevbackup01.elizacorp.com -t 1343150643 -l incr -q -W 78 -A snap_sessionid=1343152123 -A NSR_STRICT_SYNC=0 "APPLICATIONS:\Microsoft Exchange 2010 73064:nsrsnap_vss_save:Version information for C:\Program Files\Legato\nsr\bin\nsrsnap_vss_save.exe:
Original file name: nsrsnap_vss_save.exe
Version: 2.3.0.87
Comments: NetWorker Module for Microsoft Applications (x64)
50423:nsrsnap_vss_save:nsrsnap_vss_save: Unknown Application Information parameter: NSRSNAP_JOBID, may not be supported
50411:nsrsnap_vss_save:nsrsnap_vss_save: Data mover host name not specified. Assuming local host: bevexmb02.00000.com 80271:nsrsnap_vss_save:NMM .. Valid snapshot policy. Group: "Exchange" Snapshot Policy: "Serverless Backup" Snapshots Per Day: "1" Retain: "0" Backup Snapshots: "All" Level: "incr".
47363:nsrsnap_vss_save: nsrpsd service is running on BEVEXMB02.00000.com.
NMM ... Using client name BEVEXMB02, the version of the Exchange server is Exchange 2010.
82624:nsrsnap_vss_save:Save set name APPLICATIONS:\Microsoft Exchange 2010 is valid.
63335:nsrsnap_vss_save:NMM backup failed to complete successfully.
Internal error.
68151 1343152150 2 0 0 936 3576 0 bevexmb02.00000.com nsrsnap_vss_save 39 nsrsnap_vss_save: Exiting with failure. 0
* bevexmb02.00000.com APPLICATIONS:\Microsoft Exchange 2010: Backup of [APPLICATIONS:\Microsoft Exchange 2010] failed
I find it interesting that the node that is failing is the one that contains the active copies of the Exchange databases. Anyone have any idea or seen this before? Please note that I've edited out our domain information, so 00000.com is not what is actually appearing in these emails.
imasock
16 Posts
0
July 24th, 2012 12:00
Ok so I've done a little more digging and this is in my nmm.raw after a passive backup failure:
52705 7/24/2012 3:35:57 PM 1 0 0 5336 6056 0 bevexmb02.00000.com nsrsnap_vss_save Computer Name: BEVEXMB02 User Name: NT AUTHORITY\SYSTEM (SYSTEM)
73064 7/24/2012 3:35:57 PM 1 0 0 5336 6056 0 bevexmb02.00000.com nsrsnap_vss_save Version information for C:\Program Files\Legato\nsr\bin\nsrsnap_vss_save.exe:\n Original file name: nsrsnap_vss_save.exe\n Version: 2.3.0.87\n Comments: NetWorker Module for Microsoft Applications (x64)
50391 7/24/2012 3:35:57 PM 0 0 0 5336 6056 0 bevexmb02.00000.com nsrsnap_vss_save nsrsnap_vss_save: Setting directives file path to C:\Program Files\Legato\nsr\tmp\sd000001
52681 7/24/2012 3:35:57 PM 1 0 0 5336 6056 0 bevexmb02.00000.com nsrsnap_vss_save NetWorker Server Version: NetWorker 7.6.3.0.Build.840 NetWorker Source Capacity Data Zone Enabler
50423 7/24/2012 3:35:57 PM 0 0 0 5336 6056 0 bevexmb02.00000.com nsrsnap_vss_save nsrsnap_vss_save: Unknown Application Information parameter: NSRSNAP_JOBID, may not be supported
50411 7/24/2012 3:35:57 PM 0 0 0 5336 6056 0 bevexmb02.00000.com nsrsnap_vss_save nsrsnap_vss_save: Data mover host name not specified. Assuming local host: bevexmb02.00000.com
50402 7/24/2012 3:35:57 PM 0 0 0 5336 6056 0 bevexmb02.00000.com nsrsnap_vss_save nsrsnap_vss_save: Inserting APPLICATIONS:\Microsoft Exchange 2010 in saveset list
80271 7/24/2012 3:35:58 PM 0 0 0 5336 6056 0 bevexmb02.00000.com nsrsnap_vss_save NMM .. Valid snapshot policy. Group: "Exchange" Snapshot Policy: "Serverless Backup" Snapshots Per Day: "1" Retain: "0" Backup Snapshots: "All" Level: "incr".
64712 7/24/2012 3:35:59 PM 1 0 0 5336 6056 0 bevexmb02.00000.com nsrsnap_vss_save NMM .. RMAPI version: 5.3.0.1
80745 7/24/2012 3:36:13 PM 1 0 0 5336 6056 0 bevexmb02.00000.com nsrsnap_vss_save NMM ... Using client name BEVEXMB02, the version of the Exchange server is Exchange 2010.
81250 7/24/2012 3:36:14 PM 0 0 0 5336 6056 0 bevexmb02.00000.com nsrsnap_vss_save NMM .. failed to retrieve writers - will pLromote the saveset to FUL.
71641 7/24/2012 3:36:14 PM 0 0 0 5336 6056 0 bevexmb02.00000.com nsrsnap_vss_save NMM .. No previous Full backup for all components in saveset APPLICATIONS:\Microsoft Exchange 2010 for client exist. Promoting this saveset to FULL.
82624 7/24/2012 3:36:14 PM 0 0 0 5336 6056 0 bevexmb02.00000.com nsrsnap_vss_save Save set name APPLICATIONS:\Microsoft Exchange 2010 is valid.
81233 7/24/2012 3:36:14 PM 1 0 0 5336 6056 0 bevexmb02.00000.com nsrsnap_vss_save NMM .. The database state for saveset Microsoft Exchange 2010 doesn't match the NSR_EXCH2010_BACKUP value PASSIVE and will not be backed up.
63310 7/24/2012 3:36:14 PM 1 0 0 5336 6056 0 bevexmb02.00000.com nsrsnap_vss_save NMM .. There are no saveset objects to add to the replica.
63335 7/24/2012 3:36:14 PM 5 0 0 5336 6056 0 bevexmb02.00000.com nsrsnap_vss_save NMM backup failed to complete successfully.
50404 7/24/2012 3:36:14 PM 0 0 0 5336 6056 0 bevexmb02.00000.com nsrsnap_vss_save nsrsnap_vss_save: createInstanceBackup() failed
0 7/24/2012 3:36:14 PM 2 0 0 5336 6056 0 bevexmb02.00000.com nsrsnap_vss_save nsrsnap_vss_save: APPLICATIONS:\Microsoft Exchange 2010: failed
63309 7/24/2012 3:36:14 PM 1 0 0 5336 6056 0 bevexmb02.00000.com nsrsnap_vss_save NMM .. bye bye.
68151 7/24/2012 3:36:14 PM 2 0 0 5336 6056 0 bevexmb02.00000.com nsrsnap_vss_save nsrsnap_vss_save: Exiting with failure.
Obviously this line stands out to me:
81233 7/24/2012 3:36:14 PM 1 0 0 5336 6056 0 bevexmb02.00000.com nsrsnap_vss_save NMM .. The database state for saveset Microsoft Exchange 2010 doesn't match the NSR_EXCH2010_BACKUP value PASSIVE and will not be backed up.
If I'm reading this correctly, then the active node of the DAG should be excluded from the passive DB backup, but then that means I have to manually adjust the save group any time the active DAG node is changed. Is that right? I still feel like I'm missing something..
CarlosRojas
1.7K Posts
2
July 24th, 2012 23:00
Hi there,
I think this was discusses long time ago.
If you set NSR_EXCH2010_BACKUP=active and you run the backup against a node hosting only passive DB's backup will fail, and that is per design. Is like talking about regular NetWorerk client you specify a saveset C:\whatever and that folder doesn't exist, backup will fail, right?
NMM will try to backup whatever is specified in the saveset plus the value on the variable NSR_EXCH2010_BACKUP=xx
so again, if you set it to passive and the node only hosts active then backup will fail with the errors you saw already:
The database state for saveset Microsoft Exchange 2010 doesn't match the NSR_EXCH2010_BACKUP value PASSIVE and will not be backed up
There are no saveset objects to add to the replica.
So this behavior is normal and is the way it should be, so it's time to plan a correct backup strategy either backing up all DB's through a single node, by setting NSR_EXCH2010_BACKUP=all (ONLY run the backup for one node) or run the backup for all nodes by setting the correct value in that variable.
Thank you.
Carlos.
imasock
16 Posts
0
July 27th, 2012 07:00
Hi Carlos,
I'm not sure I fully understand what you mean. I am making the assumption that I should have all the DAG members (minus the virtual DAG client) in the Exchange save set. If that's the case, is it not best practice to back up the passive databases? It seems to me that the ideal situation would be to have all DAG members in the same save set, and have NSR_EXCH2010_BACKUP=passive so that the passive databases always get backed up no matter which DAG member they're on.
When I set NSR_EXCH2010_BACKUP=active and run it against both nodes (passive and active in the same save set), the job completes successfully. When I set it to passive it fails with the above errors.
CarlosRojas
1.7K Posts
0
July 27th, 2012 07:00
Hi,
Yes, you are right. What I meant is to have saveset APPLICATIONS:\Microsoft Exchange 2010 and set NSR_EXCH2010_BACKUP=passive
in both nodes.
Now, if this fails having set passive on the 2 nodes, but succeeds having active, then it's strange, as this should fail as well if one of the 2 nodes is not hosting any active DB.
I could only think of the node hosting the passive DB's is also hosting the PF (which is not replicated and resides only in one node), is this the case, that node hosting passive DB's is also hosting the PF and so when you run active DB's it succeeds?
Thank you.
Carlos.