John Ruggeri

Project Manager

Court of Appeals of Georgia

Behzad Anaraki

Principle Security Architect

Synovus

Novell File System Factory
Real World Implementations & Best Practices

Agenda

Identity Driven Storage Management Overview

Georgia Court of Appeals Case Study

Synovus Financial Case Study

Demo

Q&A

Identity Driven Storage Management

IDM

N

L

Provisioning / De-Provisioning

Role Based Access and Mgt

Novell exteNd™

Novell iChain®

NetWare® Storage

OES Linux Storage

Novell Cluster Services™

Storage Area Networks

Security

Storage

Identity Driven Storage Management

FSF

Identity Driven &

Policy Based Storage

Personal Storage Management

Group Storage Management

Trustee & Rights Analysis

Identity Driven Data Migrations

Data Manager Workflow

Analysis & Storage Trends

IDM

N

L

Provisioning / De-Provisioning

Role Based Access and Mgt

Novell Extend

Novell iChain

Netware Storage

OES Linux Storage

Novell Clustering Services

Storage Area Networks

Security

Storage

Identity Driven

Storage Mgt

The common thread:

Regulatory Compliance

HIPAA

Sarbanes-Oxley

Privacy Act

Audit Requirements

Policy based storage mgt

Productivity

Fast employee ramp-up

Free-up admin staff for strategic projects

Team Collaboration

Eliminate redundant administration tasks

Reduce helpdesk burden

Automated storage mgt.

Trend Analysis

Cost Reduction

Data Security

Consistent storage policies

De-provision access to critical data

File Rights Analysis

Intellectual Property

Identity

Identity

File System Factory
Storage Management based on Policy and Events

eDirectory™

Policy

Manage

Provision

Events

LDAP

ConsoleOne

NWAdmin

Custom/3rd

iManager

Identity Mgr

ConsoleOne®

NWAdmin

Custom/3rd

iManager

LDAP

UIMPORT

LDIF

DirXML® 1.x

File

System

Factory

You Create and Manage objects any way you want, FSF will handle the file system.

Move to

modern provisioning technology without worrying about file storage.

Netware

OES Linux

File System Factory
Storage Management based on Policy and Events

Let policy govern storage management instead of helpdesk or local admins.

eDirectory

Policy

Manage

Provision

Events

LDAP

ConsoleOne

NWAdmin

Custom/3rd

iManager

Identity Mgr

ConsoleOne

NWAdmin

Custom/3rd

iManager

LDAP

UIMPORT

LDIF

DirXML 1.x

File

System

Factory

You Create and Manage objects any way you want, FSF will handle the file system.

Netware

OES Linux

Identity-Driven Storage Management

BorderManager

ZENworks® for Desktops

Identity Mgr

Identity Mgr

AD

Active

Directory

LINUX

Identity

Driver

Driver

eDirectory

GroupWise®

Identity-Driven Storage Management

FSF

NetWare

OES LINUX

LINUX

BorderManager

ZENworks for Desktops

Identity Mgr

Identity Mgr

AD

Active

Directory

LINUX

Identity

Driver

Driver

eDirectory

GroupWise

Identity-Driven Storage Management

LINUX

Policy Based, Event-Driven

Rights Analysis

Load balancing

Storage Trend Analysis

Storage creation

Storage Migrations

Storage management

Storage cleanup

Personal user storage

Group storage

FSF

NetWare

OES LINUX

LINUX

BorderManager

ZENworks for Desktops

Identity Mgr

Identity Mgr

AD

Active

Directory

LINUX

Identity

Driver

Driver

eDirectory

GroupWise

File System Factory for:

Microsoft

Active Directory

Coming up Next

Related Sessions

TUT 348

Identity Driven Storage Management on NetWare, Linux, and Windows:

File System Factory Installation and Configuration

TUT 305

Building Affordable SANS with iSCSI

Identity Driven Storage Management
Georgia Court of Appeals Case Study

About Us

Court of Appeals of Georgia

Intermediate Appellate Court

12 Judges sitting in 4 Panels

3rd Busiest State Appellate Court in US

3,444 Appeals Filed

287 Per Judge

1.2 Cases Decided per Work Day

50 % Decided by Opinion (144 Per Judge)

