IBM Tivoli Provisioning Manager for OS Deployment, Version 7.1.1.16

Installing a multiserver infrastructure with a centralized database

About this task

You can set up a multiserver infrastructure with a single, centralized database supporting concurrent access (such as MySQL or SQL server) shared by all OS deployment servers, with server replication. Note that the default database does not support concurrent access, so you must therefore set up your own database before installing your OS deployment servers.

To install replicated OS deployment servers, perform the following steps:

Procedure

  1. Create an empty database. The OS deployment server automatically populates the database with the necessary tables.
  2. For each server, follow the appropriate process
    • On Windows, follow the installation process for installing with an alternative database from step 2 onwards.
    • On UNIX, follow the installation process, making sure that you provide the correct path to the centralized database.
      The installation process includes the following database examples:
    Note: Ensure that the Tivoli® Provisioning Manager for OS Deployment administrator passwords are identical on all servers.
  3. After all OS deployment servers have been installed and started, select Server replication from the Server parameters menu. Your new OS deployment servers appear in the Standalone servers folder of the server tree.
  4. For each server that you want to include in the infrastructure, move your standalone server into the Replicated OS deployment servers list by making it either a parent server or a child server.
    Note: Before assigning a child role to a server, you must have at least one parent server to which the new child server can belong.
  5. To make a parent server, click Make this OS deployment server a parent OS deployment server
  6. To make a child server:
    1. Click Make this OS deployment server a child OS deployment server
    2. Indicate which parent the server will be child to by selecting an appropriate parent with its specific network connection.
  7. Restart all the OS deployment servers.
  8. Click Replicate this OS deployment server only to replicate your child server with its parent
    Note: A child server is never up-to-date until it has been replicated with its parent.
  9. Optionally, click edit under Schedule to set up a replication schedule to perform regular replication of your child servers. If you have a hierarchy of more than two parent and child servers, the schedule must match the hierarchy. Top servers must be replicated first, and child servers after.


Feedback