White Paper
Storage Manager
Simplifying Data Migrations
from Micro Focus to Microsoft
with Storage Manager
We value our customer relationships and understand that
certain events, such as mergers or mandates from new
CIOs, can result in a decision to move from a Micro Focus®
network operating system to a Microsoft network. We want
to make that transition as painless as possible for our
customers while giving them the opportunity to reap
ongoing value from their Micro Focus relationship.
Micro Focus Storage Manager helps these customers
simplify and reduce the cost of their migration effort
while giving them a comprehensive storage management
solution that will automate the full lifecycle of user and
group storage on their new Windows environment.
White Paper
Simplifying Data Migrations from Micro Focus to Microsoft with Storage Manager
Cross-Empire Data Migration:
Reducing Migration Complexity,
Gaining Post-migration Value
The aftermath of a merger between companies often has significant impact on the merged entities’ IT
infrastructures. If the separate companies use different network file systems, one of these post-merger
impacts might be a decision to consolidate network platforms.
Sometimes the decision is to consolidate to a Micro Focus
environment, and other times it is a decision to consolidate to
Microsoft. A mi­gration from Micro Focus to Microsoft requires
a significant investment in time and money. And when this
decision is unavoidable, we provide our customers a way to
migrate their file system data to Microsoft in a manner that
significantly reduces the effort and expense required by other
migration options.
Maintains proper rights, permissions and file metadata that can be
lost using other migration methods
The extensive planning requirements, the need for continued data in­
tegrity and the complexity of working with two distinct systems can turn
network file system migrations into massive projects for IT. Oftentimes,
organizations engage ser­vice providers that require the upfront pur­
chase of expensive, one-time-use migration utilities. Once the migration
project is complete, the migration utilities provide no fur­ther value to
the organization.
Gives users continued access to their files during the initial phases
of the migration process
Conversely, we reduce the complexity and cost involved in file sys­
tem migration with a powerful, cross-platform data migration ca­pa­bility
built into Storage Manager. Not only does the func­tion­ality in Storage
Manager simplify the migration effort while ensuring continued data
integrity and proper file rights, but the com­pre­hensive file system man­
agement solution provides continued value to the organization long after
it completes the migration project.
The following represent some of the key benefits associated with the
Cross-Empire Data Migration subsystem built into Storage Manager:
2
Potentially saves thousands of dollars in work hours and c­ onsulting
fees
Eliminates the complexities of migrating data between disparate
networks
Significantly reduces the time to migrate, even for extremely large
enterprises
Ensures data consistency between the old environment and the
new environment during the migration
Retains existing associations among users, files and folders,
­including drive mappings
Facilitates automation of multiple migration scenarios with its
easy-to-use wizard interface
Continues to provide significant value after the migration as a
comprehensive file management solution that automates the full
lifecycle of user and group storage management
Introduction to Cross-Empire Data Migration
The Cross-Empire Data Migration subsystem built into Storage Manager
enables the transfer of file system data between storage infrastructures
on different platforms governed by different identity and security frame­
works. It automates data movement for a variety of scenarios, including
user-to-user, folder-to-user, group-to-group, folder-to-group and folderto-folder. It easily moves data across multiple servers or shares in a single
operation, while preserving file system metadata. Additionally, it can le­
verage policies in Storage Manager to move data into a managed stor­
age environment on the target system with the option of automatically
restructuring and reorganizing that data as desired during the process.
Identity map creation
Migration of closed files
Migration of remaining files, including new and modified files
Verification of successful migration
In the following sections, a folder-to-folder migration option is used to ex­
plain the different migration phases. A folder-to-folder migration moves a
folder and its contents directly from the source network to a designated
location on the target network. This method allows you to specify distinct
file system paths on both the source and target networks.
Identity Map Creation
Creating an identity map allows organizations to manage the migration of
security and ownership assignments directly from the Micro Focus source
environment to the target Microsoft environment. It enables objects that
have specific NetWare® or Open Enterprise Server network rights to files
or folders in the source environment to have those trustee assignments
migrated to the equivalent objects in the target environment.
Like all Micro Focus networking services technologies, the Cross-Empire
Data Migration subsystem is engineered to meet the uncompromising
standards of today’s enterprises. For example, its state machine archi­
tecture enhances migration performance and reliability. If a power out­
age or other complication disrupts the migration process, once power is
restored or the complication is remediated, the migration can continue
where it left off without any risk of data loss or corruption.
The Storage Manager interface provides a wide variety of migration
options that give you greater control and flexibility in managing the
data migration operation. Additionally, the wizard interface simplifies and
automates the entire process, while also allowing a phased approach
to the migration effort.
The following represent the four main phases of a migration using the
Cross-Empire Data Migration subsystem in Storage Manager:
Ownership and Trustee Assignments
When creating an identity map, you define associations between user,
group and container ownership and trustee assignments for the data
on the Micro Focus network file system and the corresponding data
owners on the target Microsoft network. Storage Manager provides a
variety of options for automatically locating and matching objects based
on a number of rules. It also provides options for creating manual as­
signments and editing assignments.
3
White Paper
Simplifying Data Migrations from Micro Focus to Microsoft with Storage Manager
Identity Map Wizard
The Identity Map Wizard in Storage Manager first generates a prelimi­
nary identity map that contains a small number of suggested entries
(for example, Public:Everyone and Supervisor:Local System). The wizard
appends and modifies these entries as it steps the administrator through
the creation of the identity map.
User Account Associations
When defining the identity map, the wizard lets the administrator desig­
nate whether Security Account Manager (SAM) accounts or Common
Name accounts are to be used on the target network. Once the adminis­
trator has selected the account type, the wizard allows the administrator
to browse source containers to select the users to be included in the
map and then browse the target containers to select its associated us­
ers. Once the selections and associations have been made, the wizard
updates the identity map. You must create a single identity map for each
Micro Focus eDirectory™ tree that you are migrating.
You can run the wizard multiple times to make changes or insert ad­
ditions into any identity map. The wizard can also run multiple times to
generate a map that contains a combination of both SAM and Common
Name user accounts. Additionally, if your organization already has a data
set that defines equivalencies, these can be imported to facilitate the
building of the identity map.
Verifying Identity Map Accuracy and Completeness
To verify the accuracy and completeness of an identity map, Storage
Manager provides a preview report that runs a check scan of the rights
and ownership assignments in the source file system in comparison to
those defined in the identity map. The preview report identifies any ob­
jects that still need a definition within the map or have not been mapped
to a target object. The preview report also gives you another opportunity
to make sure they have properly mapped existing rights from the source
system to the appropriate files and folders on the target system.
Note: If your organization does not want to maintain the rights, trustee
assignments and other metadata associated with the data on your Micro
Focus network as you migrate to Windows, you can skip the process of
creating an identity map. In this case, you would simply use the Migrate
Data Only option in the Cross-Empire Data Migration subsystem to
perform the migration.
Migration of Closed Files
Once you have created the necessary identity maps and verified their
ac­curacy and completeness, you can move on to the next migration
phase­­—the migration of closed files. You accomplish this using the Skip
Open Files option in the Data Migration Wizard, described below.
Handling Discrepancies between Source and Target Systems
In some cases, the source environment might contain certain objects
that do not have equivalent objects in the target environment. In these
instances, you must create the objects in the target environment before
you can define them in an identity map.
Additionally, the Micro Focus source environment might have objects with
certain rights that you cannot assign as a trustee in the target environ­
ment. For example, Active Directory does not support the assignment of
a container as a security object. In these cases, you can create a group
representing the container to facilitate rights assignments.
Although inherent differences in rights, trustee assignments and per­mis­
sions exist between Micro Focus and Microsoft networks, the Identity
Map Wizard in the Cross-Empire Data Migration subsystem has been
designed to identify the best match for the Micro Focus rights and trustee
assignments in the target Microsoft system. It also gives you the option
to modify the rights mappings as they deem necessary.
4
Since the migration process consumes network resources, the ideal
time to perform this phase of the migration is after work hours or during
weekends. This also helps ensure that the majority of files are closed,
increasing the number of files that you can successfully migrate during
this phase. However, when dealing with terabytes of data that need to
be migrated, you might need to start the migration during the workweek.
In these cases, threading options are available to minimize the impact
on the network.
Even though you will not be migrating open files during this phase, the
Cross-Empire Data Migration subsystem creates a log file of all the
open files that it has skipped. The Data Migration Wizard leverages
this file in the next phase of the migration. It also gives you a record of
those files that need to be closed in order to complete the migration.
Data Migration Wizard
In preparation for initiating this phase of the migration, the Data Migration
Wizard guides the administrator through a number of steps and options.
The first of these is to indicate the type of migration to be performed (for
example, user-to-user, group-to-group, folder-to-folder). When perform­
ing a folder-to-folder migration, you can specify an existing target folder
for their migrated data or have the Data Migration Wizard create a new
target folder. They can also choose whether to migrate all of the closed
files at once, or skip some files and migrate them later.
After selecting the data copy options, the wizard lets you specify how
to handle data ownership and rights. This includes using the previously
created identity map to ensure the proper migration of security rights
and file ownership from eDirectory to Microsoft Active Directory.
The final options presented by the wizard include the ability to create
filters to include and exclude certain files, and the option to run a valida­
tion test. The validation provides the opportunity to correct any potential
configuration errors before initiating the migration. Clicking the Migrate
button is the final step of this phase, which initiates the migration and
presents a page that details its progress.
Migration of Remaining Files
To migrate all the remaining files, all users must be logged out of the
source Micro Focus network to ensure that no files are open. In this
phase, not only are the previously skipped files migrated, but so are any
of the previously migrated files that have since been modified on the
source system. Any new files that users have created in the interim are
migrated, as well. The Data Migration Wizard facilitates all of these in
a two-step process.
Next, the wizard gives you the option to automatically generate map­
pings between source folders and target folders. When selected, you
can browse to and select the source and target folders that need to
be associated. It also provides the ability to have Storage Manager
automatically create new folder entries for any items that do not have
a matching target folder and to populate any subfolders that do not
exist in target folders.
In addition, the wizard allows you to specify target folders for any source
folders that it was unable to associate automatically. You can also modify
target folder assignments for any folders or subfolders that might have
been associated improperly.
Data Copy, Ownership, Filtering and Validation Options
After defining the folder-to-folder mappings, the wizard allows you to
specify certain data copy options. This includes how the wizard should
handle duplicate filenames found in the source and target folders, how
quota settings from source folders should be applied after the migration,
and how to deal with files with namespace issues that the Micro Focus
file system can’t resolve. This is also the point when the op­tion to skip
open files can be selected.
5
White Paper
Simplifying Data Migrations from Micro Focus to Microsoft with Storage Manager
Migrating Previously Skipped Files
Once users are logged out, the first operation in this phase is to migrate
all of the files that Storage Manager previously skipped. With a few slight
variations, the migration steps in this phase follow many of the same
steps that took place during the migration of closed files. The main dif­
ference is that you need to set the data copy option to the Overwrite if
Newer setting.
Another difference is that the file list Universal Naming Convention
(UNC) path on the wizard’s Copy Filter page needs to point to the UNC
path of the previously created log text file that contains the list files
skipped in the previous migration phase. This causes the migration to
focus on copying only those files that were previously skipped. The rest
of the wizard process proceeds as normal, including clicking the Migrate
button to kick off the migration of the skipped files.
Migrating New and Modified Files
In a multi-phase migration process, users will continue to use the source
network until the migration is complete. As a result, users may have
modified some files that had been migrated previously (as closed files),
and the updated versions of those files will need to be migrated. You will
also need to migrate any new files created during this time.
Storage Manager facilitates this process with a file system scan wizard
that you can use to easily create a job file that scans the network for any
files that have been modified or added since a specified time. The scan
results are placed in a text file that the Data Migration Wizard leverages
to finalize the migration.
Verification of Successful Migration
In the final phase of the migration, the CEDMScanCompare utility lets
you verify that everything has migrated as expected. This utility reports
on files located on the source Micro Focus server and the destination
Microsoft server and then compares the two to determine if any dis­
crepancies exist. The administrator can then use the report as a means
of remediating the problem.
6
Simplified Migration, Continued Value
For organizations that have decided to migrate from a Micro Focusnetwork
file system to a Windows network, Storage Manager eliminates the com­
plexities associated with such a move. The Cross-Empire Data Migration
subsystem in Storage Manager saves organi­zations significant time and
expense, reduces migration complexity, and ensures data consistency
and the integrity of the file system’s rights, permissions and metadata.
Additionally, the comprehensive storage management capabilities inher­
ent in Storage Manager provide continued value to the organization long
after the migration has finished.
To learn more about Storage Manager and how it can simplify migra­
tions from Micro Focus environments to Windows environments, contact
us today.
About Micro Focus
Since 1976, Micro Focus has helped more than 20,000 custom­
ers unlock the value of their business logic by creating enabling
solutions that bridge the gap from well-established technologies
to modern functionality. The two portfolios work to a single, clear
vision—to deliver innovative products supported by exceptional cus­
tomer service. www.microfocus.com
Micro Focus
UK Headquarters
United Kingdom
+44 (0) 1635 565200
U.S. Headquarters
Provo, Utah
801 861 4272
888 321 4272
Additional contact information and office locations:
www.novell.com
162-000043-002 | N | 09/15 | © 2015 Micro Focus. All rights reserved. Micro Focus, the Micro Focus logo, eDirectory, and NetWare, among others, are trademarks
or registered trademarks of Micro Focus or its subsidiaries or affiliated companies in the United Kingdom, United States and other countries. All other marks are the property
of their respective owners.