Hello,

I have been trying to convert a fairly old PVCS archive to a Starteam project and have met with zero success. I am worried that the archive might be simply too old to convert, PCVS was at version 6.5.00G when it was created. Also, do i need a copy of PVCS installed on the server for it to be able to convert the archive?

Thanks in advance.

My mistake, I ment version 3.6.10, 6.5.00G was the version of version manager we had.

Any advice would be most appreciated.

HI,

I done PVCS to ST migration, it went smoothly, i doesnot seen any problem while do...

We done from PVCS version manager 8 to ST 2005 R2

Regds

Orug

Hi,

I have successfully done migrations from versions 6.5 and 8.0 of version manager (although only in a limited capacity), I saw some problems with non-English characters in the names of files (but in the content was fine) so you may want to consider this if this is a scenario of yours.

For versions of PVCS version manager before 6.x I couldn't comment.

Obviously, back up all important data and test your backup works before performing any such migration.

HTH,

David

HI,

I done couple of time from PVCS 8.0.2.0 to ST, migration went smoothly, they are certain pre-requisites described at StarTeam Admin Manual, Please just follow it.

Always recomend bring your PVCS repostiory to local machine where ST was running

Import Existing PVCS users to StarTeam to maintain history of the files...

Regds

Orug

What specific problems are you incurring?

The first time I "wrapped" a project, I ran into some problems, too. The first thing I had wrong was the user account performing the wrap. The user name in BOTH tools (StarTeam and PVCS) must be EXACTLY the same (case-sensitive), and you must ensure that user has administrative rights in BOTH tools.

The second thing, as mentioned in another post, is you must copy the PVCS instance to the same server as your StarTeam server.

The next thing was many of our files had illegal characters in the filenames (specifically the parenthesis character), and many exceeded the allowable character limit (the limit is for the entire path, not just the filename). We had to correct these issues before we could even start.

The last thing that was important in our environment was to capture the Promotion State from PVCS. To do this, we had to attach Version Labels in PVCS before wrapping. StarTeam will import the Version Labels, but not the promotion state.

An additional note: the procedure wraps the back end of PVCS, which may be different than what you see in the PVCS GUI. For example, if you have renamed a file in PVCS, it show the new name in the GUI, but the backend retains the original name, and a pointer from the new name. Not really a problem if you understand going in what it is doing.

I have successfully wrapped several projects, one of which had over 80,000 files (if you count all versions of them -- really it was only about 25,000 files with many revisions).

If you post the specific error you are receiving, I might be able to help. /ubbthreads/images/graemlins/wink.gif" alt="" />

Nanci

Nanci makes a good point about the users, this is also mentioned in the documentation for StarTeam.

Another point that can helped files not being skipped during such a migration is by using ARCHIVESUFFIX = .???___ in the pvcs config file, presuming you do not need to use a wrapped version of the repository (i.e. you are going to migrate it directly after you wrap it)

HTH,

David