Verified Answers


If an answer to your question is correct, click on "Verify Answer" under the "More" button. The answer will now appear with a checkmark. Please be sure to always mark answers that resolve your issue as verified. Your fellow Community members will appreciate it!  Learn more

  • State Not Answered
  • Replies reply
    1
  • Subscribers subscribers
    3
  • Views views
    870
  • Users 0 members are here
  • Locked Locked
Related
Options
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Migrating PVCS VM From Old Server(8.1.4) to New(8.6)

MigrationDeletedUser
I haven't worked with PVCS Version Manager for about 5 years. I have inherited an existing install and have been tasked with migrating an old PVCS Version Manager install, 8.1.4.2 on Windows 2003, to a new server, 8.6 on Windows 2012.

My question is what would be the best approach to doing this migration? Is it as simple as doing a clean install of Version Manager and SLM on the new server, copying the archives to the new machine and then importing them? Or do I need to do something more complex, such as upgrading in place on the old server then moving to the new server, or install the old version of VM on the new server, copy over the archives and then upgrade VM to 8.6?

Edit; Forgot to mention that we exclusively use the web version. Not the local client install.


Thanks.
  • 0  
    Hi John,

    You would indeed start with installing VM 8.6 and SLM 2.2.0 on your Windows 2012 server, and rehost your licenses to that box.

    Next, copy all PDBs from your old server to the new one, not just the archives. If you are currently using the PVCS VM File Server you would have to make sure the Path Map entries are preserved with the identical Client Names. The Project DB path and Revision path directories can be changed as needed. If you are not using the PVCS VM File Server, you would introduce it as a way to ensure your path remain valid.

    You can preserve the VM I-Net applet settings by preserving your vm\inet\props\PVCSServlets.properties file to the new server. If you copy the entire vm\inet\props folder you will also be preserving the end-user's preferences with respect to Edit | Options, Advanced Filter, etc.

    Relevant reading:

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Cookies Preferences
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.