[p4] Move server from *nix to Windoze

Robert Cowham robert at vaccaperna.co.uk
Fri Jul 21 02:04:12 PDT 2006


The script/program p4migrate referenced in the Tech Note does handle these
cases - I have done it and it works.

You do need to be careful and very methodical!

Robert

> -----Original Message-----
> From: perforce-user-bounces at perforce.com 
> [mailto:perforce-user-bounces at perforce.com] On Behalf Of Jeff Grills
> Sent: 20 July 2006 22:44
> To: 'Jeff Jensen'; perforce-user at perforce.com
> Subject: Re: [p4] Move server from *nix to Windoze
> 
> 
> Remember to check all files, including deleted files.
> 
> Remember to check the entire depot path, not just the file name.  For
> instance:
> 
> //depot/Directory/file.txt
> //depot/directory/file.txt
> 
> I'm not totally sure, but you might need to deal with the 
> situation when a directory exists with two different cases, 
> even when the contents of the two directories do not overlap:
> 
> //depot/exampleAAA/one.txt
> //depot/exampleaaa/two.txt
> 
> I don't know if that would be a problem, or even what to tell 
> you to look for if you do have that, but it does seem like an 
> edge case that could more likely break in some manner.
> 
> j
> 
> -----Original Message-----
> From: perforce-user-bounces at perforce.com
> [mailto:perforce-user-bounces at perforce.com] On Behalf Of Jeff Jensen
> Sent: Thursday, July 20, 2006 4:12 PM
> To: perforce-user at perforce.com
> Subject: [p4] Move server from *nix to Windoze
> 
> Hi,
> 
> Perforce tech note 75 says:
> 
> "Please note: Unix-to-Windows (or case-sensitive to 
> case-insensitive) migrations are NOT SUPPORTED due to the 
> potential for data loss."
> 
> http://www.perforce.com/perforce/technotes/note075.html
> 
> 
> If I _have to_ move a Perforce server from Solaris to Windows...
> If I:
>   - verify there are no files that differ in name by case only
>   - change line endings from *nix to Windoze
> 
> What else is there that would cause Perforce not to support 
> this move use case?
> Or perhaps is it the inherant risk in both of those steps(?).
> _______________________________________________
> perforce-user mailing list  -  perforce-user at perforce.com 
> http://maillist.perforce.com/mailman/listinfo/perforce-user
> 
> 



More information about the perforce-user mailing list