High availability Content Platform Engine, Version 5.2              

Configuring file stores for high availability

File store content is managed from the Content Platform Engine application.

Ensure that the file store data is highly available and that access to content in file stores is not interrupted.
All file stores
File systems that are used for file stores must be shared or mounted through the NFS or CIFS protocol.
Each Content Platform Engine instance in a farm must have access to the same shares or mount points.
Standard file stores
Standard file stores must be installed in file systems that are highly available.
Fixed File Stores
The front end of the file system must be made highly available, as indicated previously, and the remote device must be made highly available by using its built-in capability. See your fixed file store documentation for details.
Tip:
  • A fixed file store comprises a file system-based front-end, similar to a standard file store, and a remote storage system such as Centera or NetApp/IBM® N-Series SnapLock.
  • The method and technology used to make file store data highly available can vary greatly, from file servers built on general-purpose hardware and cluster technology, such as IBM HACMP™, to specialized devices with built-in high availability such as NAS- and SAN-based offerings from EMC, NetApp or IBM.
  • The implementation and use of these technologies vary, but they can all be used to provide highly available access to data so long as they meet the criteria discussed in this section.


Feedback

Last updated: October 2013
p8phi014.htm

© Copyright IBM Corporation 2013, 2014.
This information center is powered by Eclipse technology. (http://www.eclipse.org)