Avg. Opinion is 8 Pages

National Center of State Courts Recommends 125 Cases per Judge

Customer situation

Needed automated process for managing personal and group storage

Needed to reduce hardware costs and minimize user downtime

Solution must support automated data migration of user storage to SAN with no downtime.

Approach

Engaged East Cobb Group to design, plan and implement solution

Opted to implement Novell Clustering Services and File System Factory with iSCSI SAN

Used Back fill operations with enforce policy path for seamless migration of user storage to SAN

Case Study: Georgia Court of Appeals

Georgia Court of Appeals
Identity Driven Data Migration

COURTS

CSCJ

SUPREME

APPEALS

Installed iSCSI SAN and NCS

BSmith

RJones

KJackson

RCroom

DWyatt

BSmith

RJones

KJackson

RCroom

DWyatt

HP Server

NCS

Left Hand

Networks

iSCSI SAN

Installed File System Factory

and setup storage policies for

each container

Policy

Georgia Court of Appeals
Identity Driven Data Migration

COURTS

CSCJ

SUPREME

APPEALS

Installed iSCSI SAN and NCS

BSmith

RJones

KJackson

RCroom

DWyatt

BSmith

RJones

KJackson

RCroom

DWyatt

NCS

Left Hand

Networks

iSCSI SAN

HP Server

Issued FSF Backfill Operation to populate Home Directory Attribute & Catalog users

Installed File System Factory

and setup storage policies for

each container

Policy

Georgia Court of Appeals
Identity Driven Data Migration

COURTS

CSCJ

SUPREME

APPEALS

Installed iSCSI SAN and NCS

BSmith

RJones

KJackson

RCroom

DWyatt

BSmith

RJones

KJackson

RCroom

DWyatt

NCS

Left Hand

Networks

iSCSI SAN

HP Server

RJones

KJackson

BSmith

RCroom

DWyatt

Issued Backfill with “Enforce Policy Path” to Migrate Users Home Directories

Policy

Georgia Court of Appeals
Identity Driven Data Migration

COURTS

CSCJ

SUPREME

APPEALS

BSmith

RJones

KJackson

RCroom

DWyatt

BSmith

RJones

KJackson

RCroom

DWyatt

NCS

Left Hand

Networks

iSCSI SAN

400 Users

You Are Moving …

Seamless Migration of Users Data to SAN with No Downtime

RJones

KJackson

BSmith

RCroom

DWyatt

Policy

Georgia Court of Appeals
Identity Driven Data Migration

COURTS

CSCJ

SUPREME

APPEALS

BSmith

RJones

KJackson

RCroom

DWyatt

NCS

Left Hand

Networks

iSCSI SAN

Additional Solution Benefits

SERV1/VOL1:Procedures

Delete Inhibit / Rename Inhibit

Algorithm: Random Balance

Rights: RWCEMF

Quota: 150 MB

Template: SERV1/VOL1:Procedures

DelWait: 90 Days

150MB

Copy

BSmith

BSmith

Policy

Create

RWCEMF

Lifecycle User Management

iSCSI

COURTS

CSCJ

SUPREME

APPEALS

NCS

Additional Solution Benefits

Algorithm: Random Balance

Rights: RWCEMF

Quota: 150 MB

Template: SERV1/VOL1:Procedures

DelWait: 90 Days

150MB

Rename BSmith

to BJones

BJones

Policy

Rename

Lifecycle User Management

iSCSI

COURTS

NCS

CSCJ

SUPREME

APPEALS

New workflow component allows employee’s manager to review, reassign, or vault user data prior to deletion.

Additional Solution Benefits

Algorithm: Random Balance

Rights: RWCEMF

Quota: 150 MB

Template: SERV1/VOL1:Procedures

DelWait: 90 Days

150MB

BJones

BJones

Policy

Delete

Lifecycle User Management

iSCSI

COURTS

NCS

CSCJ

SUPREME

APPEALS

Additional Benefits:
Standardized Storage Based on Policy

OWNER

MEMBERS

Additional Benefits: File System Rights Analysis

Additional Benefits:
Executive Storage Dashboard

Additional Benefits:
Quota Manager Help Desk Interface

Future Plans
Identity Driven Group Storage

Algorithm: Random Balance

