Novell Storage Manager™ of this Document The Novell Storage Manage 2.5 Admin Guide is designed to help users become familiar with the basics

Novell

Storage Manager™

February 13, 2009

Administration Guide

2.5w w w . n o v e l l . c o m

Legal Notices

Condrey Corporation makes no representations or warranties with respect to the contents of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Condrey Corporation reserves the right to revise this publication and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes.

Also, Condrey Corporation makes no representations or warranties with respect to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Condrey Corporation reserves the right to make changes to any Condrey Corporation software product described herein, at any time, without obligation to notify any person or entity of such revisions or changes.

You may not export or re-export this product in violation of any applicable laws or regulations including, without limitation, U.S. export regulations or the laws of the country in which you reside.

Copyright © 2002-2009 Condrey Corporation. All Rights Reserved.

No part of this publication may be reproduced, photocopied, stored electronically or transmitted in any fashion without the express written consent of the publisher.

Document Version: 90126

Condrey Corporation TrademarksFile System Factory is a trademark of Condrey Corporation.AuditLogin is a trademark of Condrey Corporation.IUAdmin is a trademark of Condrey Corporation.Internet User Administrator is a trademark of Condrey Corporation.

Novell and other Third-Party TrademarksNovell is a registered trademark of Novell, Inc. in the United States and other countries.Novell Directory Services is a trademark of Novell, Inc.eDirectory is a trademark of Novell, Inc.NetWare is a registered trademark of Novell, Inc. in the United States and other countries.NCP is a trademark of Novell, Inc.NLM is a trademark of Novell, Inc.Windows is a trademark of Microsoft Corporation.

All other third-party trademarks are property of their respective owners.

Condrey Corporation 125 The Parkway, Suite 500Greenville, South Carolina 29615USA

ContentsCondrey Corporation Trademarks ........................................................................................................... 2

Novell and other Third-Party Trademarks ................................................................................................ 2

Contents .................................................................................................................................................. 3

Overview ............................................................................................................................................... 6

Introducing Novell® Storage Manager 2.5 ............................................................................................... 6

Lifecycle Management of Storage ........................................................................................................... 6

Purpose of this Document ....................................................................................................................... 7

What’s new in NSM 2.5 ........................................................................................................................... 7

What is different from NSM 2.0 ................................................................................................................ 7

Known Issues .......................................................................................................................................... 8

Installation ............................................................................................................................................... 9

Install Novell Storage Manager ................................................................................................................ 9

Overview ................................................................................................................................................. 9

Install or Upgrade of the Novell Storage Manager Engine ....................................................................... 9

Installing NSMAdmin to the local workstation ........................................................................................ 15

Upgrading Novell Storage Manager for eDirectory ................................................................................ 21

Configure Novell Storage Manager via NSMAdmin ............................................................................... 22

Installing and Deploying Event Monitors ................................................................................................ 27

Deploying Event Monitors for NetWare .................................................................................................. 27

Installing the Event Monitor for OES2 Linux .......................................................................................... 30

Installing the NSM Event Monitor for OES2 Linux ................................................................................. 30

Configuring the NSM Event Monitor for OES2 Linux ............................................................................. 30

Registering the NSM Event Monitor for OES2 Linux via NSMAdmin ..................................................... 32

Best Practices for NSM Event Monitors ................................................................................................. 33

Installing and Deploying NSM Agents (formerly Sentinels) .................................................................... 33

Deploying the NSM Agent for Netware .................................................................................................. 33

Installing the Agent for OES2 Linux ....................................................................................................... 36

Configuring the NSM Agent for OES2 Linux .......................................................................................... 36

Registering the NSM Agent for OES2 Linux via NSMAdmin .................................................................. 37

Getting Started ...................................................................................................................................... 38

Management Interface ........................................................................................................................... 38

Accessing the Management Interface .................................................................................................... 38

Using the Management Interface ........................................................................................................... 40

Config Tab ............................................................................................................................................. 40

Main Tab ............................................................................................................................................... 47

..............................................................................................................................................................60

Reports ................................................................................................................................................. 62

NSM Policy Creation ............................................................................................................................. 70

Policy Types .......................................................................................................................................... 70

How is a Policy Assigned and Inherited? ............................................................................................... 70

Policy Attribute Changes ....................................................................................................................... 71

Create/Edit Primary Policy ..................................................................................................................... 71

General .................................................................................................................................................. 71

User Policy Properties ........................................................................................................................... 72

Collaborative Properties ........................................................................................................................ 74

Policy Import .......................................................................................................................................... 76

Quota Manager ..................................................................................................................................... 77

Enabling and Configuring Quota Management for a Policy ................................................................... 77

Setting up Rights to Use Quota Manager .............................................................................................. 77

Using the Quota Manager Interface ....................................................................................................... 78

Executive Dashboard ............................................................................................................................ 79

Configuring the Executive Dashboard ................................................................................................... 79

Executive Dashboard Security Principle Object ..................................................................................... 79

Using the Executive Dashboard Interface .............................................................................................. 79

Storage Statistics ................................................................................................................................... 79

Event Statistics ...................................................................................................................................... 80

Reports .................................................................................................................................................. 80

Workflow ................................................................................................................................................ 81

Configuring Workflow ............................................................................................................................ 81

Setting up the Workflow Management Structure .................................................................................... 81

Using the Workflow Interface ................................................................................................................. 81

Appendix A - Novell Storage Manager Feature Matrix ........................................................................... 83

Overview Introducing Novell® Storage Manager 2.5Novell Storage Manager introduces management and structure to an unmanaged and unstructured network storage system and, in the process, automates the full lifecycle management of user and group storage. Leveraging network directory services (commonly referred to as “the directory”), Novell Storage Manager automates a comprehensive set of storage management tasks based on events, identities and policies that reside in the directory. In the process, Storage Manager can assure storage compliance while saving time and money.

Novell Storage Manager delivers secure, automated and flexible management for personal and group storage, and saves a lot of time.

Lifecycle Management of StorageNovell Storage Manager automates the full lifecycle of user and group storage through the directory-stored policies discussed above. In addition to creating user and group storage, Novell Storage Manager automates the management of:

• Role-based Data Provisioning: This means populating created user or group folders with specific documents. An example might be HR forms for the employee to complete during his or her first day on the job.

• Rights: Novell Storage Manager ensures that file system rights are applied consistently for users based on their roles in the enterprise.

• Quotas: Novell Storage Manager manages storage quotas or storage allocation as a user’s role changes. If, for example, a user’s role is changed, the storage quota could be increased or decreased automatically—according to policy.

• Renames: When a user is renamed in Novell eDirectory, the user home folder automatically renames the associated home folder and updates the home folder attribute in the directory, so the user can log in and access his or her storage.

File Grooming and Vaulting: You can set policies to move prohibited file types to a vault location on less expensive hardware or delete them altogether.

• User Moves: A common manual process for IT departments within companies with multiple locations is moving an employee’s storage when they transfer to a new city. Novell Storage Manager completely automates this process.

• Actions for Deleted Users: When an employee leaves your enterprise, you can have Novell Storage Manager automatically vault the storage, defer the cleanup of the storage for a set number of days or queue the storage to a defined manager.

• Inactive Users: Many enterprises do not delete users immediately but move them to an inactive state. Novell Storage Manager supports this practice by allowing you to configure an Inactive Users policy. When someone gets associated with this policy, his or her storage is moved to another location and rights are removed.

Purpose of this DocumentThe Novell Storage Manage 2.5 Admin Guide is designed to help users become familiar with the basics of Novell Storage Manager and to help experienced users understand some of the new features in NSM 2.5. the Admin Guide is not complete, but will grow to become a comprehensive NSM 2.5 Administrators Guide. The NSM 2.5 Administrators Guide will be updated occasionally as new concepts are explained more completely. The appearance and style of this document will probably change as well.

What’s new in NSM 2.5New interface based on .net 3.5. The new interface requires significantly fewer clicks to perform operations, and there are no windows to find and close before the next task can be performed.

New Netware Agents, formerly known as sentinel, are now separate from the event component.

Linux Event – an event monitor that runs natively on a linux system.

Linux Agent- an agent that runs natively on a linux system.

Auxiliary Storage- a feature that allows creation and management of secondary user storage

Aux map utility- a tool to map auxiliary storage

Extended group collaborative storage including multiple group backfills

Container based collaborative storage

Janitor

Multi-threaded engine, separate threads for performing work on user storage, auxiliary storage and collaborative storage.

Quota preservation on move (when quota management is turned on in policy)

Enhanced Dynamic Template processing – depth limit and ability to hide placeholder directories

