none
File Services and Storage FAQ

Všechny reakce

  • DFS Guidelines

     

     

    Step-by-Step Guide to Distributed File System (DFS)

    http://technet.microsoft.com/en-us/library/bb727150.aspx

     

    Step-by-Step Guide for the Distributed File System Solution in Windows Server 2003 R2

    http://technet.microsoft.com/en-us/library/cc737358.aspx

     

    DFS Step-by-Step Guide for Windows Server 2008

    http://technet.microsoft.com/en-us/library/cc732863.aspx

     

    Overview of the Distributed File System Solution in Microsoft Windows Server 2003 R2

    http://technet.microsoft.com/en-us/library/cc787066.aspx

     

    Testing Anti-Virus Application Interoperability with DFS Replication

    http://blogs.technet.com/filecab/archive/2006/05/01/426926.aspx

     

    Designing Distributed File Systems

    http://technet.microsoft.com/en-us/library/cc772778.aspx

     

    DFS Replication scalability guidelines

    http://technet.microsoft.com/en-us/library/cc779936.aspx

     

     

    Hot fixes

     

    An event may be logged after you restart Windows Server 2008: "Event ID: 5 Message: The Virtual Storage Filter Driver is disabled through the registry. It is inactive for all disk drives"

    http://support.microsoft.com/kb/951007

     

    The default group failover threshold value in the Windows Server 2008 Failover Cluster Management snap-in is incorrect

    http://support.microsoft.com/kb/950804

     

    A Network Name resource that has the Kerberos protocol enabled does not come online on the first attempt in a Windows Server 2008 failover cluster

    http://support.microsoft.com/kb/950806

     

    How to configure DFSR file-type compression in Windows Server 2008

    http://support.microsoft.com/kb/951003

     

    A handle leak occurs in a Server Message Block (SMB) session between two Windows Vista-based computers or between two Windows Server 2008-based computers

    http://support.microsoft.com/kb/948572

     

    The Cluster service may stop responding on a Windows Server 2008 cluster node when an application performs VSS backup of files from a volume

    http://support.microsoft.com/kb/950267

     

    Error message when you use the Wbadmin.exe command-line tool to recover an EFI volume on a Windows Server 2008-based computer: "Online recovery of EFI System Partition is not supported. Please try recovering from Windows Recovery Environment"

    http://support.microsoft.com/kb/951038

     

    List of currently available hotfixes for Distributed File System (DFS) technologies in Windows Server 2003 R2

    http://support.microsoft.com/kb/958802

     

    Hotfix rollup package for Distributed File System Replication in Windows Server 2003

    http://support.microsoft.com/default.aspx?scid=kb;EN-US;917622

     

    FIX: You cannot access performance counters in the Distributed File System (DFS) Replication health report on a computer that is running Windows Server 2003 R2

    http://support.microsoft.com/default.aspx?scid=kb;EN-US;912850


    Laura Zhang - MSFT
    31. března 2009 10:12
    Moderátor
  • How to - Q1: How can I add "Service for Network File System" on Windows Server 2008?


    A:
    "Service for Network File System" is a role service of "File Services" role on Windows Server 2008. We can refer to the following steps to install "Service for Network File System" on Windows Server 2008 via Server Manager.

     

    1.      Launch the "Server Manager"

    2.      Click Role, Click "Add Roles" in the right panel

    3.      Click Next, Select the checkbox of "File Services", Click Next.

    4.      When the "Select Role Services" appears, select the checkbox of "Service for Network File System" 

    5.   Click Next, and click Install.


    Laura Zhang - MSFT
    31. března 2009 10:12
    Moderátor
  • How To - Q2. Why is there a 15 minutes interval limit in DFS-R and bandwidth throttling?


    A.
    This is determined by the way that the operation system stores the information of DFS replication.

    The DFS Replication schedule is stored as a binary attribute of size 336 bytes (2*24*7) which represents a schedule for a week. Each hour is represented in two bytes. Every hour is divided into four quarters, each of which occupies four bits, hence the 15 minutes interval:

    [...]      [...]       [...]       [...]
    0 14   15 29    30 44    45 59

    The four bits of a quarter takes 16 value ranges from 0X0, which indicates schedule is OFF, to 0xF, which indicates an ON schedule with full bandwidth. The levels in between defines an ON schedule with different levels of bandwidth.



    Laura Zhang - MSFT
    31. března 2009 10:16
    Moderátor
  • How To - Q3. Why can’t I see all the files in a Shared folder?


    A.
    If we can only access and view a subset of files or folders present in a shared folder, it might be for one of the following reasons:

     

    1. Share and NTFS permission

    Please check if you have granted the users with the different Share and NTFS permissions on these share folders and files. We need to verify that the user have permission to access the misrepresented folder.

     

    2. Hidden share folders

    Please check if there are any hidden share folders on the file server.

     

    3. DFS share with Access-Based Enumeration.

    When the client connects to DFS share and Access-Based Enumeration is enabled on these share folders at the same time, Windows Explorer will not display files or folders that a user does not have right to access.

     

    Access-based Enumeration

    http://technet.microsoft.com/en-us/library/cc784710.aspx


    Laura Zhang - MSFT
    31. března 2009 10:18
    Moderátor
  • How To - Q4: How can I migrate and consolidate share folders on Windows Server 2008, Windows Server 2003, Windows 2000 server, and Windows NT server?


    A: The previous version of File Server Migration Toolkit (FSMT) does not support file share consolidation on Windows Server 2008. With the release of FSMT 1.2 added support to Windows Server 2008 both on x86 and x64 systems. FSMT offers a step-by-step process which simplifies the task of migrating file services. It provides the necessary tools to help minimize the impact to users which results in a more manageable environment.

     

    • Simplify the task of moving data: FSMT helps the system administrator easily migrate and consolidate shared folders from servers running Windows NT Server 4.0, Windows 2000 family of servers, Windows 2003 family of servers, Windows Server 2008, or Windows Storage Server 2008 to a server running Windows Server 2003, Windows Storage Server 2008, or Windows Server 2008.

     

    • Minimize the impact on users: FSMT helps the system administrator configure new functionality in Distributed File System (DFS) to maintain the original Universal Naming Convention (UNC) path of files after they are moved to a new server through DFS consolidation roots. This reduces the impact of file server consolidation and migration, saves end users time spent searching for files, and ensures that line-of-business applications keep running.

     

    • ore manageable and productive: FSMT is the tool that allows administrators to overcome data migration hurdles. While the benefits of consolidation or migration to a platform with better file services is the payoff, getting there can sometimes be overwhelming. By simplifying the task of moving data and keeping the impact on users to a minimum, the company is able to increase its overall ability to manage their file services. This creates a more productive environment both for users and those in charge of planning.

     

    To download this toolkit, please browse to the following link:

     

    Microsoft File Server Migration Toolkit 1.2

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

     

    To know more about this toolkit and how to use it, please refer to the following whitepaper:

    http://download.microsoft.com/download/4/e/b/4eb8df62-08cb-420f-a41b-6d10452335cc/FSMT%20Whitepaper.doc


    Laura Zhang - MSFT
    31. března 2009 10:22
    Moderátor
  • How To - Q5: How can I backup Hyper-V virtual machines from the parent partition on a Windows Server 2008 by using Windows Server Backup?


    A: To back up Hyper-V virtual machines from the parent partition on Windows Server 2008 by using Windows Server Backup, you must register the Microsoft Hyper-V VSS writer with Windows Server Backup. To do so, please follow these steps:

     

    1.  Click Start, click Run , type regedit, and then click OK . 

    2.  Locate the following registry key:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion 

    3.  Right-click CurrentVersion, point to New, and then click Key. 

    4.  Type WindowsServerBackup , and then press ENTER. 

    5.  Right-click WindowsServerBackup, point to New, and then click Key. 

    6.  Type Application Support, and then press ENTER. 

    7.  Right-click Application Support, point to New, and then click Key. 

    8.  Type {66841CD4-6DED-4F4B-8F17-FD23F8DDC3DE} , and then press ENTER. 

    9.  Right-click {66841CD4-6DED-4F4B-8F17-FD23F8DDC3DE} , point to New , and then click String Value . 

    10.  Type Application Identifier, and then press ENTER. 

    11.  Right-click Application Identifier, and then click Modify. 

    12.  In the Value data box, type Hyper-V, and then click OK. 

    13.  On the File menu, click Exit. 

     

    For more information, please refer to the following Microsoft Knowledge Base article:

     

    958662            How to back up Hyper-V virtual machines from the parent partition on a Windows Server 2008-based computer by using Windows Server Backup

    http://support.microsoft.com/default.aspx?scid=kb;EN-US;958662


    Laura Zhang - MSFT
    31. března 2009 10:23
    Moderátor
  • How To - Q6: Are there any documents that explain SMB2?


    A:
    Jose Barreto has two posts that outlines the important improvement in SMB2

     

    SMB2, a complete redesign of the main remote file protocol for Windows

    http://blogs.technet.com/josebda/archive/2008/12/05/smb2-a-complete-redesign-of-the-main-remote-file-protocol-for-windows.aspx

     

    File Server performance improvements with the SMB2 protocol in Windows Server 2008

    http://blogs.technet.com/josebda/archive/2008/11/11/file-server-performance-improvements-with-the-smb2-protocol-in-windows-server-2008.aspx


    Laura Zhang - MSFT
    31. března 2009 10:24
    Moderátor
  • How To - Q7: Are there any documents that introduce Distributed File System Replication (DFSR)?


    A: For Distributed File System Replication (DFSR) related FAQs, please refer to the following link:

     

    Distributed File System Replication: Frequently Asked Questions

    http://technet.microsoft.com/en-us/library/cc773238.aspx


    Laura Zhang - MSFT
    31. března 2009 10:25
    Moderátor
  • Problem - Q1: Members of the Administrators group cannot access the folder although the Administrators group has the permission to it.


    Symptom

    =========

    In Windows Server 2008, you are logged on as a user which is not the built-in Administrator account. This account has been added into the Administrators group. When you try to access some folders, it fails with the "Access is denied" error. You checked the security permission of this folder and found that the "Administrators" group has the permission to access this folder. However, you are not able to access the folder using this account, although it is a member of the Administrators group.

     

    Possible Cause

    ============

    This behavior is by design. It is a result of Admin approval mode (AAM) for User Account Control.

     

    Resolution

    ==========

    To work around this behavior, you may create a security group and grant this group the permissions to this folder. Then add this user account into this group. Another method is to explictly grant the permissions for the folder to this specific user account.

     

    More Information

    ===============

    For more information about Admin Approval Mode, please refer to the following Technet article:

    http://technet.microsoft.com/en-us/library/cc772207.aspx


    Laura Zhang - MSFT
    31. března 2009 10:28
    Moderátor
  • Problem - Q2: Windows XP and Windows Server 2003 servers cannot access shares on Windows Server 2008; however, Windows Server 2008 server works fine.


    Symptom

    =========

    Windows XP and Windows Server 2003 servers intermittently could not access the file shares on a Windows Server 2008 server. However, from Windows Server 2008 server the file share could be accessed properly. If you reboot the file server, everything works fine for a while.

     

    In the event log, you may notice the following error:

     

    Log Name: Security

    Source: Microsoft-Windows-Security-Auditing

    Event ID: 5159

    Task Category: Filtering Platform Connection

    Level: Information

    Keywords: Audit Failure

    Description: The Windows Filtering Platform has blocked a bind to a local port.

     

    Application Information:

    Process ID: 3220

    Application

    Name: \device\harddiskvolume1\windows\system32\cpqmgmt\cqmghost\cqmghost.exe

     

     

    Possible Cause

    ============

    The process cqmghost.exe listed in the event log is used by "HP Insight Foundation Agent" Service.

     

    Since the Windows XP and Windows Server 2003 uses UDP by default for Kerberos Authentication and the Windows Filtering Platform has blocked a bind to a local port, the user authentication fails hence the file access. Because Windows Server 2008 uses TCP by default for Kerberos Authentication, everything works fine.

     

    Resolution

    ==========

    Disable the "HP Insight Foundation Agent Service" service on the Windows Server 2008 File server and reboot the server.

    Laura Zhang - MSFT
    31. března 2009 10:29
    Moderátor
  • Problme - Q3: Error message "The selected files could not be copied. There is not enough free space on the devicewhen you try to copy a file to a DFS shared folder from a Windows Vista-based computer or from a Windows Server 2008-based computer.


    Symptom

    =========

    On a Windows Vista-based computer or on a Windows Server 2008-based computer, you copy a file to a Distributed File System (DFS) shared folder in Windows Explorer. However, even though the shared folder has sufficient disk space, the file copy operation may not be successful. Additionally, you may receive the following error message:

     

    “The selected files could not be copied. There is not enough free space on the device.”

     

    When you check the free space for the DFS shared folder in Windows Explorer, Windows Explorer displays an amount of space that is less than what is actually available on the file server.

     

    Possible Cause

    ============

    The DFS root and the DFS shared folder are in different locations. This problem occurs when the DFS root resides on a share that has little free space. Windows Explorer incorrectly calculates the free space of the DFS root instead of the free space of the DFS shared folder that is linked to the root.

     

    Resolution

    ==========

    This is a known issue for Vista and Windows Server 2008. Please download and install the hot fix described in the following Microsoft Knowledge Base article:

     

    Error message when you try to copy a file to a DFS shared folder from a Windows Vista-based computer or from a Windows Server 2008-based computer: "The selected files could not be copied There is not enough free space on the device"

    http://support.microsoft.com/kb/954037


    Laura Zhang - MSFT
    31. března 2009 10:30
    Moderátor
  • Problem - Q4: Error code 0x8004240f occurs when you use a volume that is larger than 2 TB as backup storage in Windows Server 2008


    Symptom

    =========

    In Windows Server 2008, when you use a volume that is larger than 2 terabytes (TB) for backup storage, Windows Server Backup fails and you receive the following Error code:

     

    0x8004240f

     

    Possible Cause

    ============

    This issue occurs because Windows Server Backup always initializes disks by using a master boot record (MBR) and GPT format is not supported now.

     

    Resolution

    ==========

    The next service pack for Windows 2008 and Vista will be changed to support GPT format.

     

    To work around this problem, re-create the backup storage volume to be less than 2TB.


    Laura Zhang - MSFT
    31. března 2009 10:31
    Moderátor
  • Problem - Q5: DFSR may not operate correctly when used in conjunction with FSRM file screens.


    Symptom

    =========

    When using Distributed File System Replication (DFSR) and File Server Resource Manager (FSRM) file screens, the following symptoms may occur:

     

    ·         Windows Server 2008 Domain Controllers may not successfully replicate SYSVOL when using a non-default path.

    ·         Windows Server 2003 R2 or Windows Server 2008 DFSR participants may backlog replication and fail to stay in sync.

    ·         DFSR debug logs may show 'disk space' or 'access denied' errors when replicating files inbound.

     

    Example log 1:

    20070605 09:33:36.440 5456 MEET 1243 <Meet::Install> -> WAIT Error processing update. updateName:664225.au uid:{3806F08C-5D57-41E9-85FF-99924DD0438F}-v333459 gvsn:{3806F08C-5D57-41E9-85FF-99924DD0438F}-v333459 connId:{6040D1AC-184D-49DF-8464-35F43218DB78} csName:Users csId:{C86E5BCE-7EBF-4F89-8D1D-387EDAE33002} code:5 Error:+ [Error:5(0x5) <Meet::InstallRename> meet.cpp:2244 5456 W66 Access is denied.]

    Example log 2:

    20071228 07:32:38.429 4344 MEET 1243 Meet::Install -> WAIT Error processing update. updateName:MyUser.doc uid:{03AEF357-60A4-4669-B6FE-6504AB90B164}-v711769 gvsn:{03AEF357-60A4-4669-B6FE-6504AB90B164}-v711769 connId:{4A1F7762-04C6-4E24-9DF5-17EDCFADD8ED} csName:UserData csId:{D340C004-EC83-4955-9258-C7B834810035} code:112 Error:

    + [Error:112(0x70) Meet::InstallRename meet.cpp:2244 4344 W832 There is not enough space on the disk.]
    + [Error:112(0x70) NtfsFileSystem::Move ntfsfilesystem.cpp:925 4344 W831 There is not enough space on the disk.]
    + [Error:112(0x70) FileUtil::RenameByHandle fileutil.cpp:257 4344 W830 There is not enough space on the disk.]

     

    Possible Cause

    ============

    FSRM allows administrators to create file screens to control the types of files that can be saved within a specified path. Based on how these configuration changes are made, DFSR may not correctly function.

     

    Resolution

    ==========

    To resolve this issue try one of the following methods:

     

    ·         Do not configure FSRM to screen any paths being replicated by DFSR. This includes Windows Server 2008 SYSVOL if it is not in the default %systemroot%\sysvol path.

     

    ·         If file screens are configured for DFSR replicated folder paths (including SYSVOL), do not block any file types being replicated. In the case of a domain controller this would include (but not be limited to) files with the extension INI, INF, POL, ADML, ADMX, and ADM.

     

    ·         If screens are configured and file types being replicated are covered by FSRM, use passive mode notification rather than active blocking of files.

     

    More Information

    ===============

    DFSR may not operate correctly when used in conjunction with FSRM file screens

    http://support.microsoft.com/kb/959210

     

    Does DFS Replication support file screens created by File Server Resource Manager?

    http://technet.microsoft.com/en-us/library/cc773238.aspx#BKMK_064


    Laura Zhang - MSFT
    31. března 2009 10:32
    Moderátor
  • Problem - Q6: “File Server Resource Manager is not a valid Win32 application” error when you try to start the File Server Resource Manager.


    Symptom

    ========

    When trying to start the FSRM service you get the following error:

    Could not start the File Server Resource Manager service on Local Computer

     

    In the Event log, the following error is recorded:

     

    Error 193: 0xc1

    At the same time an event is generated on the event log.

    Event Type: Error

    Event Source: Service Control Manager

    Event Category: None

    Event ID: 7023

    Date: 8/1/2006

    Time: 12:27:53 AM

    User: N/A

    Computer:

    Description:

    The File Server Resource Manager Service terminated with the following error:

    File Server Resource Manager is not a valid Win32 application.

     

    Possible Cause

    ==============

    The DFSEXT.dll is corrupted on the problematic server. The size of DFSEXT.dll is 62KB by default on a working Windows Server 2003 server.

     

    Resolution

    ==========

    Please replace the corrupted DFSEXT.dll with the working one in Windows Server 2003 R2 Disc2

     

    1. Install "Windows Recovery Console" by running "Winnt32 /cmdcons" in the CLI.

    2. Boot into recovery console

    3. Expand the DFSEXT.dll from the Windows Server 2003 R2 Disc2 to overwrite the corrupted file under the C:\Windows\System32


    Laura Zhang - MSFT
    31. března 2009 10:33
    Moderátor
  • Problem - Q7: The FSRM MMC snap-in in a Windows Server 2003 R2 based server could not be opened.

     

    Symptom

    ========

    The FSRM MMC snap-in in a Windows Server 2003 R2 based server could not be opened. In the event log, you may receive one of the following error messages:

     

    Type: Error

    Date: Date

    Time: Time

    Event ID: 4

    Source: SRMSVC

    Description:

    File Server Resource Manager Service information: The COM Server with CLSID {efbdb74f-5b0d-4ad8-9aaf-aae0c8840a30} and name 'SrmReportManager' cannot be started.

    Error: 0x80045316, The File Server Resource Manager service encountered an unexpected error.

    Check the application event log for more information.

     

    Type: Error

    Date: Date

    Time: Time

    Event ID: 4

    Source: SRMSVC

    Description:

    File Server Resource Manager Service information: The COM Server with CLSID {61b2d373-4258-40a2-89ac-2783d8ac0e99} and name 'SrmReportManagerInproc' cannot be started.

    Error: 0x80131534.

     

    Possible Cause

    ==============

    This problem occurs because the Microsoft .NET Framework 2.0 component is corrupted.

     

    Resolution

    ===========

    Uninstall and then reinstall the .NET Framework 2.0 Redistributable Package.

    http://www.microsoft.com/downloads/details.aspx?Family-acf8-4fa1-affb-40e78d788b00&DisplayLang=en

     

    More Information

    ============

    You may be unable to open the FSRM MMC snap-in on a Windows Server 2003 R2-based computer

    http://support.microsoft.com/default.aspx/kb/949920


    Laura Zhang - MSFT
    31. března 2009 10:34
    Moderátor
  • Problem - Q8:  Users cannot change the running user context of a scheduled task to another domain account on a computer that is running Windows Vista or Windows Server 2008


    Symptom

    ========

    Consider the following scenario:

     

    1.      You have a computer that is running Windows Vista or Windows Server 2008 in a domain.

    2.      You configure a scheduled task on the computer.

    3.      When you try to change the running user context from the default user account to another account in the domain, you receive the following error message:

     

    An error has occurred for task TaskName. Error message: The specified account name is not valid

     

    By default, a NetBIOS name is the leftmost part of the DNS domain name. For example, if the DNS name is "contoso.com," the NetBIOS domain name is "CONTOSO." However, an administrator may arbitrarily choose any valid NetBIOS name. This problem occurs if the NetBIOS domain name is not the default name.

     

     

    Possible Cause

    ==============

    When the Task Scheduler records the running user context, the Task Scheduler user interface incorrectly uses the leftmost part of the DNS name as the NetBIOS domain name instead of the actual NetBIOS domain name. Therefore, if the administrator did not use the default NetBIOS name, you receive the error message that is mentioned in the "Symptoms" section.

     

    Resolution

    ===========

    Apply the hotfix described in the following Microsoft Knowledge Base article:

     

    Error message when you change the running user context of a scheduled task to another domain account on a computer that is running Windows Vista or Windows Server 2008: "The specified account name is not valid"

    http://support.microsoft.com/kb/953153



    Laura Zhang - MSFT
    31. března 2009 10:34
    Moderátor
  • Problem - Q9: The value in the Next Run Time field in Task Scheduler is incorrect in Windows Vista and Windows Server 2008.


    Symptom

    ========

    In Windows Vista or in Windows Server 2008, you create a scheduled task that has repetition settings. When you examine the next run time of the scheduled task, the value of Next Run Time field may be incorrect.

     

    For example, you create a daily scheduled task as follows:

     

    The task starts at 7:00 A.M. and has a 1-hour repetition interval.

    The repetition duration of the task is set to 3 hours.

     

    In this example, the task is expected to be triggered to start at 7:00 A.M., 8:00 A.M., 9:00 A.M. and 10:00 A.M.

     

    However, after 10:00 A.M., you notice that the value in the Next Run Time field in Task Scheduler is incorrect. This problem occurs even though correct information appears in the Trigger field in Task Scheduler. In this example, the correct value of the Next Run Time field is 7:00 A.M. the next day.

     

    The issue also occurs if you export the scheduled task and then import the task to another Windows Vista-based computer.

     

    Resolution

    ===========

    Apply the hotfix described in the following Microsoft Knowledge Base article:

     

    http://support.microsoft.com/kb/950035

     

     
    Laura Zhang - MSFT
    31. března 2009 10:35
    Moderátor
  • Problem - Q10: DFSR member waiting for initial replication because no primary member is specified.

     

    Symptom

    ========

    In the DFS Replication Health Report, you may see under the WARNINGS section servers listed with warning "This member is waiting for initial replication for replicated folder <replicated folder name>."

     

    The more detailed error message is like the following:

     

    "This member is waiting for initial replication for replicated folder <replicated folder name>.

     

    Affected replicated folders: Data

    Description: This member is waiting for initial replication for replicated folder <replicated folder name> and is not currently participating in replication. This delay can occur because the member is waiting for the DFS Replication service to retrieve replication settings from Active Directory. After the member detects that it is part of replication group, the member will begin initial replication.

    Last occurred: <time/date>

    Suggested action: Replication will begin after initial replication is complete. If this state does not change, see The Microsoft Web Site."

     

    Possible Cause

    ==============

    You may encounter the issue and see "waiting for initial replication" because no primary member is currently specified.

     

     DFSR has the concept of the primary member, which is the member that is specified during the creation of a replication group to be authoritative. During initial synchronization, if a file exists on both sending and receiving members, the version on the primary member is considered authoritative and wins out.

     

    Note that after initial synchronization is completed, the primary member is no longer primary and DFSR returns to being a normal multi-master replication engine. It is only during initial sync that a primary member is needed so that DFSR knows which set of data is authoritative to start with.

     

    It is possible to get into situations where members are waiting for initial sync to complete, but no primary member has been specified. When this situation occurs, DFSR does not automatically choose a primary member but instead waits for the administrator to manually specify the primary member. This is desirable behavior because when the replication group is being configured for the first time, we want to leave it up to the administrator to decide which member's data should win out during initial sync.

     

    If the administrator does not know which member should be authoritative, they will need to backup the data on both members, and/or manually make the data on one of the members authoritative by going through the files on each and figuring out which ones they need to keep and putting them all on the member that they will then set as primary. That could take a very long time depending on how much data they have to go through, so possibly just taking backups and restoring files later on an as-needed basis is a better option in many cases.

     

    It is not obvious when you get into this situation that DFSR is waiting for you to specify a primary member.

     

    Resolution

    ===========

    Determine and specify a primary member to make the initial synchronization.

     

    How to tell if DFSR is waiting for you to specify a primary member:

     

    1. One or more members have a 4102 event (initial sync needed) that is not followed by a 4104 event (initial sync completed). In this situation the health report will include the "waiting for initial replication" for that server in the report (like in the problem description above).

     

    2. If one or more members is waiting for initial replication as determined in Step 1, then run the following Dfsradmin command (not case sensitive) to determine if any member is primary.

     

    Dfsradmin Membership List /RGName:<replication group name> /attr:MemName,RFName,IsPrimary

     

    For example if the replication group name is RG1 the command would be:

     

    Dfsradmin Membership List /RGName:RG1 /attr:MemName,RFName,IsPrimary

     

    If there is no primary member the output will look like this:

     

    MemName RfName IsPrimary

    NA-DC-01 Data No

    NA-DC-02 Data No

     

    How to specify a primary member:

     

    Normally, you can specify the primary member via the Replication Group wizard in DFS Management console when you are creating the replication group. But in the situation where there is an existing replication group that is waiting for initial replication and no primary member is specified, you can use Dfsradmin to set the primary member.

     

    Dfsradmin Membership Set /RGName:<replication group name> /RFName:<replicated folder name> /MemName:<member you want to be primary> /IsPrimary:True

     

    For example, if you want NA-DC-01 to be primary for the replicated folder DATA in the replication group RG1:

     

    Dfsradmin Membership Set /RGName:RG1 /RFName:DATA /MemName:NA-DC-01 /IsPrimary:True

     

    Run "Dfsrdiag Pollad" against all the members to force them to pick up this change as soon as possible. You can run "Dfsrdiag Pollad /Member:<member name>" to force a poll on a remote member.Note that AD replication latency will often be a factor in how quickly the change is picked up. Dfsrdiag Pollad just tells the DFSR service to check its local DC for configuration changes. But if you ran the Dfsradmin command to set the primary member on a server that is using a different DC (very common in branch office scenarios), you will have to wait for that DC to replicate to the ones being used by the other DFSR members.

     

    In the DFSR event log on the primary member you should then see a 4002 event (successfully initialized the replicated folder) followed by a 4112 event (member is the designated primary member) once it picks up the change. The DFSR debug log ($windir$\debug\Dfsr#####.log) on the primary member will also show:

     

    20070220 14:30:46.673 344 CSMG 1154 ContentSetManager::UpdateContentSet Primary bit has changed

     

    Once the members see there is a primary member configured, the actual initial replication operation can take quite a while depending on link speed, the amount of data, whether it is prestaged, having adequate staging area configured, etc. But when it does complete the downstream member will log a 4104 event (successfully finished initial replication) in the DFSR event log.



    Laura Zhang - MSFT
    31. března 2009 10:37
    Moderátor
  • Problem - Q11: Windows Server 2008 network shares may become unresponsive with Symantec Endpoint Protection 11 or Symantec AntiVirus 10.2 client installed and Auto-Protect enabled.

     

    Symptom

    =========

    You try to access a network share that resides on a server that is running Windows Server 2008. However, the file sharing connection may drop unpredictably after some time, and then the network share becomes unresponsive.

     

    Possible Cause

    ============

    This problem occurs when the Windows Server 2008-based server is running certain versions of Symantec Antivirus. Some file filter drivers, such as SRTSP.sys, may cause this problem.

     

    Workaround

    ==========

    Disable or uninstall Symantec Antivirus on the Windows Server 2008 file server.

     

    Resolution

    ==========

    As described in the following Symantec article, this problem is fixed in Symantec Endpoint Protection 11.0.3001.2224 (MR3).Please obtain and install the latest build of Symantec Endpoint Protection.

     

    Windows Server 2008 network shares become unresponsive with Symantec Endpoint Protection 11 or Symantec AntiVirus 10.2 client installed and Auto-Protect enabled

    http://service1.symantec.com/support/ent-security.nsf/854fa02b4f5013678825731a007d06af/acb1ac0cabfc43278825746c006bc61a?OpenDocument



    Laura Zhang - MSFT
    31. března 2009 10:38
    Moderátor
  • Event ID 1102, event ID 2008, event ID 5002, or event ID 5014 may be logged when the DFS Replication service temporarily stops due to VSS

    This article applies to the following operating systems:

    • Windows Server® 2003
    • Windows Server 2008

    Symptoms

    One or more of the following event ID messages are logged in the application event log of a DFS Replication member server:

    Event Type: Information
    Event Source: DFSR
    Event Category: None
    Event ID: 1102
    Date: Date
    Time: Time
    User: N/A
    Computer: Server Name
    Description: The DFS Replication service has temporarily stopped replication because another application is performing a backup or restore operation. Replication will resume after the backup or restore operation has finished.

     

    Event Type: Information
    Event Source: DFSR
    Event Category: None
    Event ID: 2008
    Date: Date
    Time: Time
    User: N/A
    Computer: Server Name
    Description: The DFS Replication service stopped replication on volume VolumeName:

     

    Event Type: Error
    Event Source: DFSR
    Event Category: None
    Event ID: 5002
    Date: Date
    Time: Time
    User: N/A
    Computer: Server Name
    Description: The DFS Replication service encountered an error communicating with partner PartnerServerName for replication group ReplicationGroupName.

     

    Event Type: Warning
    Event Source: DFSR
    Event Category: None
    Event ID: 5014
    Date: Date
    Time: Time
    User: N/A
    Computer: Server Name
    Description: The DFS Replication service is stopping communication with partner PartnerServerName for replication group ReplicationGroupName due to an error. The service will retry the connection periodically.

    Cause

    The VSS framework notifies the DFS Replication server VSS writer when a backup is about to occur, and DFS Replication temporarily suspends activity. This behavior is by design; if the DFS Replication service did not pause during VSS snapshots, data consistent snapshots would be impossible.

    Resolution

    When the VSS framework notifies the DFS Replication VSS writer that the backup is complete, DFS Replication returns to normal operation.

    Additional references

    See the following resources for more information about this issue:

    Content by Daniel Albright, Windows Server User Assistance


    Jason Gerend, Technical Writer - Windows Server User Assistance
    9. listopadu 2009 19:29
  • Thanks for sharing this valuable information (for giving the answers) Thanks & Regards -------------------------------

    Data storage dubai

    12. května 2010 12:35
  • Why do you/Microsoft say that you can use FSMT 1.2 on Windows 2000 server when you cannot?  Even though at 

    At http://www.microsoft.com/windowsserver2008/en/us/file-print.aspx, it specifically states: “The File Server Migration Toolkit contains two step-by-step wizards that helps administrators migrate existing file servers to Windows Server 2008 R2 in an easier fashion and less error prone. FSMT can be used to migrate from Windows NT, Windows 2000, Windows 2003 R2, Windows 2008 to a new Windows Server 2008 R2 server. ”

    But the whitepaper does not mention Windows 2000 and when launching the utility on a Windows 2000 server it states: “Microsoft File Server Migration Toolkit is not supported on this version of Windows”…

    Anxoiusly awaiting a response.

    Thanks in advance

     

    21. června 2010 21:47
  • Just an FYI, but extended support for Server 2000 ends July 13, 2010.  You might want to look at upgrading that server before then. 
    22. června 2010 19:02