Rights: Template

Quota: 500 MB

Template: SERV1/VOL1:ProjectFiles

DelWait: Never

Policy

iSCSI

COURTS

NCS

CSCJ

SUPREME

APPEALS

Departmental

Group Storage

File System Factory Automatically Provisions Storage for Project Members and Project Managers

Future Plans:
Identity Driven Group Storage

Business Results

Leveraged existing investment in Netware and eDirectory

Increased User Productivity - Migrated data to SAN with no impact on users.

Implemented consistent Storage Policies for all users

Automated storage management reduced administrative cost

iSCSI solution reduced hardware costs

Business Results

Identity Driven Storage Management

Synovus Financial Case Study

Business Overview

Synovus is a diverse financial services company with more than $25 billion in assets. We are people serving people, a tradition that started more than a century ago in Columbus, Georgia, and now spans North America and beyond.

Synovus operates two distinct lines of business. Payment Processing and Financial Services. Within these two lines of business, we offer a variety of products and services.

Synovus has been named one of “The 100 Best Companies To Work For” in America by FORTUNE magazine, and has been recognized in its Hall of Fame for consecutive appearances on the list since its inception in 1998. In 2005, Synovus was also named as one of “America’s Most Admired Companies” .

Our vision for 2004 and beyond is to be the finest financial services company in the world.

Current Environment

Multiple Companies and Banks

40 Banks, over 350 branches

6,500 Users

Over 1000 NetWare, Windows, and Linux servers

eDirectory, AD/Exchange, Notes, GroupWise, ZENworks, JDBC, PeopleSoft, Vinette Portal, Banking Apps

Development environment

Technical Expertise

Identity Management Initiative

Account Provisioning

Data Synchronization

Role Base Access and Administration

Central LDAP authentication and authorization

Account Provisioning Objectives

Hire, Terminate, Transfer Employees Automatically

Setup, disable, move all accounts Automatically

Create, Delete, Move user’s storage Automatically

Assign, Deliver, Transfer Application Automatically

Data Synchronization

HR Employee Data elements

Email address, Notes, AD/Exchange, GroupWise

Badge Photo, and ID, Ccure system

Training DataBase, iLearn

Password, and Password Policy Synchronization

Role Base Access and Administration

Role based Banking Application access

Role based management using eGuide

Role based management using iManager

Environment Overview

NetWare

NetWare

GroupWise

ZENworks for Desktops

Identity Mgr

PeopleSoft

eDir Driver

NetWare

NetWare

Identity

Vault

AD

Exchange

Lotus

Notes

SQL

JDBC

Ccure

Badge

Vignette

Portal

eDirectory

Customer situation

Needed automated process for managing and migrating user specific data during hire, termination, and employee transfer

Needed to reduce costs associated with managing user resources

Solution must support Integration with IDM 2.0 solution.

Need to meet regulatory requirements

Approach

Phased approach; Home Directory, User’s NAL App copy

First address App copy for user move, then user add

Engaged Novell Consulting Custom Development team to design and deliver a IDM 2.0 LoopBack Driver

Implement IDM 2.0 and FSF to automate user add, delete, and moves.

Custom IDM Driver Integration with FSF Action Object and NAL application delivery

Develop, test, production rollout.

Identity Driven Storage Management
Synovus Bank

FSF Action Object

Operation

Options

Path1

Path2

Execute Time

Execute Options

Association

Control

Status

Result

Cleanup

Chain_Start

Chain_Next

MkDir

CopyDir

RemoveDir

SetQuota

RemoveQuota

SetTrustee

CopyTrustee

SetAttr

Rename

...

A

FSF IDM Interface – User Move Example

BSmith

SYN

FSF

ATL

TEN

Policy

Policy

BSmith

A

A

IDM 2.0

LoopBack Driver

PeopleSoft

1. User Location Code changes

in PeopleSoft

2. The Location Code Triggers

the Driver

3. Driver Reads the user’s group

membership list

4. Driver Queries the

destination for the same

groups.

SYS:\PUBLIC\ZENWORKS\APP1

SYS:\MSI\SCHEDULER

A

A

A

Group App Object

5. If Group doesn’t exist, one

will be created and the user

gets added as a member

FSF IDM Interface – User Move Example