What is different from NSM 2.0Storage reporting (sometimes referred to as snapshot management) has been moved to a separate product. It will be much faster, flexible, scalable and have many more reports and features.

Additional operations are delegated to the agent (formerly sentinel) including template copy and vault on delete.

Use Exact Case is available through user interface instead of as a load switch. This setting causes NSM to use the case that user names are stored in eDirectory.

ProxyHome is configurable and can be set in user interface.

Troubleshooting tools have been enhanced.

Known IssuesFor optimal results of browser driven elements of this system, Internet Explorer 7 is recommended.

Unicode and extended characters have limited support.

Events with object names containing unsupported characters, including ? and*, will auto-abort.

Best practice for upgrading include the recommendation that any servers prior to NW 6.5 sp7 running sentinels be removed or upgraded to sp7 or later prior to upgrade of NSM. Agent (which is now separate from event) will not run on NetWare versions prior to NW 6.5 sp 7.

URAccess has not been updated for this release.

Columns can be sorted by selecting column headers.

Linux Event and Agent require IP Addresses instead of DNS names.

NetWare does not support files larger than 4G. NetWare 6.5 sp 7 (or later) is required to handle files larger than 2G up to 4G.

Management action backfill Directory Merge only works for user storage. It does not work for group or container based collaborative storage, even though it shows up as an option in the User Interface.

UTF-8 support has not been included in the janitor reporting processing. This causes some reports to show inaccurate results when reading directories with extended characters.

InstallationInstall Novell Storage Manager

OverviewInstalling and configuring Novell Storage Manager consists of installing the engine on a NetWare 6.5 server, then deploying the user interface utility NSMAdmin on a workstation, and deploying desired Agent and Event components.

Install or Upgrade of the Novell Storage Manager EngineDownload the self-extracting executable file, Novell_Storage_Manager_2_5_for_eDirectory.exe, to begin the installation. This runs on a windows based machine running the Novell Client, connected to the server where the engine will be installed.

RequirementsNetWare 6.5 Service Pack 7 or later

ProcedureLaunch the Novell_Storage_Manager_2_5_for_eDirectory.exe and follow the prompts.

If performing an upgrade, choose the same location as the previous installed engine . If an existing installation is detected, the engine needs to be unloaded. Either allow the install program to unload the engine, or do it manually.

After unloading the engine, or if this is a new installation, a summary will be presented before the installation continues.

Installing NSMAdmin to the local workstation

Minimum RequirementsMicrosoft Windows XP SP2, Vista (32bit or 64bit)Microsoft .Net Framework 3.5Administrator Privileges

When the installation in complete, the following web page will be displayed to provide guidance in deploying Agent and Event and in setting up policies to begin managing storage.

Upgrading Novell Storage Manager for eDirectory

Configure Novell Storage Manager via NSMAdmin

1. Launch NSMAdmin executable.Click on Start->All Programs->Novell-Storage Manager->NSMAdmin

2. Login to the NSM Management Interface:

a. Server IP and Port#: <Your Servers IP Address or DNS Name>:8009b. User ID: Admin.OU.Org Note that the full distinguished dotted name is required.c. Password: xxxxxxx

3. NSMAdmin will start in Wizard Mode, click Next to continue.

4. Fill-in Server, Port, Tree, User Name, and Password fields, click Next to continue.

5. Browse for the NSM version 2.5 license or click the "Get a License" button, click Next to continue. Note: NSM requires a new license file for both fresh installs and upgrades from older versions.

6. Click Next, to extend the schema.Note: NSM requires that the eDirectory schema be extended for both new installs and upgrades.

7. NSM depends on a Proxy Account. This account by default will be created in the same container as the NSM Engine Server. If this is an upgrade please verify that the proper nsmproxy account is being referenced.

8. The NSMAdmin wizard can set the rights necessary for the proxy user. click Next to continue.

9. The NSM Engine wizard is now complete.

10. The NSM Engine will not finish initializing with this new configuration.Note: If this is an upgrade the Engine my take a few minutes to become available. As the Engine upgrades all of the existing policies, and initializes its workers.

Installing and Deploying Event Monitors

OverviewNSM for eDirectory now has two available Event Monitors one for NetWare and other for OES 2 Linux. The NetWare based Event Monitor is a NetWare Loadable Module (NLM), and uses NDAP over NCP to monitor eDirectory for events. The OES 2 SP1 Linux based Event Monitor runs as daemon, and uses LDAP to monitor eDirectory. Both Event Monitors use HTTP(S) to communicate with the Engine.

RequirementsNetWare 6.5 SP7 or later

Deploying Event Monitors for NetWare




3. Select the “Config” tab.4. Select “Event Servers” from the Component Config section.

5. If this is a new install, click the "Add" and select a server that meets the requirements for Event Monitoring.

6. If this is an upgrade, and the server meets the requirements, highlight the server to be upgraded and click the "Upgrade" button.

7. If this is an upgrade, and the server does not meet the requirements, highlight the server to be removed and click the "Remove" button.

This completes the steps for configuring a minimum of at least one event server for monitoring events in the Directory. Note: Two Event Monitors are needed per replica ring for best results.

A Results dialog confirming the results of the Event Monitor deployment is displayed.

Installing the Event Monitor for OES2 Linux

OverviewInstalling the NSM Event Monitor for Linux requires OES2-SP1 or SLES 10 SP2.

Note: NSM Event Monitors for Linux will not show up in NSMAdmin the same way as NetWare Servers. The NSM Event Monitor for Linux must be installed first on the Server. Once installed, the NSM Event Monitor will begin to send heartbeat messages to the NSM Engine which will allow the Event Monitor to be registered via NSMAdmin. Registration is required to allow the Engine to trust the Event Monitor.

Copy the novell-storagemanager-event-2.5.0-xx-installer.bin file from the NSM Engine component directory to the desired Linux server.

Installing the NSM Event Monitor for OES2 LinuxThe NSM Event Monitor for Linux must be installed from via terminal as root.

sh novell-storagemanager-event-2.5.0-xx-installer.bin

Accept the EULA.

When the installation completes the nsmevent-config utility will need to be run to configure the NSM Event Monitor for OES2 Linux. The utility can be run from the console by typing the following:

nsmevent-config

After the installation is complete the installer is prompted to configure the NSM Event Monitor for Linux using the nsmevent-config utility. The nsmevent-config checks to see if a nsmagentd.conf file

exists, and if not will create one. If the configuration (conf) file is created by the utility the utility will start in wizard mode to get the NSM Event Monitor for Linux configured, and accepting events.

Configuring the NSM Event Monitor for OES2 LinuxThe wizard mode of the utility will need to know the IP Address of the Engine Server, the port to communicate with the NSM Engine (8009 by default), the IP Address of the LDAP Server to be monitored, the port to communicate with the LDAP Server, and credentials to login for eDirectory (FDN of the NSMPROXY object). This information is saved into the nsmeventd.conf file.

/etc/opt/novell/storagemanager/event/nsmeventd.conf

Once the NSM Event Monitor is configured the utility will act as console to allow control, and management of the NSM Event Monitor for Linux.

The NSM Event Monitor for Linux logs are created in:

/var/opt/novell/storagemanager/event/log

The NSM Event Monitor for Linux binaries are located in:

/opt/novell/storagemanager/event/bin

The NSM Event Monitor has also has setup the standard rc script to allow the administrator quick access to start, stop, restart, and check the status of the NSM Event Monitor for Linux.

rcnsmeventd (start|stop|restart|status)

Registering the NSM Event Monitor for OES2 Linux via NSMAdmin1. Launch NSMAdmin, and select the “Config” tab.2. Select Event Servers from the Component Config section.

3. Click the “Add” button

4. Select the OES2 Linux Server from the list of heart beating OES2 Linux Event Servers.

5. Click the “Add” button. The NSM Event is now registered.

Best Practices for NSM Event Monitors

Things to be aware of when designing the NSM Event Monitor placement:

• Two (2) Event Monitors are needed per replica ring.

• The NetWare and OES2 Linux based Event Monitors can both be used to monitor the same replica, but should not monitor the same server.

Installing and Deploying NSM Agents (formerly Sentinels)

Deploying the NSM Agent for Netware




3. Select the “Config” tab.4. Select “Agent Servers” from the Component Config section.

5. If this is a new install, click the "Add" and select a server that meets the requirements for Agent Servers.

6. If this is an upgrade, and the server meets the requirements, highlight the server to be upgraded and click the "Upgrade" button.

7. If this is an upgrade, and the server does not meet the requirements, highlight the server to be removed and click the "Remove" button.

A Results dialog confirming the results of the Event Monitor deployment is displayed.

