Does svnadmin hotcopy lock the source repository during the copy operation?

The goal is to move a small Subversion repository to a new server with little or no downtime by creating a hotcopy of the repository on the destination host and then updating working copies to point at the new URL using svn switch --relocate.

The Subversion documentation does not explicitly state whether svnadmin hotcopy acquires an exclusive lock on the source repository that would prevent new commits during the copy, nor does it guarantee that all custom hook scripts are duplicated and remain functional on the hotcopied repository; additionally, it is unclear if clients can have their working copies relocated with svn switch --relocate while the original repository continues to accept transactions without encountering transient errors.

Key questions to resolve are: Does hotcopy block commits on the source repository while it runs? Are all pre‑commit, post‑commit and post‑update hooks copied and executable on the target repository? Can svn switch --relocate be applied to working copies while the source repository stays online without causing commit or update failures?