8
Migrating, Backing Up, and Restoring Data

This chapter describes how to migrate content and users from legacy systems to Oracle Internet File System (Oracle 9iFS) and from one instance of Oracle 9iFS to another. It also discusses basic backup and recovery features. Topics include:

• Migrating Legacy Data to Oracle 9iFS

• Migrating Data and Users from One Instance of Oracle 9iFS to Another

• Backing Up and Restoring Data

Migrating Legacy Data to Oracle 9iFS

Ideally, migration to Oracle Internet File System (Oracle 9iFS) goes so smoothly that end users initially don't notice the change. Many Oracle 9iFS administrators accomplish this goal by scheduling downtime for the weekend, when file system usage is at a low point. The administrator can then perform the migration, shut down the old server, and give the new server the same IP address, name, and other characteristics of the old system. When users arrive on Monday morning, they see the same file, e-mail, FTP, or Web server they saw before. The only difference they notice is when the administrator shows them how to use the advanced features of Oracle 9iFS, such as versioning or multiple foldering.

Migration Checklist

When migrating from other file servers to Oracle 9iFS, you need to think about how to move:

The user list from the old system to the new one. In short, you need to recreate each user as an Oracle 9iFS user.

The group list. You need to recreate the groups and add members to them.

Content. The actual files and folders need to be copied from the old system to the new one.

Applications. Any applications you run on the server or that you run remotely from the server need to move to the new system.

Network configuration. You need to build the same network configuration around the new file server that you had around the old one. Issues like assigning an IP address or server name are covered in the Oracle Internet File System Installation Guide.

Migrate the Users

The first task in moving to a new Oracle 9iFS is creating the user list. Currently, there is no automatic way to copy the user list from an existing Windows or UNIX file server, so you need to use one of three options for creating users:

• Oracle 9iFS Manager

• The Web interface

• XML configuration files

For details on all three methods, consult "Step 2: Create Users and Groups" in Chapter 4, "Setting Up Oracle Internet File System".

Keep in mind that, when you create a user, you need to not only create the unique username and password, but also the e-mail ID for the user.

Scripted User Creation

If your file system's management tools provide a way of dumping the user list to a tab- or comma-delimited file or similar format, you could then write a simple script that would translate this user information into a set of XML files, following the format required for XML-based user creation in Oracle 9iFS. You could then load the files into your new Oracle 9iFS through one of the protocol servers (most likely the Command Line Utilities, since it was designed for this kind of scripted administrator activity).

Recreate the Groups

Recreating the groups requires creating the groups, then adding the users to them. Since Oracle 9iFS supports nested groups, you can add a group to another group during this step. For details on creating groups and adding members, see "Step 2: Create Users and Groups" in Chapter 4, "Setting Up Oracle Internet File System".

Scripted Group Creation

If your management tools let you export group information to a file, you could then write a translation script to convert the groups into XML format and then load them into Oracle 9iFS.

Migrate the Content

After creating users and groups, the next step is to move the files and folders into Oracle 9iFS.

What actually gets moved? The files and folders themselves, as well as the basic metadata about them that any Copy command would support during a copy operation through FTP, Windows networking, or some other protocol. The filename, size, and date last modified are the key attributes that get copied along with the content.

However, there may be content that you cannot migrate from the old system to Oracle 9iFS. For example, if your old file system or document repository stores owner information, this type of metadata may not be copied with the file. The owner in this case becomes the Oracle 9iFS user copying the file, not the original owner in the old system.

Similarly, if applications running on the old system maintain metadata about files, this information will not be copied with the files. For example, a document management system may point to files in the old file system and add attributes to these files. Since this information is intrinsic to the document management system, not the file system, the extra metadata will not get copied along with the files.

Protocols for Copying Data

When copying the files, you'll be using one of the network protocols:

• FTP: The most lightweight protocol, FTP will move large amounts of data faster than the other protocols. For bulk operations, such as migrating from an existing system, FTP is the protocol of choice. You need to use either command line FTP or a GUI FTP client for this step. For more information about the FTP Quote commands, see Appendix F, "FTP Quote Commands".

• SMB: The Windows file-sharing protocol SMB provides the ease of drag-and-drop copy operations from one system to another. However, SMB itself is a more complex protocol than FTP, performing extra operations like attempting to create a 0 kilobyte version of a file before actually copying the file. Therefore, SMB requires some sacrifice of performance for ease of use. For more information on drag-and-drop copy operations with SMB, see "Drag and Drop Files into Oracle 9iFS" in Chapter 4, "Setting Up Oracle Internet File System".