BSmith

SYN

FSF

ATL

TEN

Group App Object

Policy

Policy

BSmith

A

A

IDM 2.0

LoopBack Driver

PeopleSoft

SYS:\PUBLIC\ZENWORKS\APP1

SYS:\MSI\SCHEDULER

A

A

A

6. The new group App association

will be added by copying the

App object

FSF IDM Interface – User Move Example

BSmith

SYN

FSF

ATL

TEN

Group App Object

Policy

Policy

BSmith

A

A

IDM 2.0

LoopBack Driver

PeopleSoft

A

A

A

Group App Object

7. The Driver populates the FSF Action Object for the Zen App file copy.

8. FSF copies the Zen App from the Source to the Destination

SYS:\PUBLIC\ZENWORKS\APP1

SYS:\PUBLIC\ZENWORKS\APP1

SYS:\MSI\SCHEDULER

SYS:\MSI\SCHEDULER

FSF IDM Interface – User Move Example

BSmith

SYN

FSF

ATL

TEN

Group App Object

Policy

Policy

BSmith

A

A

IDM 2.0

LoopBack Driver

PeopleSoft

A

A

A

Group App Object

9. User is moved by the

Driver to the new

location

10. FSF Migrates the user’s

Home Directory files

11. User logs in and the Zen

application is

distributed to desktop

FSF IDM Interface – User Move Example

SYS:\PUBLIC\ZENWORKS\APP1

SYS:\MSI\SCHEDULER

BSmith

SYN

FSF

ATL

TEN

Group App Object

Policy

Policy

BSmith

A

A

IDM 2.0

LoopBack Driver

PeopleSoft

A

A

A

Group App Object

Business results

Leveraged existing investment in Netware and eDirectory

Reduced costs associated with user moves and storage management

Increased user productivity

Saved time & resources by implementing a comprehensive integrated IDM solution.

Identity Driven Storage Management
Synovus Bank

DEMO

For More Information

Visit www.novell.com/products/filesystemfactory

Visit www.filesystemfactory.com

Discuss on the FSF forum at http://support.novell.com/forums/

Send product questions/suggestions to FSFDev@novell.com

Q & A

Introduction

Get to know the audience

Who are they?

How much do they know about FSF?

Have heard about it

Why they are in attendance:

To learn about FSF

State Question Policy – We will take questions during the presentation. If we get behind schedule we may have to postpone questions until the end.

Although these driving forces are different in many ways, and although they affect many different parts of your business, they all share an important common thread – they are all linked to identity.

A comprehensive identity driven storage management solution can help you solve your storage management needs across your enterprise and address each of these areas as they relate to storage management.

File System Factory™ is tied directly to eDirectory in that it takes action based on events in eDirectory, no matter if DirXML, Identity Manager, LDAP, UIMPORT, ConsoleOne, custom code, or anything else initiated the event. You control FSF actions using policies that are stored in the Directory itself, much like ZenWorks® policies.

File System Factory™ will work with an organization’s current network and user provisioning process, even if it involves custom code, batch processes, or manual data entry. File System Factory™ makes it simple for an organization to migrate to a newer provisioning process such as those mentioned above. If your current provisioning process includes the creation of home directories for users, you may be unable or reluctant to take advantage of new technology such as DirXML or LDAP because you would lose the home directory creation in the end. File System Factory™ can also be valuable resource in adding an additional provisioning process.

Besides being independent of account creation and deletion technology, FSF is also independent of management technology. This allows departmental administrators or helpdesk personnel to adopt and use newer management tools and procedures without concern for file system management. This also may aid in securing the data in that these administrators may no longer actually need access to it.

Since the data is now controlled by policy, organizations may rest assured that the data is being managed appropriately. There are numerous further benefits here tied to new government regulations over data management.

In recent years, Novell® customers have seen a great deal of effort put into transitioning eDirectory by building interfaces that automate the management of user accounts in eDirectory. Tools such as Identity Manager allow identity provisioning and exchange between the Directory and a myriad of external data sources and applications. File System Factory™ now enables Identity Manager customers that currently use NetWare for file and print to do so in new and dynamic ways by providing new levels of automation and management opportunities that previously have not been possible.

