You can move the content of a project area from one repository
or server to another.
To determine if it is appropriate to move your projects to another
repository or server, consider the following reasons:
- Capacity balancing: As projects grow, you can reduce the overload
on a server by moving one or more projects to a server with more capacity.
- Archiving: A project is completed and does not need the same quality
of service as active projects.
- Splitting repositories: Instead of managing many projects in one
repository, you can split them into multiple repositories.
- Testing projects: As projects change, you can move them from a
test to a production repository.
Prerequisites
Before you move a project,
remember to preserve the following characteristics:
- Both the source and target repositories must be based on the same
version.
- The item ID for the project is preserved across repositories.
- Both the source and target repositories are based on the same
LDAP or user directory.
- Links between artifacts must be resolved after a move.
- All artifacts associated with a project area are collected.
Important: Moving your projects is
not supported if you must migrate the repository contents after the
move.