Re: Consolidaion Root Wizard Question
- From: ctconline <ctconline@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Sat, 25 Feb 2006 18:41:26 -0800
Jill.
Thank you so much. This is very helpful information. Maybe you could help
me with more specific information. Is it possible to have the Consolidation
Root Host only be the host and not actually have the files located on it?
Let me see if I can clear this up for you... Here is my current situation:
We are currently using about 5 Windows 2000 file servers in a Windows 2000
AD. We aren't using any dfs at this point. We decided to move all files to
NAS and implement dfs. So we bought 2 NAS units which are running Windows
2003 Storage Server Standard.
In reading the documentation for FSMT, I realized that a requirement for the
Consolidation Root Wizard was Windows 2003 Server Enterprise Edition. So we
purchased an additional server (not NAS) with Windows 2003 Server Enterprise.
Our ultimate goal is to move all file shares to NAS units which will use dfs
for load balancing and fault tolerance. So, my plan is to use the Enterprise
Edition server as the root host which points to the targets which will be
located on the NAS units.
Is this scenario possible? If so, here are some other questions...
Where do I run the Consolidation Root Wizard from?
Where do I run the FSMT from?
Thank you for your time.
"Jill Zoeller [MSFT]" wrote:
I asked the FSMT Program Manager, Mark Sterin, to give some insight about.
server downtime. Here is his response:
There are 2 time windows when the access is down:
1. rename old servers and set up the roots using FSMT - depending on the
number of servers can take 10-30 min (basically, NT reboot time + run
Consolidation Roots Wizard)
2. When the data is copied, turn off the access to shared and do the final
pass re-copy the changed data if any, and sync up ACLs. This could take a
few hours depending on the number of files per share and the perf. of disks
on the target machine.
2a) It's a good idea to do one server (or share) in a first "pilot" project
to validate the downtime for this stage.
2b) this time will be at least as long as the largest share will take, so
to minimize this time you may want to split migration project in a few and
separate the shares with largest number of files in a dedicated projects -
this way downtime for other shares will be minimized
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Want to learn more about Windows Server file and storage technologies? Visit
our team blog at http://blogs.technet.com/filecab/default.aspx.
"Jill Zoeller [MSFT]" <jillz@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:uKnaxXwNGHA.3360@xxxxxxxxxxxxxxxxxxxxxxx
I'm checking on this for you with the FSMT team.
--
This posting is provided "AS IS" with no warranties, and confers no
rights.
Want to learn more about Windows Server file and storage technologies?
Visit our team blog at http://blogs.technet.com/filecab/default.aspx.
"ctconline" <ctconline@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:C0C43396-2DE8-424E-AC7C-E6F2E94FF36A@xxxxxxxxxxxxxxxx
I have read all of those. I am asking for someone who has real world
experience with these tools. How long of a maintenance window is
required?
"Jason Tan (MSFT)" wrote:
Hello,
Thanks for posting!
Before migration I suggest you review the following article for
reference:
Microsoft File Server Migration Toolkit FSMT Site:
http://www.microsoft.com/windowsserver2003/upgrading/nt4/tooldocs/msfsc.mspx
Overview of the Microsoft File Server Migration Toolkit white paper of
FSMT
http://www.microsoft.com/windowsserver2003/upgrading/nt4/tooldocs/msfst_over
view.mspx
Frequently Asked Questions About File Server Migration
http://www.microsoft.com/windowsserver2003/upgrading/nt4/tooldocs/msfst_faqs
.mspx
Hope the information helps.
Best Regards,
Jason Tan
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no
rights.
--------------------
| Thread-Topic: Consolidaion Root Wizard Question
| thread-index: AcYzSJAdDSSP2RS+RM+fOx1v4dLfSg==
| X-WBNR-Posting-Host: 65.40.43.165
| From: =?Utf-8?B?Y3Rjb25saW5l?= <ctconline@xxxxxxxxxxxxxxxxxxxxxxxxx>
| Subject: Consolidaion Root Wizard Question
| Date: Thu, 16 Feb 2006 14:30:17 -0800
| Lines: 9
| Message-ID: <7280F25E-ED45-4444-B9D9-91AA32743CA7@xxxxxxxxxxxxx>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
| Newsgroups: microsoft.public.windows.server.migration
| NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
| Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
| Xref: TK2MSFTNGXA01.phx.gbl
microsoft.public.windows.server.migration:22510
| X-Tomcat-NG: microsoft.public.windows.server.migration
|
| In reading the documentation for the FSMT, it says that I must provide
a
| maintenance window when I can rename the old file servers. I'm in the
| planning stage and I'm trying to determine how much of a window do I
need.
| How long after renaming the servers and running the Consolidation Root
Wizard
| will it take before users can access the file servers by legacy UNC
paths?
|
| I have a lot of data to migrate to dfs and I need to minimize the
impact
on
| the users. We are a 24/7 operation with very small maintenance
windows.
| Thanks for any help.
|
- Follow-Ups:
- Re: Consolidaion Root Wizard Question
- From: Jill Zoeller [MSFT]
- Re: Consolidaion Root Wizard Question
- References:
- RE: Consolidaion Root Wizard Question
- From: Jason Tan (MSFT)
- RE: Consolidaion Root Wizard Question
- From: ctconline
- Re: Consolidaion Root Wizard Question
- From: Jill Zoeller [MSFT]
- Re: Consolidaion Root Wizard Question
- From: Jill Zoeller [MSFT]
- RE: Consolidaion Root Wizard Question
- Prev by Date: Re: NT4 Old Domain Not Accessible Or Recognized
- Next by Date: Novell 4.11 -> Win 2003 AD migration
- Previous by thread: Re: Consolidaion Root Wizard Question
- Next by thread: Re: Consolidaion Root Wizard Question
- Index(es):
Relevant Pages
|