Cloning a Web content repository

Syndicating items from one server to another, either after migration or to roll out a new server, can take a long time. Your database backup and restore features can be used to clone data from one repository to another, making your system ready for syndication to be used from then on for incremental updates. There are two basic cloning scenarios:

• Cloning all items from one server to another.

  For example, cloning data from one authoring server to another authoring server.

• Cloning all items from one server to a another, but then removing unrequired data from the cloned server.

  For example, cloning data from an authoring server to a delivery server where you would want to remove version history and draft items from the delivery server repository.

These procedures only describe how to clone a Web content repository.

To clone a Portal environment, XMLaccess export and import should be used to transfer the Portal data to the target environment

• Cloning preparation

  Prepare your source and target systems prior to cloning a Web content repository.

• Cloning data

  These procedures describe how to clone Web content data from one system to another.

Parent topic:

Maintaining Web content

---