This post is more than 5 years old
14 Posts
0
1672
Exchange 2010 NMM backup fails sometimes
Hi all,
Versions:
Exchange 2010 Standalone
NMM 2.4.1
Networker Server:version 7.6.5.7.Build.1231
Sometimes , backup fails with following error : Sorry messages are in french and i translated some of them
"[nsrsnap.c 2047] Calling start_savecmd..
[nsrsnap.c 2060] Calling snap_wait..
[nsrsna.c 2081] Calling parse_fs_logs_and_prefix..
86745:nsrsnap_vss_save:Informations de version pour C:\Program Files\EMC NetWorker\nsr\bin\nsrsnap_vss_save.exe :
Nom du fichier d'origine : nsrsnap_vss_save.exe
Version : 2.4.1.92
Comments: NetWorker Module for Microsoft Applications (x64) 50411:nsrsnap_vss_save:nsrsnap_vss_save : Data mover hostname not specified. Local host assumed by default: wmail2.cg10.local 50412:nsrsnap_vss_save:nsrsnap_vss_save : Invalid argument :
-g specified without sessionID
50338:nsrsnap_vss_save:
syntaxe : nsrsnap_vss_save [ ]
50420:nsrsnap_vss_save: options : [-mvWL] [-c nom-client] [-f fichier rép.]
50421:nsrsnap_vss_save: [-g groupe]
43597:nsrsnap_vss_save: [-s serveur]
50422:nsrsnap_vss_save: [clé -A=valeur]
67780:nsrsnap_vss_save: [-G vide les métadonnées VSS Writer dans des fichiers XML, à raison d'un fichier par writer.]
67781:nsrsnap_vss_save: [-? affiche les entrées de saveset de données d'application 'valides.]
62872:nsrsnap_vss_save:nsrsnap_vss_save : impossible pour snapvss_validateAparams() de valider un ou plusieurs paramètres d'information d'application.
68151:nsrsnap_vss_save:nsrsnap_vss_save : sortie avec échec.
Here are the Application Informations for Exchange 2010 networker client:
NSR_SNAP_TYPE=vss
NSR_EXCH_RETAIN_SNAPSHOTS=yes
NSR_ALT_PATH=d:\temp
NSR_EXCH_CHECK=yes
NSR_ESE_UTIL_SEQUENTIAL=False
NSR_ESE_UTIL_THROTTLE=False
NSR_CHECK_JET_ERRORS=all
It seems that sometimes NMM is backing up Exchange 2010 in DAG mode.
DAG is not utilized nor configured in our Exchange 2010 environment.
Any ideas ?
Thx
Bruno
CarlosRojas
1.7K Posts
0
June 16th, 2015 08:00
Hi Bruno,
Not sure if I understood correctly. Did you mean that you had File System backups together with the Exchange backup?
This is not recommended, and if I remember well, not even supported...old version of NW and NMM
Let's see how it goes now that you have split the FS and Exchange backups, however you will need to make sure that FS and Exchange backup do NOT overlap, or else backup will fail.
Thank you,
Carlos
CarlosRojas
1.7K Posts
0
June 12th, 2015 02:00
Hi Bruno,
Are you actually retaining snapshots? Could you please let me know what is your snapshot policy? This could be the reason for the failure (despite the error message complains about the command usage).
On the other hand, can you please develop more regarding "sometimes"? In what situations the backup fails? Is it maybe different groups or client instance that fails? Different schedule?
Thank you,
Carlos
CGAUBE
14 Posts
0
June 12th, 2015 03:00
I found this in event viewer of the Exchange 2010 server:
RM_ESM_2010: Executing get-MailboxServer -Identity "WMAIL2" Properties = DatabaseAvailabilityGroup
It occurs at the beginning of the backup
Could it be an explanation ?
CGAUBE
14 Posts
0
June 12th, 2015 03:00
Hi Carlos,
We don't retain snapshots.
By "sometimes" , i mean that the same backup , same client, same schedule most of the time ends successfiully but not on some days. I can't see if an event occurred previous day of the backup which could have some influence on the backup.
Could it be related to a wrong interpretation of NMM regarding DAG ?
Actually, we don't use DAG nor configured it.
CGAUBE
14 Posts
0
June 12th, 2015 06:00
Carlos,
I think i was wrong when i said that we didn't keep snapshots.
Here are the application informations for the exchange client
NSR_SNAP_TYPE=vss
NSR_EXCH_RETAIN_SNAPSHOTS=yes --> I think that it means that we do retain snapshots
NSR_ALT_PATH=d:\temp
NSR_EXCH_CHECK=yes
NSR_ESE_UTIL_SEQUENTIAL=False
NSR_ESE_UTIL_THROTTLE=False
NSR_CHECK_JET_ERRORS=all
CarlosRojas
1.7K Posts
0
June 12th, 2015 08:00
Hi Bruno,
Actually is the other way around
I was asking if you really need to retain snapshots, meaning that you have snapshots being rolled-over to backup device, and other persistent snapshots, staying locally on the storage for faster restore (these are not being saved to backup device).
If you are NOT retaining snapshots, please remove that variable from the application information.
Also, can you please share the information about the snapshot policy you have configured for that group?
Can you check as well if there is any orphaned or left behind snapshots, by running vssadmin list shadows?
If no persistent snapshots (retained snapshots), there shouldn't be any snapshot left behind, so please check and delete those snapshots if possible.
Thank you,
Carlos
elvinperez
87 Posts
0
June 12th, 2015 09:00
Hi Bruno,
execute the config check and loaded the issue.
Regards
CarlosRojas
1.7K Posts
0
June 15th, 2015 03:00
Hi Bruno,
Yes, please set the variable to false, as the serverless backup should take only one snapshot and roll it over to backup device.
So did you run any backup today around 7:00, when the snapshot was created? If not, is there any other third party application taking those snapshots? Is this a physical or virtual machine?
If Shadow Copy is enabled, please go ahead and disable it, as that will lead to backup failures
If that snapshot is no longer needed, please delete that snapshot, to make sure we don't leave behind any other snapshot.
Thank you,
Carlos
CGAUBE
14 Posts
0
June 15th, 2015 03:00
Hi Elvin
The config checker did not show any problem.
Actually, i have additional info: I discovered that failure occurred every friday and successful end of group occurred any other day in the nwk schedule.
For the moment, i'm checking if any scheduled task or special event could interact whith the group these days.
I'll post reply asap.
Thx
CGAUBE
14 Posts
0
June 15th, 2015 03:00
Hi Carlos,
As i replied to Elvin, i'm wondering why our problem only occurs on fridays and never the other days?
For the moment , i don't have any certainty for this .
Here is the snapshot list:
>vssadmin list shadows
vssadmin 1.1 - Outil ligne de commande d'administration du servicede cliché instantané de volume
(C) Copyright 2001-2005 Microsoft Corp.
Contenu du jeu de clichés instantanés n° : {10d3b35c-adc3-4522-8335-857bcb957cfe}
Contenait 1 clichés instantanés à la date de création : 15/06/2015 07:00:02
ID du cliché instantané : {7bcbe819-3682-4499-95e4-d2a631aad67b}
Volume original : (C:)\\?\Volume{d679845b-b0a2-11e1-9d0b-806e6f6e6963}\
Volume de cliché instantané : \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy4
Ordinateur d'origine : wmail2.CG10.LOCAL
Ordinateur de service : wmail2.CG10.LOCAL
Fournisseur : 'Microsoft Software Shadow Copy provider 1.0'
Type : ClientAccessible
Attributs : Persistent, Accessible par client, Pas de libération automatique, Aucun rédacteur, Différentielle
It's a volume snapshot , taken each day in differential mode, at 7H00 , on C:\ volume:
nothing to do whith powersnap snapshots taken at 4H00 at the group strating.
So, i think i'll delete NSR_EXCH_RETAIN_SNAPSHOTS=yes or set it to False (right ?).
Regarding the snapshot policy for the group , here are the parameters:
Snapshot: yes
Policy: Serverless Backup
Pool: My pool (advfile device on F:\ local disk)
CGAUBE
14 Posts
0
June 15th, 2015 08:00
Hi Carlos,
I just set the parameter to false. I have to wait next friday's session to check the result.
Today i ran a backup at 4H00 , so 3 hours before taking the snapshot.
I don't see any third party app which could take snapshots.
On the Exchange server, Shadow Copy is enabled on C:\ partition (not at volume level) , for fast restoration purpose in case of data loss.
For that reaseon, it's difficult for me to delete the snapshot
CarlosRojas
1.7K Posts
0
June 16th, 2015 04:00
Hello Bruno,
I'm afraid there is an overlapping of the backup and the snapshot you have configured for C:\
Please note that only one VSS operation at a time is allowed, so you will have to check the schedule of the backup so it doesn't overlap, however my recommendation is to disable snapshot on C:\
Thank you,
Carlos
CGAUBE
14 Posts
0
June 16th, 2015 06:00
Hello Carlos,
I've made some updates.
Firstable, move backup of two folders from nsr snap group to normal nsr group .
Only keep APPLICATIONS:\MicrosoftExchange 2010 in snap type group.
Midified NSR_EXCH_RETAIN_SNAPSHOTS=no (in place of False which is not authorized)
Delete C:\ snapshot .
Normally, i shouln't have any problem .
I'll wait till friday to see if error persists or not.
I'll do an update at that moment.
Again , thanks for your help.
CGAUBE
14 Posts
0
June 17th, 2015 08:00
Hi Carlos,
Yes , i HAD 2 client folders backed up within the the same group.
Now, i've separated these savesets in 2 different non-overlapping groups.
Further, by removing pool specification in the client configuration and adding it in the group configuration , the backups seem to be successful.
I'll wait till friday to confirm that this case is solved.
Thanks
CGAUBE
14 Posts
0
June 19th, 2015 00:00
Hola Carlos,
I would like to confirm that the problem is solved.
Steps folloed :
- separating filesystem and exchange backups in two non overlapping vss groups.
- Deleting mention of snapshot pool at client level
- Adding snapshot pool at group level (by editing the pool).
- adding *@* in the remote access field of the client
All works fine.
Thanks again Carlos
See you.