Solutions

VM: How to copy or move a Version Manager Project Database (PDB) to another location
Your subscription to document S121539 will expire in 341 days (Renew).  To cancel this subscription, click Cancel Subscription above.



ID:    S121539
Published:    29 January 2002
Updated:    18 June 2013

Operating System(s)

  • All Unix
  • All Windows

Product(s)

  • PVCS Version Manager
 

Description

Somtimes, an existing project database has to be moved to a different location from where it was originally created. This could include moving the data to a different server.

Resolution

There are different ways of doing this, all with their own advantages and disadvantages.
 
For project databases accessed through the file system and not using the VM File Server:
  1. Restoring from a full backup
    This method works specifically if the project database is going to be in the exact same location on the new server that it was on the old server.
    NOTE: If the original path includes the server name, the new server should be renamed to match the original server.  If this is not possible, see options 3 and 4 for making changes to the path.
     
  2. Importing the archive directory structure
    This method is only valid if your project database's archive structure exactly reflects the project database view you have in the GUI.
     
  3. Using the VM GUI Edit | Copy feature
    If you choose to copy a project database into a new location, you can use Edit| Copy. VM will create a new project database in the specified location.

    Note: As of VM 8.1.2, the Copy feature is significantly improved and included copying shared file relationships as well as Workspaces. Using VM 8.1.2 or later, the Copy feature is a viably alternative to the ExportPDB / ImportPDB route listed below, providing you can access both the source and destination location.
     
  4. Using PCLI ExportPDB / ImportPDB commands
    A very useful feature in PCLI (Project Command-Line Interface - see PCLI User's Guide and Reference) is the possibility to export a project database and import it into a new location.

    All those methods are described in full detail in the attached WORD document. It is suggested that you study them all and then decide on whichever suits you the most.
For project databases accessed through the VM File Server available as of VM 8.0.x
 
Any of the above options listed for project databases accessed through the file system may also be used but may not be necessary.
 
The VM File Server is designed to make project databases more portable for the administrator.  The "Client Name" in a Path Map definition that is specified through the File Server Admin utility resolves to the physical location, or "Project DB Path", using a string substitution.  Because of this, the entire project database metadata and revision library can be picked up as a structure and moved to another location on the network and the result is transparent to the end users.   All that is required is that the "Project DB Path" be updated to point to the correct location.
 
Important Note:  If there is a change in the structure of the project database, then a Vtransfer command should be used to resolve the move.  Information on the Vtransfer command can be found in the Version Manager Command-Line Reference Guide and in the Version Manager Administrator's Guide (Chapter 4, "Configuring and Using the Version Manager File Server").

Migration ID

KB39987

Applies To

PVCS Version Manager All

Attachment

File NameFile SizeDownLoad
moving_pdb.doc 51K HTTP
moving_pdb_JP(Japanese version).doc 62K HTTP

Rate this Solution

Find Answers

Type a question or describe what you are looking for below

My Recent Searches

Welcome kb sso

Additional Assistance

  • Submit a Case Online
  • FAQs