In addition to bug fixes, Novell Dynamic File Services 2.1 provides the following enhancements and changes for installation and upgrade:
You can perform an in-place upgrade from Dynamic File Services 2.0 to Dynamic File Services 2.1. A computer restart is required. For information, see Section 5.0, Upgrading to Dynamic File Services 2.2.
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. After the reinstallation, you must register a license key, and perform the verification tasks described in Section 5.5, Post-Upgrade Changes and Tasks. For information about uninstalling the product, see Section B.0, Using the Uninstall Tool to Modify, Repair, or Remove Dynamic File Services.
Dynamic File Services 2.1 requires Microsoft .NET 4.0.2 to be installed before the product can be installed or upgraded. For information, see Section 2.3, Software Requirements.
Dynamic File Services 2.1 requires a Registration License Key. For information, see Registering the License Key
in the Dynamic File Services 2.2 Administration Guide.
In a cluster, you add the Windows Registry entry for Dynamic File Services setup to the cluster resource so that the Service’s value can be used to decrypt the license file from any active node. For information, see Section 4.1.5, Dynamic File Services License Key.
The user who installs Dynamic File Services is automatically added to the Dynamic File Services group. This allows the user to create and manage pairs, policies, schedules, and cloud accounts. Other user names can be added to the group after the installation is completed. For information, see Configuring Administrators for Pair Management
in the Dynamic File Services 2.2 Administration Guide
Dynamic File Services 2.1 allows reviewers to be specified separately for each retention pair. When you upgrade to version 2.1, the Dynamic File Services Retention Review group is automatically added to the Reviewers list for each retention pair. Other users and groups can be added to the Reviewers list after the upgrade is completed. For information, see Configuring Reviewers for a Retention Pair
in the Dynamic File Services 2.2 Administration Guide.
New file type definitions have been added to the C:\Program Files\Dynamic File Services\DswFileTypes.cfg file. When you upgrade to version 2.1, the old file is saved as DswFileTypes_v2.0.cfg. If you personalized the file type definitions, you should merge your additions or changes in the new file after the upgrade is completed.
The policy database definitions and associations are now managed in a single database file. The default location is:
C:\ProgramData\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.
The cloud engine executes policy tasks to move files in a retention pair from the primary path to the secondary path that resides in a cloud-based storage location. The cloud accounts database is stored in the C:\ProgramData\Dynamic File Services\Clouds folder.
Dynamic File Services 2.1 provides Cloud events for notification and audit tracking. If you upgrade from an earlier version, these events are deselected by default. After an upgrade, you can use the Audit Configuration tool and Notification Configuration tool to enable these events. For information, see Configuring Audit Tracking Events
and Configuring the Notification Service
in the Dynamic File Services 2.2 Administration Guide.
The Dynamic File Services 2.1 Notification Service has changed the encryption of email and Twitter account credentials. When you upgrade to version 2.1, the credentials are decrypted, then re-encrypted. After an upgrade, you should verify that your notification setup for email and Twitter accounts are working as expected. For information, see Section 5.5, Post-Upgrade Changes and Tasks.
In a cluster, you add the Windows Registry entry for Dynamic File Services setup to the cluster resource so that the Service’s SSL certificate can be used from any active node. Previously, the SSL certificate was server-centric in a cluster. For information, see Section 4.1.6, Dynamic File Services SSL Certificates.
The SyncPair utility has been 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.