Newbie Admin and respoitory setup questions

[lduresky]

I am new to Vault and VSS, and our organization is switching over from VSS to Vault. I will be one of the admins. I have read that you should not have too many respositories as Vault has not been tested with dozens or hundreds of respoitories. I have also read that you shouldn't have too many files/projects within each repository.

Is there a size limit where a repository stops preforming well? We are trying to decide on a repository structure now.

Is it still true that you cannot copy between repositories?

What is the best way to learn about assigning user and group rights? In the Admin Too Guide, or is there a specific support site for it?

Also, where can I learn about Archiving old projects once they are no longer really needed, but we want to keep them around for a while just in case!

Thanks

[lbauer]

I have read that you should not have too many respositories as Vault has not been tested with dozens or hundreds of respoitories. I have also read that you shouldn't have too many files/projects within each repository. Is there a size limit where a repository stops preforming well? We are trying to decide on a repository structure now.

There are many factors that affect peformance. Repository size isn't as much of a factor as the number of users and transactions going on in a particular repository. For instance, performance would be better with 500 files checked out in each of 5 repositories, rather than 2500 files checked out in one repository.

Is it still true that you cannot copy between repositories?

Yes, that's true. We are working on an import/export tool for our next release. An import/export operation will take some time, so we still recommend users give some thought to setting up their repositories, to minimize the need for the tool.

How many users do you have, and how much code?

You probably don't need hundreds of repositories. A few might be enough. Put projects that share code into the same repository. A particularly large project could have its own repository, or you could put two or three smaller projects into a repository together. The level expected activity would be a key factor.

What is the best way to learn about assigning user and group rights? In the Admin Too Guide, or is there a specific support site for it?

The Admin Tool help for Folder Security is a good place to start. If you have specific questions, post back.

Also, where can I learn about Archiving old projects once they are no longer really needed, but we want to keep them around for a while just in case!

There's not a specific archive function in the current version. You can just leave the project in the repository.

I believe you'll be able to archive with the Import/Export tool in our next release.