Use a job or policy sweep to move content for large numbers
of documents and annotations from one storage area to another.
About this task
Content administrators often need to move content between
storage areas. You might want to do so for the following reasons:
- To retire an obsolete storage device by moving all the content
to a replacement device.
- To archive content by moving it from a primary storage device
to an archival device or lower-cost storage.
- To move federated content from the source repository to a FileNet® P8 device.
- To move content to fixed storage for regulatory purposes.
- To apply your decisions about the way that content is to be stored
to existing content. For example, configuring a storage area to encrypt
content has no effect on the existing stored content. For more information,
see Controlling the way that content is stored.
Both job and sweep policies have properties for specifying
the following items:
| What |
The document and annotations whose content is
to be moved. |
|---|
| Where |
The storage area to which content is to be moved. |
|---|
| When |
When the sweep can run. For policy sweeps, sweep
scheduling is specified as part of the sweep component as opposed
to the policy component. |
|---|