Good afternoon, how to configure the NMM 2.1.1 NMC 7.6.1 to backup Active Directory on Windows server 2008 sp1 x64 Std. What need to specify file sets and what command must be specified in the Backup commands, etc.
Anyway I think you are falling into a known bug, as per esg120766
Anyway, you could try to use the variable to skip missing files, however being this AD server, I would try to avoid skipping any system file.
I remember that WSUS caused some issues in the past, with previous versions.
The variable to skip system missing files is (to be added in Application Information):
NSR_IGNORE_MISSING_SYSTEM_FILES=yes
BUG ID NW118610. This issue is seen when user selects some temporary folder like C:\WSUS or H:\WSUS etc to store the Windows Server Update Services.
Resolution
Upgrade to NMM 2.3
Workaround: User has to select a database (available in drop down menu) in Windows Server Update Services wizard. Then System Component backup will pass through.
Anyway, as explained earlier the log you should look into is ALWAYS nmm.raw, so please, render it as described in previous emails and paste here the output (from last backup should be enough), as sometimes not all the information is shown in the group completion report, and NMM has more granularity in the output.
My first suggestion is to install NMM 2.3, 2.1.1 is quit old.
Secondly, you have 2 options to backup AD, and this is VSS mode, by backing up SYSTEM COMPONENTS:\ saveset, using backup command nsrsnap_vss_save and Application Information NSR_SNAP_TYPE=vss, and including this client entry in an snapshot group. That simple.
I would also recommend though to add C:\ and other critical volumes related to AD in the same client, so it should looks like this:
C:\
SYSTEM COMPONENT:\
(Any other drive if applies)
In the other hand you can also backup AD in granular mode, by setting saveset as follows:
For example, your domain is: corporate.com
Saveset should be DC=corporate,DC=com
Backup command should be nsradsave and that's it. This client is not using VSS, so you can add that client to any regular group with NO snapshot option selected.
I hope that answers your question, however taking a look at the documentation always helps.
If you are backing up ADAM there are few changes, and that is perfectly clear in NMM documentation, but remember, install NMM 2.3, as there are lots of bugs already solved in that version.
Feb 01 15:47:01 networker: NetWorker savegroup: (info) srv02.intranet.s-k.kz:C:\: No full backups of this save set were found in the media database; performing a full backup
Feb 01 15:47:01 networker: NetWorker savegroup: (info) srv02.intranet.s-k.kz:SYSTEM COMPONENTS:\: No full backups of this save set were found in the media database; performing a full backup
Feb 01 15:47:02 networker: NetWorker client: (notice) srv02.intranet.s-k.kz: A backup was attempted with save when NetWorker Module for Microsoft (NMM) is installed. Please consult the NMM Administration Guide for client resource configuration information
Feb 01 15:47:02 networker: NetWorker client: (notice) srv02.intranet.s-k.kz: A backup was attempted with save when NetWorker Module for Microsoft (NMM) is installed. Please consult the NMM Administration Guide for client resource configuration information
Feb 01 15:47:02 networker: NetWorker savegroup: (info) srv02.intranet.s-k.kz:C:\: No full backups of this save set were found in the media database; performing a full backup
Feb 01 15:47:03 networker: NetWorker savegroup: (info) srv02.intranet.s-k.kz:SYSTEM COMPONENTS:\: No full backups of this save set were found in the media database; performing a full backup
Feb 01 15:47:03 networker: NetWorker client: (notice) srv02.intranet.s-k.kz: A backup was attempted with save when NetWorker Module for Microsoft (NMM) is installed. Please consult the NMM Administration Guide for client resource configuration information
Feb 01 15:47:03 networker: NetWorker client: (notice) srv02.intranet.s-k.kz: A backup was attempted with save when NetWorker Module for Microsoft (NMM) is installed. Please consult the NMM Administration Guide for client resource configuration information
Feb 01 15:47:04 networker: NetWorker media: (waiting) Waiting for 1 writable volume(s) to backup pool 'srv02' tape(s) on networker
Feb 01 15:47:04 networker: NetWorker media: (waiting) Waiting for 1 writable volume(s) to backup pool 'srv02' tape(s) on networker
Feb 01 15:47:34 networker: NetWorker savegroup: (info) srv02.intranet.s-k.kz waiting for 1 job(s) to complete
Feb 01 15:49:09 networker: NetWorker savegroup: (info) Added 'networker' to the group 'srv02.intranet.s-k.kz' for bootstrap backup
Feb 01 15:49:13 networker: NetWorker savegroup: (alert) srv02.intranet.s-k.kz completed, Total 2 client(s), 1 Failed, 1 Succeeded. Please see group completion details for more information.
Feb 01 15:49:13 networker: Failed: srv02.intranet.s-k.kz
Feb 01 15:49:13 networker: Succeeded: networker
Feb 01 15:49:13 networker: saveset srv02.intranet.s-k.kz:srv02.intranet.s-k.kz:index: percentage of inactive files by count: 0.00, by space: 0.00
Feb 01 15:49:13 networker: saveset networker:networker:bootstrap: percentage of inactive files by count: 0.00, by space: 0.00
Feb 01 15:49:13 networker: Start time: Wed Feb 01 15:47:00 2012
Feb 01 15:49:13 networker: End time: Wed Feb 01 15:49:13 2012
Feb 01 15:49:13 networker: --- Unsuccessful Save Sets ---
Feb 01 15:49:13 networker: * srv02.intranet.s-k.kz:C:\ 1 retry attempted
Feb 01 15:49:13 networker: srv02.intranet.s-k.kz:C:\: No full backups of this save set were found in the media database; performing a full backup
Feb 01 15:49:13 networker: * srv02.intranet.s-k.kz:C:\ 79702:save:NetWorker Module for Microsoft is installed. Please configure the backup with NetWorker Module for Microsoft Applications only.
Feb 01 15:49:13 networker: * srv02.intranet.s-k.kz:SYSTEM COMPONENTS:\ 1 retry attempted
Feb 01 15:49:13 networker: srv02.intranet.s-k.kz:SYSTEM COMPONENTS:\: No full backups of this save set were found in the media database; performing a full backup
Feb 01 15:49:13 networker: * srv02.intranet.s-k.kz:SYSTEM COMPONENTS:\ 5197:save: using `SYSTEM COMPONENTS:\' for `SYSTEM COMPONENTS:\'
Feb 01 15:49:13 networker: * srv02.intranet.s-k.kz:SYSTEM COMPONENTS:\ 79702:save:NetWorker Module for Microsoft is installed. Please configure the backup with NetWorker Module for Microsoft Applications only.
Feb 01 15:49:13 networker: * : Failed with error(s)
Feb 01 15:47:02 networker: NetWorker client: (notice) srv02.intranet.s-k.kz: A backup was attempted with save when NetWorker Module for Microsoft (NMM) is installed.
You need to set the backup command:
nsrsnap_vss_save and make sure that the group where that client is included is Snapshot backup.
here is the error which I have not experienced, yet to
Feb 01 17:03:57 networker: --- Unsuccessful Save Sets ---
Feb 01 17:03:57 networker: * srv02.intranet.s-k.kz srv02.intranet.s-k.kz:C:\: No full backups of this save set were found in the media database; performing a full backup
Feb 01 17:03:57 networker: * srv02.intranet.s-k.kz C:\: Backup of failed
Feb 01 17:03:57 networker: * srv02.intranet.s-k.kz SYSTEM COMPONENTS:\: Backup of [SYSTEM COMPONENTS:\] failed
Feb 01 17:03:57 networker: 1 retry attempted
Feb 01 17:03:57 networker: 52051:nsrsnap:Printing savecmd=nsrsnap_vss_save after parsing
Feb 01 17:03:57 networker: 79549:nsrsnap:[nsrsnap.c 1891] Invoking command: "nsrsnap_vss_save -A optype=conventional -A "NSR_SNAP_TYPE=vss" -A "NSR_ALT_PATH=C:\mount_replica\" -A NSR_PARENT_JOBID=736069 -b srv02 -c srv02.intranet.s-k.kz -g "srv02.intranet.s-k.kz" -LL -m srv02.intranet.s-k.kz -s networker -l full -q -W 78 -A snap_sessionid=1328094209 -A NSR_STRICT_SYNC=0 "C:\ SYSTEM COMPONENTS:\
Feb 01 17:03:57 networker: 73064:nsrsnap_vss_save:Version information for C:\Program Files\Legato\nsr\bin\nsrsnap_vss_save.exe:
Feb 01 17:03:57 networker: Original file name: nsrsnap_vss_save.exe
Feb 01 17:03:57 networker: Version: 2.3.0.87
Feb 01 17:03:57 networker: Comments: NetWorker Module for Microsoft Applications (x64)
Feb 01 17:03:57 networker: 50423:nsrsnap_vss_save:nsrsnap_vss_save: Unknown Application Information parameter: NSRSNAP_JOBID, may not be supported
Feb 01 17:03:57 networker: 50411:nsrsnap_vss_save:nsrsnap_vss_save: Data mover host name not specified. Assuming local host: srv02.intranet.s-k.kz
Please run vssadmin list writers on the AD server and check if System Writer is present.
It's quit common this kind of issues after some Windows Updates. If System Writer is not present you will need to re-register VSS dll's, and reboot is mandatory besides, there is a chance that is not only about the VSS dll's unregistered, but some permissions issue.
Please see below the procedures to re-register the VSS dll's:
=======================
WINDOWS 2003 SERVER x86
=======================
Following are the suggested updates for vss and some basic troubleshooting for it:
net stop "Background Intelligent Transfer Service"
net stop "COM+ Event System"
net stop "Microsoft Software Shadow Copy Provider "
net stop "Volume Shadow Copy"
cd /d %windir%\system32
net stop vss
net stop swprv
regsvr32 /s ATL.DLL
regsvr32 /s comsvcs.DLL
regsvr32 /s credui.DLL
regsvr32 /s CRYPTNET.DLL
regsvr32 /s CRYPTUI.DLL
regsvr32 /s dhcpqec.DLL
regsvr32 /s dssenh.DLL
regsvr32 /s eapqec.DLL
regsvr32 /s esscli.DLL
regsvr32 /s FastProx.DLL
regsvr32 /s FirewallAPI.DLL
regsvr32 /s kmsvc.DLL
regsvr32 /s lsmproxy.DLL
regsvr32 /s MSCTF.DLL
regsvr32 /s msi.DLL
regsvr32 /s msxml3.DLL
regsvr32 /s ncprov.DLL
regsvr32 /s ole32.DLL
regsvr32 /s OLEACC.DLL
regsvr32 /s OLEAUT32.DLL
regsvr32 /s PROPSYS.DLL
regsvr32 /s QAgent.DLL
regsvr32 /s qagentrt.DLL
regsvr32 /s QUtil.DLL
regsvr32 /s raschap.DLL
regsvr32 /s RASQEC.DLL
regsvr32 /s rastls.DLL
regsvr32 /s repdrvfs.DLL
regsvr32 /s RPCRT4.DLL
regsvr32 /s rsaenh.DLL
regsvr32 /s SHELL32.DLL
regsvr32 /s shsvcs.DLL
regsvr32 /s swprv.DLL
regsvr32 /s tschannel.DLL
regsvr32 /s USERENV.DLL
regsvr32 /s vss_ps.DLL
regsvr32 /s wbemcons.DLL
regsvr32 /s wbemcore.DLL
regsvr32 /s wbemess.DLL
regsvr32 /s wbemsvc.DLL
regsvr32 /s WINHTTP.DLL
regsvr32 /s WINTRUST.DLL
regsvr32 /s wmiprvsd.DLL
regsvr32 /s wmisvc.DLL
regsvr32 /s wmiutils.DLL
regsvr32 /s wuaueng.DLL
net start "COM+ Event System"
Note that once you reboot, you will need to run again vssadmin list writers, and ensure System writer is there, if it is not you will need to reassign correct permissions. Despite I could give you the commands, you should consider engaging Microsoft. This is not NetWorker/NMM issue but pure Microsoft Windows issue.
Please let me know if re-registering VSS brings System writer back. If it does then please run a new backup and let me know.
Yes Carlos, I just changed on your advice, but error occurs Feb 01 18:27:47 networker: 47 363: nsrsnap_vss_save: nsrpsd service is running on SRV02.intranet.sk.kz. Feb 01 18:27:47 networker: snapvss_quoow_save: Dumping disk quota databases into OS drive Feb 01 18:27:47 networker: 82 624: nsrsnap_vss_save: Save set name C: \ is valid. Feb 01 18:27:47 networker: 82 624: nsrsnap_vss_save: Save set name SYSTEM COMPONENTS: \ is valid. Feb 01 18:27:47 networker: 83 724: nsrsnap_vss_save: ERROR: Found 'System Writer' missing which is required for SYSTEM COMPONENTS backup. Feb 01 18:27:47 networker: List of valid saveset entries for APPLICATIONS on client SRV02.intranet.sk.kz ... Feb 01 18:27:47 networker: 63 335: nsrsnap_vss_save: NMM backup failed to complete successfully. Feb 01 18:27:47 networker: Internal error. Feb 01 18:27:47 networker: 68151 1328099250 2 0 0 7056 3368 0 39 srv02.intranet.sk.kz nsrsnap_vss_save nsrsnap_vss_save: Exiting with failure. 0 Feb 01 18:27:47 networker: Feb 01 18:27:47 networker: --- Successful Save Sets ---
the second customer with the same problems with backup Active Directory, I re-registered the VSS and leaves an error:
--- Unsuccessful Save Sets ---
Feb 02 10:51:23 networker: * srv01.intranet.s-k.kz srv01.intranet.s-k.kz:C:\: No full backups of this save set were found in the media database; performing a full backup
Feb 02 10:51:23 networker: * srv01.intranet.s-k.kz C:\: Backup of failed
Feb 02 10:51:23 networker: * srv01.intranet.s-k.kz SYSTEM COMPONENTS:\: Backup of [SYSTEM COMPONENTS:\] failed
Feb 02 10:51:23 networker: path.
Feb 02 10:51:23 networker: 80771:nsrsnap_vss_save:NMM .. FAILED to get correct file path for d:\WSUS\SERVERBASE\UpdateServicesDbFiles\, filespec='SUSDB.mdf', Writer Name : SqlServerWriter.
Feb 02 10:51:23 networker: 48462:nsrsnap_vss_save:PS: (CMTDXlator::ProcessSelectedComponent) FAILED
Feb 02 10:51:23 networker: 48462:nsrsnap_vss_save:PS: (CMTDXlator::ProcessChildrenComponents) FAILED
Feb 02 10:51:23 networker: 48462:nsrsnap_vss_save:PS: (CMTDXlator::ProcessWriterSavesetComponents) FAILED
Feb 02 10:51:23 networker: 48462:nsrsnap_vss_save:PS: (CMTDXlator::ProcessWriterSavesets) FAILED
Feb 02 10:51:23 networker: 48462:nsrsnap_vss_save:PS: (CMTDXlator::PrepareSnapshotObjects) FAILED
Feb 02 10:51:23 networker: NMM .. Error generating files and directives list for the backup.
Feb 02 10:51:23 networker: 64036:nsrsnap_vss_save:NMM .. Error preparing list of files for backup: Error generating files and directives list for the backup.
Feb 02 10:51:23 networker: 63372:nsrsnap_vss_save:NMM .. Registration of snapshot set failed -- Error generating files and directives list for the backup
Feb 02 10:51:23 networker: 77175:nsrsnap_vss_save:NMM .. completed commit replica with status of false.
Feb 02 10:51:23 networker: 63335:nsrsnap_vss_save:NMM backup failed to complete successfully.
Feb 02 10:51:23 networker: Internal error.
Feb 02 10:51:23 networker: 68151 1328158193 2 0 0 4636 2444 0 srv01.intranet.s-k.kz nsrsnap_vss_save 39 nsrsnap_vss_save: Exiting with failure. 0
Feb 02 10:51:23 networker: --- Successful Save Sets ---
yet I would like to ask that in the understanding of EMC Networker means SYSTEM COMPONENTS: \
CarlosRojas
1693 Posts
2591
0
Posted February 1st, 2012 22:00
Hi Alex,
Is this a cluster or a Hyper-V VM?
Anyway I think you are falling into a known bug, as per esg120766
Anyway, you could try to use the variable to skip missing files, however being this AD server, I would try to avoid skipping any system file.
I remember that WSUS caused some issues in the past, with previous versions.
The variable to skip system missing files is (to be added in Application Information):
NSR_IGNORE_MISSING_SYSTEM_FILES=yes
BUG ID NW118610. This issue is seen when user selects some temporary folder like C:\WSUS or H:\WSUS etc to store the Windows Server Update Services.
Resolution
Upgrade to NMM 2.3
Workaround: User has to select a database (available in drop down menu) in Windows Server Update Services wizard. Then System Component backup will pass through.
Anyway, as explained earlier the log you should look into is ALWAYS nmm.raw, so please, render it as described in previous emails and paste here the output (from last backup should be enough), as sometimes not all the information is shown in the group completion report, and NMM has more granularity in the output.
Thank you.
Carlos.