In addition to bug fixes, Novell Dynamic File Services 2.1 provides the following new features and changes for the Service and management tools:
Dynamic File Services Group: The user that installs Dynamic File Services is automatically added to the Dynamic File Services group. This allows the user to create and manage pairs, policies, and schedules. Other user names can be added to the group. For information, see Section 6.3, Configuring Administrators for Pair Management.
Retention Reviewers: The Dynamic File Services Retention Review group is automatically assigned as a reviewer of a retention pair. You can remove it from the Reviewers list, if desired. For information, see Section 12.2.1, Adding or Removing Reviewers for a Retention Pair.
Cloud Engine: You can use your cloud storage as the secondary path of a retention pair. The Cloud Engine allows Dynamic File Services to read and write files to cloud storage, while preserving the ACLs and metadata for the files. See Section 4.11, Using Cloud Storage as the Secondary Path in a Retention Pair
Cloud Database: The Cloud database stores information about the cloud accounts you have defined on the Dynamic File Services server, including credentials and retention pair associations. See Cloud Database Files.
Cloud Engine Logging Levels: You can configure the logging levels for the Cloud Engine. See Section 6.7, Configuring the Logging Level for Engines.
Policy Database: The policy database definitions and associations are now managed in a single database file. The default location is:
C:\Program Data\Dynamic File Services\Policies\DswPolicyDatabase_v2.xml
Pair Check Utility:
The Synchronize Pair utility was renamed as the Pair Check utility. For information, see Dynamic File Services Pair Check Utility
in the Dynamic File Services 2.2 Client Commands and Utilities Reference.
Pair Tiering: Dynamic File Services allows you to tier your storage solution by using the secondary path of a standard pair as the primary path of a retention pair. The standard pair and retention pair can reside on the same or different server. Previously, tiering was allowed only if the standard pair and retention pair were on different Dynamic File Services servers.
Pair tiering can be used to move data from local storage to filers to cloud storage at different stages of its life cycle. See Section 1.1.5, Tier Data across Local Storage, Filers, and Cloud Storage.
Cloud Storage: You can specify a path on cloud storage as the secondary path of a retention pair.
Retention Pair Reviewers: You can use the Section 12.2.1, Adding or Removing Reviewers for a Retention Pair.
tab in a retention pair’s Properties dialog box to add and remove reviewers for pair. SeePolicy Database: The policy database definitions and associations are now managed in a single database file. The default location is:
C:\Program Data\Dynamic File Services\Policies\DswPolicyDatabase_v2.xml
When you upgrade to version 2.1, your existing policy database files are consolidated into this single file. Any policies saved in the Snapshots folder are also converted to the new database format.
Use File Content to Determine Type: For a File Types policy, you can determine file types based on actual file content format. See File Types.
Moving Ownerless Files: A {No owners} entry is available in the Select a User browser dialog box for the File Owners policy option. See File Owners.
File Types Configuration File: The following changes were made to the definitions in the DswFileTypes.cfg file:
The application category is used for non-binary application files.
The octet-stream category is used for binary, executable files, such as .dll, .exe, and .bin.
MIME Types Configuration File: The DswMimeTypes.cfg file allows you to add, remove, or modify MIME type mappings to file extensions. For information, see Section 9.3.3, Configuring MIME Types and Categories for the Content Filter.
You can set up your cloud storage provider as a cloud account in Dynamic File Services. See Section 11.0, Creating and Managing Cloud Accounts.
You can specify a path on a cloud account as the secondary path for a retention pair. See Section 4.11, Using Cloud Storage as the Secondary Path in a Retention Pair.
Performance enhancements were made for the Web-based Retention Review Service.
The Section 12.2.1, Adding or Removing Reviewers for a Retention Pair.
tab on the Pair Properties page allows you to specify users and groups as reviewers of a specific retention pair. SeeThe following event types have been added to the Notification Service events:
Pair Modified
Cloud Account Created
Cloud Account Deleted
Cloud Account Modified
Cloud Path Included in a Pair
Change Logging Options
If you upgrade, these events are deselected by default. After the server restart, you can configure these events for email addresses and Twitter accounts. For information, see Section 6.6, Configuring the Notification Service.
The following event types have been added to Audit Tracking events:
Pair Modified
Cloud Account Created
Cloud Account Deleted
Cloud Account Modified
Cloud Path Included in a Pair
Change Logging Options
If you upgrade, these events are deselected by default. After the server restart, you can configure these events for audit tracking. For information, see Section 6.5, Configuring Audit Tracking Events.