Hi community!

I am currently observing the following behavior on our NetWorker 9.0.0.6 server on Windows 2012R2.

I set up a client and entered two save sets for the client:

C:\Program Files\tools

X:

The X: is a drive letter that does not exist on the client. I did this just for curiosity how to find out what error message will show up when NetWorker tries to save "X:". Suprisingly I get no indication of an error at all in the monitoring view. When digging in the logs/policy directory I found the following log. There at least an info shows up that X: does not exist. The client level is also 9.0.0.6.

C:\Program Files\EMC NetWorker\nsr\logs\policy\Bronze\Failing Clients\backup_000887_logs\889.log

6999:save: X:: No such file or directory

nw-srv-9.company.com: C:\Program Files\tools level=incr, 0 KB 00:00:00      0 files

Completed savetime=1464352391

90015:save: The backup of VSS emit save set 'C:\Program Files\tools' succeeded.

94694:save: The backup of save set 'C:\Program Files\tools' succeeded.

94694:save: The backup of save set 'pseudo_saveset' succeeded.

94694:save: The backup of save set 'pseudo_saveset' succeeded.

The following questions came up here regarding this:

* Can someone confirm this behavior?

* Is this a bug or a feature?

* Is there any option to get NetWorker to report this as an error in the managment console monitoring view?

Best wishes

Stefan