
Solved!
Go to SolutionBacking up Windows 2008 R2 on NW 7.4.5 - VSS Error
running Networker 7.4.3 on windows 2003, the client windows 2008 R2, networker 7.4 SP5 64bit.
cannot backup the client because of : Error: the client is giving error: unable to set up VSS filesystem directives
Responses (27)
Solutions (0)
Hello - Here is a link to the NW 7.5 SP3 for Windows x64 package >
http://powerlink.emc.com/km/live1/en_US/Offering_Technical/Software_Download/nw75sp3_win_x64.zip
Support > Software Downloads and Licensing > Downloads J-O > Networker then scroll down to the Networker 7.5 SP3 section.
Thanks.
Reply Hello - Seems you are trying to backup a W2K8 R2 client with NW 7.4.5 .
Please bear inmind that this is not supported.
NW 7.5.3 needs to be installed on the client in order to backup W2K8 R2.
Please apply the supported version and let me know the results.
Thanks.
Reply Anandkrishna
36 Posts
1208
0
Posted July 26th, 2010 13:00
Hello Mostafa
NW 7.5.2 and NW 7.5.3 are the only version that supports the backup of win2k8 R2. I have attached the NW software compatibility guide for further reference. Kindly let me know if you need any further assistance on this.
1 Attachment
InformationProtection_SCG.pdf
InformationProtection_SCG.pdf
Reply I installed like suggested, Networker 7.5 SP3 64 bitsBuilt415 on the client, and started getting this error from the client:
39078: winworkr:SYSTEM error:client'142.x.x.x" is not properly configured on the networker server
I am no longer getting any error regarding VSS since I installed networker client 7.5
You'r help is very appreciated.
Thanks,
Mostafa
Reply Hello - Seems you have passed the VSS issuse and now dealing with a possible cliet config issue.
Bear inmind that you cannot disable VSS (backup) with W2K8 therefore VSS=off is no longer applicable.
Focusing on the new error "client'142.x.x.x" is not properly configured on the networker server"
Please do the following and let me know the results:
- on the NW server, stop nsr services
- rename /nsr/tmp/ folder to /nsr/tmp_old
- start nsr services
(I suspect NW server may still have cached info regarding the client prior to the upgrade, clearing the cache would resolve this)
Test the backup and let me know the results.
If the error persist you may email me the NW server's daemon.raw at stamp_john@emc.com
Thanks.
John
Reply

jstamp
88 Posts
1647
0
Posted July 27th, 2010 12:00
Hi Mostafa,
If the client enabler code is set to no, then this means the client somehow has not been granted a license or unable to retrieve a license.
Please run the command nsrlic -v in order to review your current license allocation status.
If the client connection licenses have been exhausted, here is a temp enabler for 5 client connections
d25054-902ea0-765698 .
Please note that you will need to contact licensing to aquire the auth codes and proper licenses as per your entitlement.
Licensing may be contacted at (408)566-2000 or licensing@emc.com
Thanks.
John