• CUP: If you want to script other activities around the copy operation, such as assigning owners or ACLs to a file, then CUP (Command Line Utilities) is the protocol you should use. For more information about CUP, see Appendix A, "Command Line Utilities Reference".

• WebDav: A protocol designed for Internet and intranet collaboration on files, WebDav lets you drag and drop data from one system to another.

• NFS: The Network File System (NFS) protocol is used to provide file sharing between a client machine and a server machine across a network. The NFS protocol is a standard protocol which is widely used for file sharing on UNIX platforms.

Moving E-mail

Moving e-mail is a slightly different process. Since there is no native copy interface between e-mail servers in the way, for example, you can easily copy from one Windows NT or 2000 file server to another. Therefore, when copying e-mail, you must either do it through an e-mail client, or write a copy utility that speaks to the different ports running IMAP on the old and new systems.

When you copy e-mail, be sure to copy it to the users' Mail directory, or any subdirectories (such as Inbox) underneath them. Since the IMAP protocol server points to the mail directory, users will not be able to see e-mail in other folders through IMAP.

Migrate Your Applications

The trickiest part of the migration will probably be moving the applications running on the old system to the new one. Effectively, there are three types of application migrations:

• Moving applications running on other Oracle 9iFS instances.

• Migrating embedded applications. If you have a server-side application already running on the old server, you need to move the application logic and user interface to Oracle 9iFS. For example, if you have an existing web site management system, you may need to recreate the application components on the new Oracle 9iFS instance.

• Migrating standalone applications. You may have application executables stored on a server, ready to be run remotely by any user from a client machine double-clicking the file from Windows.

Moving Oracle 9iFS Applications

Moving Oracle 9iFS applications from one system to another really depends on whether the developers followed best practices when designing how to deploy the application. Ideally, the developers wrote scripts that copy the different application components to the correct directories in the correct order, so that recreating the application on a new system requires pointing the scripts at a different system.

An Oracle 9iFS application may include some or all of the different parts of the Oracle 9iFS SDK:

• Subclasses

• Custom parsers

• Custom renderers

• Custom Web interface components, written as Java Server Pages (JSPs) or static HTML

• Custom agents and overrides

• Various configuration files designed to register these components and configure the system

For a complete list of application components and what they do, consult the Oracle Internet File System Developer Reference.

Migrating Embedded Applications

Undoubtedly the most difficult situation for application migration occurs when you have a server-side application already running. For example, you may have deployed a document or knowledge management system with its own custom metadata, security, business logic, and user interfaces, all designed for the old operating system.

These sorts of applications, if they can run remotely from the actual document repository, may still work. If they can connect to the file server via one of the standard network protocols, then the application can continue to work. The only complication may occur if changes on Oracle 9iFS, such as users applying restrictive ACLs, somehow interfere with the application.

Otherwise, you will need to rewrite the application, using the Oracle 9iFS SDK. The Oracle 9iFS Java API exposes all the capabilities of the file system, including versioning, check-in/check-out, and searching. Since these content management capabilities are provided as pre-existing components, rewriting a content management application may only require adding additional business logic and the user interface.

Migrating Standalone Applications

Lastly, you might have executables stored on a file server, run by users accessing the application across the network. In these cases, Oracle 9iFS imposes no special restrictions. If you could run it from your old file server, you will be able to run it from the new one.

An increasing number of applications, such as Sun's Star Portal or Microsoft Access, are designed for remote execution from a client. Since Oracle 9iFS is designed for scalability, you can better accommodate the remote execution of these applications by a growing number of users by hosting them on Oracle 9iFS.

Migrating Data and Users from One Instance of Oracle 9iFS to Another

Using the Import/Export utility, you can automate the migration of content and users from one instance of Oracle 9iFS to another without losing versioning information, multiple links, and custom subclassing information.

To do this, you first export the data to an "ExportSet," then import the data from the ExportSet into a different Oracle 9iFS instance. The Import/Export utility retains both the content and its structure, enabling you to export an entire folder hierarchy including metadata.

Note: This utility is designed for exporting an entire directory, not just an individual file.

Using a similar technique, the import and export process can be used to migrate user definitions from one Oracle 9iFS instance to another.

Creating the Export Set

The first step is to create the ExportSet.

1. At the command line, enter:

   ifsexportcontent
   
   

2. On the Import/Export screen (see Figure 8-1), enter information in the four sections:
   • User Login Information

   • Service Information

   • Import/Export Information

   • Export Content Information

3. Click the Export Location(s) button.

