Prev: CALs
Next: Still can not disable password complexity requirements
From: Silvester on 29 Apr 2010 10:04

I posted this over at technet but no luck so i'll try here.

I'll do my best explaining and give all the info you may need.
Running Win 2K8 R1 standard w/ SP2 64-bit
Exchange 2007
NFS service installed

I'm trying to get Granular backup using Netbackup 6.5.4 however no such

luck. Netbackup requires NFS service to be installed however there are
NFS
errors on both exchange and Netbackup and it fails. If I try to restart
NFS
in the services.msc I get error. I then need to restart the server for
NFS
to start again.

I'll copy & paste some of the errors below, I've done A LOT of googling
and
haven't found any solutions except that it may be a problem related to
SP2
and to roll-back...this is not a solution that is feasable to my
manager.

This error when I try to restart the NFS service.

> The Client for NFS service on local computer started and then stopped.
> Some
> services stop automatically if they are not in use by other services or
>
> programs

my last attempt I got this error in the Windows logs:
> Windows(R) failed a request to initialize the Network File System (NFS)
>
> redirector
> <[d:\longhorn\base\fs\remotefs\nfs\client\nfsclient\service.c:199]
> : 0: The operation completed successfully.

> Windows may be low on system resources. Try increasing available system
>
> resources by closing programs, then start Client for NFS manually Client for NFS cannot start.

Other errors that I've seen in past troubleshooting.

> Server for NFS is not configured for either Active Directory Lookup or
> User
> Name Mapping.
>
> Server for NFS could not create all the endpoints configured. Server for
> NFS
> will attempt to continue but some NFS clients may not function
> properly.
>
> Server for NFS creates RPC endpoints to receive requests from Network
> File
> System (NFS) clients. Without any RPC endpoints Server for NFS will not
> be
> able to receive any requests on this computer.
>
> Without either Active Directory Lookup or User Name Mapping, Server for
> NFS
> cannot grant file access to users.
>
> Configure Server for NFS for either Active Directory Lookup or User Name
>
> Mapping using the Nfsadmin command-line tool
> Client for NFS requested a mount with file locking enabled, and the
> remote
> Network File System (NFS) server does not support file locking.
>
> Client for NFS mounted the shared resource anyway. File locking may not
> be
> available.
>
> To avoid this warning in the future, enable file-locking suppport on the
>
> remote NFS server


We are a professional Services company so we have certified staff in
Microsoft and both Netbackup and no one is able to solve the problem.
Our NetBackup guy says he's done this exact install at a client with NO
NFS
configuration and it worked.


--
Silvester
------------------------------------------------------------------------
Silvester's Profile: http://forums.techarena.in/members/214276.htm
View this thread: http://forums.techarena.in/windows-server-help/1332485.htm

http://forums.techarena.in

From: Silvester on 4 May 2010 11:21

anyone have any input?? :(


--
Silvester
------------------------------------------------------------------------
Silvester's Profile: http://forums.techarena.in/members/214276.htm
View this thread: http://forums.techarena.in/windows-server-help/1332485.htm

http://forums.techarena.in

 | 
Pages: 1
Prev: CALs
Next: Still can not disable password complexity requirements