Studio Press

Just another Blogger Blog

Small Business Server Support

How to Install the File Server Resource Manager Services?

As with all Windows Server 2003 R2 features, the File Server Resource Manager component must be installed via the Add/Remove Windows Components module. To install the component, follow these steps:

  1. Start the Add/Remove Programs Control Panel applet (Start, Settings, Control Panel, Add or Remove Programs).
  2. Click Add/Remove Windows Components.
  3. Select "Management and Monitoring Tools" and click Details.
  4. Select the File Server Resource Manager check box, as the figure at http://www.windowsitpro.com/articles/images/2003r2filescrenfsrminstall.gif shows.
  5. Click OK.
  6. Click Next to the main Windows Components dialog box.
  7. Click Finish. You'll need to reboot for the changes to take effect.
From: http://windowsitpro.com/article/articleid/49718/how-do-i-install-the-file-server-resource-manager-services.html

How to "Clone" a File Service to a New File Server

As an admin, you might want to move all file services from a NetWare or OES 1 server to an OES 2 Linux server on new hardware with both the migration source and destination servers being in the same directory. You want to do that without disrupting your users.

Here is a step-by-step process for planning and carrying out the migration:

  • Step One: Install an OES 2 Linux file server with NSS
You'll want to have significantly more storage space on the migration destination server than the source server. As part of installing NSS, you should create a pool for the new storage. You can use NSSMU to set up a pool for all volumes. When you use NSSMU to do this, activate the drive that you're going to place NSS on, and set up the pool and name it. Set up the pool to consume all the drive space.
  • Step Two: Migrate all file data from the source server to the migration destination server
Assume that you have enough data that you think it will take a week to migrate. On Monday night after your end users go home, start the data migration process. Do is by logging in as root on the destination server and running the following command:
 migfiles -s  -n -P POOL [-m]
Do this every night through the week after your users go home. The first time that this command is ran, omit the -m option. The mig files command picks up where it left off the night before in migrating the source server data.
  • Step Three: Modify user working directory
Run the following command:
 mls -s  > mls.yaml
The mls command lists all files, trustees, attributes, and quotas from the source server.
 maptrustees -s  -d  maptrustees.yaml
Then run
 migtrustees -d  maptrustees.yaml
is the LDAP server address for both the source and destination servers.
  • Step Four: After the data is moved, migrate file rights, attributes, and quotas
If a large data set is involved you should give yourself sufficient time for this.
Rights, attributes, and quotas are migrated by running the following command:

After running this command, run the following command:

 maprights -n mls.yaml > maprights.yaml
The maprights command sets up mappings to the destination NSS file system.
Finally, run the following command:
 migrights maprights.yaml
The migrights command applies all mappings to the destination NSS file system.
  • Step Five: Notify users to log in again
The last step is to ask users to log in again. If you want to send a message to your users, you can create a message file with the command vi message. Type in something like this.
Dear #{first} #{last},

We have finished migrating your files onto the new file server. In order to transfer over to the new system, you will need to relogin to your computer.

Regards,
#{from} of your friendly IT staff.
After creating this file, named message, run the following command:
 mignotify -a login -e myusername@mycompany.com -s smtp.mycompany.com -m message -i maptrustees.yaml
This will email the message you created to all of your users who have had their file services migrated, if the mail attribute has been set in e Directory for your users.
  • Notes of Interest
This scenario was for cloning the file servers on the same directory server. To clone a file server into another directory, run maptrustees with the -r option. This generates random passwords for your users. Then, run migtrustees with the destination LDAP server in the new directory. After this, notify the users of a password change using mignotify by using the #{password} variable the message file.
The migfiles, migtrustees, and migrights commands all have -i flag for --verbose-information. If you want to see the status of these utilities as they are running, then use this flag.
You can also just pipe commands as follows:
 mls -s  | maprights -n | migrights -i

Source: http://wiki.novell.com/index.php/How_to_%22clone%22_a_file_service_to_a_new_file_server

key reasons to deploy Distributed File Services in Windows Server 2003 R2

The following key reasons to deploy Distributed File Services (DFS) in Windows Server 2003 R2 highlight major new features and improvements.

1. Effective WAN network usage

Only changes made to a file need to be transmitted over the WAN, thanks to the remote differential compression (RDC) algorithm, which serves as the basis for DFS Replication.

2. Potential to eliminate backup processes at the branch office

With an efficient, wide area network (WAN)–friendly way to collect content for the corporate central office, DFS Replication makes it possible to eliminate the local backup at the branch and rely on daily backup from the corporate office.

3. High availability

A namespace offers a simple way to redirect users to other servers that contain required data when their primary server is down, helping to achieve a higher level of server availability. You can use DFS Replication to synchronize data on all servers that host a particular folder in the namespace. As a result, no matter which folder the user connects to, the user sees the same data.

4. Ease of data access with namespace virtualization