4. Depending on the outcome of the export action, a Success or Exception dialog displays. To view the details of the operation, consult the log file.

Figure 8-1 Export Content Screen

Text description of the illustration 7expcont.gif

Refer to Table 8-1, "Export Options" for a description of each field and a sample entry.

Table 8-1 Export Options

Option Name	Description	Example
Username	The name of an Oracle 9iFS administrator.	system
Password	The password for the Oracle 9iFS administrator.	manager9ifs
Service	The name of a ServiceConfiguration file.	IfsDefault
Schema password	The password for the Oracle 9iFS schema.	ifssys
Log file	The name of the file to consult to see if the Export Set was created successfully.	export.log
Verbose logging	Select True for a detailed log.	True
Maximum number of files per folder	The maximum number of files put into a folder while creating the ExportSet on the local system. If you specify more than 50, a folder hierarchy is created.	53
File location	The directory on the local system where the export will be created.	/Public/Development/Specifications
Filename	The name of the ExportSet that will be created on the local system.	DevSpecs
Content file prefix	The prefix used for any content file or directory created on the local system during an export. The default is to pick up the filename.	DevSpecs
Export location(s)	The Oracle 9iFS locations to be exported.	/private/jsmith/backups /public

Importing the ExportSet

The second step is to import the ExportSet into the second Oracle 9iFS instance.

1. At the command line, enter:

   ifsimportcontent
   
   

   This script must be located in $ORACLE_HOME/9ifs/bin.

2. On the Import/Export screen (see Figure 8-2), enter information in the three sections:
   • User Login Information

   • Service Information

   • Import/Export Information

3. Click the Import Location(s) button. The utility checks that the class objects are the same.
   • If everything matches, the Success dialog displays. You can open the Import to folder/location file to check that the information is there.

   • If not, exceptions are written to the log file, the Exception dialog displays, and the command line from where ImportContent was run.

   • If the import fails, it is likely because their are directory users in the ExportSet that have no counterparts in the import system. See "Handling Phantom Users" to resolve this problem, then perform the import operation again.

Figure 8-2 Import Content Screen

Text description of the illustration 7impcont.gif

Refer to Table 8-2, "Import Content Options" for a description of each field and a sample entry.

Table 8-2 Import Content Options

Option Name	Description	Example
Username	The name of an Oracle 9iFS administrator.	system
Password	The password for the Oracle 9iFS administrator.	manager9ifs
Service	The name of a ServiceConfiguration file.	IfsDefault
Schema password	The password for the Oracle 9iFS schema.	ifssys
Log file	The name of the log file.	import.log
Verbose logging	Select True for a detailed log.	True
File location	The local file system location where the ExportSet was created.	File location = /private/jsmith/backups
Filename	The name of the ExportSet that will be imported.	DevSpecs
Import to Folder/location	Where the originally exported objects will be foldered.	/RestordFiles/Development/temp
Create Phantom users	Set to Yes to create "phantom" users to match directory users in the ExportSet that don't exist in the import system. If you select No, and there are unmatched directory users, the import action fails.	Yes

Handling Phantom Users

If there is a directory user in the ExportSet that doesn't exist in the import system, the import fails unless you create "phantom" users. Phantom users are users added to the import system, without user profiles or group membership information (hence the name, phantom). After the import is complete, you can turn the phantoms into real users by importing the users explicitly or deleting them.

Import a Profile

A phantom user can become a real user by importing the user from a UserExportSet. To add the profile, export the user from the system where the user exists and import it into this one. See "Exporting and Importing Users".

Delete a Phantom User

You can delete undesired phantom users on the Phantom User Handler screen (see Figure 8-3, "Phantom User Handler Screen").

Figure 8-3 Phantom User Handler Screen

Text description of the illustration 7usehand.gif

1. At the command line, enter:

   ifsphantomuserhandler
   
   

2. On the Phantom User Handler screen, enter information in the three sections, as shown in:
   • User Login Information

   • Service Information

   • Import/Export Information

Table 8-3 Handle Phantom Users Options

Option Name	Description	Example
Username	The name of an Oracle 9iFS administrator.	system
Password	The password for the Oracle 9iFS administrator.	manager9ifs
Service	The name of a ServiceConfiguration file.	IfsDefault
Schema password	The password for the Oracle 9iFS schema.	ifssys
Log file	The name of the log file.	import.log
Verbose logging	Select True for a detailed log.	True
Delete phantom users	Set to True to delete the phantoms. Set to False to just list them in the log.	True

Exporting and Importing Users

