Unsolved
This post is more than 5 years old
2 Intern
•
186 Posts
0
804
July 1st, 2009 17:00
2 way NMM backup
Hello all,
So i have a DC that i want to backup in 2 different ways. I was wondering if anyone else has done this and if they have had problems.
First way, I want to do a grandular backup of AD only. I have tested this and it works on one domain but not the other. The domain it works on is a domain without Symantec backup exec installed. Backup exec creates an OU on AD and NMM has problems reading this OU. (Case lodged with EMC) Awaiting Patch generation.
The second way of backing up this DC is via a snapshot. I hav e a snapshot group configured and this client is in the group. the save set call is
SYSTEM COMPONENTS\
It kinda works and fails.
Error message from the failed component is
AUNNDCDCP02 SYSTEM COMPONENTS\: NSRSNAPCK::success
AUNNDCDCP02 6999:nsrsnap_save: SYSTEM COMPONENTS\: No such file or directory
AUNNDCDCP02 25048:nsrsnap_save: SYSTEM COMPONENTS\: Failed.
AUNNDCDCP02 25056:nsrsnap_save: SYSTEM COMPONENTS\: Path is not ok.
52051:nsrsnap: Printing savecmd=nsrsnap_save after parsing
SYSTEM COMPONENTS\
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] ...
Has anyone else used the latest version of the NMM component?
It might be my imagination or is this component just dodge?
So i have a DC that i want to backup in 2 different ways. I was wondering if anyone else has done this and if they have had problems.
First way, I want to do a grandular backup of AD only. I have tested this and it works on one domain but not the other. The domain it works on is a domain without Symantec backup exec installed. Backup exec creates an OU on AD and NMM has problems reading this OU. (Case lodged with EMC) Awaiting Patch generation.
The second way of backing up this DC is via a snapshot. I hav e a snapshot group configured and this client is in the group. the save set call is
SYSTEM COMPONENTS\
It kinda works and fails.
Error message from the failed component is
AUNNDCDCP02 SYSTEM COMPONENTS\: NSRSNAPCK::success
AUNNDCDCP02 6999:nsrsnap_save: SYSTEM COMPONENTS\: No such file or directory
AUNNDCDCP02 25048:nsrsnap_save: SYSTEM COMPONENTS\: Failed.
AUNNDCDCP02 25056:nsrsnap_save: SYSTEM COMPONENTS\: Path is not ok.
52051:nsrsnap: Printing savecmd=nsrsnap_save after parsing
SYSTEM COMPONENTS\
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] ...
Has anyone else used the latest version of the NMM component?
It might be my imagination or is this component just dodge?
0 events found
No Events found!
ble1
6 Operator
•
14.4K Posts
•
56.2K Points
0
July 11th, 2009 02:00
snapshot. I hav e a snapshot group configured and
this client is in the group. the save set call is
SYSTEM COMPONENTS\
Try SYSTEM COMPONENTS:\
Also, see if SYSTEM COMPONENTS:\some_writer works for you....
dugans1
2 Intern
•
186 Posts
0
July 12th, 2009 16:00
I also have a Snapshot group configured and this client is in the group.
The problem i am having here is that we also use Veritas Backup exec in our environment.
When we try and do a backup of AD in this manor the backup fails due to an OU being created by backup exec.
The developers are aparently releasing a patch to fix this.
dugans1
2 Intern
•
186 Posts
0
July 12th, 2009 22:00
Her is what we did to fix it.
save set in the client configuration should have been configured as follows
SYSTEM COMPONENTS:\
not
SYSTEM COMPONENTS\
also in the servers file in the res directory an incorrect entry in the file.