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 using the Batch Importer tool, and want to return to a previous configuration.
The restored backup data completely and permanently overwrites the current database in the \Database folder.
Restoring a .PDXZ backup file completely and permanently deletes all library files before copying its contents into the \Library folder.
Restoring a .BAK backup file doesn't delete, change or replace any files contained in the \Library folder.
Consider whether you should back up the current database and library before restoring your backup file.
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 Microsoft SQL Server version. A database backup can only be restored into the same, or higher, SQL Server version.
For example, SQL Server 2016 (version 13.0) can accept a 13.0 database, as well as upgrade an older SQL Server 2014 (12.0) database. It can't use a higher-level database backup from SQL Server 2019 (15.0). Restoring a database into a higher-level version does not automatically change the database compatibility level to the newer version. To use the new version's added features, search the web for SQL Server database compatibility level after upgrade
Do not restore a higher backup file into an older PDXpert Server release. A backup can be restored only into the same, or higher, PDXpert release.
For example, a PDXpert server 14.0.2700.5 can restore a 14.0.2700.5 backup file, and can upgrade an older 12.2.1000.4 backup file. A PDXpert server 14.0.2700.5 doesn't accept backups from higher releases, say, 15.0.3000.5. Refer to PDXpert's release notes for further compatibility details.
Ensure that all users have closed their PDXpert client application. All client connections are closed when the backup file is restored.
Do not add files to the server's \Data folder or its subfolders. Unrecognized files may interfere with proper operation or may be deleted without warning. If the folder has been moved, the actual name may not be \Data but perhaps \PLM-Data, \PDXpert, or something else.
To use the restored data, your software license key must allow 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 an expiration date after the PDXpert software release date.
On the PDXpert Application Server window:
Select the Manage page.
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 \Library subfolder. See the Reset the database and library help topic.button to clear the previous database and all files contained in the
Copy your saved library files into the empty data directory path's \Library subfolder.
Ensure that these files are related to (and were copied immediately after) the database backup .BAK file that you'll restore in the next step.
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. The system makes a new database index. 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.
Make sure 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 lets the installed PDXpert release 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 [as PDF]
- 0001. Welcome!
- 0002. Help styles
- 0100. PDXpert Application Server
- 0101. Server overview
- 0200. How to...
- 0300. Console reference
- 0400. How to start the PDXpert client
- 0500. PDXpert introduction
- 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. How to work with documents
- 1000. How to start a document
- 1003. Fill in the new document
- 1004. Add or remove references
- 1005. Start and update a task
- 1006. Save your document
- 1007. Remove your document
- 1008. Release your document
- 1009. Manage a released document
- 1010. Revise a released document
- 1011. Cancel a released document
- 1100. How to work with parts
- 1101. How to work with 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. Add or remove materials
- 1209. Start and update a task
- 1210. Save your part
- 1211. Remove your part
- 1212. Release your part
- 1213. Revise a released part
- 1214. Manage a released part
- 1215. Cancel a released part
- 1300. How to revise multiple markups
- 1400. How to work with change forms
- 1401. Processing a change
- 1500. How to start a change form
- 1503. Start and update a task
- 1504. Analyze a submitted change
- 1505. Fix change form routing errors
- 1506. Remove your change form
- 1507. Review a routed change
- 1508. Resolve an on-hold change
- 1509. Analyze an accepted change
- 1510. Use a released change
- 1511. View a completed change
- 1512. Analyze a stopped change
- 1513. View a rejected change
- 1514. Remove a canceled change
- 1515. Return a submitted change
- 1600. How to work with file attachments
- 1700. How to report, import & export
- 1701. Run a report
- 1702. Export a PDX package
- 1703. Use the DataGrid
- 1704. Use the Report/Export Wizard
- 1800. Import & update items
- 1801. Use the Batch Importer
- 1802. Item Master import
- 1803. Iteration-level relational imports
- 1804. Bill of materials import
- 1805. References import
- 1806. Revision files import
- 1807. Sources import
- 1808. Item-level relational imports
- 1809. Item files & links import
- 1810. Materials import
- 1811. Groups collection import
- 1812. Materials collection import
- 1813. Organizations collection import
- 1814. Persons collection import
- 1815. Custom collection import
- 1900. View & export via ODBC
- 1901. View database objects
- 1902. Create an ODBC connection
- 1903. ItemViews reference
- 1904. ReferencePairViews reference
- 1905. SourcePairViews reference
- 1906. SourceItemMasterView reference
- 1907. StructurePairViews reference
- 1908. ChangeViews reference
- 1909. ChangePairViews reference
- 1910. FilePairMasterView reference
- 2000. How to do other tasks
- 2100. Menu reference
- 2200. Document reference
- 2300. Part reference
- 2400. Change Form reference
- 2500. System Rules reference
- 2501. System Rules tool
- 2502. General: Copy files to snapshot
- 2503. General: Copy previous tasks
- 2504. General: Item uniqueness definition
- 2505. General: Reviewer comment required
- 2506. Default File Access
- 2507. Password Policy
- 2508. References Tabs
- 2509. BOM: Limit part to one row
- 2510. BOM: Lock part unit of measure
- 2511. 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