The mission of File System Factory™ is to provide a Policy-based storage management subsystem targeted for medium to large installations that completely automates the load balanced creation, management, and deletion of personal and collaborative disk space. FSF takes the headaches out of storage allocation, management and cleanup on networks with large and dynamic user populations. File System Factory™ integrates with your current Directory provisioning process, independent of the method, to deliver a fully automated and managed NetWare file system integration solution.

This means that you create and manage objects in the Directory in any way that you wish; and File System Factory™ will handle the rest with respect to file system creation, management, and cleanup. This also means that any existing DirXML or Identity Manager driver can drive user and group storage provisioning without modification!

In recent years, Novell® customers have seen a great deal of effort put into transitioning eDirectory by building interfaces that automate the management of user accounts in eDirectory. Tools such as Identity Manager allow identity provisioning and exchange between the Directory and a myriad of external data sources and applications. File System Factory™ now enables Identity Manager customers that currently use NetWare for file and print to do so in new and dynamic ways by providing new levels of automation and management opportunities that previously have not been possible.

The mission of File System Factory™ is to provide a Policy-based storage management subsystem targeted for medium to large installations that completely automates the load balanced creation, management, and deletion of personal and collaborative disk space. FSF takes the headaches out of storage allocation, management and cleanup on networks with large and dynamic user populations. File System Factory™ integrates with your current Directory provisioning process, independent of the method, to deliver a fully automated and managed NetWare file system integration solution.

This means that you create and manage objects in the Directory in any way that you wish; and File System Factory™ will handle the rest with respect to file system creation, management, and cleanup. This also means that any existing DirXML or Identity Manager driver can drive user and group storage provisioning without modification!

In recent years, Novell® customers have seen a great deal of effort put into transitioning eDirectory by building interfaces that automate the management of user accounts in eDirectory. Tools such as Identity Manager allow identity provisioning and exchange between the Directory and a myriad of external data sources and applications. File System Factory™ now enables Identity Manager customers that currently use NetWare for file and print to do so in new and dynamic ways by providing new levels of automation and management opportunities that previously have not been possible.

The mission of File System Factory™ is to provide a Policy-based storage management subsystem targeted for medium to large installations that completely automates the load balanced creation, management, and deletion of personal and collaborative disk space. FSF takes the headaches out of storage allocation, management and cleanup on networks with large and dynamic user populations. File System Factory™ integrates with your current Directory provisioning process, independent of the method, to deliver a fully automated and managed NetWare file system integration solution.

This means that you create and manage objects in the Directory in any way that you wish; and File System Factory™ will handle the rest with respect to file system creation, management, and cleanup. This also means that any existing DirXML or Identity Manager driver can drive user and group storage provisioning without modification!

One of the main goals of File System Factory is to be able to begin making an appreciable difference in ANY organization no matter what situation relative to storage management the organization may be in. This means that we must be able to help:

- provision storage for preexisting users in the tree.

- begin managing user storage that already exists in its current location.

- migrate user storage to new storage locations.

This is done with an operation called “Backfill”. FSF is managed using a browser through the NetWare Remote Manager (NoRM) interface. Backfill is one of many operations available in the interface.

Remember that a given policy that points to one or more storage locations on the network. If the policy that covers a given user changes, and the new policy points to different locations than the original policy, File System Factory™ will move the user data so that it resides in a location pointed to by the newly applicable policy definition.

During a backfill operation, storage will be created according to the policy for any users that do no have a home directory.

For those users that already have storage on the network, FSF can begin helping out immediately.

During a full backfill operation, the administrator has the capability of selecting the “Enforce Policy Paths” option. If the “Enforce Policy Paths” option is not selected, FSF will catalog the existing storage location and begin managing the storage according to the policy. If this option is selected, this will instruct File System Factory™ to fully analyze the location of each user’s home directory. If the directory is not in a location pointed to by the applicable policy, the data is moved to a location specified by the policy.

Many customers have used FSF to migrate user storage to Clusters and SAN storage systems. Again, all attributes and capabilities of FSF related to scheduling and throttling as well as “seamless” data movement apply.

This is a very powerful feature of File System Factory™ in that it may be used to move user data to a different volume or server.

One of the main goals of File System Factory is to be able to begin making an appreciable difference in ANY organization no matter what situation relative to storage management the organization may be in. This means that we must be able to help:

- provision storage for preexisting users in the tree.

- begin managing user storage that already exists in its current location.

- migrate user storage to new storage locations.

This is done with an operation called “Backfill”. FSF is managed using a browser through the NetWare Remote Manager (NoRM) interface. Backfill is one of many operations available in the interface.

Remember that a given policy that points to one or more storage locations on the network. If the policy that covers a given user changes, and the new policy points to different locations than the original policy, File System Factory™ will move the user data so that it resides in a location pointed to by the newly applicable policy definition.

During a backfill operation, storage will be created according to the policy for any users that do no have a home directory.

For those users that already have storage on the network, FSF can begin helping out immediately.

During a full backfill operation, the administrator has the capability of selecting the “Enforce Policy Paths” option. If the “Enforce Policy Paths” option is not selected, FSF will catalog the existing storage location and begin managing the storage according to the policy. If this option is selected, this will instruct File System Factory™ to fully analyze the location of each user’s home directory. If the directory is not in a location pointed to by the applicable policy, the data is moved to a location specified by the policy.

Many customers have used FSF to migrate user storage to Clusters and SAN storage systems. Again, all attributes and capabilities of FSF related to scheduling and throttling as well as “seamless” data movement apply.

This is a very powerful feature of File System Factory™ in that it may be used to move user data to a different volume or server.

File System Factory policies are based on full life-cycle management of storage.

Polices are created and pointed to one or more storage systems. These may be different locations on the same volume, different volumes, different servers, a cluster, a SAN, or any combination. Other attributes of the policy are defined that cover storage creation, management, and cleanup.

The policy is then assigned to the tree at some level. Just as with ZenWorks® policies, FSF policies may be assigned to containers, groups, or even individual users. The same inheritance model applies. In this example, the policy is assigned to the Atlanta container. At this point, FSF is ready to provision storage.

When BSMITH is created in the tree, FSF will intercept the event in eDirectory and apply the appropriate policy to provision the storage. The load-balancing algorithm defined in the policy will be used to select a location, the storage will be created, the rights and quota will be assigned based on the policy, and optionally the user home directory may be pre-populated with a set of files and directories from a template pointed to by the policy.

At that point, the user storage is managed for the life of the user based on many types of events that may occur such as a rename or a move.

For example, if BSMITH were to be renamed to BJONES (possibly due to a marital status change), then FSF would take action to rename the home directory accordingly.

When the user is deleted, the user’s storage will be automatically cleaned up according to the policy definition. This may be never, immediately, or after some defined amount of time, such as 90 days. The newest version of File System Factory includes a workflow subsystem, which may according to the policy allow the employee’s manager (defined using eGuide) to review the data, reassign it to another employee, or store it in a vault for later use or reassignment.

Deletes, renames, moves

Managed for the life of the user

Scenario 1: New Tree – No User Home Directories

If you are just starting out, File System Factory™ can give your new users managed home directory space with little effort on your part. Follow these steps:

Decide how you are going to create the user objects and where you are going to put them in the tree.

Decide which servers and volumes will hold the user home directories.

Create a File System Factory™ Policy and point it to the servers and volumes that will hold the user home directories. Associate the Policy with the container(s) that will hold the users.

Create the users using any method. Home Directories will be automatically created and assigned for all users.

Use template to populate each home directory with documents

Any new accounts added to the associated containers will have the Policy applied and be given new managed home directories.

Also, when you delete any existing or new accounts, the home directory space can automatically be cleaned up immediately or after a determined period.

File System Factory policies are based on full life-cycle management of storage.

Polices are created and pointed to one or more storage systems. These may be different locations on the same volume, different volumes, different servers, a cluster, a SAN, or any combination. Other attributes of the policy are defined that cover storage creation, management, and cleanup.

The policy is then assigned to the tree at some level. Just as with ZenWorks® policies, FSF policies may be assigned to containers, groups, or even individual users. The same inheritance model applies. In this example, the policy is assigned to the Atlanta container. At this point, FSF is ready to provision storage.

When BSMITH is created in the tree, FSF will intercept the event in eDirectory and apply the appropriate policy to provision the storage. The load-balancing algorithm defined in the policy will be used to select a location, the storage will be created, the rights and quota will be assigned based on the policy, and optionally the user home directory may be pre-populated with a set of files and directories from a template pointed to by the policy.

