You need to back up your Content Engine data, including the version
3.5.2 GCD, the object store databases and the file stores.
To create Content Engine data
backups:
- Back up the version 3.5.2 Global Configuration Data (GCD), which is in the SYSINIT path.
The default location is C:\Program Files\FileNet\Content
Engine\sysconfig\sysinit.
- Back up the object store databases using the database or
other tools.
By backing up the object store database,
you can create replica object stores later on. Using a replica allows
the upgrade process to proceed outside of the production environment,
and the version 3.5.2 production system remains intact and functional.
- If you are moving your Content Engine and the file stores to
UNIX, copy the file store files and directories to the UNIX® (version 5.0.0) server by completing the
following substeps.
Remember: These copy operations
must be repeated if you make updates to the content of the version
3.5.2 production system.
Later in this process, you will
provide the proper input to the Content Engine Web
Upgrade Tool or its command-line option to indicate where the file
store is located on UNIX. The
upgrade tool enters this information into the version 5.0.0 system.
- Using tools appropriate to your environment, copy the
file stores from the Windows® system
to the UNIX system. If you created full-text indexes for the file
store, you can save resources by not copying them with the file store
directory and files. You recreate the indexes using version 5.0.0
of Content Search Engine after the
file store is in its new location. The file store stakefile area.sf gets
copied when you copy all the other version 3.5.2 file store files
and directories
- Verify that the utility that copies or restores the
file store onto the UNIX system can preserve the folder structure
of the original file store.
- Ensure the logical structure of the Windows security
settings are translated to the UNIX system (for example, the Content Engine user only, or the Content Engine user plus group access).
In particular, the UNIX user ID who runs the Content Engine application server must
have read-write permission to all files under this copied file store
directory structure and read-write-execute permission for all directories
on the UNIX file store directory structure. The owner of the copied
files and directories must be the same as the UNIX user ID that runs
the Content Engine application
server.
- If you use the command-line Content Engine Upgrader to perform the
upgrade, you must take appropriate steps to configure Windows access
to the file stores on the UNIX system by the tool.
These
steps depend on the type of storage. Some storage devices allow simultaneous
access using both CIFS and NFS. Or you might use an NFS gateway (for
example, Microsoft Windows Services for UNIX) to enable communication
between the version 3.5.2 Windows-based Enterprise Manager and the
command-line option of Content Engine Web
Upgrade Tool, as the NFS clients on the replica server, and the relocated
file storage areas, with UNIX as the NFS server.