Installing the Agent for OES2 Linux

RequirementsThe Linux Agent requires an OES2sp1 machine with NSS installed. The NSS software must be installed, even if using native Ext3 or Reiser file systems. The OES2SP1 installation CD maybe required if any dependencies are missing.

Note: A 32-bit binary is provided. Installing this program on OES2sp1 64-bit is experimental and is unsupported at this time.

The NSM Event Monitor for Linux must be installed from via terminal as root.

sh novell-storagemanager-agent-2.5.0-xx-installer.bin

Accept the EULA, and allow the installation process to complete. Yast maybe called to install any missing dependencies.

Configuring the NSM Agent for OES2 LinuxWhen the installation completes the nsmagent-config utility will need to be run to configure the NSM Agent for OES2 Linux. The utility can be run from the console by typing the following:

nsmagent-config

After the installation is complete the installer is prompted to configure the NSM Agent for OES2 Linux using the nsmagent-config utility. The nsmevent-config checks to see if a nsmagentd.conf file

exists, or if not it will create one. If the configuration (conf) file is created by the utility the utility will start in wizard mode to get the NSM Agent for OES2 Linux configured, and accepting work from the NSM Engine.

Registering the NSM Agent for OES2 Linux via NSMAdmin1. Launch NSMAdmin, and select the “Config” tab.

2. Select Agent Servers from the Component Config section.

3. Click the “Add” button

4. Select the OES2 Linux Server from the list of heart beating OES2 Linux Agent Servers.

5. Click the “Add” button. The NSM Agent is now registered.

Getting StartedManagement InterfaceNovell Storage Manager™ NSMAdmin program is designed to provide a user management interface to manage network user, group and collaborative storage. The following are some of the operations that performed to manage a Novell Storage Manager™ using NSMAdmin

• Define Policies Storage management policies • Associate Policies with objects in the directory tree.• Configure NSM Parameters.• Perform storage management Action operations.• Track storage management process.

In addition to the NSMAdmin program, NSM has several web interfaces to help assist in the storage management process: an Executive Dashboard designed to provide access to reports and statistics from a separate interface for individuals who need easy access to the data, but who don’t need daily access to the actual management of Novell Storage Manager™ (see Chapter 14, Executive Dashboard.); an interface for help-desk or other personnel to manage quota for users whose storage is managed by Novell Storage Manager™ (see Chapter 13, Quota Manager); and a Workflow interface to help managers reassign files and folders when a worker leaves the organization.

Accessing the Management Interface

Novell Storage Manager™ Admin is a Windows application. NSMAdmin is built using the .Net framework (requires .net 3.5).

To access the Management Interface from a Windows workstation, run the executable (NDSAdmin.exe) from the local client workstation. Authentication is required at this point. Enter the server name or IP address with the secure port (usually 8009, NSM Admin will not authenticate over a non secure connection,) username, and password. The user must have appropriate rights to be able to access the functions of Novell Storage Manager.

The interface does have a timeout feature, and after a period of inactivity, re-authentication will be required. The authentication form will be presented again, requiring the password to be re-entered to continue. The timeout interval is configurable in the management interface.

Using the Management Interface

Once authenticated, the NSMAdmin start page is presented. The start page contains links to resources on NSM and information about updates and NSM News. The Start Page will include links to updated help information, Getting started links, NSM FAQs, Best Practices and trouble shooting. The start page also displays general overview graphs of the storage currently managed by NSM.

Config TabThe Config tab includes all of the operations to setup and configure Novell Storage Manager.

Engine ConfigurationThese elements provide configuration options for various features in Novell Storage Manager.

Executive DashboardThese options enable Executive Dashboard, and determine the information that will be available through the Executive Dashboard interface. All Executive Dashboard reports are disabled by default.

To secure access to the Executive Dashboard, Novell Storage Manager™ uses Security Equivalence to determine who has rights to login to the Executive Dashboard. To accomplish this, Novell Storage Manager™ supports any object type that supports security equals to (e.g. group and organizational role objects). Note: When setting the object for security principle, only user or group objects can be selected by browsing.

A single user may be designated as the security principle. If this option is selected, only this user will have access to the Executive Dashboard.

The external URL for accessing Executive Dashboard is http://your.server.name.or.ip.address:8008/FSF/HTTP_FSFExecutiveDashboard or for SSL:https://your.server.name.or.ip.address:8009/FSF/HTTP_FSFExecutiveDashboard

Options for the Executive Dashboard:Enable Executive Dashboard. If this box is checked, Executive dashboard is enabled. If it is

not checked, the external interface for Executive Dashboard will not be available. Report types are only selectable when this option is enabled.

Policy Statistics allows generation of a report which details the number of users and groups that are managed by given policies. It will also provide summary details of users and groups managed by all policies.

Storage Statistics reports disk space usage per volume grouped by policy.

Report Disk Usage allows generation of a report which details disk space usage grouped by policy, volume, user or group based upon the following time frames:

Time Frame --------------------------------------- Today 1 week ago 24 hrs ago 1 month ago 72 hrs ago 3 months ago

Events Statistics reports events processed by NSM daily for the following NSM Event Types:

User Group ---------------------------------------- Add Add Delete Delete Deferred Delete Deferred Delete Rename Rename Move N/A Set Policy N/A

Log File ManagementNovell Storage Manager™ maintains the following sets of log files related to its operation. These logs are relatively small in size and will not significantly impact free space on the volume. As a general rule, keeping the logs for at least 30 days is advised. The Engine automatically purges these logs based on the values set here.

Audit LogsThese logs are held in the AUDITLOG directory to track raw events in eDirectory and are used

by the Global Event Subsystem in Novell Storage Manager™ to resolve duplicate events. The minimum purge age for this parameter is 30 days.

Detail Reports These logs are held in the LOGS directory and record the actions that the Engine takes as it

operates on the Directory and the file system. These logs also record any actions taken in the web interface as well as the administrator name and browser address. The minimum purge age for this parameter is 30 days.

Management RightsConfiguration options for the Management Interface involve setting up users who have rights to run the Management Interface. To allow any user access who has rights to the server object for the server running the engine component select “Supervisor rights to the server object.” To set the rights based

on equivalency to an eDirectory object, select “Security Equivalent to the following object:” then browse to the desired user object. Any user security equivalent to the selected object will be able to run the management interface. Note: When setting the object for security equivalence, only user or group objects can be selected by browsing.

Action ObjectsThe Action Object panel is used to enable Action Objects in the NSM Engine (Refer to Action Object Manual for information on Action Objects). The Action Object container ensures that the NSM engine will only run Action Objects in this specified container.

Use Exact CaseIf the Exact Case option is set, NSM will create home directories using the case user names are stored in eDirectory .

WorkflowWorkflow includes a separate interface to allow managers to determine what should be done with the home directory of a deleted user. The intent of this subsystem is to allow policy definitions by which Novell Storage Manager™ can assign storage for deleted employees to their manager when they leave the organization. Workflow will not apply unless activated here. Checking the box and pressing Apply will automatically unload the engine. Load the engine again at the server console to restart. Workflow will consume system resources therefore should not be enabled unless policies in the directory tree have workflow configured.

The external URL for accessing the workflow interface ishttp://your.server.name.or.ip.address:8008/FSF/HTTP_FSFWorkFlow or for SSL:https://your.server.name.or.ip.address:8009/FSF/HTTP_FSFWorkFlow

Client TimeoutThe Client timeout option provides the ability to increase or decrease the default NSMAdmin client timeout (default is set to 30 minutes.) If the NSMAdmin is idle for this period of time, the engine will require the user to re-authenticate.

Component ConfigThe options in the component Config section are for managing the event and agent servers. Much of the operations for this section are detailed in the installation portion of this document.

Event ServersThe Event Servers tool lists the event servers providing data to the engine server and allows the administrator to view details on those event servers. The tool shows the version of each event server, along with the last time that every event server delivered events to the engine. The event count shown for each server is the number of events sent from that event server as of the last Heartbeat from the event server to the NSM Engine (encompassing events from the time the engine was last loaded.)

Selecting an Event Server from the list will enable the options available for the selected NSM Event server.

An Event server can be removed using the red X icon in the Event Servers section.

Additional options include reloading the Event Server and updating the Event Server, however, these options are only available for NetWare Event servers.

Selecting the Display Replica Coverage for all servers will return a list of the partitions stored on the server, and the replica type of each partition.

Agent ServersNSM Agent Servers take the load off of the Engine by locally handling the work to be completed in the file system, primarily copy data functions. NSM determines which agent will be used by determining the destination for the data. Proxy agents can be set up for servers which cannot run the agent, to help manage the work and reduce workload on the engine. For example, a proxy may be configured for servers on one side of a WAN environment to move data from one server to another on the same side of a WAN link. This will keep the data from crossing the WAN link only to cross back again.

