This DISASTERY_RECOVERY:\ saveset configuration for NMM is being confusing for some customers, as people trend to configure that saveset using nsrsnap_vss_save, but in this case only save command, and a NON-SNAPSHOT group will work.
Please feel free to mark the question as answered if you don't need any further information.
I have gone through the NMM admin guide and have found the following information for you:
For backup of the System State, specify SYSTEM COMPONENTS:\ as the saveset in the Client resource
The SYSTEM COMPONENTS:\ save set contains many individual system writers and you cannot mention individual system writers.They all will be backed up as a single saveset.
To know the writers which gets backed up, please refer NMM admin guide ver 2.3 page 99
This has a list of writers which are included under SYSTEM COMPONENTS:\ saveset.
As suggested by Siva you can use SYSTEM COMPONENTS:\ for system state backup. But there is a restriction on this saveset, you can restore it to same machine instace. This is restriction is from Microsoft on windows 2008 servers.
SYSTEM COMPONENTS:\ wont be usefull, incase if the server fails and you have to migrate to new hardware or do a reinstallation with new instance.
I configured a group for backup system components. The group has a snapshot policy configured.
When the backup is started the following error occurred.
savegrp: suppressed 4 lines of verbose output 20146:nsrsnap_save:Skipping backup of SYSTEM COMPONENTS:\. 53285:nsrsnap_save:Found no paths to backup. 20135:nsrsnap_save:Could not find paths to backup. usage: nsrsnap_save [ ] [path_1 path_2 ...] options: [-BCEiKnPqQSuUvVx] [-b pool] [-c client-name] [-D Debug] [-e expiration time] [-f dirfile]. [-F file] [-g group] [-I input file] [-l level] [-M ] [-R snapset_savetime] [-s server] [-S] [-t date]. [-w browse time] [-y retention time] [-A key=value] ... Server001 Server001:SYSTEM COMPONENTS:\: No full backups of this save set were found in the media database; performing a full backup Server001 25048:nsrsnap_save:SYSTEM COMPONENTS:\: Failed. Server001 25056:nsrsnap_save:SYSTEM COMPONENTS:\: Path is not ok.
Hi Error msgs in NMM and NSRADSAVE regarding "Could not find path" is often due to resolve issues in DNS / Hostsfile.
Verify you have short and long (FQDN) in DNS and Hostfile also under client configuration in alias place both short and long name like
exchange01
exchange01.company.com
Please note NMM also is case senetive in name resolution sometimes I see client answer with name in uppercase and sometime in lowercase then you can have an alias and hostfile like:
exchange01
EXCHANGE01
excahnge01.compant.com
EXCHANGE01.company.com
But in short, please verify the name resolution between client and backup server.
It should be nsrsnap_vss_save for snapshot groups.
It should be empty (save.exe) for DISASTER_RECOVERY:\ saveset, and this is the same for regular NW clients and also for NMM clients besides, NMM clients configured in NMC for DISASTER_RECOVERY:\ saveset should NOT be included in any snapshot group, as that saveset is not backed up using snapshot backup.
CarlosRojas
1.7K Posts
0
January 16th, 2013 00:00
Hi Sokratis,
Thanks for the feedback.
This DISASTERY_RECOVERY:\ saveset configuration for NMM is being confusing for some customers, as people trend to configure that saveset using nsrsnap_vss_save, but in this case only save command, and a NON-SNAPSHOT group will work.
Please feel free to mark the question as answered if you don't need any further information.
Thank you.
Carlos.
pn1lDbv3G612259
105 Posts
1
September 11th, 2012 21:00
Hi Peterson,
I have gone through the NMM admin guide and have found the following information for you:
For backup of the System State, specify SYSTEM COMPONENTS:\ as the saveset in the Client resource
The SYSTEM COMPONENTS:\ save set contains many individual system writers and you cannot mention individual system writers.They all will be backed up as a single saveset.
To know the writers which gets backed up, please refer NMM admin guide ver 2.3 page 99
This has a list of writers which are included under SYSTEM COMPONENTS:\ saveset.
Please let us know if you have further questions.
Thank you
ShivaKiran
nmc2
268 Posts
1
September 11th, 2012 22:00
As suggested by Siva you can use SYSTEM COMPONENTS:\ for system state backup. But there is a restriction on this saveset, you can restore it to same machine instace. This is restriction is from Microsoft on windows 2008 servers.
SYSTEM COMPONENTS:\ wont be usefull, incase if the server fails and you have to migrate to new hardware or do a reinstallation with new instance.
Regards,
Prajith
PetersonPS
1 Rookie
•
39 Posts
0
September 12th, 2012 10:00
Hi,
I configured a group for backup system components.
The group has a snapshot policy configured.
When the backup is started the following error occurred.
savegrp: suppressed 4 lines of verbose output
20146:nsrsnap_save:Skipping backup of SYSTEM COMPONENTS:\.
53285:nsrsnap_save:Found no paths to backup.
20135:nsrsnap_save:Could not find paths to backup.
usage: nsrsnap_save [ ] [path_1 path_2 ...]
options: [-BCEiKnPqQSuUvVx] [-b pool] [-c client-name] [-D Debug] [-e expiration time] [-f dirfile].
[-F file] [-g group] [-I input file] [-l level]
[-M ] [-R snapset_savetime] [-s server] [-S] [-t date].
[-w browse time] [-y retention time]
[-A key=value] ...
Server001 Server001:SYSTEM COMPONENTS:\: No full backups of this save set were found in the media database; performing a full backup
Server001 25048:nsrsnap_save:SYSTEM COMPONENTS:\: Failed.
Server001 25056:nsrsnap_save:SYSTEM COMPONENTS:\: Path is not ok.
CarlosRojas
1.7K Posts
0
September 18th, 2012 06:00
Hi Peterson,
What is the backup command you have set for that client?
What is the saveset?
Thank you.
Carlos.
iimnordic
1 Rookie
•
19 Posts
0
October 3rd, 2012 05:00
Hi Error msgs in NMM and NSRADSAVE regarding "Could not find path" is often due to resolve issues in DNS / Hostsfile.
Verify you have short and long (FQDN) in DNS and Hostfile also under client configuration in alias place both short and long name like
exchange01
exchange01.company.com
Please note NMM also is case senetive in name resolution sometimes I see client answer with name in uppercase and sometime in lowercase then you can have an alias and hostfile like:
exchange01
EXCHANGE01
excahnge01.compant.com
EXCHANGE01.company.com
But in short, please verify the name resolution between client and backup server.
CarlosRojas
1.7K Posts
0
October 9th, 2012 01:00
Hi Peterson,
Do you have in place the correct backup command?
It should be nsrsnap_vss_save for snapshot groups.
It should be empty (save.exe) for DISASTER_RECOVERY:\ saveset, and this is the same for regular NW clients and also for NMM clients besides, NMM clients configured in NMC for DISASTER_RECOVERY:\ saveset should NOT be included in any snapshot group, as that saveset is not backed up using snapshot backup.
Thank you.
Carlos.
Sokratis1
5 Posts
0
January 10th, 2013 11:00
Thank you Carlos very much!! the command did the trick!
also do not forget for windows clients the application information: NSR_SNAP_TYPE=VSS
it is needed by command: nsrsnap_vss_save
GPIL
4 Posts
0
August 25th, 2015 16:00
Can we configure incremental backups for system state on given server . Is this supported on networker 8.1.2.1