At that point, the user storage is managed for the life of the user based on many types of events that may occur such as a rename or a move.

For example, if BSMITH were to be renamed to BJONES (possibly due to a marital status change), then FSF would take action to rename the home directory accordingly.

Moves will be discussed on the next slide.

When the user is deleted, the user’s storage will be automatically cleaned up according to the policy definition. This may be never, immediately, or after some defined amount of time, such as 90 days. The newest version of File System Factory includes a workflow subsystem, which may according to the policy allow the employee’s manager (defined using eGuide) to review the data, reassign it to another employee, or store it in a vault for later use or reassignment.

Deletes, renames, moves

Managed for the life of the user

Scenario 1: New Tree – No User Home Directories

If you are just starting out, File System Factory™ can give your new users managed home directory space with little effort on your part. Follow these steps:

Decide how you are going to create the user objects and where you are going to put them in the tree.

Decide which servers and volumes will hold the user home directories.

Create a File System Factory™ Policy and point it to the servers and volumes that will hold the user home directories. Associate the Policy with the container(s) that will hold the users.

Create the users using any method. Home Directories will be automatically created and assigned for all users.

Use template to populate each home directory with documents

Any new accounts added to the associated containers will have the Policy applied and be given new managed home directories.

Also, when you delete any existing or new accounts, the home directory space can automatically be cleaned up immediately or after a determined period.

File System Factory policies are based on full life-cycle management of storage.

Polices are created and pointed to one or more storage systems. These may be different locations on the same volume, different volumes, different servers, a cluster, a SAN, or any combination. Other attributes of the policy are defined that cover storage creation, management, and cleanup.

The policy is then assigned to the tree at some level. Just as with ZenWorks® policies, FSF policies may be assigned to containers, groups, or even individual users. The same inheritance model applies. In this example, the policy is assigned to the Atlanta container. At this point, FSF is ready to provision storage.

When BSMITH is created in the tree, FSF will intercept the event in eDirectory and apply the appropriate policy to provision the storage. The load-balancing algorithm defined in the policy will be used to select a location, the storage will be created, the rights and quota will be assigned based on the policy, and optionally the user home directory may be pre-populated with a set of files and directories from a template pointed to by the policy.

At that point, the user storage is managed for the life of the user based on many types of events that may occur such as a rename or a move.

For example, if BSMITH were to be renamed to BJONES (possibly due to a marital status change), then FSF would take action to rename the home directory accordingly.

Moves will be discussed on the next slide.

When the user is deleted, the user’s storage will be automatically cleaned up according to the policy definition. This may be never, immediately, or after some defined amount of time, such as 90 days. The newest version of File System Factory includes a workflow subsystem, which may according to the policy allow the employee’s manager (defined using eGuide) to review the data, reassign it to another employee, or store it in a vault for later use or reassignment.

Deletes, renames, moves

Managed for the life of the user

Scenario 1: New Tree – No User Home Directories

If you are just starting out, File System Factory™ can give your new users managed home directory space with little effort on your part. Follow these steps:

Decide how you are going to create the user objects and where you are going to put them in the tree.

Decide which servers and volumes will hold the user home directories.

Create a File System Factory™ Policy and point it to the servers and volumes that will hold the user home directories. Associate the Policy with the container(s) that will hold the users.

Create the users using any method. Home Directories will be automatically created and assigned for all users.

Use template to populate each home directory with documents

Any new accounts added to the associated containers will have the Policy applied and be given new managed home directories.

Also, when you delete any existing or new accounts, the home directory space can automatically be cleaned up immediately or after a determined period.

In a typical environment, the manager of a working group determines that it would be nice to have a directory on the network for the group to use to share data. He or she goes to the network administrator and makes the request. The administrator must perform a list of actions to fulfill this request. This involves:

Creating the group object.

Adding the members to the group object.

Deciding where to put the storage for the group.

Creating the disk space for the group.

Optionally creating a set of subdirectories in the storage.

Communicating with the manager to determine which parts of the storage the group should have access to and what access to give.

Giving the group appropriate access.

Communicating with the manager to determine which parts of the storage the manager should have special access to.

