We address administrative topics of an IBM FileNet Content Manager solution, including deployment, system administration and maintenance, and troubleshooting. Implementation topics include system architecture design with various options for scaling an IBM FileNet Content Manager system, capacity planning, and design of repository design logical structure, security practices, and application design. An important implementation topic is business continuity. We define business continuity, high availability, and disaster recovery concepts and describe options for those when implementing IBM FileNet Content Manager solutions.
Many solutions are essentially a combination of information input ingestion , storage, information processing, and presentation and delivery. This book is intended to be used in conjunction with product manuals and online help to provide guidance to architects and designers about implementing IBM FileNet Content Manager solutions. When determining problems with the endpoint, it is important to remember that the endpoint operates in conjunction with two other components of the Tivoli environment: the endpoint manager and the gateway.
Therefore, you need to assess the state of several Tivoli Management Framework components when troubleshooting endpoints: the endpoint itself, the gateways it can connect to, and the endpoint manager that is on the Tivoli server. Tivoli Kernel Services. To learn more about Redbooks and Redpapers, click here. Vol 25, No. A : Vol 25, No. Nikolai Bezroukov. This document is an industrial compilation designed and created exclusively for educational use and is distributed under the Softpanorama Content License.
Original materials copyright belong to respective owners. Quotes are made for educational purposes only in compliance with the fair use doctrine. We are making such material available to advance understanding of computer science, IT technology, economic, scientific, and social issues. We believe this constitutes a 'fair use' of any such copyrighted material as provided by section of the US Copyright Law according to which such material can be distributed without profit exclusively for research and educational purposes. Grammar and spelling errors should be expected. The site contain some broken links as it develops like a living tree The more the number of agents, the more requests can be processed concurrently.
Every agent requires system resources, therefore the number of concurrent agents is limited by the server's resources. Agents always run on the same machine as the archpro program and are automatically started by the archpro program. Domino dispatcher The Domino dispatcher not shown in the diagram is the interface between the archpro program and the CommonStore for Lotus Domino task which we explain later in this chapter.
It translates Domino requests into the language of the archpro program.
- Microbial Ecology of Aerial Plant Surfaces;
- Footer links.
- Investigative Computer Forensics: The Practical Guide for Lawyers, Accountants, Investigators, and Business Executives.
- Burying the Sun (Russian Saga);
- Enterprise Content Management | IBM Redbooks!
- Content Manager Implementation and Migration Cookbook.
- Upcoming Events.
The Domino dispatcher is a multi-threaded application allowing multiple CommonStore for Lotus Domino tasks to connect to it and send requests. It runs on the same machine as the archpro program, and is automatically started by the archpro program. Jobs are requests to CommonStore for Lotus Domino. According to the request stated in the job, it sends the request along with the file to the Domino dispatcher, which in turn forwards it to the archpro program. Archiving tasks process requests that add or modify content in the archive for example, archiving, updating, or deleting s.
There are retrieval tasks that process requests that retrieve content from the archive for example, searches or single document retrieval. CSLD tasks are not Domino server add-on tasks, but stand-alone applications. Multiple tasks can run on one machine. The crawler is a Notes agent that gets its configuration from the CSLD configuration database which we explain later in this chapter on a Domino server.
It goes through the Notes databases matching the configured criteria, and creates archive or deletion jobs in the CSLD jobs database which we explain later in the chapter on the Domino server. This independent program is the central application for the following functions: Policy-driven archiving Policy-driven deletion Administrator-triggered retrieval When used for policy-driven archiving or administrator-triggered retrieval, the crawler checks whether documents in the specified Lotus Notes databases meet a set of selection criteria, which is called a policy.
If documents meet these criteria, the crawler creates archiving or deletion jobs for them. It contains the configuration documents and the policies required for archiving. The schedules, document selection criteria, and archiving polices are defined in the configuration database. It collects all requests, such as archiving, retrieval, search, and viewing, and passes them onto the CSLD task.
The Web dispatcher runs on the same machine as the archpro program, and is automatically started by the archpro program. Overview of CommonStore 7. It can archive Exchange messages including attachments from any Exchange mailbox that resides on an Exchange Server.
Try BLU Acceleration on Cloud
CommonStore for Exchange Server provides the following functions: Migrating s from Exchange mailboxes or public folders to an archive Searching for content in an archive Displaying archived content Retrieving archived content Deleting archived content and archive repository definition An message consists of: Message body Message properties visible or invisible Attachments optional An archive is a repository that serves as a container for archived s. Automatic functions are set up centrally and include policy-driven archiving.
Entire message: Archives the entire including message body, properties, and attachments. Component: Decomposes the s into separate files, one file for each component and one MSG file for the message body. Nothing no link is a specialized type of deletion and is designed for the purpose of archiving envelope of journal messages. This option is only available with archiving type of Entire and Component. Overview of CommonStore 9. It maintains a list of logical archives and controls the flow of information to and from these archives.
All input and output data is routed through the archpro program. Archpro distributes the requests among the archive agents, which are the interfaces to the archive. For every archive supported by CommonStore, there is a special agent. An agent calls the APIs of the archive. When an instance of the CSX task is started, it reads the configuration data from this Active Directory. Additionally, the CSX System Manager writes client-relevant information into the configuration folder. It is responsible for performing interactive and automatic archiving and retrieval, during which it transforms Exchange messages into files and vice versa.
Overview of CommonStore It investigates mailboxes and public folders to see whether any message meets certain selection criteria. These criteria are defined in policies. If the messages meet the criteria that you defined in policies, the crawler creates archiving requests for them. Each crawler does this for exactly one Exchange Server. In addition, the crawler initiates the automatic removal of retrieved content, also known as restubbing. CSX Task: Poller The poller component continually looks for interactive job messages in the job folder.
Interactive jobs are created by clients Outlook users. The job messages contain the information necessary to perform the jobs. The poller converts this information and puts it in an internal job queue. It then accesses the Outlook messages referred to in the job messages and reads the content to be archived or identifies the content to be retrieved. It finally creates the job request and passes it to archpro. CSX Task: Committer The committer component receives the answers from archpro and processes the instructions within it.
If an operation is successful, this results in modifications of the original messages according to the instructions. For archiving jobs, this means that content might be deleted from the original messages according to the selected deletion type. Additionally, the status is set to archived and a few properties are added to the message.
For retrieval jobs, it means restoring archived content and setting the status to retrieved. The committer is also responsible for restubbing. The term restubbing describes the process of deleting retrieved content after a certain time and resetting the status to archived. When messages are restubbed, this is done in accordance with the deletion type that is specified at the time that the message is archived.
Restubbing does not involve communication with archpro. CSX configuration folder The configuration folder contains all of the information that Microsoft Outlook clients require to run the CommonStore functionality. CSX job folder The job folder contains interactive client requests to archive or retrieve messages. They are collected in the folder before they are picked up by a CSX task. Search server The search server is a separate Web application server process for the search function. It is automatically started by the archpro. It routes the search requests through the archpro to the archives that support this function Tivoli Storage Manager does not support it.
After receiving the results from the archpro, it arranges them into a list and passes that list to the requesting Web application that shows it in the browser window. The result list enables the requesting user to view the messages and attachments that are found in a browser. In addition, the user can restore the archived content to a special folder in the user s mailbox. You can use it to view the archived content in a Web browser.
The Web dispatcher is installed as part of the archpro and is automatically started by it. Content Manager is built on a multi-tier distributed architecture, with a Library Server that manages, indexes, and searches documents, and Resource Managers that manage the objects. A single Content Manager implementation supports a single Library Server, along with one or many Resource Managers and clients Library Server The Library Server manages the content metadata and is responsible for access control to all content. It maintains the indexing information for all multimedia content held in a Resource Manager.
Users submit requests through the Library Server. The Library Server validates the access rights of the requesting client and authorizes the client to directly access the object in the designated Resource Manager. The Library Server also maintains referential integrity between the indexing information and the objects themselves. It is built on relational database management system.
With Content Manager, no persistent processes operate on the Library Server; all content management functions are stored procedures run by the database. Content metadata in the Library Server is backed up and recovered using standard database tools. The Resource Manager supports caching and replication, and provides hierarchical storage management when used in conjunction with IBM Tivoli Storage Manager.
The Resource Manager architecture provides an extensible model that enables the support of additional Resource Managers in the future. Search client adds an easy-to-use Web interface that specific users compliance and litigation officers can use to perform general discovery steps on s stored in the Content Manager by CommonStore. Search provides the following functions: Helps authorized personnel for example, legal department and compliance officers to search across archived mailboxes.
Locates business-critical s through provided search features; for example, you can search based on the fields, such as to, from, cc, and attachment content.
IBM FileNet Content Manager Implementation Best Practices and Recommendations
Helps to respond to requests to demonstrate adherence to corporate-compliance plans. Helps to respond to legal requests for record discovery requests associated with litigation. Creates result sets of records for analysis or transfer. It offers an archiving solution to manage the entire life of an , from creation to disposition, and seamlessly integrate every stage of the process, including: Flexible capture Scalable archive repository Messaging system volume management Controlled retention and destruction Wide spectrum of secure, long-term storage device support Access to archive using search and discovery We discuss Search in more detail in Chapter 7, Search for CommonStore on page Best Practices for Setting Up an IBM CommonStore Solution.
Solution planning This chapter discusses the solution planning for an IBM CommonStore solution based on client requirements.
The insight can help clients, project managers, sales people, and even technical staff to avoid common pitfalls during the planning and setup phase of an implementation project of a CommonStore solution. We cover the following topics in this chapter: Requirement gathering and management Sample project plan Main deliverables of the solution planning The main focus of this chapter is a CommonStore solution independent from the system in use.
This chapter is not intended to provide an overview of certain subjects of project management nor does it promote a single method. It shows some examples of what we encountered during similar projects. We also provide an overview of the implications that the requirements have on project planning and implementation. Before deep diving into technical features of software products that make up a solution such as CSLD and Content Manager, a sufficient process of requirements gathering and management must be established. A well-known risk is to start with implementing parts of the solution before deciding what the requirements are and how these requirements are reflected in the solution.
However, it is almost never possible to define a full set of requirements at the beginning of the project. Therefore, we recommend that you maintain a list of assumptions, which contains all issues that cannot be decided at the beginning of solution planning such as archiving format and retention periods, or issues that cannot be defined in detail as required such as network bandwidth or data volumes to archive. The goal of requirement management is also to minimize the entries in the list of assumptions Requirement workshop A common approach is to conduct a requirements workshop to plan a CommonStore solution.
This is the place where requirements mainly from a business point of view are gathered. However, it is advisable to invest a reasonable amount of time in judging the technical feasibility of the CommonStore solution based on these business requirements. There are three main areas of requirements that you should consider: Mailbox management Long-term retention and discovery compliance Message monitoring and supervision In the remainder of this IBM Redbook, we discuss the first two areas, because these are the most common ones.
Introducing requirements for a CommonStore solution In the last few years, we have seen a change of drivers for implementing CommonStore solutions. Five years ago, the main driver for CommonStore solutions was mailbox management with a focus on reducing disk space that is consumed by mail files, addressing the growing mail volume, and moving older s to cheaper storage. This has changed dramatically.
In the last two years, almost every business is facing the demands of compliance regulations and the ongoing integration of into critical business processes. Business drivers are the adherence to regulatory and company rules, meeting compliance criteria set by internal or external instances, and the usage of to create business value. The biggest challenge to achieving compliance is to understand the regulations that are applicable and their impact on a CommonStore solution.
The current political focus on regulatory compliance and the raft of new regulations coming into effect in almost every country makes it challenging to ensure that existing compliance policies are up-to-date. This makes the discussion of compliance a large part of the requirement workshop. It is important when defining regulatory compliance policies to ensure that maximum synergy is achieved for the outlined requirements.
In some cases, such as where numerous industry and geography specific regulations are applicable, it might be wise to seek specialist advice. Before starting with the requirements workshop, it might be even advisable to conduct an internal audit of the existing compliance environment and to contrast with the required compliance environment.
The resulting gap analysis reveals compliance exposures and helps to define the new or adapted polices that are required. Another fact that makes matters complex is that is personal, asynchronous, and unstructured. Some people even use their mail file as their primary document repository.
Mail files are always a source of a huge amount of intellectual capital and process or organizational knowledge. However, was never designed for such uses. You should have all these circumstances in mind when you plan a CommonStore solution. It is common for different groups within the same organization to have differing requirements. These can greatly increase the complexity and cost of delivering the required CommonStore solutions.
It is advisable to significantly reduce the number of separate policies by using a modular approach with a limited number of variations. We recommend a top-down approach to firstly fulfill the common, major requirements and secondly to review and to fulfill the special, minor requirements. Information Technology IT has a key role to play in assisting clients to assess the impact of compliance within their organization by providing tools to support and monitor the required CommonStore solutions.
These tools help to reduce the costs associated with compliance by automating manual processes and reducing delivery time by improving collaboration between the many groups internal and external that are vital for success. Compliance tools can also help reduce risk by providing management with an improved visibility of the compliance process and by helping to avoid human error. Chapter 2. Solution planning Two or more workshops might be necessary. The first series of workshop should be about business requirements including compliance policies.
Involve the following parties: Legal departments or departments dealing with compliance rules for the company Security and contingency IT architects Service provider representatives knowledgeable of the mail system After or during the definition of business requirements, another important subject of the planning phase of a CommonStore solution is an assessment of the current IT environment, which is the basis for further technical planning.
The assessment document must contain information about hardware, software versions, network bandwidth, locations, and data volumes. There are some questionnaires that are available from IBM, which we discuss in 3. For further management of requirements and to provide a means of cross-checking the CommonStore solution at any time, a set of use cases can be helpful. At least the main processes should be available as use cases with which it is always possible to rate the quality of the solution and the project progress. Functional and nonfunctional requirements The main deliverable of the requirement workshops is a document containing the functional and nonfunctional requirements for the CommonStore solution.
Functional requirements define the internal workings of the CommonStore solution, that is, the calculations, technical details, data manipulation and processing, and other specific functionality that show how the use cases are to be satisfied. They are supported by nonfunctional requirements, which impose constraints on the design or implementation such as performance requirements, quality standards, or design constraints. The core of the requirement is the description of the required behavior, which must be clear and readable.
This behavior might come from organizational or business rules, or it might be discovered through elicitation sessions with users, stakeholders, and other experts within the organization.
Many requirements can be uncovered during the use case development. When this happens, the person responsible for the requirement analysis should create a placeholder requirement with a name and summary, and research the details later, to be filled in when they are better known. Central archiving and deletion policy management might include records management. Make critical business documents centrally stored and available even after years.
Provide the means for search and retrieval of s. Provide management reporting on adherence of compliance rules and other regulations. Integrated solution for current business processes. Usage of different clients, also independent clients that are not part of the mail system. Usage of dedicated clients for search and retrieval. Search on s using full-text, different categories of documents for individual users, or both. Automatically offload s from user mail files.
Support for mobile and offline users. Manual options for categorizing and archiving. Reduce the size of user mail files. In systems engineering and requirements engineering, nonfunctional requirements are requirements that specify criteria that you can use to judge the operation of a system, rather than specific behaviors.
Contrast this with functional requirements that specify specific behavior or functions. Typical nonfunctional requirements are reliability, scalability, and cost. Nonfunctional requirements are often called the ilities of a system. Other terms for nonfunctional requirements are quality attributes and quality of service requirements. Some examples for nonfunctional requirements for a CommonStore solution are: Availability certain service level agreements Usability by target user community Documentation Legal and licensing issues Maintainability Chapter 2.
We recommend that you review this list frequently and discuss new or changed requirements. This list is also influenced by the technical feasibility of a CommonStore solution. Depending on the established standard for requirements management or for project management in general, different methods apply to this task. Some examples are: IBM Global Services Method Institute of Electrical and Electronics Engineers IEEE standards for software specification Accelerated Value Method based on value frames It is not important which method you use for the CommonStore solution, but it is essential to follow the rules of the selected method and to use the tools that the method provides.
For instance, the worst case for not properly managing requirements can be a ready deployed pilot system, which is already filled with production data, and in this phase someone from the business team wants an additional field to be added in the Content Manager index. Often the requirements for a CommonStore solution have an impact on user experience and functionality of the system.
Users must be aware that archived documents have to be searched, retrieved, or both before the data can be used further. Beyond that it is a demand to deal with offline users and locally saved data, such as notebook users with local replicas of their mail files. Another example of the impact of a CommonStore solution is the full-text-search feature of the system, especially when it is Lotus Notes.
Within Lotus Notes, users can create a full-text index of all the information contained in their mail files. After archiving documents from the mail file, there is some information for building the full-text. The main objective of the requirements management task is to handle such changes in user experience and functionality Requirements versus expectations There is a difference between requirements and expectations. The main expectation is often that a CommonStore solution can be implemented out-of-the-box and does not require much planning.
However, we learned in many projects that there is always a certain degree of customizing that is involved. A good example is the Domino mail template, which is customized in almost every project. Some of the lessons learned from our projects: Do not underestimate the time required for testing.
A CommonStore solution is not likely to be operated by the already existing staff members in place. It requires adjustments in terms of the number and organization of administrative staff. Additionally, the establishment of new interfaces might be necessary, for example, to the legal department.
It shows the relations between the several project tasks and highlights best practices from the field. A typical structure for a project plan can be: Assessment phase Current IT environment assessment Requirements workshop Functional and nonfunctional requirements Use cases Design phase High-level solution design Sizing Chapter 2.
In the structure given previously, the requirement gathering and documenting is the main part of the assessment phase. Refer to 3. Throughout the whole duration of the project, we recommend that you use prototyping and involve the business people early and extensively. Unlike other solutions, there are two or three projects phases that bind a reasonable amount of the available resources: assessment and design. This can be a significantly larger share than in other projects. This is because the requirements can be so various and requirement management is an ongoing process. It can involve a lot of interaction between the project team and the approvers of the mail file design.
It is a good practice to add the task of knowledge transfer into the project plan. As stated previously, the CommonStore solution requires more new skills. These new skills must be built by the operating and support staff and other people responsible for the solution in the early stages of the projects. If this is not possible, it is advisable to have several hand-over sessions for transferring the knowledge to support and operation personnel.
We provide two sample project plans in the additional material for this IBM Redbook. The solution planning deliverables are: Assessment of the current IT environment Documentation of functional and nonfunctional requirements Review of compliance policies Risk analysis: Identification and mitigation recommendations Enterprise deployment schedule and labor estimate Detailed project plan Pilot definition Document hardware specifications Mail template design changes and documentation In conclusion, even if you have to provide all of the deliverables listed previously, solution planning is an important project phase.
Decent planning can ensure the success of your CommonStore solution, and is the foundation for all other project phases such as solution design and deployment. Solution design This chapter discusses the CommonStore solution design. We cover the following topics in this chapter: Key information for CommonStore solution design Understanding solution components Requirement-gathering questionnaires Sample CommonStore solutions The primary focus of this chapter is to detail the questions that you have to ask to get detailed requirements so that you can design the right system architecture for the archiving solution.
We highlight the differences where necessary. Understand all the components that comprise a CommonStore solution. Know what each component does and how it interacts with the other components from a high component level and in a detailed subcomponent level. Gather requirements using questionnaires to: Understand the primary requirement for the archiving solution.
Understand the existing mail system infrastructure. Gather specific business requirements. Perform sizing based on the input from the questionnaires and the sizing tool. Map requirements to system architecture design. From the requirements that you gathered from the questionnaires and the output from the sizing tool, map this information to architect the CommonStore solution. The results from a CommonStore solution design should include defining the following system architecture elements and decisions: The software components required for the solution. The hardware requirement processing speed, memory, disk storage for the software components based on the sizing output.
The component topology; this includes: Whether multiple CommonStore servers are required and how to pair or distribute the servers among the existing mail servers. Whether multiple Resource Managers are required and how to set them up for example in different locations. Setting up the CommonStore server and Content Manager server both Library Server and Resource Manager on the same machine or on separate machines or nodes.
This depends partially on sizing and partially on available resource, preference, and performance requirement. Whether to enable journaling feature, and if yes, how to set it up. Whether to enable full-text search feature. Archiving policy and deletion or retention policy. To design an efficient working solution, it is important to understand the components that make up a CommonStore solution and how they work with each other.
CommonStore is not a stand-alone solution. CommonStore is considered a system integration or application gateway product for the two environments. Content Manager the archive repository that we focus on in this IBM Redbook consists of the following components: Library Server Resource Manager For an overview of these components, see 1. For CommonStore Search, we provide an overview of Search in 1. Chapter 3. Solution design In this section, we reiterate some of the concepts and go into more details about requirement gathering process.
A requirement is an opportunity to address a business problem. A good requirement is one that is complete, consistent, correct, modifiable, traceable, unambiguous, prioritized, understandable, and verifiable.
Gathering and evaluating requirements is an important exercise that: Reduces the likelihood that an inappropriate solution is implemented Exposes other problems that might also have to be addressed Drives the creation of the project acceptance criteria Reduces the likelihood of scope creep Tips: Perform a thorough requirement-gathering exercise before the implementation of a solution.
Document the results and ultimately use them to determine the satisfactory completion of the project. Interview the business leaders and technical staffs. Ask the right questions and obtain the right background information and requirements. Accurate requirements are crucial in the design of the solution. We organize the questionnaires into three main categories: Primary solution requirement and the design implications Current mail system infrastructure and mail usage Specific business requirements The answers to some of these questions also serve as input to the sizing tool that helps you to estimate the hardware required for your solution.
For more details, see Chapter 4, Sizing on page For a complete set of the standard questionnaires that are used by the CommonStore lab services professionals, see Appendix A, archiving questionnaires for solution planning and sizing on page Primary solution requirement and the design implications At the solution design and planning stage, you must get a clear picture of why there is a need to implement the solution.
In other words, you have to understand the primary reason for implementing the archiving CommonStore solution. There are two main reasons to implement a CommonStore solution: Mailbox management Long-term retention and discovery compliance Based on the primary reason or requirement of the archiving solution, you can derive the software requirements that you require for the implemented solution. Implementing the solution for mailbox management Every year, system grows exponentially.
You require sufficient infrastructure to manage s. CommonStore mailbox management solution helps you to archive old or unwanted s from the production servers to the less expensive and less used external storage. The solution helps you to reduce the backup times of the active, frequently used data, optimize the data storage on the production servers, and minimize the associated operational costs. Implementing the mailbox management solution improves system usage and performance. You do not have to enable journaling or full-text indexing features for this type of the solution.
Implementing the solution for long-term retention and discovery Over the years, s have become a tool that people use to hold business correspondences and important documents such as contracts and financial spreadsheets. Some regulations require the company to retain all of the s for a specific period of time. You must find a way to not only archive s, but archive all the necessary s, retain them for a specified time, and enable authorized personnel to search the s from a central repository. That is, you have to implement an archive solution for longer-term retention and discovery.
Solution design: Defining software components For a solution that is designed for long term retention and discovery, you have to integrate the following software components into your existing mail server environment: CommonStore to archive old s to the back-end repository: Use CSLD or CSX based on the existing mail servers.
Content Manager as the back-end archive repository to store the archived s. Search component that enables high performance full-text indexing of the archived s for archiving and discovery purpose. To archive all or specific sets of s for discovery purpose, you have to enable the following features in your CommonStore solution: Journaling to ensure that all or a subset of s are captured for archiving.
Full text search to enable future discovery searches on the archived s. The only assured way to capture every single or s from a specific user is through journaling. We recommend that you consult with IBM consultants to ensure that the solution design is feasible and optimal for your business requirement and environment Current mail system infrastructure and mail usage To design a CommonStore solution, it is important to know what is the existing mail system infrastructure.
For example, you must know the platforms that are used. The operating system that you are using today for your mail servers most likely dictates the platforms that you use for the CommonStore solution.
Content Manager Implementation and Migration | ecejyredagij.ml
To obtain the existing mail system infrastructure and usage, we include the following set of questions: How many mail servers do you currently have? Do you use clustering? If there are multiple mail servers, are they located at multiple sites? What is the topology and available bandwidth of the current infrastructure? The number of s that your solution has to archive within a defined operation time determines the number of CommonStore servers that you require for your solution.
Knowing the number of the mail servers you have and where they are located and how they are being used helps you to determine how to distribute the CommonStore servers across multiple mail servers. The bandwidth of the network might affect the archiving speed of the solution. This is especially true in a distributed environment where there are multiple mail servers located in geographically different locations.
For example, if you implement a CommonStore solution for long-term retention and discovery and you have to centrally archive s from different servers across different locations, then slow network speed affects how fast the s can be archived to the central repository. In this type of the environment, assuming that you work with Domino server, it is possible to design a system such that you can: a. Journal the mail databases at the local mail servers. Replicate the journal databases from local servers to one central server. Archive s from the replicated journal databases in the central server.
This is where you might discover the potential bottleneck of your system. Work with a network engineer and test the network speed to ensure that the network throughput can accommodate expected file transferring rate between the servers. Design your system accordingly. For Exchange server, it might be Windows NT, Windows or Knowing this information along with the available platforms that CommonStore for Lotus Domino and Exchange Server support and the available platforms that Content Manager supports, helps you to determine the platform you use for each solution component.
You must also take sizing into consideration. Make sure that the platform you use along with the servers can accommodate system performance requirement that is, to be able to archive the expected number of s within a specified period of time. What software do you use for backing up the mail servers? If you already use a specific system for backup, you can use the same system with Content Manager for long-term storage if it is compatible with Content Manager. For example, if the current system uses Tivoli Storage Manager for Domino server backup, it is only logical to configure Content Manager to use Tivoli Storage Manager in the archiving solution.
What is the current disk capacity of all the mail servers together? How much of this storage is already consumed by the mail databases today? If you cluster your mail servers, what is the size of a single version of all the databases not all the replica together? What is the estimated rate at which the current storage is growing? If you cluster your servers, what do you estimate is the growth rate for a single replica of all the databases? The previous two questions give you an idea of the minimum storage size necessary to archive s today and in future.
It becomes critical when you want to implement a long-term retention and discovery solution where you have to journal s and retain them for a specific number of years. The answers are used as input for sizing.