In addition to bug fixes, Novell Dynamic File Services 2.0 provides the following new features and changes for the Service and management tools:
The Dynamic File Services Retention Review group is used to configure reviewers to manage the retained data in a retention pair. For information, see Section 12.2, Configuring Reviewers for a Retention Pair.
License Key registration is required to create multiple pairs and policies. A single pair and policy are available in evaluation mode. See Section 6.2, Registering the License Key.
C:\ProgramData\Dynamic File Services is used as the default location for storing program data files on the Windows Server 2008/2008 R2 and Windows Vista/7 operating systems.
Pairs that provide a merged view are now referred to as standard pairs.
Retention pairs are a new type of pair that allows you to specify a primary path that contains active files, and a secondary path where a retention repository is used to store inactive files. Files can be moved from the primary path to the repository by using policies, the option, and the option for a pair. For information, see Section 12.1, Understanding the Retention Repository.
The following new capabilities support retention pairs:
Policy engine creates a retention repository on the secondary path
Remote primary path and secondary path support
Non-administrator reviewers via the Dynamic File Services Retention Review group
Retention Review events
Notification review schedule
Retention Review Service provides a Web UI for retention data review
Review Transaction History records delete and restore actions during retention reviews
Export review actions as reports in .csv and .html format
UserName-SID database so files do not become orphaned if owners become invalid
The Frequency option for policies is replaced by the Schedule feature. A schedule can be associated with and disassociated from a policy. For information, see Section 10.0, Creating and Managing Policy Schedules.
An identity-based filter option is available for Groups. For information, see File owners.
The File Types filter option has been expanded to include a list of perceived type associations that are defined in the ..\Dynamic File Services\DswFiletypes.cfg file. For information, see File Types.
Policy names can be modified.
Policy schedules are now available as a separate manageable unit. Schedules determine when automated policy runs are executed. A schedule can be associated with and disassociated from a policy. You can use the same schedule for multiple policies. For information, see Section 10.0, Creating and Managing Policy Schedules.
Policy schedule frequency has been expanded to include quarterly and custom dates. See Section 10.1.2, Schedule Frequency Options.
The Retention Review Web interface is available for viewing and managing data that has been moved to the retention repository in a retention pair. For information, see Section 12.6, Reviewing Files in the Retention Repository. Instructions for non-administrator reviewers are available in the Novell Dynamic File Services 2.0 Retention Review Quick Start.
The Twitter notification add-on for the Notification Service allows you to Tweet notifications to configured Twitter accounts. See Section 6.6.3, Setting Up Twitter Notifications.
Events can be configured separately for each email address and Twitter account. Previously, events were set globally for all recipients. See Section 12.3, Configuring Reviewers to Receive Notifications.
Retention review events are available in the Notification Service. See Retention Review Events.
Schedule events are available in the Notification Service. See Policy Schedule Management Events.
Registration events are available in the Notification Service. See Registration Events.
The Repair tool was revised to allow you to apply the last-known-to-be-valid snapshot of the databases. You can also manually take a snapshot of the databases. SeeSection 14.0, Repairing the Pair, Policy, and Schedule Databases.
The Filter Driver Diagnostics tool allows you to capture information about your configuration and runtime errors to help troubleshoot merged view problems. See Section 16.15, Diagnosing a Filter Driver failure.