Exporting and importing users also requires the creation of an ExportSet, called the UserExportSet in this case, that is then imported into the second Oracle 9iFS instance. In addition, when importing users it is necessary to migrate their passwords.

Create the UserExportSet

1. At the command line, enter:

   ifsexportusers
   
   

2. On the Import/Export screen, enter information in the three sections:
   • User Login Information

   • Service Information

   • Export User(s) Information

   The information you enter on this screen is identical to the information you enter on the Export Content screen, except Export User has two more options and the Export User option replaces the Export Location option.

   The additional options are:

   • Get all groups: To include any groups the user belongs to directly or indirectly (because a group the user belongs to in inside of another group).

   • Get direct groups: To include only those groups of which the user is a direct member.

   To specify which users to include in the UserExportSet, you identify them in the Export User(s) Information section of the screen (see Figure 8-4). Type the user name in the text box and click the Add User button.

   For details about the other options, see Table 8-1, "Export Options".

3. Click the Export User(s) button.

4. Depending on the outcome of the export action, a Success or Exception dialog displays. To view the details of the operation, consult the log file.

5. (Optional) Following the instructions in "Creating the Export Set", create an ExportSet of files outside of the users' home folder hierarchies which you want to export. If additional files are not needed, you can skip this step.

Figure 8-4 Export User Screen

Text description of the illustration 7exuser.gif

Import the UserExportSet

1. At the command line, enter:

   ifsimportusers
   
   

   This script must be located in $ORACLE_HOME/9ifs/bin.

2. On the Import/Export screen, enter information in the three sections:
   • User Login Information

   • Service Information

   • Import/Export Information

   Refer to Table 8-2, "Import Content Options" for a description of each field and a sample entry.

3. Click the Import User(s) button. The utility checks that the class objects are the same.
   • If everything matches, the Success dialog displays. You can open the Import to folder/location file to check that the information is there.

   • If not, exceptions are written to the log file, the Exception dialog displays, and the command line from where ImportContent was run.

   • The import fails. If the import fails, it is likely because their are directory users in the ExportSet that have no counterparts in the import system. See "Handling Phantom Users" to resolve this problem, then perform the import operation again.

   At this point, the users are unable to log into that second schema, as credential information does not yet exist.

4. (Optional) If you created an ExportSet of additional files, follow the steps in "Importing the ExportSet" to import the ExportSet of additional files into the second schema, placing them in a public location.

5. (Optional, if all home folders are not located correctly.) Move the home folders and any other files and folders to the desired location in the folder tree of the second schema using any of the Oracle 9iFS clients.

Figure 8-5 Import Users Screen

Text description of the illustration 7impuser.gif

Migrate the Users' Credential Information

If the users use the Oracle 9iFS Credential Manager, migrate credential information for the users to the second schema's credential management tables.

1. At the command line, enter:

   ifsmigratepasswords
   
   

2. On the Migrate Passwords screen (see Figure 8-6, "Migrate Passwords Screen"), enter information into the three sections:
   • Import/Export Information

   • From Database Information

   • To Database Information

   As the administrator, you have entered this information before, when connecting to the Oracle 9iFS repository. For more information, see Chapter 3, "Working with Oracle 9iFS Manager". This information is being used to connect to the Credential Manager table. For more information on the credential manager, see "Credential Manager Users" in Chapter 4, "Setting Up Oracle Internet File System".

3. Click the Migrate User Password(s) button.

Figure 8-6 Migrate Passwords Screen

Text description of the illustration 7migpass.gif

Backing Up and Restoring Data

All Oracle 9iFS data is currently stored inside the database, which allows you to rely on the usual backup and recovery mechanisms used for all other Oracle data. This is an important step when migrating data; if you use FTP to migrate data, all versioning, ACLs, ownership of files, and extended attributes will be lost. It is highly recommended that you back up your data before you migrate your data.

For more information on using Oracle's backup and recovery mechanism, see the Oracle9i Recovery Manager User's Guide and the Oracle9i Recovery Manager Reference. This guide explains what to do for the different possible scenarios, what software is required, and what to set up.

When saving files, there is no way of restoring a single document from a backup. The database is saved in a way which does not allow you to restore complete data files or to restore until a defined point in time, to save the document with all repository data describing it, or to restore this information back into the system.

Performing Backups with the Import/Export Utility

The Import/Export utility can be used to back up and restore a subset of the Oracle 9iFS repository, rather than the entire database, while retaining data such as versioning, security, and custom attribute information.

A detailed description of how to use the Import/Export Utility is provided in "Migrating Data and Users from One Instance of Oracle 9iFS to Another".