Novell Dynamic File Services v2.1, User does not see files that reside on the secondary through the merged view.

User does not see files that reside on the secondary through the merged view.

• Ensure the "Dynamic File Services" Service is running by right clicking on the "Dynamic File Services Controller" (Blue round icon in bottom right of Desktop). "Service Enabled" should be Checked. 
• Enable Service if it is not running.

• Ensure the Filter Driver is loaded.  In a DOS box, use the command "fltmc" to display loaded filter drivers.  Ensure that "DSWFlt" is displayed in the list.
  
• "fltmc load dswflt" if the filter driver is not running.
• Note: fltmc requires Administrator rights. To launch an elevated CMD prompt, go to the windows "Start " button, type in "cmd.exe" search field, right click cmd.exe in the list, and choose "Run as administrator". 
  

• Filter Driver can only manage up to 16 Pairs.
• Will need to reduce the number of pairs on the server to be less than 16.
• To do this properly, files that reside on the secondary will need to be moved back the primary prior to breaking a pair.

• A Windows Share Must be defined at the same location on the Primary where the NDFS Pair is defined.
  
• Example:  If the pair is create at E:, then a Windows Share must be created at E:,  If the pair is created at E:\Primary, then a Windows Share must be created at E:\Primary.

• ProxyUser (NDFS-ServerName) may have sufficient rights
• If both the Primary and Secondary are local devices, then the configuration will be simple.
• The default rights should be sufficient to allow the "Dynamic File Service" service and Filter Driver to work correctly.  However if rights have been  restricted, then there may be an issue.
  
• If the Primary is local and the Secondary is remote on another server with Active Directory:
• On the Primary:
  
• Verify ProxyUser managing the "Dynamic File Services" Service. By default it will be a user by the name of "NDFS-ServerName"
  

• The "NDFS-ServerName " must be a member of "Dynamic File Services Storage Rights" Group.
  

• The "Dynamic File Services Storage Rights" must be a "Domain Admins" Group.

• The "Dynamic File Services Storage Rights" must have ALL rights to the Windows Share, where the Pair is defined. 

• The "Dynamic File Services Storage Rights" must have ALL NTFS rights, where the Pair is defined on the Primary.

• The Windows share on the Primary where the pair is defined must be published in Active Directory.

Provide Name and Network Path.

Pair-01 is now published through Active Directory.

• On the Secondary
  
• The "Dynamic File Services Storage Rights" must have ALL share permissions to the Windows Share, where the Pair is defined on the secondary.   Note: This share should not be published in AD. 
  
• The "Dynamic File Services Storage Rights" must have ALL NTFS rights, where the Pair is defined on the Secondary.
  
• Microsoft Dynamic Disk may have been reordered.
• If the system has been defined with Microsoft Dynamic Disk and one or more disks have been removed form the system, the Disk will be reordered and cause the merged view to fail.  Contact support for a new version of "DswIoctlsLib.DLL".

Also see: https://www.novell.com/documentation/dynamic_file_services/dynamic_admin_win/data/planning.html

NDFS expects Users/Rights to exist on the Primary prior to any policy move of files to the secondary.  Configuration issues are the most common reason for the merged view to fail.

If users are not able to see files through the merged view, move the files from the secondary back to the primary, to allow the business to continue to function while root cause is determined.

Provide the following information when contacting support:

• Config.txt created from "C:\Program Files\Dynamic File Services\DswDump.exe"
• Right click on the "Dynamic File Services Controller" (Blue round icon in bottom right of Desktop).Filter Driver Diagnostics,  "Save filter driver configuration" and "Save filter driver runtime log"
• Output form "net share" or "net view\\ComputerName"