Thursday, 22 October 2015

70-411 Exam Cram - Configure File and Print Services

Configure Distributed File System

Install and configure DFS namespaces

  • A standalone namespace is recommended if the namespace server is not a member of an Active Directory domain, or if the domain functional level is below Windows Server 2008

Configure DFS replication targets

  • Replication targets are not required to be namespace servers
  • You can create a custom topology to perform one-way replication between DFS replication targets
  • The 'Full mesh' replication topology will replicate data bi-directionally
  • Hub and spoke requires at least 3 servers
  • The 'Full mesh' replication topology is not recommended when you have a replication topology with more than 10 servers
  • EFS is not compatible with DFS replication

Configure Replication scheduling

  • The replication group schedule default is 24 hours a day 7 days a week. You can edit the replication group schedule to improve performance of other applications during business hours

Configure Remote Differential Compression settings

  • Remote Differential Compression is ideal in a Wide Area Network (WAN) scenario, because only the changes in files are replication. In a Local Area Network (LAN) environment or when there are large numbers of small files, Remote Differential Compression can decrease performance or cause high CPU utilisation

Configure staging

  • When configuring Distribution File System Replication (DFSR), you must size the conflict and deleted folder and staging folder appropriately. You can use the Set-DfsrMembership cmdlet to do this. If the folders are not sized appropriately, replication can be slow or stop. Cleaning up the staging folder will not resolve the issue permanently
  • Set-DFSRMembership is used to configure settings for a DFS replication member including the local content path, staging settings, and more
  • The staging folder should be configured as below:
    • Read/Write - The staging folder should be as large as the largest 32 files
    • For Read Only - The staging folder should be as large as the largest 16 files

Configure Fault Tolerance

  • To provide high availability for a DFS namespace, you can deploy the namespace server on a failover cluster using the DFS management snap-in

Clone a DFS Database

  • The export command and the creation of a replication group are run on the upstream server
  • The import command is run on the downstream server
  • The upstream and downstream servers do not need to be part of an existing replication group and replication does not need to be paused
  • Export-DFSRClone, Robocopy and Import-DFSRClone can be used to setup a new replica including the seeding of files
  • You can also use Windows Server Backup to preseed files

Recover DFS Databases

  • To manually recover a DFS database that has suffered an unexpeted shutdown, run the following command:
    • wmic /namespace:\\root\microsoftdfs path dfsrVolumeConfig where volumeGuid="<volume-GUID>" call ResumeReplication
  • In the event of power failure resulting in corruption to the DFS database, you can clone a DFS database instead of waiting for automatic nonauthoritative recovery to complete, before importing a clone, remove the server from the replication group before starting recovery, use DFSRAdmin membership delete to complete this

Optimise DFS replication

  • The DFS Staging folder must be sized appropriately to optimise replication performance
  • If Event ID 4208 occurs many times in one hour, increase the size of the staging folder by 20%

No comments:

Post a Comment