Using project move, you can move the content of a project
area from one repository or server to another.
Projects can be moved from one repository to another for various
reasons:
- Capacity balancing: As projects grow, a server gets overloaded
and one or more projects need to be moved to a server with more capacity.
- Archiving: A project is complete and no longer needs the same
quality of service as an active project. It might even be moved to
a repository which is not active at all, but is stored away to be
references in the future if needed. One of the goals of archiving
inactive projects is to recover the space consumed by projects.
- Splitting repositories: Some repositories might manage many projects
and you prefer to split them into multiple repositories.
- Moving projects to production: As projects change over time, the
contents of a project can be moved from the prototype repository to
a development repository.
Prerequisites
Before moving any project,
consider the following:
- Both source and target repositories must be based on the same
version.
- The item ID is preserved across repositories.
- Both source and target repositories are based on the same LDAP
or user directory.
- Links between artifacts must be resolved after a move.
- It should be possible to collect all artifacts associated with
a project area.
- Any solution that requires pre-processing or post-processing (migration)
of the entire repository contents is not supported and should be avoided.