Giving the manager appropriate special access.

Repeatedly performing steps 5-9 throughout the life of the group and storage.

File System Factory™ automates steps 3-10 of the above list though the use of Policies, template processing, and NDS event monitoring.

Organizations can now drive collaborative storage creation, management, and deletion as a provisioning process using any tool or process that can create groups in the Directory.

“Seamless” Data Movement

Moving data on the network is a non-trivial operation. It must be conducted in such a manner to ensure that the user that owns the data and the integrity of the data itself is not impacted.

Simply copying the data to the new location and deleting the data in the old location is not good enough. What if files are open during the move process or the user is logged in or logs in during the process? What if others share access to the storage? How is the user cognizant of the fact that a migration of his files is in progress?

File System Factory™ contains safeguards to ensure “seamless” migration of the data by taking the necessary precautions to avoid these and other situations and educate the user about the migration process.

For example, File System Factory™ will defer migration of data for a user that is logged in to the server holding the home directory until the user is no longer logged in. Once migration begins the user’s Home Directory attribute will be temporarily changed to point to a PROXY location that contains information about the move process.

“Seamless” Data Movement

Moving data on the network is a non-trivial operation. It must be conducted in such a manner to ensure that the user that owns the data and the integrity of the data itself is not impacted.

Simply copying the data to the new location and deleting the data in the old location is not good enough. What if files are open during the move process or the user is logged in or logs in during the process? What if others share access to the storage? How is the user cognizant of the fact that a migration of his files is in progress?

File System Factory™ contains safeguards to ensure “seamless” migration of the data by taking the necessary precautions to avoid these and other situations and educate the user about the migration process.

For example, File System Factory™ will defer migration of data for a user that is logged in to the server holding the home directory until the user is no longer logged in. Once migration begins the user’s Home Directory attribute will be temporarily changed to point to a PROXY location that contains information about the move process.

“Seamless” Data Movement

Moving data on the network is a non-trivial operation. It must be conducted in such a manner to ensure that the user that owns the data and the integrity of the data itself is not impacted.

Simply copying the data to the new location and deleting the data in the old location is not good enough. What if files are open during the move process or the user is logged in or logs in during the process? What if others share access to the storage? How is the user cognizant of the fact that a migration of his files is in progress?

File System Factory™ contains safeguards to ensure “seamless” migration of the data by taking the necessary precautions to avoid these and other situations and educate the user about the migration process.

For example, File System Factory™ will defer migration of data for a user that is logged in to the server holding the home directory until the user is no longer logged in. Once migration begins the user’s Home Directory attribute will be temporarily changed to point to a PROXY location that contains information about the move process.

“Seamless” Data Movement

Moving data on the network is a non-trivial operation. It must be conducted in such a manner to ensure that the user that owns the data and the integrity of the data itself is not impacted.

Simply copying the data to the new location and deleting the data in the old location is not good enough. What if files are open during the move process or the user is logged in or logs in during the process? What if others share access to the storage? How is the user cognizant of the fact that a migration of his files is in progress?

File System Factory™ contains safeguards to ensure “seamless” migration of the data by taking the necessary precautions to avoid these and other situations and educate the user about the migration process.

For example, File System Factory™ will defer migration of data for a user that is logged in to the server holding the home directory until the user is no longer logged in. Once migration begins the user’s Home Directory attribute will be temporarily changed to point to a PROXY location that contains information about the move process.

“Seamless” Data Movement

Moving data on the network is a non-trivial operation. It must be conducted in such a manner to ensure that the user that owns the data and the integrity of the data itself is not impacted.

Simply copying the data to the new location and deleting the data in the old location is not good enough. What if files are open during the move process or the user is logged in or logs in during the process? What if others share access to the storage? How is the user cognizant of the fact that a migration of his files is in progress?

File System Factory™ contains safeguards to ensure “seamless” migration of the data by taking the necessary precautions to avoid these and other situations and educate the user about the migration process.

For example, File System Factory™ will defer migration of data for a user that is logged in to the server holding the home directory until the user is no longer logged in. Once migration begins the user’s Home Directory attribute will be temporarily changed to point to a PROXY location that contains information about the move process.

BUS 145

2003-12-08T12:43:39