I have another backup server backuping the same client and it worked only differance is that backup is running on DataDomain device and the old one ran on tape.
Most likely you entered the backup command (nsrsqlsv) into the wrong field. Consequently, NW thinks it is a standard file backup and executes 'save' instead (look at the error) and of course the filesystem MSSQL: does not exist for file backups.
Thanks for the reply guys ,but the syntax is rigth .
I have triple checked it (by the way I have 8 year experience with Networker) so the reason is else ware .May be the DataDomain is the answer or it config at the networker.I though may be some one had the same problem.
There has to be a workaround that doesn't compromise security though.
Probably new nsrauth (which should be rssauth). Current implementation is just too limited and I see no benefits (and security at this level comes as bonus so I hardly see it as something beneficial in first place).
I do agree with the previous response ,this level of security will not save you so you do not need it (only in especial cases-small or cheep environments –when saving money for sec products ).Now to the case, I do not really know you environment so I would recommend to 1.do the same change on backup sever and relating storage node(if there is one) .
2.clean the clients info in backup> server local hosts>backup server(instance)>delete backup client info.
4.check again the config is right and run the backup.
5.If there is still this issue do a debug level –D 9 when running the backup.
I want to help you so please describe your environment (FW,storage nodes,vtl/boost and ,NW version,DD OS version etc..) so it will be little bit easier.
36115_carloscor
217 Posts
601
0
Posted June 19th, 2011 08:00
Hello Alexey,
This is obviously a wrong syntax.
Can we please have the exact command you are running?
Thank you.
Carlos.