Novell Dynamic File Services 2.2 Readme

September 2014

1.0 Documentation

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

2.0 What’s New and Changed in Version 2.2

Novell did the following:

  • Made bug fixes.

  • Added support for the following:

    • The Management Console on Window 8 and 8.1.

    • The Service and Management console on Windows Server 2012 R2 and Windows Server 2012 R2 with update.

  • Added code to assist Novell’s compliance team with usage tracking.

  • Added code to not allow more than 16 standard pairs to be created.

  • Updated the UI with the new Novell look and feel.

  • Removed support for the following:

    • 32-bit platforms

    • Cloud connections

    • Twitter notifications

    • Windows XP

    • Windows Server 2003

3.0 System Requirements

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

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

4.0 A System Reboot Is Required after an Upgrade

A computer restart is required after upgrading from Dynamic File Services 2.1 to Dynamic File Services 2.2. During the upgrade, the product databases and configuration files are automatically updated to the new format, and your existing license key is automat ically 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.

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.