2.3 What’s New for Dynamic File Services 2.0

In addition to bug fixes, Novell Dynamic File Services 2.0 provides the following new features and changes for the client commands and utilities since Dynamic File Services 1.6:

2.3.1 Registration Actions

Registration is required to create multiple pairs and policies on the Dynamic File Services server. The registration action allows you to register a product key and check its status. See Section 3.7, Registration Actions.

2.3.2 Pair Actions

Dynamic File Services now supports two types of pairs: standard and retention. The following changes and enhancements were made to provide this support in the command line interface:

Standard Pair

The standard pair supports the merged view of two paths for users. Only local primary paths are supported for standard pairs. The secondary path can be a local path, a remote share on a network filer (like NetApp or EMC), or a remote share on a supported Windows platform. Standard is the default pair type.

Retention Pair

The retention pair provides a retention repository on the secondary path. Users see files only on the primary path. Primary path and secondary path for a retention pair can be any combination of a local path, a remote share on a network filer (like NetApp or EMC), or a remote share on a supported Windows platform.

You can perform the following actions on a retention pair:

A review schedule indicates when review notifications are sent to designated reviewers. This works only if the Notifications Service is configured, and if reviewers are configured to receive notifications about the retention review events. You can associate one review schedule with a retention pair.

Upgrade Changes for Existing Pairs

If you upgrade to version 2.0 and have existing pairs, each pair’s definition is modified to add the pair type “standard” in the pair database.

Pair Type Option

The -pairType option allows you to specify the type of pair to create. See -pairType.

Exclude/Include Option

The -exclude and -include options for a pair are not supported for pairs with remote primary paths. Only retention pairs allow remote primary paths. See Section 3.8.5, Add Exclude/Include Paths to a Pair.

2.3.3 Policy Actions

The following changes and enhancements were made to policy actions:

Policy Schedules

Dynamic File Services now manages a policy separately from its policy. For information, see Section 2.3.4, Schedule Actions.

Upgrade Changes for Existing Policies

Schedules are now managed separately from policies. If you upgrade to version 2.0 and have existing policies, each policy’s schedule is extracted from the policy, and saved as a schedule with the same name as the policy. You can associate one policy schedule with a policy.

Renaming a Policy

You can now modify a policy name. See Section 3.9.3, Modify a Policy.

Policy Action Options

The following changes and enhancements were made for policy actions:

Policy Action Option

Change Description

-execute

This option replaces the -run option. See Execute a List of Policies on a Pair.

-run

This filter option is now an alias for the -execute option. See Execute a List of Policies on a Pair.

Filter Options

The following changes and enhancements were made for policy filter options:

Filter Option

Change Description

-execute

This option is new for policies. It replaces the -run option. See Execute a List of Policies on a Pair.

-fileTypes

This filter option was expanded to use the perceived types defined in the Dynamic File Services\DswFileTypes.cfg file in addition to the MIME and perceived types found in the server’s Windows Registry. See -fileTypes [-fileContent].

-groups

This filter option is new for policy filters. It allows you to move files based on a group identity. See -groups.

-run

This filter option is replaced by the -execute option. It is still supported as an alias. See Execute a List of Policies on a Pair.

2.3.4 Schedule Actions

Schedules are now managed separately from policies. For the command line, you can create a schedule for policies and retention reviews. See Section 3.10, Schedule Actions.

The following enhancements were added for policy schedules:

Filter Option

Change Description

-custom

This filter option is new for policy schedules. See Section 3.10.3, Add a Policy Schedule.

-quarterly

This filter option is new for policy schedules. See Section 3.10.3, Add a Policy Schedule.

last

When specifying the schedule dates option, use the “last” option to specify that the policy runs on the last day of every month. The policy runs on day 28, 29, 30, or 31, according to how many days are in the month.

The notification review schedule for retention pairs supports only monthly, quarterly, yearly, and custom frequencies.