PDXpert PLM Software Installation Guide

Last update: 2011-10-24

Moving your PDXpert PLM database and file library

• Introduction
• How PDXpert stores your data and files
• Determining your system's file library location and size
• Moving a system with a large library
• Moving a system with relatively small library
• Validating your database & library
• Uninstall your previous PDXpert Application Server
• Other considerations

Introduction

A PDXpert system consists of the PDXpert Application Server, a database, and one or more PDXpert client applications.

You may want to move the PDXpert data to a new computer when you upgrade the operating system, change the SQL Server edition (from, say, Express to Standard edition, or from SQL 2005 to SQL 2008 R2), or convert from a single-user to multi-user system.

This Note describes the steps for moving the PDXpert database from one computer to another, or for installing the system after upgrading the operating system.

How PDXpert stores your data and files

Your new computer's SQL Server version must be equal to, or later than, the old system's SQL Server. For example, if the old server uses SQL Server 2008, then the new server cannot have SQL Server 2005: it must have SQL Server 2008 or SQL Server 2008 R2. Before running the PDXpert installer on the new server computer, you may need to manually install the most current SQL Server release.

The PDXpert database stores information about documents, parts and change forms. The database also contains the collection members; administrator-defined operating rules; license and user account configuration; and system-managed "housekeeping" data.

Files that have been attached to these items are stored within a separate Library folder, with references to these files stored in the database. A library file is simply a copy of the original file, renamed to ensure uniqueness.

Other system data, such as the search index, is also stored outside the system database but this data is recreated on demand, and therefore will not be moved.

Determining your system's file library location and size

If you're moving a relatively new PDXpert system, you can skip this section and the next section since the Library folder is likely to be quite small. For newer systems, jump to Moving a system with relatively small library.

The PDXpert Application Server console on your current server computer displays the location of your database and library. Open the PDXpert Application Server console, click on the Settings tab, and note the location shown in the Data and library base path setting.

To determine your system library folder's size, open your current server computer's Windows Explorer, and navigate to the folder shown in the Data and library base path setting. Within the Data folder is a \Library subfolder. Right-click on this \Library folder, select Properties from the context menu, and note the Size or Size on disk properties.

Moving a system with a large library

When you have a large library, it may be faster and more reliable to move the PDXpert database and the library folder separately.

1. On the old server computer, back up your database using the default type Database with Library (*.pdxz). Note the actual name and location of the saved backup PDXpertDB [release][timestamp].pdxz file.

2. Disable client responses. On the console's Settings tab, clear the Broadcast server response to client checkbox.

   On releases prior to PDXpert 7.0, you must stop the client communication service to clear this checkbox.

3. On the new server computer, install your PDXpert Application Server software.

   You may need to manually install the most current SQL Server release before running the PDXpert installer on the new server computer.

4. Use Windows Explorer to copy the library files from the old server computer \Library folder (a) across the network directly to your new server computer \Library folder, or (b) to a backup disk and then onto the new server computer. Each server computer's \Library folder will be located within the server data folder as described above.

5. Copy the backup PDXpertDB [release][timestamp].bak file from the old server computer onto a local drive on the new server.

   Do not attempt to restore the database across the network from a mapped drive. The restore operation will fail.

6. Use the PDXpert Application Server console on the new server computer to restore the database.

A large database may require 10 to 20 minutes of indexing before you can begin to search for items. Large file libraries may take many hours until all file attachments are included in the index. You can monitor the indexing progress from within the PDXpert client: Tools menu > Index Status...

You're now ready to validate the moved database and library.

Moving a system with relatively small library

This procedure describes how to move the PDXpert data when you have a small library (perhaps less than 4GB).

1. On the old server computer, back up your database using the default type Database with Library (*.pdxz). Note the actual name and location of the saved backup PDXpertDB [release][timestamp].pdxz file.

   This backup may take a while; it's complete when the Last backup date and time is updated.

2. Disable client responses. On the console's Settings tab, clear the Broadcast server response to client checkbox.

   On releases prior to PDXpert 7.0, you must stop the client communication service to clear this checkbox.

3. On the new server computer, install your PDXpert Application Server software.

   You may need to manually install the most current SQL Server release before running the PDXpert installer on the new server computer.

4. Copy the backup PDXpertDB [release][timestamp].pdxz file from the old server computer onto a local drive on the new server.

   Do not attempt to restore the database across the network from a mapped drive. The restore operation will fail.

5. Use the PDXpert Application Server console on the new server computer to restore the database.

Validating your database & library

Run the PDXpert client.

Depending upon your network configuration, the PDXpert client will usually discover the new server. However, if the Application Configuration window is displayed, enter the new server computer's name or IP address. Click the OK button to connect to the new server.

Verify that your settings are correct, and the library files are accessible. From within the PDXpert client, search for an existing part or document with a file attachment. Open the item and confirm that the file attachment can be copied from PDXpert to your local computer's Desktop.

Uninstall your previous PDXpert Application Server

After the new system has been verified as working correctly, uninstall the PDXpert Application Server from the old server machine to ensure that no one mistakenly connects to the obsolete database.

Other considerations

• Ensure that your new server computer has the same (or better) capabilities for indexing library files by installing Windows Search IFilters.
• Ensure that your new server computer is backed up regularly. If you rely on an automated backup, verify that it's compatible with your new database engine, and that its scope includes the contents of the \Library folder.