Linux Agent Servers must be configured to allow the engine to delegate work to them. Agents are configured after installation. Once an agent is installed on a server, it sends a “heart beat” message to the Engine, letting it know that it is available to be configured. The installed Agent is not “trusted” and must be added to the Agent Server list. This is done by selecting “Add to Agent List.” This adds the server to the “trusted” Agents list within the Engine.

Selection of an Agent Server in the list of agents will highlight the actions that can be performed on the server, and allows the administrator to configure Agent Proxy for servers that are not able to run the Agent component.

An Agent server can be removed using the red X icon in the Agent Servers section.

Additional options include reloading the Agent Server and updating the Agent Server, however, these options are only available for NetWare Agents.

Client ConfigThis section enables customization of the NSMAdmin client and is stored on the individual workstation.

Communication

Proxy SettingsThe Proxy setting option is used to change the proxy for the NSMAdmin utility. By default NSMAdmin uses the Internet Explorer Settings. If an organization has set a different proxy setting and this causes communication problems for NSMAdmin, select the No Proxy option.

Directory Object Selector SettingsNSMAdmin creates a cache of directory objects for use in the Storage Management Panel. The cache speeds up display and use of the panel for environments with large number of directory objects. This option can be disabled by selecting the Disable Caching option. The cache by default will be refreshed every 20 minutes, but can be changed to an appropriate value for an individual environment and situation. As noted, caching is disabled when “Show Policy Info” is checked in the Storage Management panel, to ensure accurate information is displayed.

Quick AccessThe Quick Access option allows users to select the most used items in the NSMAdmin program and have the items appear on the Quick Access Toolbar (QAT). Items may be added or removed from the QAT by right clicking on the tools from their default location, or in the Quick Access window in Client configuration. By default the QAT is located in the title bar of NSMAdmin, but the location of it can be changed using the menu at the end of the QAT.

Main TabThe Main Tab is the heart of NSMAdmin. This section of the program provides all of the active management interfaces for NSM. From the Main Tab, NSM Polices can be created, managed and deployed.

HomeThe tools in the home section are primarily informational.

Start PageFrom the Main tab the NSMAdmin Start Page can be redisplayed (Front page).

Engine StatusThe engine Status form provides an overview of the current status of the NSM engine. It shows

whether events are being accepted and/or processed from the event servers. Click on the red or green status icon to toggle the function.

Counters identify what types of actions have been taking place. The General status and the Work Queue Status give details on version information and engine action details. Counters provide

detailed counts of what actions are being performed by NSM.

Storage ManagementThe Storage Management Tool provides a navigational view of the directory tree and objects of interest when using Novell Storage Manager.

In order to understand how to use the right panel functions of the Storage Management tool , a basic knowledge of NSM policies is required (for a detailed explanation refer to the next section on NSM Policy Creation. ) NSM has two types of storage management policies; Primary polices that are used to provision and manage user and collaborative storage, and auxiliary policies that are used to provision and manage secondary storage associated to users. A single primary policy can be associated to a directory object, like an OU. The associated primary policy can be configured to create and manage user storage for users under the organization unit. The same policy can be configured to create and manage storage for directory groups under the OU. The Policy can also be configured to create collaborative storage space for all users in the OU. The same policy can be used create either one, two or all three types of storage.

Only one NSM primary policy can only be associated with an OU. This means that if there is a need to have User and Collaborative storage for an OU, the policy associated with the OU must be setup to manage both user and collaborative storage. As stated earlier, the collaborative area of a primary policy can be setup to manage shared storage for directory groups and/or the OU. The option is selectable in the collaborative section of the policy editor.

The Storage Management Tool's primary purpose is to manage the associations between storage management policies and other eDirectory objects like OUs, Groups and Users. The left panel is designed to navigate the directory tree and select OUs. The Right panel displays the contents of the selected OU and provides options to manage storage for the OU. From this panel, NSM Policies can be created, and actions performed on directory objects.

Left Panel – Tree expansion (containers only)This pane shows the containers in the tree in hierarchical form. To expand the subordinate level, click on the plus sign next to the desired container. To view objects in a container, select the container by clicking on it. This will show the objects at that level in the right pane.

Selecting a container in the left panel and right clicking provides several options:

• Create OU – Creates an OU under the Object selected in left window.

• Create Primary Policy – Creates a primary policy in the selected OU.

• Create Auxiliary Policy – Create an auxiliary policy in the selected OU.

• Set Context – Sets the context to the left window to the object current selected. Context can be reset to root at any time with the same option.

Right Panel – Object listsUnderstanding how to use the Storage Management right panel is critical to using NSM 2.5. The key to successfully using this panel is to always know if you are managing storage for Users, Groups or Directory Containers. Select the appropriate icon in order to set the mode for the right window. The mode selection will determine which action-operation options (formerly called Backfill operations in NSM 2.0) are active in the right window. For example, to run a consistency check on users, the user icon must be selected before selecting user action.

The Right panel by default displays Containers, Groups, Users and Policies. The check boxes to the right of the mode buttons can limit or expand the directory objects displayed in the right panel. The “Show Policy Info” checkbox when checked shows information about the policies related to the directory objects. Displaying this information can be resource intensive. In order to provide the most accurate policy information at all times when the "Show Policy Info" checkbox is checked the cache settings configured in the “Client Config" tool will be ignored, and no caching will take place.

Action Operations (formerly Backfill Operations)In some cases, it may be necessary to retroactively apply a given policy to existing user storage and collaborative storage. Or it may be necessary to perform some administrative corrective action or operation on a large set of users, groups or containers. Novell Storage Manager™ collectively refers to

this type of operation as an Action Operation (formerly Backfill). An Action operation is issued through the Storage Management Tool.

Perform an Action operation on a container, a group, or an individual user object. User Action operations on a group will pull users from the group membership. User Action operations on a container will pull all users in the given container as well as all subordinate containers. Each user object is analyzed and worked with independently, regardless of whether the Action is initiated via container, group, or directly on an individual user. Each of the three ways of initiating an Action has a slightly different appearance. Some options are presented before initiating the Action.

• Mask Option -When running the Container or Group action, an option is present to enter a search filter to limit the objects analyzed. Standard wildcard characters are supported and multiple strings can be entered, separated by the “|” character.

• Sub-container Option-When running the Container action, an option is present to turn off the analysis of sub-containers. When this option is selected, only the objects in the selected container are analyzed and processed.

• Apply to associated Auxiliary Policies – If applicable, this option will allow the management action to be performed on the storage associated with the primary user policy and on the storage associated with any auxiliary policies connected to the user’s primary policy.

• Run in Check Mode – When selected, the action will be evaluated and all tasks associated with the operation will be listed, but will not actually be executed. Uncheck this option and click “Process Selected Targets” again to actually perform the action.

Setting the Scope for ActionsAction operations are different between user storage management and collaborative storage management. Because a policy can define behavior for both user and collaborative storage, it is necessary to define the scope for action operations. To be sure it is clear what operations are being performed select either User, Collab-Group, or Collab-Container scope. The Actions menu will change depending on what is appropriate for the given scope.

User Mode Scope - Selecting the Users Mode will set the focus of the Action Operations (Formerly called Backfill Operations) to perform user based action operations (see list below). If multiple users are selected the User Actions will be applied to all selected users. User Action operations on a group will pull users from the group membership. User Action operations on a container will pull all users in the given container as well as all subordinate containers. Each user object is analyzed and worked with independently, regardless of whether the Action is initiated via container, group, or directly on an individual user.

Collaborative Group Action Scope - Selecting the Collab-Group Icon will set the scope of the right window to group based collaborative storage actions and will set the focus of the Action Operations (Formerly called Backfill Operations) to perform group based collaborative storage action operations (see list below). Users will not be shown in the filtered list. If multiple groups are selected the Group Actions will be applied to all selected groups.

Collaborative Container Action Scope – Selecting the Collab-Container Icon will set the scope of the right window to container based collaborative storage. Users and groups will not be shown in the

filtered list. The focus of the Action Operations will be to perform container based collaborative storage operations.

The following two tables indicate which Management Actions are available in each scope and describes each management action.

Management Actions (formerly Backfill)Management Action User Mode Collaborative

Group ModeCollaborative Container Mode

Consistency Check Manage Enforce Policy Path Groom Apply Attributes Apply Members Apply Quota Apply Rights Apply Template Recover Home Directory Assign Home Directory Directory Merge Remove from Engine Database

