Novell Dynamic File Services 2.1 Readme

June 8, 2012

1.0 Documentation

The following resources provide information about Novell Dynamic File Services 2.1:

2.0 What’s New in Version 2.1

Dynamic File Services 2.1 includes many new capabilities. For information, see the following:

3.0 System Requirements

For information about system requirements and installation guidelines, see Planning the Installation in the Novell Dynamic File Services 2.1 Installation Guide.

For information about requirements for pairs and policies, see Planning for Pairs and Policies in the Novell Dynamic File Services 2.1 Administration Guide.

4.0 Installation and Upgrade Issues

This section describes known issues for installing or upgrading Dynamic File Services.

4.1 A System Reboot Is Required after an Upgrade

A computer restart is required after upgrading from Dynamic File Services 2.0 to Dynamic File Services 2.1. During the upgrade, the product databases and configuration files are automatically updated to the new format, and your existing license key is automatically registered. The restart is required to apply the settings.

A computer restart is not required if you uninstall the old product (making sure to keep the existing program data files), then install the new product. The retained databases and configuration files are updated to the new format during the reinstallation. However, your existing license key is not automatically registered. After the reinstallation, you must register a license key.

4.2 Disabling Simple File Sharing on Windows XP

You can test Dynamic File Services features on a Windows XP workstation by installing the Service component along with the Management component. Using the Service component on a workstation is allowed for testing purposes only, and is not supported for a production environment. In order to use the Service component on a Windows XP computer, you must disable simple file sharing.

By default, simple file sharing is enabled on Windows XP computers if the computer is not a member of an Active Directory domain. Simple file sharing allows you to easily share folders in a workgroup, but you cannot prevent specific users and groups from gaining access to your shared folders. If simple file sharing is disabled, you can specify which users and groups have access to shared folders on your computer, and those users must provide a password to gain access to your shared folder.

When you run the Dynamic File Service on a Windows XP computer, the Windows simple file sharing feature must be disabled. This allows the Service to control access to files and folders in a pair. You cannot set up pairs and policies until simple file sharing is disabled.

To disable the simple file sharing feature:

  1. Use one of the following methods to open the Folder Options dialog box:

    • In the Control Panel, double-click Folder Options.

    • Open a Windows Explorer browser, then select Tools > Folder Options.

  2. In the Folder Options dialog box, select View to see the Advanced Settings options.

  3. In the Advanced Settings section, deselect the Use simple file sharing (Recommended) check box.

    This is usually the last option in the list.

  4. Click Apply to All Folders, then click OK to apply and save your changes.

5.0 Known Issues

This section contains known issues in this release of Dynamic File Services.

5.1 File Transfer Size Exceeded Error

A File Transfer Size Exceeded error can occur if a policy or manual move attempts to upload a file that exceeds the maximum file size allowed by your cloud provider.

The maximum size per file that can be uploaded to cloud storage is governed by the service level agreement with your cloud storage provider. The storage quota and file size limit is enforced by your provider. In addition, a file must be smaller than the remaining available space below your quota. For information, see Maximum File Size for Uploads to Cloud Storage in the Dynamic File Services Administration Guide.

5.2 Browse for Include/Exclude Returns a Blank Screen

The Include/Exclude feature cannot be used on a retention pair that has a remote primary location. A blank screen is returned when you browse for folders to include or exclude.

This issue affects only retention pairs because only retention pairs can use remote primary locations.

5.3 Restriction for Path Folder Names when a Pair’s Paths Are on the Same Drive

The folder names for a given pair’s primary path and a secondary path must not begin with the same or similar sequence of characters if both paths are on the same device. When the initial sequence of characters is too similar, a fatal error occurs when you navigate the pair’s files with a file browser. This is not a problem if the paths are on different drives.

For example, assume that a pair on server1 has a primary path F:\bob, a secondary path F:\bobsecondary, and a network share \\server1\bob on the primary path. A fatal error occurs when Bob accesses the share \\server1\bob and attempts to navigate the files with Windows Explorer.

5.4 Remote Merged View for a Windows Client Fails with NetApp

When you use a NetApp Filer as the Secondary share path in a Dynamic File Services pair with a Windows 2008 Server as the Primary share path, the merged view fails for a Windows Client using SMB2 (such as a Windows 7 or Windows Vista computer).

To work around this issue, you can do one of the following:

  • Enable SMB2 on the NetApp Filer.

    We tested NetApp Release 8.0.1RC3X167-Mode to verify that this solved the problem.

  • Disable SMB2 on the Windows 2008 Server running Dynamic File Services that hosts the Primary Share, then enable SMB1 on the Windows 2008 Server.

  • Disable SMB2 on the Windows Client (Windows 7 and Windows Vista).

To disable SMB2 and enable SMB1:

  1. Log in to the server as a user with Administrator privileges.

  2. At the command prompt, open the Registry Editor by entering

  3. In the Registry Editor, go to the following location:


  4. Create a DWORD value named Smb2, then set its value to 0.

    This disables server-side SMB2 on the server. (A value of 1 enables SMB2.)

  5. If there is no value named Smb1, create a DWORD value named Smb1, then set its value to 1.

    This enables server-side SMB1 on the server. (A value of 0 disables SMB1.)

  6. Exit the Registry Editor.