Connecting to a share on Linux via Windows 2003 (SP1) NFS Client Jordansphere Scenario: We have an NFS share on a Centos 6.x server – which other Linux machines use for a data repository. A requirement arose in the network to use a Windows 2003 to server to connect to this share. I believe Windows 2003 SP2 and 2008+ all ship with the NFS Client (although you may need to install/add the feature). Windows 2003 (SP1) does not.

Therefore you’ll need to download and install Windows Services for Unix: When downloaded, unzip and run the Microsoft Installer (SfuSetup.msi) Select Custom install. You’ll ONLY need to install NFS ->NFS Client & Auth Tools for NFS. Deselect the other options. Press Next and the select Local User Name Mapping Server ->Password and group file Before pressing Next at this stage you might want to get a list of groups (/etc/group) and password (/etc/passwd) from your Linux server and put them on your Windows 2003 server.

(i just copied and pasted the relevant users and groups to a file). You’ll see below that I created the files in C: NFSdetails. The windows machine option is a default. Follow the defaults for the rest of the installation.

You may need to reboot the server. On our Linux NFS server we enabled the client name/permissions in the /etc/exports file so user authentication wasn’t necessary. However, I thought I would have a play. This may come in handy if you’re using password based control. (optional) Next we will configure the NFS Client. Start ->All Programs ->Windows Services for UNIX ->Services for UNIX administration. Click Client of NFS I gave full permissions to User and Group.

I wasnt bothered by “ Other“. Next select User Name Mapping. You’ll see the paths you created earlier for passwd/group files under the Configuration tab. Then select Maps at the top. Click the List Windows Users and List UNIX users and select the windows user you want to associate with the Linux user. When selected press Add.

Installation Screen for Windows Services for NFS on Windows Server 2003. Windows Client for NFS. Nov 12, 2008 how to install client nfs on windows 2008. Windows Server. But where can I find and install 'client for NFS'? In windows 2003, it can be found.

You should then see the entry in the Mapped users section below. Press Apply and the click the Configuration tab again.

Select Synchronize Now. You should then be able to map a network drive by right clicking the My Computer ->Map Network Drive. Select the Drive (eg Z:) you want to use and map the folder eg ( 10.0.20.5 fileserver ).

When migrating a SAP system from UNIX/Oracle or UNIX/DB2 to Windows/SQL it is sometimes useful to be able to mount a UNIX file system on a Windows server. The (NFS) is used by most UNIX and Linux operating systems such as Solaris, HPUX, AIX etc. The Windows equivalent of NFS is known as SMB or CIFS SAP fully support “heterogeneous” SAP application servers, that is a UNIX/Oracle or DB2 database server and Windows/Intel application servers.

The Windows platform offers integrated clustering/HA (documented, supported and free of charge from SAP) and single sign on. Windows applications servers are fully supported on both Hyper-V and VMWare. How to Setup Windows to UNIX File System Interoperability There are several technologies to enable connectivity between Windows servers and UNIX operating systems: 1. Samba is a freeware software available from that exposes UNIX server file systems as Windows (actually SMB Compatible) shares. Samba also allows some integration into Microsoft Windows Domains & Active Directory. Samba is configured and managed on the UNIX server and requires installation/configuration by the UNIX administrator 2. Windows 2003 has an add on component called has a component called Client for NFS.

Services for UNIX setup is used to. Windows 2008 and Windows 2008 R2 the Services for Network File System have been made part of the File Server Role. Bukhari Shareef Hadees In Hindi Download. The Server Manager tool is used to as of Windows 2008 or later. Windows 2008 and higher also has additional interoperability features for UNIX environments called however installation of this component is not required to enable simple NFS connectivity In all cases it is highly recommended to use the Windows 2008 R2 product if possible.

Check the or post a question in this blog to verify if your SAP version is supported on Windows 2008 R2. In general all SAP Kernel 7.0 or higher systems are supported on. Installation Tasks: 1. Follow the and basic configuration To install Services for NFS components 1. Click Start, point to Administrative Tools, and then click Server Manager. In the left pane, click Roles.

Under Roles Summary in the right pane, click Add Roles. The Add Roles Wizard appears. Select the File Services check box to install this role on the server, and then click Next. Select the Services for Network File System check box, and then click Next. Confirm your selection, and then click Install. When the installation completes, the installation results appear. Logon to the UNIX host and type id –u adm id –g adm or while logged on as adm type id 3.

The next step involves “mapping” the Windows user id to the UID and GID of the adm account on the UNIX server There are three ways of doing this, however in most cases we recommend option #1 Username mapping: #1 Configure the explained in this blog – (Recommended technique) #2 Configure or (for Win2008 or higher) – optional #3 if required (for ) – optional 4. Ensure the Windows host is defined in the /etc/hosts file on the UNIX server. Add the UNIX server to the Windows Drivers etc hosts file on the Windows server 5. Ensure NFS configuration (/etc/dfs/dfstab or similar) on the UNIX server is correct – the Windows hostname must be allowed to mount the file system usually 6. Using Windows Explorer or command line with the unixserver:/export (recommended) or use the traditional Windows 7. Test creating and deleting a file 8. Install a SAP instance using SAPInst or use SAPInst to export the UNIX/Oracle system to Win/SQL Note: SAP requires that the NFS connection has a drive letter.

