PDXpert PLM Software
On-line Help Guide
This help topic describes the current PDXpert PLM release. Earlier releases may be different. To view your release's version of this topic, open PDXpert and press the F1 key or select the Help menu.
Restore data from a backup
You can restore a database and related library files from a previous backup. You may need to do this if you're moving PDXpert to a new server or recovering from a computer failure. You may also want to restore a previous database if you're experimenting with configuration options or importing legacy data, and want to return to a previous configuration.
The restored data completely and permanently overwrites all data in the current database, as well as all library files. Consider whether you should back up the current database and library before replacing it with another.
Microsoft recommends restoring a SQL Server database from an internal fixed drive. The operation may fail – possibly without any warning – if you select a compressed, network-mapped, or external volume.
Do not restore a newer backup file into an older SQL Server instance. A Microsoft SQL Server database backup can only be restored into the same, or higher, SQL instance.
For example, SQL Server 2014 (version 12.0) can accept an 12.0 database, as well as upgrade an older SQL Server 2012 (11.0) database. It can't use a higher-level database backup from SQL Server 2016 (13.0).
Do not restore a newer backup file into an older PDXpert release. A backup can be restored only into the same, or higher, PDXpert release.
For example, the PDXpert server 11.0.30620.2 can accept a backup of 11.0.30620.2 and can upgrade an older release, such as 10.1.30033.2. The PDXpert server can't "downgrade" a higher-level backup from release 12.0.31408.4. Refer to PDXpert's release notes for further compatibility details.
Ensure that all users have closed their PDXpert client application.
To use the restored data, your software license key must permit use of the installed PDXpert release. A software license purchased as a subscription must be current. If your software license key is for a perpetual license, then the key must have a support expiration date after the installed PDXpert release date.
On the PDXpert Application Server window:
Click on the Manage tab.
If the database and file attachments were saved using the default backup format Database with Library (*.pdxz), then skip this step and go to the next step.
If the database and file attachments were saved separately using the alternative backup format Database without Library (*.bak), then:
On the PDXpert Server, click the Reset the database contents help topic.button to clear the previous database. See the
In Windows File Explorer, delete any content contained in the \Library subfolder of the data directory path (as shown on the Manage tab).
Copy your saved library files into the empty data directory path's \Library subfolder.
Ensure that the copied library files match the date and time of the database backup.
In the System changes area, click the button to open the Restore From Backup dialog. Navigate to the location where your backup file is saved, select the correct backup file, and click the button to immediately load the backup file into the server. A new database index is created, and a large database may take a while to re-index.
If the database was saved by an older release of PDXpert, then the database is automatically upgraded to the current schema. After upgrading, the database cannot be used with the older release.
Verify that the restored system is accurate, consistent, and correct.
Accurate: The restored system — parts, documents, change forms, collections, etc. — contains exactly what you expect and is not, for example, an older backup.
Consistent: The database items refer to the matching set of library file attachments.
Correct: The right software license key is loaded, users can log into the client, and items can be searched, found and opened.
Log into the PDXpert client application.
Your PDXpert client may request a valid software license key that allows the installed PDXpert release to use the restored data.
Wait until all items are indexed ().
Search for an item with a file attachment that was saved just before the backup. View or copy the attachment to confirm its content.
If you can open the item record, but can't confirm its file attachment, then the library files have not been restored to the correct location or are inconsistent with the database.
Help Guide Contents [PDF]
- 0001. Welcome!
- 0002. Help conventions
- 0100. PDXpert Application Server
- 0101. Server overview
- 0200. How to...
- 0300. Console reference
- 0400. How to start the PDXpert client
- 0500. Program concepts
- 0600. How to set up PDXpert
- 0700. How to use the Item Explorer
- 0800. How to use the Collection Explorer
- 0900. How to work with documents
- 0901. Manage documents
- 1000. How to start a document
- 1003. Fill in the new document
- 1004. Add or remove references
- 1005. Save your document
- 1006. Remove your document
- 1007. Release your document
- 1008. Manage a released document
- 1009. Revise a released document
- 1010. Cancel a released document
- 1100. How to work with parts
- 1101. Manage parts
- 1200. How to start a part
- 1203. Fill in the new part
- 1204. Add, modify or remove BOM parts
- 1205. Import a CAD BOM
- 1206. Add or remove approved sources
- 1207. Add or remove references
- 1208. Save your part
- 1209. Remove your part
- 1210. Release your part
- 1211. Revise a released part
- 1212. Manage a released part
- 1213. Cancel a released part
- 1300. How to revise multiple markups
- 1400. How to work with change forms
- 1401. Processing a change
- 1402. Originate a new change form
- 1403. Analyze a submitted change
- 1404. Fix change processing errors
- 1405. Remove your change form
- 1406. Review a routed change
- 1407. Resolve an on-hold change
- 1408. Analyze an accepted change
- 1409. Use a released change
- 1410. View a completed change
- 1411. Analyze a stopped change
- 1412. View a rejected change
- 1413. Remove a canceled change
- 1414. Return a submitted change
- 1500. How to work with file attachments
- 1600. How to report, import & export
- 1601. Create a report
- 1602. Export a PDX package
- 1603. Use the Report/Export Wizard
- 1700. Import & update items
- 1701. Initialize your PLM database
- 1702. Use the External Data Importer
- 1703. Item Master import
- 1704. Iteration-level relational imports
- 1705. Bill of materials import
- 1706. References import
- 1707. Revision files import
- 1708. Sources import
- 1709. Item-level relational imports
- 1710. Item files & links import
- 1711. Materials import
- 1712. Groups collection import
- 1713. Materials collection import
- 1714. Organizations collection import
- 1715. Persons collection import
- 1716. Custom collection import
- 1800. View & export via ODBC
- 1801. View database objects
- 1802. Create an ODBC connection
- 1803. ItemViews reference
- 1804. ReferencePairViews reference
- 1805. SourcePairViews reference
- 1806. SourceItemMasterView reference
- 1807. StructurePairViews reference
- 1808. ChangeViews reference
- 1809. ChangePairViews reference
- 1810. FilePairMasterView reference
- 1900. How to perform other tasks
- 2000. Menu reference
- 2100. Item Explorer reference
- 2200. Document window reference
- 2300. Part window reference
- 2400. Change Form window reference
- 2500. System Rules reference
- 2501. System Rules window
- 2502. General: Copy files to snapshot
- 2503. General: Item uniqueness definition
- 2504. General: Reviewer's comment required
- 2505. Default File Access
- 2506. Password Policy
- 2507. References Tabs
- 2508. BOM: Allow duplicate parts
- 2509. BOM: Lock part default unit of measure
- 2510. BOM: Allow partner parts
- 2600. Collections reference
- 2601. Managing collections
- 2602. Custom attributes
- 2700. Places/Organizations/Persons
- 2800. General
- 2900. Documents
- 3000. Parts
- 3100. Changes
- 3108. Custom collections
- 3200. Other reference topics
- 3300. Software licenses & legal notices