You are on page 1of 23

Overview of the Microsoft File Server

Migration Toolkit
Microsoft Corporation
Published: September 2008
Abstract
The File Server Migration Toolkit helps ou cop files and folders from servers running
Microsoft! "indo#s! 200$ Server% Microsoft! "indo#s! 2000 Server or Microsoft!
"indo#s &T! Server '(0 operating sstems to a server running Microsoft!
"indo#s Server) 2008 or Microsoft! "indo#s! Storage Server 2008( "hether ou
plan to consolidate multiple file servers or migrate data from one file server to another%
the File Server Migration Toolkit is designed to simplif the process of coping data and
minimi*e the impact of the consolidation or migration on end users(
This #hite paper briefl describes the tools included in the File Server Migration Toolkit%
their benefits% and their re+uirements(
The information contained in this document represents the current view of Microsoft
Corporation on the issues discussed as of the date of publication. Because Microsoft
must respond to changing market conditions, it should not be interpreted to be a
commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of
any information presented after the date of publication.
This White Paper is for informational purposes only. MC!"#"$T M%&'# ("
W%!!%(T'#, ')P!'##, MP*'+ "! #T%T,T"!-, %# T" T.' ($"!M%T"( (
T.# +"C,M'(T.
Complying with all applicable copyright laws is the responsibility of the user. Without
limiting the rights under copyright, no part of this document may be reproduced, stored in
or introduced into a retrieval system, or transmitted in any form or by any means
/electronic, mechanical, photocopying, recording, or otherwise0, or for any purpose,
without the e1press written permission of Microsoft Corporation.
Microsoft may have patents, patent applications, trademarks, copyrights, or other
intellectual property rights covering sub2ect matter in this document. '1cept as e1pressly
provided in any written license agreement from Microsoft, the furnishing of this document
does not give you any license to these patents, trademarks, copyrights, or other
intellectual property.
,nless otherwise noted, the e1ample companies, organi3ations, products, domain
names, e4mail addresses, logos, people, places, and events depicted herein are
fictitious, and no association with any real company, organi3ation, product, domain name,
e4mail address, logo, person, place, or event is intended or should be inferred.
5 6778 Microsoft Corporation. %ll rights reserved.
Microsoft, Windows, Windows (T, Windows #erver, Windows #erver #ystem are either
registered trademarks or trademarks of Microsoft Corporation in the ,nited #tates and9or
other countries.
The names of actual companies and products mentioned herein may be the trademarks
of their respective owners.
Contents
,vervie# of the Microsoft File Server Migration Toolkit((((((((((((((((((((((((((((((((((((((((((((((((((((((-
Contents((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((( $
,vervie# of the Microsoft File Server Migration Toolkit((((((((((((((((((((((((((((((((((((((((((((((((((((((.
/ntroduction to the Microsoft File Server Migration Toolkit(((((((((((((((((((((((((((((((((((((((((((((((.
File Server Migration Toolkit 0enefits(((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((( 1
File Server Migration "i*ard ,vervie#((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((( 8
2FS Consolidation 3oot "i*ard and 2fsconsolidate(e4e ,vervie#((((((((((((((((((((((((((((((--
Consolidation and Migration Scenario(((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((( -2
Sstem and 5ccount 3e+uirements(((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((( -1
Scalabilit Considerations for 2FS Consolidation 3oots(((((((((((((((((((((((((((((((((((((((((((((((-6
5dditional 3esources(((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((( -6
5ppendi4: 0asic 2FS Creation and Startup Performance(((((((((((((((((((((((((((((((((((((((((((((2-
Overview of the Microsoft File Server
Migration Toolkit
Introduction to the Microsoft File Server
Migration Toolkit
Microsoft! "indo#s! server technologies deliver lo# total cost of o#nership 7TC,8 and
reliable file services that are essential to enterprise computing infrastructures( The
Microsoft! "indo#s Server) 2008 operating sstems deliver an e4citing set of
customer9focused improvements in file services% especiall for customers currentl using
Microsoft! "indo#s &T! Server 200$ SP- to provide file services(
The File Server Migration Toolkit helps ou cop files and folders from servers running
Microsoft! "indo#s! 200$ Server% Microsoft! "indo#s! 2000 Server or "indo#s &T
Server '(0 operating sstems to a server running "indo#s Server 200$% "indo#s
Storage Server 200$% "indo#s Server 2008 or Microsoft! "indo#s! Storage
Server 2008( "hether ou plan to consolidate multiple file servers or migrate data from
one file server to another% the File Server Migration Toolkit is designed to simplif the
process of coping data and minimi*e the impact of the consolidation or migration on end
users(
5fter the consolidation or migration is complete% our organi*ation can take advantage of
features in "indo#s Server 2008 such as Shado# Copies for Shared Folders% and
enhancements to other technologies% such as 2istributed File Sstem 72FS8 and File
Services 3esource Manager 7FS3M8( For more information about file services available
in "indo#s Server 2008% see the technical overvie# of "indo#s Server 2008 File
Services at http:::technet(microsoft(com:en9us:librar:cc;;-.'8(asp4(
The tools provided in the File Server Migration Toolkit are described belo#( For
information about the tool re+uirements% including server and client compatibilit% see
<Sstem and 5ccount 3e+uirements= later in this document(
File Server Migration Wizard
The File Server Migration "i*ard is a graphical user interface 7>?/8 tool for coping files%
folders% and their securit settings from one or more source file servers to a target file
server( The #i*ard #alks ou step b step through the cop process% #hich includes
creating a migration pro@ect #here pro@ect9specific settings are stored% monitoring the
5
progress of the file coping% and vie#ing a final report of the coping results( Aou can
start and stop a migration pro@ect at an time% and settings are maintained for that pro@ect
the ne4t time ou start the #i*ard(
FS Consolidation !oot Wizard
The 2FS Consolidation 3oot "i*ard reduces the impact of file server consolidation or
migration on end users b maintaining the original ?niversal &aming Convention 7?&C8
paths of files and folders after the are copied to a ne# server( 0ecause the original ?&C
paths are maintained% ou do not need to inform users about ne# server names% and line9
of9business applications as #ell as shortcuts and ,BC links in user files and e9mail
messages continue to #ork after the consolidation or migration is complete(
fsconsolidate"e#e co$$and%line tool
2fsconsolidate(e4e is the command9line tool that is invoked b the 2FS Consolidation
3oot "i*ard to perform the tasks that are necessar to maintain the original ?&C paths
of files and folders( Aou can use 2fsconsolidate(e4e to create ne# 2FS consolidation
roots% modif or correct settings that ou specified in the 2FS Consolidation 3oot "i*ard%
and remove 2FS consolidation roots and settings that ou originall created b using the
2FS Consolidation 3oot "i*ard(
File Server Migration Toolkit &enefits
The File Server Migration Toolkit provides the follo#ing benefits(
Si$'lifies the co$'le# and error%'rone $igration 'rocess
The File Server Migration "i*ard validates all settings before coping files to ensure that
coping #ill complete successfull( 5n errors and #arnings encountered during
validation are provided in the report for ou to revie# before continuing the migration( The
initial coping of data does not re+uire do#ntime of the source file servers% and ou can
re9run the coping process as man times as necessar to re9cop files that have
changed since the last coping pass( Choosing #hether to cop securit settings is eas
D @ust select the securit9related options in the #i*ard( The File Server Migration "i*ard
also provides an option to stop sharing source folders after the migration is complete(
Maintains ()C 'aths and eli$inates broken shortcuts and links
?sing 2FS consolidation roots to maintain the original ?&C paths of files ensures a
transparent migration e4perience for end users( There is no need to use a separate utilit
that can identif and fi4 broken links on client computers% such as ,BC links or
application9related links in the registr( ?sers can continue to access shared folders @ust
*
as the did prior to the migration% and line9of9business applications continue to #ork
correctl(
Maintains securit+ settings after the $igration
To ensure the securit of files and folders after the are migrated to a target file server%
the File Server Migration "i*ard applies permissions that are the same as or more
restrictive than the #ere on the source files and folders% depending on the option ou
select( For e4ample% if ou do not choose to cop securit settings from the source to the
target files and folders% the #i*ard applies permissions to the target files% folders% and
shared folders b granting Full Control permission to the local 5dministrators group of the
target file server( /f ou select the Co'+ securit+ settings option% the File Server
Migration "i*ard copies all securit settings for files% folders% and shared folders%
including &TFS file sstem permissions% auditing% o#nership% and shared folder
permissions( /f ou also select the !esolve invalid securit+ descri'tors option% the
#i*ard cleans up securit descriptors #hose securit identifiers 7S/2s8 cannot be
resolved on the target file server(
Consolidates shared folders with the sa$e na$es fro$ different servers
Migrating shared folders from multiple source file servers to a single target file server can
result in name conflicts if t#o or more shared folders have the same name( For e4ample%
a shared folder called Teams on source file servers named FS- and FS2 #ill cause a
conflict if the are both copied to the same target file server named Corp9FS9- because
the ?&C path EECorp9FS9-ETeams can represent onl one of the shared folders( The File
Server Migration "i*ard eliminates this problem b using default target shared folder
names that have the format #harename:#ource#erver(ame% #here #harename is the
name of the shared folder on the source file server% and #ource#erver(ame is the name
of the source file server( Aou can modif the default target shared folder name for each
source folder prior to beginning the migration(
Su''orts server clusters as source and target file servers
The 2FS Consolidation 3oot "i*ard and 2fsconsolidate(e4e can create 2FS
consolidation roots on server clusters% and the File Server Migration "i*ard can create
the necessar File Share resources to represent shared folders on the target server
clusters(
,rovides roll%back functionalit+
/f net#ork connectivit or other problems prevent the File Server Migration "i*ard from
completing the migration successfull% the #i*ard can attempt to restore access to the
source file servers( This roll9back process allo#s users to continue accessing data on the
-
source file servers #hile ou investigate and repair the problem and then complete the
migration(
File Server Migration Wizard Overview
The File Server Migration "i*ard provides a number of options for coping data( For
e4ample% ou can:
Cop permission% auditing% and o#nership information that is associated #ith files
and folders(
3esolve invalid securit descriptors on the target files and folders(
Stop sharing the shared folders on the source file servers after the coping is
finali*ed(
Prestage the target file serverDfor e4ample% b restoring a backup of the source
file serverDand then use the File Server Migration "i*ard to recop changed files
and share the target folders(
Specif the 2FS root server that hosts 2FS consolidation roots that are created
b the 2FS Consolidation 3oot "i*ard( "hen ou select this setting% the 2FS links
that correspond to each copied folder are updated #ith the ne# ?niversal &aming
Convention 7?&C8 paths of the target folders(
Specif an e4isting 2FS namespace #here ou #ant to add 2FS links for each
copied shared folder( Aou can select this setting even if ou do not use the 2FS
Consolidation 3oot "i*ard(
The File Server Migration "i*ard does not provide the follo#ing features:
Bocal group migration
0and#idth throttling
Migrating files and folders from servers running operating sstems other than
"indo#s Server 200$% "indo#s 2000 Server% "indo#s &T Server '(0% or "indo#s
Storage Server 200$(
The follo#ing sections describe the four phases of the File Server Migration "i*ard(
Setu' 'hase
2uring this phase% ou set up a migration pro@ect b customi*ing settings related to the
migration( For e4ample% ou select the source file servers% specif the location to migrate
the files to on the target server% and so forth( These settings are stored in an (FMB pro@ect
.
file% #hich allo#s ou to stop a migration pro@ect at an time and return to the settings the
ne4t time ou start the File Server Migration "i*ard(
5fter ou configure settings% the File Server Migration "i*ard validates our settings and
creates a report that describes successful validation tasks and #arns ou about potential
conflicts or other problems that might be encountered during the migration( The figure
belo# illustrates the File Server Migration "i*ard after it has completed the Setup phase(
Co'+ 'hase
2uring this phase% the File Server Migration "i*ard creates the target folders and begins
coping files from the source file servers to the target file server( &o server do#ntime
occurs during this phase( ,pen files #ill be skipped during this phase but #ill be closed
and copied during the Finali*e phase(
The #i*ard sho#s the coping progress for the entire pro@ect and for a selected shared
folder as illustrated in the follo#ing figure(
/
5t the end of this phase% the File Server Migration "i*ard creates a report that describes
successful and failed cop attempts( Aou can repeat this phase multiple timesG onl
changed files #ill be copied in successive attempts(
Finalize 'hase
2uring this phase% the File Server Migration "i*ard completes the migration( 0ecause
users are disconnected from the source file servers during this phase% #e recommend
that ou begin this phase during a maintenance #indo#( "hen the Finali*e phase is
complete% the File Server Migration "i*ard creates a report that describes the final
results of the coping( /f the Finali*e phase is not successful% ou have the option of
rolling back servers to a prefinali*e state(
Co$'lete 'hase
2uring this phase% ou can vie# a report that contains details about the source file
servers and shared folders that #ere copied( The report also contains links to (t4t files
that describe an errors that occurred #hen individual files #ere copied(
The follo#ing figure illustrates the report that is created after the migration is complete(
01
FS Consolidation !oot Wizard and
fsconsolidate"e#e Overview
To maintain the original ?&C paths of files% the 2FS Consolidation 3oot "i*ard and
2fsconsolidate(e4e use ne# functionalit in 2istributed File Sstem 72FS8( These tools
also modif 2omain &ame Sstem 72&S8 records and "indo#s /nternet &ame Service
7"/&S8 records 7through registr entries8 for nonclustered servers( For server clusters%
the tools create a &et#ork &ame resource( These modifications enable users #ho
attempt to access the original ?&C path of the files to be redirected to the 2FS root
server that hosts the namespace( The 2FS root server sends the client a referral that
contains the current ?&C path of the files( "hether the files still reside on the source file
server 7before the files are migrated8 or #hether the reside on the target file server 7after
the files are migrated8% users can continue to access the files b using their original ?&C
path(
00
The follo#ing figure illustrates a page in the 2FS Consolidation 3oot "i*ard( ,n this
page% ou specif the original names of the servers #hose ?&C paths ou #ant to
maintain% and ou specif the current names of the servers after the #ere renamed(
7The servers must be renamed prior to running this #i*ard to allo# the 2FS root server to
respond to re+uests from clients to access the original server names(8
)ote
5fter ou complete the migration% ou can use the 2istributed File Sstem snap9
in% the 2fscmd(e4e command9line tool% and the 2fsutil(e4e command9line tool to
manage 2FS namespaces created b the 2FS Consolidation 3oot "i*ard(
Consolidation and Migration Scenario
This scenario describes a fictional consolidation and migration pro@ect to illustrate ho#
the #i*ards in the File Server Migration Toolkit interact% the changes that the make% and
ho# the original ?niversal &aming Convention 7?&C8 paths are maintained(
/n this scenario% an administrator #ants to consolidate three source file servers running
"indo#s Server 2008 into a single server running "indo#s Server 2008( The
administrator also #ants to maintain the original ?&C paths of the files after the are
02
migrated( The source file server names% source shared folder names% and original ?&C
paths that are used in this scenario are sho#n in the follo#ing table(
Source file server Source shared folder na$es Original ()C 'ath
FS- Teams EEFS-ETeams
Templates EEFS-ETemplates
FS2 Teams EEFS2ETeams
Tools EEFS2ETools
FS$ 5rchive EEFS$E5rchive
Public EEFS$EPublic
These servers are illustrated in the follo#ing figure(
The t#o phases of the migration are setting up 2FS consolidation roots and migrating the
data to the target file server% described as follo#s(
Setting u' FS consolidation roots
2uring a maintenance #indo#% the administrator begins the process of setting up 2FS
consolidation roots to maintain the original ?&C paths of files( The steps in this process
are as follo#s:
-( The administrator renames the source file servers to FS-93et% FS293et% and
FS$93et% #here <3et= means <3etired(= 73enaming the source file servers is
necessar so that the 2FS root server can respond to users #ho attempt to access
the original server names( 3enaming a server re+uires ou to restart the server%
#hich is #h this task is performed during a maintenance #indo#(8
2( The administrator runs the 2FS Consolidation 3oot "i*ard% #hich sets up 2FS
consolidation roots for each of the source file servers and creates 2FS links for each
03
of the source shared folders( The 2FS consolidation roots and 2FS links are created
on a server named 2FS9-% as sho#n in the follo#ing table(
FS consolidation
root na$e
FS link na$e ()C 'ath of FS link
target
Original ()C 'ath
HFS- Teams EEFS-93etETeams EEFS-ETeams
Templates EEFS-93etETemplates EEFS-ETemplates
HFS2 Teams EEFS293etETeams EEFS2ETeams
Tools EEFS293etETools EEFS2ETools
HFS$ 5rchive EEFS$93etE5rchive EEFS$E5rchive
Public EEFS$93etEPublic EEFS$EPublic
5t this point% the environment is full functional% and 2istributed File Sstem 72FS8
enables users to access their data b using the original ?&C paths(
Migrating the data to the target file server
"hen the data migration is scheduled to begin% the administrator uses the File Server
Migration "i*ard to set up a migration pro@ect( 5s part of the pro@ect% the administrator
can select various options% such as #hether to cop securit settings% #hether to disable
shared folders on source file servers after migration is finished% and so forth( The
administrator also specifies the name of the 2FS root server% 2FS9-% that hosts the
consolidation roots( This option enables the File Server Migration "i*ard to automaticall
populate the list of source file servers 7as entered in the 2FS Consolidation 3oot "i*ard8
and update the e4isting 2FS link targets to point to the ?&C path of the migrated shared
folders on the target server called C,3P9FS9-(
5fter the migration pro@ect is set up% the administrator uses the File Server Migration
"i*ard to begin coping files from the source file servers to the target file server(
0ecause file coping does not disrupt usersI access to the source file servers% the
coping can take place antime( The administrator can repeat the coping phase to
perform an incremental cop of ne# or changed files(
To complete the migration% the administrator starts the Finali*e phase in the File Server
Migration "i*ard( 0ecause the Finali*e phase disconnects users from the source file
servers% the administrator begins this phase during a maintenance #indo#( /n the Finali*e
phase% the #i*ard snchroni*es all files and folders on the target file server so that the
files% folders% and their securit settings are identical to those on the source file server(
04
"hen the migration is complete% the target file server% C,3P9FS9-% is configured as
sho#n in the follo#ing table(
Target shared folder na$e ()C 'ath of FS link target Original ()C 'ath
TeamsJFS- EEC,3P9FS9-ETeamsJFS- EEFS-ETeams
TemplatesJFS- EEC,3P9FS9
-ETemplatesJFS-
EEFS-ETemplates
TeamsJFS2 EEC,3P9FS9-ETeamsJFS2 EEFS2ETeams
ToolsJFS2 EEC,3P9FS9-EToolsJFS2 EEFS2ETools
5rchiveJFS$ EEC,3P9FS9-E5rchiveJFS$ EEFS$E5rchive
PublicJFS$ EEC,3P9FS9-EPublicJFS$ EEFS$EPublic
/n this table% notice ho# the File Server Migration "i*ard renames the target shared
folder names b appending the source file server name( This prevents shared folder
name conflicts #hen the folders are moved to a single server( Ko#ever% the original ?&C
paths are still maintained as part of the 2FS consolidation roots that are set up b the
2FS Consolidation 3oot "i*ardG therefore% renaming the shared folders does not affect
users( "hen the migration process is complete% the File Server Migration "i*ard updates
the ?&C paths of the 2FS link targets to point to the target file server(
The follo#ing figure illustrates the environment after the migration is complete(
05
S+ste$ and Account !e5uire$ents
Aou can install the File Server Migration Toolkit on 4819 and 41'9based servers running
"indo#s Server 200$% "indo#s Storage Server 200$% "indo#s Server 2008 or
"indo#s Storage Server 2008( The follo#ing sections describe additional re+uirements
for the tools in the toolkit(
FS Consolidation !oot Wizard and fsconsolidate"e#e
re5uire$ents
S+ste$ re5uire$ents
The 2istributed File Sstem 72FS8 root server that hosts 2FS consolidation roots must
meet the follo#ing re+uirements:
The 2FS root server cannot be a domain controller(
The 2FS root server must run "indo#s Server 200$ Cnterprise Cdition SP2%
"indo#s Server 200$ 2atacenter Cdition SP2% "indo#s Storage Server 200$
0*
Cnterprise Cdition% "indo#s Server 2008 2atacenter Cdition or "indo#s Storage
Server 2008 Cnterprise Cdition(
/f the 2FS root server is part of a server cluster% before ou run the 2FS
Consolidation 3oot "i*ard% ou must create the resource group #here the 2FS
consolidation root #ill be created or ou must identif an e4isting resource group( The
resource group must contain an /P 5ddress resource and a Phsical 2isk resource(
"indo#s Fire#all must also allo# "M/ calls as this is ho# the 2FS 3oot Server is
identified as a cluster( See the Microsoft "eb site for connecting to "M/ remotel
starting #ith "indo#s Lista http:::go(microsoft(com:f#link:MBink/2N-202.0( For
similar information for "indo#s Server 200$ and earlier% see the Microsoft "eb site
http:::msdn(microsoft(com:en9us:librar:aa$862607LS(8.8(asp4(
Clients that access the 2FS namespaces that are set up b the 2FS Consolidation 3oot
"i*ard and 2fsconsolidate(e4e must run one of the follo#ing operating sstems or
"indo#s Server Sstem products:
"indo#s Server 200$
"indo#s 2000 Server
"indo#s &T Server '(0 #ith Service Pack 1a 7SP1a8
"indo#s Storage Server 200$
Microsoft! "indo#s! FP Professional
Microsoft! "indo#s! 2000 Professional
Microsoft! "indo#s &T! "orkstation '(0 #ith SP1a
Microsoft! "indo#s! Lista)
Microsoft! "indo#s! Server 2008
I$'ortant
5fter ou run the 2FS Consolidation 3oot "i*ard or 2fsconsolidate(e4e% ou
must delete and recreate all clientsO persistent drive mappings to the maintained
?&C paths( /f ou do not% clients cannot access the consolidated data( 3estarting
the client does not reset persistent drive mappings% so ou must delete and
recreate the mapped drives manuall 7using the net use driveletter6 7delete and
net use driveletter6 88()C'ath commands8 or b using a script( This issue onl
affects persistent drive mappings( 2rives that are mapped through logon scripts
at each log on #ork correctl(
Clients running Microsoft! "indo#s! 68 or Microsoft! "indo#s! 6. cannot access
namespaces that are set up b the 2FS Consolidation 3oot "i*ard( Ko#ever% these
0-
clients can access the migrated shared folders b using the ?&C paths that point to the
ne# file server(
)ote
/f ou are using a non9clustered 2FS root server to host consolidation roots%
client computers #ill use the &TBM authentication protocol #hen the connect to
the 2FS root server( This onl applies #hen a client re+uests 2FS referralsG
#hen a client accesses a file server% the client #ill use #hatever authentication
protocol is supported(
Account re5uire$ents
Aou must be a member of the local 5dministrators group on the 2FS root server that
hosts 2FS consolidation roots(
File Server Migration Wizard re5uire$ents
S+ste$ re5uire$ents
The target file servers and source file servers that ou specif in the File Server Migration
"i*ard must meet the follo#ing re+uirements:
Source file servers must be running "indo#s Server 2008% "indo#s Storage
Server 2008% "indo#s Server 200$% "indo#s Storage Server 200$% "indo#s 2000
Server or "indo#s &T Server '(0(
Target file servers must be running "indo#s Server 2008% "indo#s Storage
Server 2008% "indo#s Server 200$ or "indo#s Storage Server 200$(
Source and target file servers can be server clusters( This re+uires a resource
group to be identified and it must contain a phsical disk resource and at least one
net#ork name not created b the 2FS Consolidation 3oot "i*ard(
"indo#s Fire#all must allo# "M/ calls as the File Server Migration "i*ard uses
"M/ to determine if the source server is a cluster( For more information see the
Microsoft "ebsite at http:::msdn(microsoft(com:en9us:librar:aa$862607LS(8.8(asp4(
Target volumes must be formatted #ith the &TFS file sstem(
Source folders must be shared( /f ou #ant to migrate folders that are not shared%
ou must share them first(
0.
Account re5uire$ents
To run the File Server Migration "i*ard% ou must be a member of the local
5dministrators group on the source and target file servers(
Scalabilit+ Considerations for FS
Consolidation !oots
0ased on our performance testing% #e recommend that ou plan to consolidate no more
than .09-00 servers per single 2FS consolidation root server% #ith a ma4imum of 200
servers 7assuming an average of .00 shared folders per server that is consolidated using
the 2FS Consolidation 3oot "i*ard or 2fsconsolidate(e4e(8 This recommendation is
based on the follo#ing goals:
9ee'ing the startu' latenc+ of the istributed File S+ste$ service to less
than one $inute on the FS consolidation root server( This is especiall
important in the case of clustered 2FS consolidation root servers% #hich have
additional cluster failover latenc(
9ee'ing the client i$'act low( Prior to consolidation% client load is spread
across man servers( 5fter consolidation% clients must first contact a single 2FS
consolidation root server to obtain a referral that directs the client to a server that
contains the consolidated data( /n addition% the 2FS Consolidation 3oot "i*ard and
2fsconsolidate(e4e add the 2&S and &et0/,S names of all consolidated servers to
the 2FS consolidation root server as part of the consolidation process( 7This is ho#
the 2FS consolidation root server is able to redirect clients accessing ?&C paths
pointing to the old servers to the ne# servers(8 "ith a large number of additional
names% performance issues might occur #hen a large number of clients use the 2FS
consolidation root server for the mapping operation that maps the old server names
7before the #ere renamed8 to the ne# server names(
For details of the performance testing that led to our recommendations% see P5ppendi4:
0asic 2FS Creation and Startup PerformanceP later in this document(
Additional !esources
FS Web site
For links to demonstrations% case studies% documentation% and fre+uentl asked
+uestions 7F5Qs8 about 2istributed File Sstem 72FS8% see P2istributed File Sstem and
File 3eplication ServicesP on the Microsoft "eb site at http:::go(microsoft(com:f#link:M
Bink/dN-8'2-(
0/
File Server Migration Toolkit Web site
To do#nload the File Server Migration Toolkit% see <Microsoft File Server Migration
Toolkit= on the Microsoft "eb site at http:::go(microsoft(com:f#link:MBink/dN-28.2;
9nowledge &ase articles about rena$ing do$ain controllers
/f ou need to rename a domain controller before running the 2FS Consolidation 3oot
"i*ard% refer to the follo#ing Rno#ledge 0ase articles:
For instructions about renaming domain controllers running "indo#s &T Server
'(0% see article -.0268 in the Microsoft Rno#ledge 0ase at
http:::go(microsoft(com:f#link:MBink/dN288;0(
For instructions about renaming domain controllers running "indo#s 2000
Server% see article 261.62 in the Microsoft Rno#ledge 0ase at
http:::go(microsoft(com:f#link:MBink/dN288;-(
Solution Accelerator for Consolidating and Migrating File and ,rint Servers
The Solution 5ccelerator for Consolidating and Migrating File and Print Servers is a
documentation set that provides guidance for consolidating and migrating file and print
servers running "indo#s &T Server '(0 to "indo#s Server 200$ and "indo#s Storage
Server 200$( /t details the benefits of consolidation and migration and provides technical
information% recommendations% processes% build notes% @ob aids% test scripts% and a #ell9
documented and tested process for consolidation and migration( To do#nload the
Solution 5ccelerator% see <Solution 5ccelerator for Consolidating and Migrating File and
Print Servers from "indo#s &T Server '(0= on the Microsoft "eb site at
http:::go(microsoft(com:f#link:MBink/dN2';-6(
SubInAC:"e#e co$$and%line tool
Sub/n5CB is a command9line tool that enables administrators to obtain securit
information about files% registr kes% and services% and transfer this information from user
to user% from local or global group to group% and from domain to domain( To do#nload
Subinacl(e4e% see<Sub/n5CB 7Sub/n5CB(e4e8= on the Microsoft "eb site at
http:::go(microsoft(com:f#link:MBink/dN2$'-8(
Technical overview of Windows Server 2113 file services
For information about file services available in "indo#s Server 200$% see <Technical
,vervie# of "indo#s Server 200$ File Services= on the Microsoft "eb site at
http:::go(microsoft(com:f#link:MBink/dN28816(
21
Windows Server 2113 Web site
For information about "indo#s Server 200$% see <"indo#s Server 200$= on the
Microsoft "eb site at http:::go(microsoft(com:f#link:MBink/dN-;0;.(
Windows Storage Server 2113 Web site
For information about "indo#s Storage Server 200$% see <"indo#s Storage
Server 200$= on the Microsoft "eb site at http:::go(microsoft(com:f#link:MBink/dN288;2(
A''endi#6 &asic FS Creation and Startu'
,erfor$ance
"e used the follo#ing hard#are for the 2FS consolidation root server:
/ntel 41' processor
- gigabte 7>08 35M
$('0 gigahert* 7>K*8 Pentium ' #ith hperthreading
-.0 >0 "estern 2igital hard disk% model "2-100S29;.K000% 5T5 interface
"indo#s Server 200$ #ith the 41' version of Service Pack -
To create the namespaces and links% scripts #ere run directl on the 2FS consolidation
root server% not across the net#ork( Bink targets for all links #ere e4actl the same( These
tests #ere performed on non9clustered root servers( &amespaces created on clustered
root servers have additional cluster failover latenc(
)ote
The performance measurements #ere taken based on single runs and not as
averages of multiple runs( The intent is to provide a general idea of performance
impact of adding more 2FS namespaces and 2FS links(
)a$es'ace Creation and Startu' :atenc+ Statistics for a )a$es'ace with )o :inks
)u$ber of !oots Ti$e to Create )a$es'ace FSS;C"<=< Startu' :atenc+
2. $(81 seconds Bess than - second
.0 ;(0$ seconds Bess than - second
-00 -'(06 seconds Bess than - second
2.0 $.(-1 seconds Bess than - second
.00 - minute% -0($$ seconds Bess than - second
20
-000 2 minutes% 20(18 seconds 5ppro4imatel - second
.000 -2 minutes% $(60 seconds 20 seconds
-0%000 2. minutes% -1(62 seconds - minute% -2 seconds
)a$es'ace Creation and Startu' :atenc+ Statistics for a )a$es'ace with 25 :inks
,er )a$es'ace
)u$ber of !oots Ti$e to Create )a$es'ace FSS;C"<=< Startu' :atenc+
2. -6(11 seconds Bess than - second
.0 $8(.1 seconds Bess than - second
-00 - minute% -8(08 seconds 5ppro4imatel - second
2.0 $ minutes% -2(62 seconds 5ppro4imatel - second
.00 1 minutes% $;(.' seconds 2 seconds
-000 -$ minutes% -0(.. seconds . seconds
.000 - hour% -2 minutes%
';(.' seconds
- minute% -1 seconds
-0%000 2 hours% .2 minutes%
'2(-' seconds
$ minutes% -2 seconds
)a$es'ace Creation and Startu' :atenc+ Statistics for a )a$es'ace with 511
:inks ,er )a$es'ace
)u$ber of !oots Ti$e to Create )a$es'ace FSS;C"<=< Startu' :atenc+
2. -- minutes% $1(2- seconds 2 seconds
.0 2$ minutes '0(82 seconds ' seconds
-00 .' minutes% $1(. seconds -- seconds
2.0 2 hours% 2. minutes% 2$($;
seconds
.8 seconds
.00 ' hours% .' minutes%
.2(12 seconds
2 minutes% 2- seconds
-%000 6 hours% .8 minutes%
$'(01 seconds
' minutes% -8 seconds
22
)a$es'ace Creation and Startu' :atenc+ Statistics for a )a$es'ace with 0111
:inks ,er )a$es'ace
)u$ber of !oots Ti$e to Create )a$es'ace FSS;C"<=< startu' latenc+
2. '$ minutes% .0(-; seconds . seconds
.0 - hour% 2' minutes%
2-(1' seconds
-- seconds
-00 - hour% .1 minutes%
$;(88 seconds
2. seconds
2.0 $ hours% .6 minutes%
.'(0. seconds
- minute% -- seconds
.00 -0 hours% .. minutes%
2-(1' seconds
. minutes% - second
-%000 28 hours% 2; minutes%
$'(.1 seconds
-2 minutes% -; seconds
)a$es'ace Creation and Startu' :atenc+ Statistics for a Single Stand%Alone
)a$es'ace
)u$ber of :inks Ti$e to Create )a$es'ace FSS;C"<=< Startu' :atenc+
2. - minute% 00(;1 seconds 0 seconds
.0 - minute% 0-('. seconds 0 seconds
-00 - minute% 02(86 seconds 0 seconds
2.0 - minute% 08(-8 seconds 0 seconds
.00 - minute% 20($' seconds 0 seconds
-%000 - minute% .;('2 seconds 0 seconds
.%000 -1 minutes% .8('$ seconds 2 seconds
-0%000 - hour% 6 minutes%
.1('. seconds
8 seconds
2.%000 6 hours% ; minutes%
-.('0 seconds
'8 seconds
23
.0%000 21 hours% .1 minutes%
-;(.8 seconds
$ minutes% -2 seconds
24