Management Action DescriptionManagement Action DescriptionConsistency Check Performs check to determine if object is managed by

NSM.Manage Performs action to begin managing objects based on

policy.Enforce Policy Path Performs action to potentially move storage for objects

that are managed by NSM. Optionally, it will set an object as managed if it is not previously managed.

Groom Performs action to groom files in storage that is managed by NSM based on policy.

Apply Attributes Performs action to apply specified file system attributes to storage for an object that is managed by NSM.

Apply Members Performs action to provision member storage for groups and containers that are managed by NSM. Only applicable for collaborative group-based and container-based storage.

Apply Quota Performs action to apply quota to storage for an object that is managed by NSM.

Apply Rights Performs action to apply file system rights to storage for an object that is managed by NSM based on policy.

Apply Template Performs action apply a NSM template to storage for an object that is managed by NSM.

Recover Home Directory Performs action to recover and apply managed home directory based on NSM database for an object that is managed by NSM.

Assign Home Directory Performs action to assign home directory attribute for an object that is not currently managed by NSM.

Directory Merge Performs action to merge the contents of a specific directory with that of an object that is managed by NSM.

Remove from Engine Database

Performs action to remove managed objects from the NSM Engine database.

Note: Although Directory Merge is listed as available on collaborative storage, it is not active at this time.

Auxiliary Policy Action OperationsThe Auxiliary storage Action operations are designed to allow existing auxiliary storage that was not created by Novell Storage Manager to be brought into the NSM system to become managed storage. These operations can be performed from the Storage Management panel or from the Policy Management Panel. The key to the new process is uniqueness. For a given Auxiliary Storage, the User CN and the target folder names must match, but also must be unique. If two users share the same CN and are associated to the same Auxiliary Policy, NSM will not connect the storage. Likewise, if there are two folders with the same name in the target paths on the Aux Policy, the Management Action Process will not hook them up.

The Auxiliary Action Operations are performed on the actually auxiliary policy as compared to traditional NSM Action Operations which are run on the identity directory objects (users, groups and containers)

