File system migration tool question

Discussion in 'Server Migration' started by nf, Feb 21, 2008.

  1. nf

    nf Guest

    After reading through numerous posts and literature, i have come up with two
    different options for migrating my old W2K file server to my new W2003 server.

    1. a. use FSMT to move the files across while both servers are online (no
    downtime at all)
    b. remove old server and rename new server to old servers name (downtime
    only for rebooting)

    or

    2. use FSMT and DFS but doing that will cause me to have to rename the old
    server causing downtime and users will not be able to access anything until
    the whole process is complete.

    my question is, if i use option 1, am i missing or losing something by not
    using DFS?
     
    nf, Feb 21, 2008
    #1
    1. Advertisements

  2. Dear Customer,

    Thank you for posting here.

    Analysis:
    =========

    I think option 1 that you mentioned should be a better and simple one.
    Also, your steps should be OK for option 1.

    FSMT will preserve the share and NTFS security settings of share folders
    after they are migrated to the new server, it is much easier to be
    operated. You won't lose or miss anything with FSMT to migrate. After that,
    you can rename the new file server.

    If the files and folders are replicated to the new file server through DFS,
    it will cause some time for the system to generate the replication topology
    and then replicate files and folders. The process may be long if the file
    server holds a large number of folders.

    Additional Suggestions:
    =====================

    You'd better to make the old windows 2000 file server and the new windows
    2003 file server as the member server within a domain.

    1. You may install File Server Migration Tool on the new file server.

    2. Launch the File Server Migration Wizard.

    3. Create a new migration project and save it in "C:\FileServerMigration"

    4. When you add source file server, please input hostname (inputting IP
    address of server is not supported)

    5. Please unselect the checkbox of "Resolve invalid Security descriptors"
    and select the checkbox of "Copy security settings"

    6. You may find that all the files and folders with Share and Security
    permission have been replicated to the target server.

    7. Since the Security descriptors (users and groups) are stored in Active
    Directory Database, all the folders and files can be accessible as normally.

    8. Please remove old file server and rename new file server to the old
    servers name.

    9. Please note: you may perform the migration in the spare time since this
    migration can be transplant to the clients.

    References:
    ============

    Download: Microsoft File Server Migration Toolkit
    http://www.microsoft.com/downloads/details.aspx?FamilyID=d00e3eae-930a-42b0-
    b595-66f462f5d87b&DisplayLang=en

    File Server Migration Toolkit Whitepaper
    http://download.microsoft.com/download/9/6/3/963f5b22-6304-4f15-a2af-35e0b81
    046af/FSMT%20Whitepaper.doc

    I hope all the information will help.

    Thanks.

    David Shen
    Microsoft Online Partner Support
     
    David Shen [MSFT], Feb 22, 2008
    #2
    1. Advertisements

  3. nf

    nf Guest

    Thanks David for answering my post, but I have a question on what you posted.
    In step 9, you mention performing the migration in the spare time, does that
    mean only when no-one is accessing the source server?
     
    nf, Feb 22, 2008
    #3
  4. nf

    windowsfirst Guest

    windowsfirst, Feb 23, 2008
    #4
  5. nf

    nf Guest

    nf, Feb 25, 2008
    #5
  6. Dear Customer,

    Thanks for your response.

    For your concern about the step 9, yes, it is recommended that we migrate
    the file server in non-business time. If some users are using files on the
    file server in a specifically way (which may lock the files), the migration
    process will be affected.

    Hope it helps. Thanks.

    David Shen
    Microsoft Online Partner Support
     
    David Shen [MSFT], Feb 25, 2008
    #6
  7. Dear Customer,

    Thanks for your response.

    For your concern about the step 9, yes, it is recommended that we migrate
    the file server in non-business time. If some users are using files on the
    file server in a specifically way (which may lock the files), the migration
    process will be affected.

    Hope it helps. Thanks.

    David Shen
    Microsoft Online Partner Support
     
    David Shen [MSFT], Feb 25, 2008
    #7
  8. nf

    nf Guest

    ok, thanks
     
    nf, Feb 25, 2008
    #8
  9. Dear Customer,

    Thanks for your response.

    I'm glad to hear that you have resolved the issue. You are welcome to
    Newsgroup for further questions.

    Thanks.

    David Shen
    Microsoft Online Partner Support
     
    David Shen [MSFT], Feb 26, 2008
    #9
  10. nf

    nf Guest

    David,

    I came across an issue when I went and selected the source server. When I
    look at the detail of the Target share and the target location, it doesn't
    match the source servers location, won't that be a problem? should i modify
    the target share and target location to match exactly what the file layout of
    the source server looks like?
     
    nf, Feb 27, 2008
    #10
  11. Dear Customer,

    Thank you for your reply. Is the target share name different from the
    source one? If yes, it should be the default behavior and can be customized.

    By default, target shared folders are named by FSMT as
    Sharename_SourceServerName, where Sharename is the name of the shared
    folder on the source file server, and SourceServerName is the name of the
    source file server. The source file server name is appended to prevent name
    conflicts.

    If you are migrating a small number of shared folders, you can remove the
    source server name by editing the name shown in Target share for each
    source shared folder.

    For large migrations, you can edit the .xml file as follows:

    1.Create the migration project and add the source file servers.

    2.Close the File Server Migration Wizard.

    3.Locate the .xml project file for the migration project. By default,
    project files are stored in a folder called "FileServerMigration"

    4.Use Notepad to open the .xml project file.

    5.Search for <TargetShare>Sharename_SourceServerName</TargetShare> and
    remove _SourceServerName as needed.

    For example, if you want to remove the server name_MyOldFS from the target
    share names, you need to replace all occurrences of the
    _MyOldFS</TargetShare> string with the </TargetShare> string.

    Note: Tags in the .xml file are case sensitive. You need to type the tags
    exactly as they are shown here.

    6.Save and close the .xml file, restart the File Server Migration Wizard,
    and select the project file that you modified.

    Hope it helps. Thanks.

    David Shen
    Microsoft Online Partner Support
     
    David Shen [MSFT], Feb 28, 2008
    #11
  12. nf

    nf Guest

    yes the target, for now, is different since after the migation i will change
    the target name and IP to the source as you had mentioned. Thank you for the
    explanation and I will change it manually.
     
    nf, Feb 28, 2008
    #12
  13. Hello NF,

    How are things going? I've not heard back from you in a few days and wanted
    to check on the status of the issue. Please let me know how the
    troubleshooting steps turned out.

    Thanks.

    David Shen
    Microsoft Online Partner Support
     
    David Shen [MSFT], Mar 3, 2008
    #13
  14. nf

    nf Guest

    not too good David. On Friday I migrated successfully our file server from
    one Windows 2000 server to a new Windows 2003 server using the File Migration
    Tool. Everything went fine till the next day at 1:30pm when the new server
    blue screen with the following:
    IRQL_NOT_LESS_OR_EQUAL
    STOP 0x0000000A(0x10021001,0xD000001B,0x00000001,0x8082651E)

    Nothing else.. no listing in the event viewer at all of the mishap. I had to
    revert back to the old file server for now till i figure out what is going on
    since we can't afford to be down a file server. I can't figure out what went
    wrong since the server had been running since the previous week with no
    issues.
     
    nf, Mar 3, 2008
    #14
  15. Hello NF,

    Thank you for your reply.

    The Stop Error code you mentioned (0x0000000A, IRQL_NOT_LESS_OR_EQUAL)
    indicates Windows or a kernel-mode driver accessed paged memory at
    DISPATCH_LEVEL or above. It generally occurs if paged memory (or invalid
    memory) is accessed when the IRQL is too high. It usually occurs after the
    installation of a faulty device driver, system service, or BIOS. Also, I
    think it should not be related to the previous file server migration.

    To troubleshoot this kind of kernel crash issue, we need to debug the
    crashed system dump. Unfortunately, debugging is beyond what we can do in
    the newsgroups. A suggestion would be to contact Microsoft Customer Service
    and Support (CSS) via telephone so that a dedicated Support Professional
    can assist with your request. Please be advised that contacting phone
    support will be a charged call.

    You may obtain the phone numbers for specific technology request please
    take a look at the web site listed below:

    http://support.microsoft.com/default.aspx?scid=fh;EN-US;OfferProPhone#faq607

    Having said the above, I would like to share some basic troubleshooting
    methods for this crash with you. You may try them at the same time when
    contacting Microsoft CSS.

    A.To resolve an error caused by a faulty device driver, system service, or
    BIOS

    1.Restart your computer.
    2.Press F8 at the character-based menu that displays the operating system
    choices.
    3.Select the Last Known Good Configuration option from the Windows Advanced
    Options menu. This option is most effective when only one driver or service
    is added at a time.

    B.To resolve an error caused by an incompatible device driver, system
    service, virus scanner, or backup tool.

    1.Check the System Log in Event Viewer for error messages that might
    identify the device or driver that caused the error.
    2.Try disabling memory caching of the BIOS.
    3.Run the hardware diagnostics supplied by the system manufacturer,
    especially the memory scanner. For details on these procedures, see the
    owner's manual for your computer.
    4.Make sure the latest Service Pack is installed.
    5.If your system has small computer system interface (SCSI) adapters,
    contact the adapter manufacturer to obtain updated Windows drivers. Try
    disabling sync negotiation in the SCSI BIOS, checking the cabling and the
    SCSI IDs of each device, and confirming proper termination.
    6.For integrated device electronics (IDE) devices, define the onboard IDE
    port as Primary only. Also, check each IDE device for the proper
    master/slave/stand-alone setting. Try removing all IDE devices except for
    hard disks.

    C. If the problem still persists, please call Microsoft CSS.

    I hope the problem will be resolved soon. Thank you for your time and
    cooperation!

    David Shen
    Microsoft Online Partner Support
     
    David Shen [MSFT], Mar 4, 2008
    #15
  16. nf

    nf Guest

    I will end up calling them. But just to answer your questions. I have
    verified that i have the latest drivers, bios, etc availible. I haven't had
    to upgrade any of them since the system came in with the latest. Nothing in
    the event viewer says anything about the crash or even lists the crash? I ran
    the diagnostics disks from Dell (twice) and it came up fine every time.
     
    nf, Mar 4, 2008
    #16
  17. nf

    nf Guest

    David,

    Since I wil probably once again start the migration all over again later
    this week. Should i delete the existing volume(files) on my target server? or
    can the File Migration tool figure out the changes needed to be made and go
    from there?
     
    nf, Mar 4, 2008
    #17
  18. Hello NF,

    Thank you for your reply.

    Yes, we can restart the file migration. In this case, we can ensure
    everything exists on the source file server first. Then you can and then
    stop file sharing and delete the existing folders and files on the target
    server. After that, you can use FSMT to migrate shares from the source file
    server again.

    Hope it helps.

    David Shen
    Microsoft Online Partner Support
     
    David Shen [MSFT], Mar 5, 2008
    #18
  19. Hello NF,

    I am just writing to see how everything is going. If you have any updates
    or need any further assistance on this issue, please feel free to let me
    know. I am glad to be of assistance.

    David Shen
    Microsoft Online Partner Support
     
    David Shen [MSFT], Mar 13, 2008
    #19
  20. nf

    nf Guest

    Everything good so far...been running for three days now. thanks
     
    nf, Mar 18, 2008
    #20
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.