Solved!
Go to SolutionError nsr_vss_save NSR when backup DAG Exchange 2010
Hi carlos,
Now i facing problem from networker when running backup DAG on Exchange server 2010 on platform Windows server 2012.
here message error when backup DAG :
APPLICATIONS:\Microsoft Exchange 2010: Backup of [APPLICATIONS:\Microsoft Exchange 2010] failed
save:
Starting slave backup job on host : SERVER1.
51340:nsrsnap_vss_save:jobhandler(340): Created Job ID: 544514
Save command: nsrsnap_vss_save.exe -s serverbackup.xxx.xx.xx -g DAILY_MAILBOX -m SERVER2.xxx.xx.xx -l incr -t 1453893796 -W 78 -LL -Z DAG.xxx.xx.xx -A optype=conventional -A NSR_SAVE_FROM_SAVEGRP_NSRSNAP=Yes -A NSR_SNAP_TYPE=vss -A CIRCULAR_PROMOTION_POLICY=Promote -A NSR_FEDERATED_BACKUP=yes -A NSR_FEDERATED_PSOL=SERVER1,SERVER2 -A NSR_EXCH_INCL_SA=TRUE -A "NSR_ALT_PATH=F:\\mount_replica" -A NSR_EXCH2010_DAG=DAG -A NSR_EXCH2010_BACKUP=Preferred -A NSR_EXCH_CHECK=no -A NSR_PARENT_JOBID=544509 -A D
Starting slave backup job on host : SERVER2.
51340:nsrsnap_vss_save:jobhandler(340): Created Job ID: 544515
Save command: nsrsnap_vss_save.exe -s serverbackup.xxx.xx.xx -g DAILY_MAILBOX -m server1.xxx.xx.xx -l incr -t 1453893796 -W 78 -LL -Z DAG.xxx.xx.xx -A optype=conventional -A NSR_SAVE_FROM_SAVEGRP_NSRSNAP=Yes -A NSR_SNAP_TYPE=vss -A CIRCULAR_PROMOTION_POLICY=Promote -A NSR_FEDERATED_BACKUP=yes -A NSR_FEDERATED_PSOL=server1,server2-A NSR_EXCH_INCL_SA=TRUE -A "NSR_ALT_PATH=F:\\mount_replica" -A NSR_EXCH2010_DAG=DAG -A NSR_EXCH2010_BACKUP=preferred -A NSR_EXCH_CHECK=no -A NSR_PARENT_JOBID=544509 -A D
85940:nsrsnap_vss_save:Slave backup with job id (544515) failed on host 'SERVER2'
115725:nsrsnap_vss_save:One of the slave job failed, sending Failed Sync Signal
95937:nsrsnap_vss_save:A slave job failure has been identified, stopping all slave jobsnsrsnap_vss_save: Exchange federated ..Updated saveset response with hresult 0x54f.
Internal error.
102333 1453986206 3 0 0 4012 8040 0 server2.xxx.xx.xx nsrsnap_vss_save NSR error 21 Exiting with failure. 0
NSR_SNAP_TYPE=vss
CIRCULAR_PROMOTION_POLICY=Promote
NSR_FEDERATED_BACKUP=yes
NSR_FEDERATED_PSOL=SERVER1,SERVER2
NSR_EXCH_INCL_SA=TRUE
NSR_ALT_PATH=F:\mount_replica
NSR_EXCH2010_DAG=DAG
NSR_EXCH2010_BACKUP=preferred
NSR_EXCH_CHECK=no
please Help for your advice.
Regards
Yc
2724
0
Posted January 29th, 2016 05:00
Hi yadic
Thank you for creating this thread here and for contacting me through Twitter.
Could you please give me some information about your environment such as:
- NW client and NMM version and build installed on the 2 DAG nodes
- NW server version and build
Do you have a fixed IP for the DAG itself? Please note that IP-less DAG is not yet supported.
Please give a try to a non-federated backup, to make sure that process work with no problems or else, if it fails, we can get more information.
If there was a failure, I would need the nmm.raw file from the node where you ran the non-federated backup.
Thank you,
Carlos
2724
0
Posted January 29th, 2016 15:00
Hi carlos,
i used module NMM version 8.2 and NW server version 8.2 Build 681.
yes for cluster DAG used fixed IP but not configured as IP-less DAG.
here i attach nmm raw file from the node when failed backup DAG.
previously backup DAG always success but i don't know the reason now backup DAG failed.
thanks
yadi
2724
0
Posted February 1st, 2016 17:00
hi carlos,
thank you for your advice, finally backup DAG Success...
regards
yadic
2724
0
Posted February 2nd, 2016 05:00
Glad to know it is working now for you.
Thank you for letting us know.
Thank you,
Carlos
2724
0
Posted August 16th, 2017 13:00
I am receiving this same error periodically for my exchange 2013 backups. I have seen numerous references to this on this forum and on the web, but no definitive answers at least that solve my issue. I have verified that the aliases exist for each physical node and the dag. Yet occasionally it will fail with this error. I am looking for a fix that will stop this from happening. Thanks
2724
0
Posted August 17th, 2017 02:00
Hi wgblum
Can you please share the following information?:
1.- Screenshot of the clients configuration (all tabs)
2.- nslookup for forward and reverse lookup for all nodes, including the DAG.
Alsl note the error in this thread, it mentions different names for the DAG, so if this is your case have you followed the steps detailed here for the resolution?
If so, then please verify the name resolution, as this is most likely either a configuration or name resolution issue.
Thank you,
Carlos
2724
0
Posted August 17th, 2017 08:00
Thank you Carlos. I have found one issue so far based on your suggestions. Please confirm the DAG requires a reverse PTR in DNS that is the only issue I have found with name resolution so far. If it does I will have our network folks create one. If that does not resolve the issue I will post our configuration tabs next. Thanks again
319
0
Posted August 18th, 2017 07:00
I added the reverse PTR records for the DAG yesterday afternoon and last night's job completed successfully. I will continue to monitor for this as it has happened randomly in the past. Thank you very much for the help!
CarlosRojas
1693 Posts
2723
0
Posted February 1st, 2016 05:00
Hello yadic
This is a configuration issue, based on the error below.
To prevent showing any computer name I've changed them enough to still show the error:
mail-server.corp.domain.co.id nsrsnap_vss_save NSR critical NMM .. The rollover failed with error 'Backup failed while creating coversave. Client 'mailserver.domain.co.id is not properly configured on the NetWorker Server.. Please make sure you have configured at least one NetWorker Device and client resources are configured for the application host [DAG] and the Mount Host [mailserver.corp.domain.co.id] on NetWorker Server [nwserver.corp.domain.co.id]'
As you can see, it complains that there is not an entry for the client (physical node) with includes the "domain" part of the FQDN so please add taht entry to the alias field of the client, and also please make sure you add all the aliases needed in the client entry of the DAG itself so for example, imagine you DAG is called DAG, you will need to add all required entries:
DAG
DAG.corp.domain.co.id
DAG.domain.co.id
Same for the physical nodes of the DAG.
Thank you,
Carlos