Auxiliary Action Operations include:• Manage (two options)o Use path specified by Auxiliary Attributeo Use path specified by NSM Engine Database (repairs Auxiliary Attribute• Groom • Apply Attributes• Apply Quota• Apply Rights• Assign Auxiliary Attributeso Assign using value in policy if Auxiliary Attribute not seto Assign using value in Policy and overwrite existing database values

The last auxiliary action operation - Assign Auxiliary Attributes – is a very powerful option and complex operation. The first option will look to see if there are any existing storage folders in the target paths configured in the policy and look to see if the folders names match the user CNs in the associated policies reference the auxiliary policy. If a unique match is found and the auxiliary attribute on the user for that policy is not set the operation will set the attribute and catalog the storage. If the attribute already has a value or no unique match is found (no two folders with the same name) no action is performed.

The other action will use the target path in the policy to see if unique folder matches can be found. If a match is found the action operation will overwrite the current auxiliary attribute and the database entry for the user.

Additional Right Click OperationsPolicy Management

This option focus changes depending on the object selected. If a User, Group or Container is selected the following options are available:

• Assign Policy – Graphic option to assign policies to directory objects• Create Primary Policy• Create Auxiliary Policy• Edit Assigned Policy• Edit Effective Policy

I f a policy is selected the following options are available:

• Create Primary policy• Create Auxiliary Policy• Edit Policy• Delete policy

The Policy Management options can also be invoked from the Policy Management button in the tool bar

Path AnalysisThe path analysis is available if the object selected with the right click has a storage path assigned to the object.

The following options are available:

• Folder Trustees - enumerates all users and objects that have any type of rights to the given folder and how the user got those rights. This includes file system trustee assignments or eDirectory object trustee assignments, including so-called "backdoor" rights assignments that filter through eDirectory into the file system.

• View Quota - This option shows the quota set for the folder. Option shows if quota is set, the quota size and the space available.

• File types – This option lists file types that are currently in the folder

• File Trustees - - enumerates all users and objects that have any type of rights to the given file and how the user got those rights. This includes file system trustee assignments or eDirectory object trustee assignments,

PropertiesThis option performs an analysis and displays details about the selected object. The properties will only display if the object is in the NSM database.

Policy ManagementThis option provides a list of all policies found in the directory. Each policy can have either User Properties or Collaborative Properties or both configured for use. In addition, policies configured for collaborative storage can be set to manage group collaborative storage, or container collaborative storage or both. The policy list also includes Auxiliary Policies can be listed in the table. The four left columns in the form display how the policy is configured. The form also provides options to filter the list of policies and to limit the scope of the list by only showing user, collaborative or auxiliary policies

From the Policy Management form quite a few policy options are available, these include:• Create Primary Policy• Create Auxiliary Policy• Edit Policy• Delete Policy• Perform Policy Actions (Auxiliary Policy Only)

Figure 1 NSM 25 UI Doc - Policy MGNT Actions- Graphic 30

The Auxiliary storage Actions are as described above in the Storage Management section.

Pending EventsThis tool provides the list of pending events in the engine. All of the pending events are listed, with details on the status of those events. Some events process very quickly and may actually have completed before they can be viewed. Others may remain in the queue for a long time, waiting for some condition to be met before they can be completed. There is a separate tab for deferred events. If a user is deleted, and the policy on that user indicates that the home directory should not be deleted for 30 days, that event will remain in the queue until the time is up before it can be completed, but will be shown on an alternate tab.

Each event also has a transaction number associated with it. Clicking on the transaction number provides additional information about the event and the object it is working on, and some additional options for troubleshooting purposes. Each option is explained in detail on the page to assist with troubleshooting.

Engine ProcessingOn the top right of the event list are the engine status icons for Accepting/Not Accepting and Processing/Not Processing. Clicking on these icons will toggle the action. Once turned off, the task selection item will change from Stop to Start. To turn the function back on, select the Start Accepting Events or Start Processing Events option. Stop processing events will cause the engine to stop working on the events in the queue. The engine will continue until the current event(s) in process are complete. Additional events will still queue up, unless Stop Accepting Events is selected. If this is turned off, no new events will be accepted from the event monitors. The event monitors will continue to collect and queue events, so events will not be missed, and when the engine is accepting events, all the queued events will be submitted. Work delegated to agents may complete but will not be reported to the engine until processing has been restarted. Select Start Processing events to resume the engine processing.

Volume ListThe Volume List allows administrators to rebuild the Volume cache list used in NSM dialogs to display a list of volumes on the network. NSM uses a Volume cache to speed the operation of NSM Admin. The Rebuild volume list will search the tree for all available volumes. This option may also be needed if during the course of creating or modifying a policy a volume does not appear in the list. Run this utility and retry the operation. This operation is run automatically at engine startup.

Figure 2 NSM 25 UI Doc - Volume List Graphic 31

Object Diagnostic Performs diagnostics on a single user object and returns details stored regarding that user object in Novell Storage Manager. (Object Diagnostics only works on objects managed by NSM. This same option is available in the Storage Management form by right clicking on the user object and selecting the “Object Diagnostic” menu item.

Figure 3 NSM 25 UI Doc - Object Prop Graphic 32

Server DiagnosticsSelect this option to perform a connectivity test to the volumes on the server specified. The browse button will return a list of server, select the server and press submit.

Figure 4 NSM 25 UI Doc - Server Diag Graphic 33

Reports The reports tab provides access to reports that provide information about NSM and reports about the network storage. Note: NSM 2.5 does not have a general storage reporting feature like NSM 2.0. The feature has been removed from the product. The reports have changed to better help administrators use NSM’s core functionality to better manage network user and collaborative storage.

Figure 5 NSM 25 UI Doc - Reports - Graphic 19

View Consistency Check ReportsConsistency Check reports are stored and available for review. Selecting this option bring up the list of consistency check reports available.

Figure 6 NSM 25 UI Doc - Con Check Report 20

Double-clicking the desired report will bring it up for review.

Figure 7 NSM 25 UI Doc - Con Check Rpt DSPt 21

View Action Reports (Formerly Backfill Reports)Action reports are stored each time an Action operation is performed. Use this option to view the results of any Action operation performed. A list of available Action reports will be presented, identifying the report by the object it was run on, and the time it occurred.

Figure 8 NSM 25 UI Doc - Con Check Rpt DSPt 21

Double-clicking any item in the list will bring up the action report.

Figure 9 NSM 25 UI Doc - Action Rpt DSPt 23

Anomaly ReportAnomaly Reports are a major new feature in NSM 2.5. The reports are designed to find and report on certain types of anomalies that can occur over time from the manual management of user and collaborative storage. The Following reports are available:

• Name Mismatch• Objects Not Cataloged• Orphan Candidates• Missing Home Directories• Path Cross Talk• Missing Auxiliary Storage• Duplicate Storage Pointer

Figure 10 NSM 25 UI Doc - Anomaly RPT Graphic 24

Runtime ReportsRuntime reports are used to report on the current state of NSM and to configure Janitor Operations for the Anomaly Reports and Global Statistics.

Runtime Config (formerly DumpConfig)Runtime Config Reports are used to build reports on the current configuration and processing taking place in the NSM Engine. In NSM 2.0 these reports were called DumpConfig Reports and could be quite large due to reporting on the entire configuration and status of the NSM Engine. In NSM 2.5 the Runtime Config reports have been configured let administrators choose if they want the entire configuration or only certain parts of the configuration. Options include:

• All Settings• Engine Work• Delegated Work• Full Process List• Agent Servers• Event Servers• Policy List• Full Replica matrix• Volume List• Action Object Processing

Figure 11 NSM 25 UI Doc - Runtime CFG Report 25

Double clicking on any runtime report will open the report in notepad (or configured program for .txt files.

JanitorThe janitor by default is scheduled to run every 24 hours at midnight. The janitor collects the information used in the Anomaly Reports and the Global Statistics. Administrators can use this option to force the Janitor to run to collect current information. A word of caution – the Janitor can be resource intensive. Care should be used when running the Janitor on large networks during peak traffic load on the NSM Engine Server.

Event StatisticsThe Event statistics page gives a daily view of the same event statistics that are tracked on the Engine Console. The current day and the previous three days are shown. Counts will be different from the engine status counts as that view counts from engine load time. Events tracked include user and group add, delete, deferred delete, rename, user move and user set policy.

Figure 12 NSM 25 UI Doc - Event Stats Graphic 26

Volume StatisticsThe Volume statistics page lists all the paths in use in Novell Storage Manager™ policies. The amount of space on the volume, the amount of space in use, the amount of space available and the percentage free are displayed. A status graphic indicates where space is getting low.

Figure 13NSM 25 UI Doc - Volume Stats Graphic 27

Global Statistics Global Statistics provide a graphic view of the current state of your storage. The reports can be configured to choose the servers, volumes and paths for the reports. The class (user, collaborative or auxiliary storage) can also be selected .

Figure 14 NSM 25 UI Doc - Global Stats Graphic 28

NSM Policy CreationNSM Policies are objects in eDirectory. Generally NSM policies will be created using NSMAdmin’s Policy Editor. NSM policies can also be created by any tool that can create eDirectory objects, for example, LDIF, LDAP, or other tools. NSM 2.5 introduces a new and very power policy editing to speed creating and modifying NSM policies.

Policy TypesNSM has two types of storage management policies; Primary polices that are used to provision and manage user and collaborative storage, and auxiliary policies that are used to provision and manage secondary storage associated to users. A single primary policy can be associated to a directory object, like an OU. The associated primary policy can be configured to create and manage user storage for user under the organization unit. The same policy can be configured to create and manage storage for directory groups under the OU. The Policy can also be configured to create collaborative storage space for all users in the OU. The same policy can be used create one, two or all three types of storage. NSM 2.0 Primary policies are fully compatible with NSM 2.5.

This is important because only one NSM primary policy can only be associated with an OU. This means that if there need is to have User and Collaborative storage for an OU, the policy associated with the OU must be setup to manage both user and collaborative storage. As stated earlier, the collaborative area of a primary policy can be setup to manage shared storage for directory groups and/or the OU. The option is selectable in the collaborative section of the policy editor.

A new type of Policy in NSM 2.5 is the Auxiliary policy. Auxiliary policies are used to manage additional user storage locations. For example, the HR department folder for each employee, a Lotus Notes Directory, or any other needs you may have for folders managed by the user’s identity. Auxiliary policies are linked to the primary policy that manages the Home Directory. By linking AUX policies to the primary policy, NSM can manage multiple pieces of storage per user.

How is a Policy Assigned and Inherited?A user storage policy may be assigned to the following object types:

• Organization• Organizational Unit• Group• User

When Novell Storage Manager™ performs an analysis on an individual user object, it must determine which policy, if any, to use. NSM determines this by searching in the following order until a policy is located or the list is exhausted:

1. Direct assignment to the user itself.2. An assignment to a group that the user is a member of. The groups are searched in the order that

the user was added to them in eDirectory.3. The parent container of the user object.4. The parent’s parent container and so on up to the [Root].

Policy Attribute ChangesThe attributes of a Policy may be modified at anytime using NSMAdmin; after which any eDirectory events on objects that use that policy will result in the new values being applied. No policy attribute change will be automatically retroactive against files systems affected by the policy. Action operations may be used to retroactively apply certain policy changes.

Create/Edit Primary PolicyTo create a primary policy select create primary policy from either the Policy Management form or from the Storage Management Form. To edit a primary policy select a policy in either form, right click on the policy and select the edit option. The Primary Policy Form has three sections: General, User, and Collaborative.

GeneralThe General section has options to name the NSM policy and select the container to place the policy object. Designate if the policy will be used to manage user storage, collaborative or both. The Process events buttons can be used to designate that the policy will function as a blocking policy. This will limit policy inheritance in the directory tree. The final field is a free text field to add a description to a policy.

Figure 15 NSM 25 UI Doc - Policy Create - General Graphic 42

General Policy Option Field Description

New Policy Name CN of NSM Primary Policy

Container Location of NSM Policy in directory tree

User Policy Options User Policy Options Activates the user portions of the Primary policy (default selection)

Process Events for Associated User Storage

Activates policy as a NSM Blocking Policy – Blocks NSM User policy inheritance

Collaborative Policy Options

User Policy Options Activates the collaborative portions of the Primary policy

Process Events for Associated Collaborative Storage

Activates policy as a NSM Blocking Policy – Blocks NSM collaborative policy inheritance

Policy Description Description Free text field to add a description to a policy.

User Policy PropertiesThis selection opens the user policy properties interface form. This form contains all the elements than can be used in creating a Novell Storage Manager™ policy to manage user storage.

Figure 16 NSM 25 UI Doc - Policy Editor - Graphic 40

User Policy Field DescriptionGeneral Options Policy Inheritance Policy will be inherited by subcontainers

Policy Weight Used to decide which policy should be applied to users who are members of multiple groups that have policies

assigned. Platform Specific Option Indicate whether the default server user

attribute should be set to the same server as the home directory.

Target Placement Distribution Specifies subordinate leveling directoriesLeveling Algorithm Specifies the Load-Balancing algorithm to

be used in selecting between the defined paths.

Max Unreachable Paths The point at which newobject or set policy eventsaffected by this policyshould be held pendingavailability of paths specified in the policy.

Paths Points to one or moretarget locations to create user storage.

Provisioning Default Rights Specifies the trustee rights that each USER should be granted to their home directory.

Policy-Defined Attributes

Specifies the attributes for the user home folders

Template Folder Points to a directory that will be copied into each new User home directory.

Data Move Schedule Specifies a weekly schedule for when data will be moved during a data migration operation.

Cleanup Storage Cleanup on Delete

Specifies that user storage should be deleted when user is removed from directory. Option to specify how many days storage should be retained before deleted.

Vault On Delete Storage will be moved to a vault location when user is removed from the directory. If a # of days option is selected storage will be moved to vault and deleted from vault after specified number of days.

Quota Initial Quota Specifies the default quota that should be placed on the each User’s home directory.

Quota Management Quota Management options sets the ceiling for quota management and for quota increases.Quota Ceiling is also used to set the upper preserved quota when users are moved.

Grooming Vault path Specifies the location for storage to be vaulted.

Grooming Rules Rules to determine what types of files should be groomed.

Auxiliary Policies Associated Auxiliary Policies

Select Auxiliary policies to link to primary policy.

Collaborative PropertiesThe collaborative properties form is much like the User properties form. It displays only those attributes applicable to collaborative storage. For more details on the attributes used for collaborative storage, see the section on creating shared storage.

Figure 17 NSM 25 UI Doc - Policy Create - Coll Graphic 43

Collaborative Policy Field DescriptionGeneral Options Group Based Storage Designates policy to create Group based

collaborative storagePolicy Inheritance Policy will be inherited by subcontainersContainer Based Storage

Designates policy to create Container based collaborative storage

Dynamic Template Processing

New for NSM 2.5 – These options allow limits to be placed on the dynamic processing to reduce time and overhead in the processing. Limiting search depth for these elements can speed up processing. Checking Enable Dynamic Template processing turns on this feature. If there are no –MEMBER- or –GROUP- or –OWNER- designations in the template, this should not be selected.

If the dynamic elements are at known levels, restricting this will eliminate searching for these elements when adding new members or performing a Management action to Apply Members.Selecting “Ignore Hidden attribute on dynamic template” allows dynamic elements to be marked Hidden, but then does not hide the individual directories these directives indicate should be created. For example, if this is selected and there is a –MEMBER- directory in the template indicating each member should have a directory created, the –MEMBER- can be flagged hidden so it won’t be seen by end users. The individual directories will not be hidden.

Target Placement Distribution Specifies subordinate leveling directoriesLeveling Algorithm Specifies the Load-Balancing algorithm to

be used in selecting between the defined paths.

Max Unreachable Paths The point at which new object or set policy events affected by this policy should be held pending availability of paths specified in the policy.

Paths Points to one or moretarget locations to create user storage.

Provisioning Default Rights Specifies the trustee rights that each USER should be granted to their home directory.

Policy-Defined Attributes

Specifies the attributes for the user home folders

Template Folder Points to a directory that will be copied into each new User home directory.

Data Move Schedule Specifies a weekly schedule for when data will be moved during a data migration operation.

Storage Location Object Container

Specify location to create NetStorage SLOs for Collaborative storage

Cleanup Storage Cleanup on Delete

Specifies that user storage should be deleted when user is removed from directory. Option to specify how many days storage should be retained before deleted.

Vault On Delete Storage will be moved to a vault location when user is removed from the directory. If a # of days option is selected storage will be moved to vault and deleted from vault after specified number of days.

Quota Initial Quota Specifies the default quota that should be

placed on the each User’s home directory.

Grooming Vault path Specifies the location for storage to be vaulted.

Grooming Rules Rules to determine what types of files should be groomed.

Policy ImportA valuable new feature in NSM 2.5 is the ability to import policy attributes from existing policies. The feature allows NSM policy creators to choose the attributes to import into new policies. All policy attributes can be imported except for Policy Associations, and target paths.

Figure 18 NSM 25 UI Doc - Policy Import Graphic 41

To use policy import – select the policy import button on the bottom of the Policy Edit form. Browse for the policy to import from and the policy’s attributes will appear in the import form window. Select the attributes to be imported from the left panel. User and collaborative attributes can be imported.

Quota ManagerQuota Manger includes a separate external interface to allow a specified user (for example a help-desk administrator or support personnel) to increase users’ quotas upon request, without having to have rights to the file system.

Novell Storage Manager™ adds an attribute to the Organizational Person class called cccFSFactoryHomeDirectoryQuota. A help-desk administrator or support person is given the Write right to this attribute on the users he or she is to manage, and this attribute enables them to be a quota manager on those users who have policies with quota management enabled. The steps for using quota manager are as follows:

1. Enable and configure Quota Manager on each policy covering users where quota management is desired. Be sure the users are covered by the policy. If the policy was applied after the users were created, a backfill may be required to include those users in the FSF database.

2. Set up the rights for the user(s) to be the administrator of the disk space quotas.3. Manage user disk space quotas using the external Quota Manager Interface

These steps are detailed here.

Enabling and Configuring Quota Management for a PolicyQuota management is enabled at the policy level. To activate, simply go to the Quota Control, found on the user properties page of any Storage Manager™ policy. Select the check-box “Enable Quota Manager Quota Preservation for this policy” to enable quota management interface for managing user quotas.

Options can then be set to determine how the quota can be managed. Choosing no maximum will allow the quota manager to continue to increment the limit until the volume space is exhausted. Otherwise, an upper limit maximum may be set. The other option determines how the quota is raised by the manager. A predetermined amount can be set, and the administrator will be able to raise a user’s quota by that amount until it reaches the maximum (if set.) Otherwise the administrator will be able to type in the new user quota.

Setting up Rights to Use Quota ManagerUsers in eDirectory can have the rights set to use Quota Manager. Organization Roles, groups, or other object that use security equivalence can be used as well. To make an object the quota manager, select the portion of the tree where the users exist that the quota manager will be allowed to manage. Remember these users must be managed by FSF policies with quota management enabled. Set the attribute rights of the desired object for the attribute cccFSFactoryHomeDirectoryQuota to Write. This can be set for the whole tree, for an organization or organizational unit, or all the way down to an individual user, if desired. Because this feature uses eDirectory rights, the traditional inheritance applies, including the use of inherited rights filters.

Using the Quota Manager InterfaceOnce quota management has been enabled on a policy and a user has been identified as a quota manager, the quota management tasks can be performed in a separate user interface.

Enter the URL for the quota manager in any web browser. The default URL is http://your.server.name.or.ip.address:8008/FSF/HTTP_FSFQuotaMgr or for SSL:https://your.server.name.or.ip.address:8009/FSF/HTTP_FSFQuotaMgr.

It will be necessary for the user to log in. If the user is in the Novell Storage Manager™ index, the common name will be sufficient; otherwise a fully distinguished name is required.

Once logged in, the initial screen requires the help-desk administrator or other designated quota manager user to enter a username to manage. This can be a full name or a standard search string, such as bob*. This will return a list of users in the tree which match the search spec (or username) and are managed by FSF policies which have quota management enabled.

Each user will have a stoplight indicator showing what percentage of their directory quota is in use. The stoplights are based on directory space available and go from green to yellow to red based on the following percentages:

Green = space available > 25% of quota

Yellow = space available < 25% of quota

Red = space available < 10% of quota

Click on the stoplight to manage the user’s quota.

From the “Home Directory Statistics and Quota” page the quota administrator will be able to manage the quota based on the policy settings. If an increment interval has been set, the manager will be able to add the default amount by clicking the button. If no interval has been set, the manager will be able to manually type in the new quota. In addition to the quota information, the manager can view file statistics based on file extension. Statistics include the size of the largest file, the number of files and subdirectories, and a list indicating number of files by extension, and sorted by size.

Executive DashboardExecutive Dashboard includes a separate interface to allow specified users to view statistics and generate reports based on the storage managed by Novell Storage Manager™.

Configuring the Executive DashboardThe configuration page for the Executive Dashboard is found in management interface by selecting the Config Tab and selecting “Engine Config.” By default, all of the options are turned off.

The first item in the configuration allows Executive Dashboard to be enabled. If this is not selected, the external interface for Executive Dashboard will not be available. Next, select the name of the object which will have rights to use the external interface for the Executive Dashboard. See the next section (Executive Dashboard Security Principle Object) for more details. Select the appropriate check boxes to enable the desired features for reports which can be generated. The reports available are Event Statistics, Storage Statistics, Policy Statistics and Report Disk Usage.

Executive Dashboard Security Principle ObjectTo secure the Executive Dashboard, Novell Storage Manager™ uses Security Equivalence to determine who has rights to login to the Executive Dashboard. To accomplish this, Novell Storage Manager™ supports any object type that supports security equals to (e.g. group and organizational role objects). Note: When setting the object for security principle, only user or group objects can be selected by browsing.

One user may also be designated as the security principle. If this option is selected, only this user will have access to the Executive Dashboard.

Using the Executive Dashboard InterfaceEnter the URL for the Executive Dashboard in any web browser. The default URL is http://your.server.name.or.ip.address:8008/FSF/HTTP_FSFExecutiveDashboard

or for SSL:

https://your.server.name.or.ip.address:8009/FSF/HTTP_FSFExecutiveDashboard.

It will be necessary for the user to log in. If the user is in the Novell Storage Manager™ index, the common name will be sufficient; otherwise a fully distinguished name is required.

Once logged in, the user will have access to those elements of the dashboard enabled in the configuration.

Storage StatisticsThe Storage statistics page gives a comparison graph of disk storage usage over time. It shows storage in use by user home directories (managed by Storage Manger) and group home directories.

Event StatisticsThe Event statistics page gives a daily view of the same event statistics that are tracked on the Engine Console. The current day and the previous three days are shown. Counts will be different from the engine status counts as that view counts from engine load time. Events tracked include user and group add, delete, deferred delete, rename, user move and user set policy. Volume Statistics

The Volume statistics page shows volume usage by policy. For each policy, the volumes specified in the Target paths are shown with statistics showing space in use and space remaining.

ReportsThe report page allows configuration and generation of reports for various statistics related to objects managed by Novell Storage Manager™. The reports that can be generated are as follows:

Disk space usage reports relative to • Users• A specific Policy• Groups• A specific Volume

These graphical reports provide information on how much disk space is available to the selected report category, and how much is actually in use. It is possible to select multiple time periods to be able to observe change over time. To generate one of these reports, select the subject for the report (Policy, Volume, User or Group.) If Policy or Volume is selected, the appropriate drop down list box will be enabled. Select an item from the list. Select one or more time frame, and press submit to generate the report.

Number of users managed by Novell Storage Manager™ policies by• Individual policy• All policies

This report will give a listing of one or all policies and the number of users managed by that policy.

To generate this report select either Individual Policy, or All Policies. If Individual Policy is selected, the drop down list box will be activated. Select the desired policy and press submit.

WorkflowWorkflow includes a separate interface to allow managers to determine what should be done with the home directory of a deleted user. The intent of this subsystem is to allow policy definitions by which Novell Storage Manager™ can queue storage for deleted employees up to their manager when they leave the organization. This mechanism leverages the eDirectory attributes managed by the Organizational Chart function in eGuide™. The screen shot below shows that Sue Jensen and Tom Stuart both report to Bob Smith in the Engineering organization. If the Novell Storage Manager Policy governing storage for Tom is configured, when Tom leaves the organization, his home directory contents will be queued up to Bob, who can then inspect the contents, approve the deletion, vault the data, or assign it to another individual at that point or at a later date; perhaps when Tom’s replacement has been hired.

Configuring WorkflowWhen configuring a policy that will govern user home directory storage, it is possible to enable and configure workflow processing for users covered by the given policy. If workflow is enabled for the policy, then the deletion of any user object covered by the policy will trigger the queuing in the workflow subsystem. The administrator has the option of restricting how long the deleted employee’s manager has to do something with the data. Select and specify a maximum number of days, or forever.

When a user covered by a policy with workflow enabled is deleted, the workflow process takes over.If the deleted user does not have a manager defined in eGuide™, then deletion process will proceed for that user according to the policy as if workflow were not enabled.

When workflow processing has completed, either by the manager approving the deletion or by the approval period specified in the policy expiring, the deletion of the home directory according to the policy will take place.

Setting up the Workflow Management StructureAs discussed above, Novell Storage Manager™ leverages the Organizational Structure defined in eGuide™. See the eGuide™ documentation for information on configuring and using eGuide™. Novell Storage Manager™ monitors changes to the Organizational Structure in eDirectory and maintains information about these relationships so that when a user is deleted, Novell Storage Manager™ will know who the manager is for the given user and can queue it appropriately. Novell Storage Manager only maintains this information for those users whose home directory is managed. As with other aspects of Novell Storage Manager, it may be necessary to perform a backfill operation on preexisting users in order to have them managed.

Using the Workflow InterfaceMuch like the Executive Dashboard and Quota Manager components of Novell Storage Manager™ 1.2, the end-user interface for the Workflow component is external to the NetWare Remote Manager interface. Most administrators do not want end users seeing or touching the Remote Manager, so there

is a separate interface that employee managers will use to attach and manage data that has been queued to them.

The default URL is http://your.server.name.or.ip.address:8008/FSF/HTTP_FSFWorkFlow or for SSL:https://your.server.name.or.ip.address:8009/FSF/HTTP_FSFWorkFlowIt is suggested to add these as links in an organizational portal or on a management web page that users commonly access.

It will be necessary for the user to log in. If the user is in the Novell Storage Manager™ index (which they will be if they are managed), the common name will be sufficient; otherwise a fully distinguished name is required.Once logged in, the employee manager will view all workflow entities which have been assigned to him and can then perform operations on them. The documentation in the user interface will detail these operations.

Appendix A - Novell Storage Manager Feature Matrix

Feature

FSF 1.2.1

eDirectory

NSM 2.0

eDirectory

NSM 2.5

eDirectory

Full storage lifecycle storage management event and policy driven solution

Advanced multiple queue event processing system

Real time directory service event driven system for provisioning, modifying and managing network file system

NetWare Server eDirectory Event Monitor

OES &SUSE Linux Server eDirectory Event Monitor*

Delegate copy task to Agent Servers

Delegate all copy operations to Agent Servers to speed up operation and decrease bandwidth usage

OES Linux NSM Agent

NSM Soft Appliance Engine for OES Linux

Full system fault tolerance State Machine Architecture

User Storage Management

Provision NetWare user home directory

Feature

FSF 1.2.1

eDirectory

NSM 2.0

eDirectory

NSM 2.5

eDirectory

Provision OES Linux user home directory (NSS)

Provision OES Linux user home directory – ext2/3 & Reiser

Rename, Move Cleanup NetWare user home directory

Rename, Move Cleanup OES Linux user home directory – NSS

Rename, Move, Cleanup OES Linux user home directory – ext2/3 & Reiser

Vault User home directory – NetWare & OES Linux - NSS

Vault User home directory –OES Linux – ext2/3 & Reiser

Provision Auxiliary User Storage Locations NW & OES Linux (NSS, ext2/3 & Reiser)

Rename, Move Cleanup Auxiliary User Storage Locations NW & OES Linux (NSS, ext2/3 & Reiser)

Catalog & Manage existing NetWare user home directory

Catalog & Manage existing OES Linux user home directory - NSS

Catalog & Manage existing OES Linux user home directory – ext2/3 & Reiser

Review, reassign or vault employee data when an employee leaves an organization

Vault & Groom NetWare & OES Linux user home directory - NSS

Vault & Groom OES Linux user home directory – ext2/3 & Reiser

Feature

FSF 1.2.1

eDirectory

NSM 2.0

eDirectory

NSM 2.5

eDirectory

Groom user’s storage before moving to vault location when user is removed from eDirectory.

Assign, update and manage user directory storage quotas

Personal storage space file system trustee assignment

Recover File System Trustee assignments

Recover Home Directory Attribute

Set attribute flags on home directories

Personal storage load balancing, multi-server distribution and space balancing

Assign user storage template of files and folders to prepare a personal home directory structure

Reapply storage template as template files and folders are modified

Populate Home Directory Attribute for users with storage but attribute is not populated

User storage migration transparent and seamless to the user

Automated user storage migration, triggered by moving user object in the directory.

Automated User Data Migration for server consolidation

Collaborative Storage Management

Create collaborative storage based on eDirectory Groups NetWare

Feature

FSF 1.2.1

eDirectory

NSM 2.0

eDirectory

NSM 2.5

eDirectory

Create collaborative storage based on eDirectory Groups OES Linux - NSS

Create collaborative storage based on eDirectory Groups - ext2/3 & Reiser

Backfill collaborative storage for multiple eDirectory Groups – NSS, ext2/3 & Reiser

Create collaborative storage based on eDirectory Containers (Os & OUs) OES Linux & NetWare

Apply NSM Vault Rules to move files to vault location

Move deleted collaborative folders to a given vault location.

Enhanced Backfill operations applied to collaborative storage (Recover Attributes, Restore Trustees, Quota, Template)

Assign, update and manage collaborative directory storage quotas

Collaborative storage space file system trustee assignment

Collaborative storage load balancing, multi-server distribution and space balancing for

Assign collaborative storage template of files and folders to prepare collaborative storage structure

NetStorage integration via automatic provision & management of NetStorage objects

Automated Collaborative Storage Data Migration to assist in server consolidation

Additional Features

Feature

FSF 1.2.1

eDirectory

NSM 2.0

eDirectory

NSM 2.5

eDirectory

NSM Janitor Process to enhance

NSM Action Objects

Enhanced Identity Manager Integration using NSM Action Objects

Novell Identity Manager Support

LDAP Support

LDIF Support

Enhanced Data Migration subsystem

Data consistency reports – Allowing administrators to discover current problems with existing user storage and ability to solve storage problems

Administrator Dashboard providing quick access to all of the reports, statistics and data managed by Novell Storage Manager

Executive Dashboard providing management with a Web location to view the current state of user-directory storage on the network

User Storage Status Indicators illustrates what percentage of a user's directory quota is in use

File and Directory Security Analysis quickly see who has rights to a file or directory, indicating how rights were derived/obtained

Help desk quota management without assigning file system rights to help desk

Feature

FSF 1.2.1

eDirectory

NSM 2.0

eDirectory

NSM 2.5

eDirectory

Client based auto discovery of personal and shared storage space – no login scripts or drive mappings

Storage system health check monitoring

Enhanced NSM Admin program – Operations quickly reachable

Fined grained control of NSM policies to provide flexible options for blocking NSM Policy inheritance

Creates Orphaned Home Directory Eligible Report

User Storage Report to assist in developing quotas for user storage

Support for extended characters in Novell eDirectory object names

Documents

Novell Storage Manager™ of this Document The Novell Storage Manage 2.5 Admin Guide is designed to help users become familiar with the basics