It is therefore always necessary to logon the Windows host and ensure the NFS drives are connected prior to starting the SAP application server. NFS is not a particularly robust protocol therefore it is not to be used as a Export or Import location. It is not permitted to export an SAP system to dump files on an NFS source. In addition it is not recommended to store dump files on a NFS source and import on a Windows server.

Always read/write to dump files on a local disk Several Great Uses of Windows to UNIX File System Interoperability During OS/DB Migrations from proprietary UNIX systems to Intel/AMD commodity solutions the R3LOAD export/dump files need to be transferred to Windows. SAP Migration Monitor supports FTP to transfer dump files to a Windows environment. However this requires the installation of FTP on the Windows server. There are three good reasons for establishing Windows to UNIX interoperability: 1. The ability to use powerful Intel/AMD servers for the Migration. This will greatly speed up the export/import process 2. The ability to use SAPInst GUI to complete the full OS/DB Migration process without the need to use command line tools.

Has been documented in this blog, however the latest versions of SAPInst for SAP Kernel 7.0 systems and higher can be exported/imported provided that the UNIX file system containing the SAP profiles is exposed. SAPInst will check the profile directory before starting the export. Provided a Wintel server can access the profile directory, SAPInst will allow a GUI based export of a UNIX system. Increasing numbers of customers are using modern Intel and AMD servers as SAP application servers connecting to UNIX database servers. Modern Intel and AMD based servers are vastly cheaper than proprietary UNIX servers and deliver comparable or better performance. SAP OLTP type applications such as ECC 6.0 usually require 60% to 80% of the system CPU resources on the Application Tier with the remainder on the Database Tier.

Therefore 60% to 80% of the SAPS (Unit of SAP workload sizing) can run on low cost Intel or AMD commodity servers. As of February 2010 a typical fully configured SAP application server deployed in our customer base costs less than $15,000 inclusive of 96-128GB RAM service & support. A typical medium size SAP system may have about 100,000 SAPS in total with 30,000 SAPS for Database Layer and about 70,000 SAPS for the SAP Application Layer (a typical 30% Database / 70% Application Tier split). In this hypothetical case where the application workload requirement is equal to 70,000 SAPS, this requirement can be met with only 3 Intel or AMD servers at a cost of approximately $45,000 in total. The energy consumption is much lower than UNIX systems and the rack space required is only 2U each or less if blades are used. Many customers compare the workload capabilities of modern Intel and AMD based servers and the total all up cost including Operating System License, Energy/Aircon/rackspace, 3 year maintenance and administration + OS patching costs ( practically zero for a Windows 2008 R2 server with and all other ) find that Intel/AMD based systems cost is 1/8 th to 1/10 th that of proprietary UNIX platforms.

Additional information about vs. UNIX system and. Windows NFS Services also allows a customer to preserve a single SAP Transport directory and domain during a migration from UNIX/Oracle to Win/SQL.

During a period of 2-6 weeks the Dev and QAS systems are running on Win/SQL and the Production system is running on UNIX/Oracle. It is still supported to transport configuration settings, SAP Security and ABAP programs from a Win/SQL Development system to a Production system running on UNIX/Oracle (because SAP is largely OS/DB independent). Useful Links Below are some useful links. If you have any questions feel free to post them in this blog. – a very good overview of setup and configuration process for Win2003 – a generic overview of UNIX side configuration – troubleshooting NFS Client (Win2008 R2) – general overview of NFS Client (Win2008 R2) More information on SAP Benchmarks can be found on the. The above statements about SAPS as unit of SAP sizing and cost of various hardware platforms are derived out from real SAP customer deployment or migration.

The term “SAPS” is used as a measure of equivalent workload. Thanks to: Ashish Sahu – owner of Warwick Chai – owner of. >In all cases it is highly recommended to use the Windows 2008 R2 product if possible. What specific advantages does the 2008r2 implementation have over the 2003r2 one?

It's just that 2003 has the superior GUI, flatter configuration layout and organisation, etc. Which just makes it far more productive to use in general. >NFS is not a particularly robust protocol In what way does it lack robustness?

Most UNIX facilities are highly robust. If I have Solaris 11.1 and Windows Server 2003 r2 x64, which would be more reliable: 1. Configure Solaris to use SMB/CIFS so Windows doesn't have to do anything exotic; 2.

Configure Windows to use NFS so Solaris doesn't have to do anything exotic? My previous research has indicated NFS is a superior, faster, more efficient protocol. Your webpage is the first I have seen to claim the opposite. I would like to see your rationale. Hi, In our environment, SAP team accessing a share from SAMBA server (samba1) through Windows 2008 (win1) and SAP instances (DSAP) are running on that windows box. Driver Scanner Mustek Se A3 Usb 1200 Pro on this page.

Suddenly SAP team got Transport error and they found that they are not able to access NFS share ( samba1.xx.xx) from Win1 windows server but they are able to access the same NFS share ( samba1.xx.xx) from other windows server (win2,win3, etc). So we thought the problem in permission from this win1 server, but the permission is perfect like previous stage which was working time. Finally, we did reboot then the share ( samba1.xx.xx) is accessible from win1 server.

So could you please tell me what would be the cause for this issue and how can rectify it for future. (it happens 2 times).