A namespace offers uniform access across multiple file servers, making it easier for users to “remember” their server names and easily access their data.

5. Ease of publishing content to branch locations from the central office

DFS Replication makes it is easy to distribute core content in the corporate central office to all remote offices.

6. Local access for users without going across the WAN

With content easily publishable to local servers that are part of a namespace, users in branch offices can access their data locally. If a server malfunctions, the namespace automatically refers clients to the next closest server.

7. Easier management of data and server locations

IT administrators benefit from a new, easy-to-use Microsoft Management Console snap-in called DFS Management. This snap-in greatly simplifies the management of DFS Replication and DFS Namespaces.

8. Large-scale deployments

DFS Replication is a scalable, reliable, multimaster replicator that can scale to several thousand nodes and arbitrary topologies because it stores its configuration in Active Directory. You can achieve large fan-out deployments by using hub-and-spoke topologies.

Source: http://www.microsoft.com/windowsserver2003/technologies/storage/dfs/topdeploy.mspx

History of File Servers

In the mid-1980s enterprises became increasingly interested in ways to connect a rapidly growing population of personal computers. Novell proposed an approach using software to connect each workstation to a network file server that would manage both the network and access to network resources. At the same time 3Com Corporation was creating Ethernet adapter cards, building hardware connectivity needed for such approach.

Novell grew upon the strength of its Netware operating system, used for file serving, and by the late 1980s had a 50% market share of local area networks. Seeing the potential growth in this arena IBM and Microsoft both introduced their own file server strategies.

Twenty years after its peak, Novell and 3Com have virtually disappeared from the Server market; today disk servers (a NAS or a SAN) supplied by one of the leading vendors such as EMC or NetApp are typically attached to a file server running the Microsoft Windows or Linux operating systems. Large data centers, that serve millions of customers (such as Google's), run server farms on specialized equipment with large, complex operating systems.

Types of file servers

A file server may be dedicated or non-dedicated. A dedicated server is generally designed specifically for use as a file server, with workstations attached for reading and writing files and databases. A workstation may share files with other workstations on the network directly however by turning on its "Server" service and then by creating a "Share" -- this process creates a non-dedicated file server that is primarily being used as a workstation.

File servers may also be categorized by the method of access: Internet file servers are frequently accessed by File Transfer Protocol (FTP) or by HTTP (but are different from web servers, that often provide dynamic web content in addition to static files). Servers on a LAN are usually accessed by SMB/CIFS protocol or NFS protocol. Database servers, that provide access to a shared database via a database device driver, are not regarded as file servers. Most file servers are simultaneously print servers too, as they provide access to printers via network. A single file serving computer may be accessible by multiple means: it may run an FTP server, an CIFS server, etc., serving the same files.

Design of file servers

In modern businesses the design of file servers is complicated by competing demands for storage space, access speed, recoverability, ease of administration, security, and budget. This is further complicated by a constantly changing environment, where new hardware and technology rapidly obsoletes old equipment, and yet must seamlessly come online in a fashion compatible with the older machinery. To manage throughput, peak loads, and response time, vendors may utilize queuing theory to model how the combination of hardware and software will respond over various levels of demand. Servers may also employ dynamic load balancing scheme to distribute requests across various pieces of hardware.

The primary piece of hardware equipment for servers over the last couple of decades has proven to be the hard disk drive. Although other forms of storage are viable (such as magnetic tape and RAM) disk drives have continued to offer the best fit for cost, performance, and capacity.

Storage

Since the crucial function of a file server is storage, hardware has been developed to operate multiple disk drives together as a team, forming a disk array. A disk array typically has cache (temporary memory storage that is faster than the magnetic disks), as well as advanced functions like RAID and storage virtualization. Typically disk arrays increase level of availability by using redundant components other than RAID, such as power supplies. Disk arrays may be consolidated or virtualized in a storage area network (SAN).

Filers

In 1990s, introduction of specialized file serving devices, the NetApp filers, popularized the concept of network-attached storage (NAS). To this time, file servers were still implemented with general-purpose servers and OSes. NetApp changed this with introducing specialized network appliances, with a proprietary software and scalable to multiple disk enclosures holding tens or hundreds of disks grouped in multiple disk arrays. Filers later extended to non-file protocols, such as iSCSI, but still NAS is popularly perceived as mainly a file serving technology.

Security

File servers generally offer some form of system security to limit access to files to specific users or groups. In large organizations, this is a task usually delegated to what is known as directory services such as openLDAP, Novell's eDirectory or Microsoft's Active Directory.

These servers work within the hierarchical computing environment which treat users, computers, applications and files as distinct but related entities on the network and grant access based on user or group credentials. In many cases, the directory service spans many file servers, potentially hundreds for large organizations. In the past, and in smaller organizations, authentication can take place directly to the server itself.

Source: http://www.answers.com/topic/file-server
iYogi Server Services

Labels